FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17CA140 · Cessna 172R

23 Feb 2017 · Cahokia, IL, United States

Ideal Aviation Cessna 172R · Accident

Report a problem

Event

NTSB case
CEN17CA140
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Unknown

Cessna 172R

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N51827
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 15 years (built 2002)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Unknown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was parked on the operator's ramp when Federal Aviation Administration inspector(s), during a routine ramp inspection, found that the airplane had substantial damage to the firewall and structure aft of the firewall. Airplane maintenance records showed an entry stating that the damage was due to a suspected hard landing. The operator stated that the damage must have occurred between the airplane's 100-hour inspection on September 27 and an oil change performed on October 24, 2016. The operator's mechanic stated that the damage was found when the engine cowl was removed for the oil change.

A review of airplane flight logs showed about 20 different people had flown the airplane over 48 flights between the time of the 100-hour inspection and the oil change. On October 8, 2016, a student pilot was performing touch and gos when the airplane bounced two or three times during the flight's final landing. The student pilot stated that, when she turned off the runway onto the taxiway, she noticed the airplane was not steering properly and reported to the air traffic control tower that she had some mechanical difficulty that required maintenance assistance. The student pilot's flight instructor and a company lineman responded and noticed that the airplane had a flat nosewheel tire. The lineman inflated the tire, and the student pilot and flight instructor taxied the airplane to the operator's maintenance facility. The flight instructor informed the operator's mechanic of the bounced landing and flat tire. The mechanic stated that he replaced the nose tire, performed a brief exterior walk-around visual inspection of the airplane, noting it appeared airworthy, and returned it to service. A hard landing inspection was not performed. Other than the bounced landing reported on October 8, 2016, no other concerns about the other flights were reported to the operator.

Probable cause

A hard landing for reasons that could not be determined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17CA140
Event ID
20170328X60448
Case number
CEN17CA140
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 24e3226f82f637c2396860993ac6c78e19e6d450370570ae5be582c87f5234da; retrieved 2026-09-16T05:07:40.844Z.