ERA13CA154 · Cessna 172P
Eastern Kentucky University Cessna 172P · Accident: loss of control in flight during landing
From I39 · Richmond, KY to Samuels Field (BRY)
Event
- NTSB case
- ERA13CA154
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- Visual Meteorological Cond
Cessna 172P
- 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
- N89847
- Operator
- Eastern Kentucky University
- Onboard fatalities
- Unknown
- Route
- From I39 · Richmond, KYTo Samuels Field (BRY), Bardstown, KY
- Aircraft age
- Not recorded
- 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
- Landing · flare/touchdown
- 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
- Loss of control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the student pilot, who was on his first solo cross-country flight, wind at the destination airport was from 120 degrees at 6 knots, so he chose to land on runway 20. Abeam the intended point of landing, the student pilot reduced power, added 10 degrees of flaps, and obtained the desired descent airspeed. He maintained that airspeed on the base leg, and, turning onto final, noted that the airplane was high. The student pilot then lowered the flaps completely while continuing to maintain the desired approach airspeed. The student pilot stated that, shortly afterward, the airplane “ballooned,” and then “dropped immediately” and impacted the runway in a nose-low attitude. He reported that the stall warning horn sounded from "slightly before” the airplane “ballooned” until it impacted the runway. The student pilot did not report any preexisting preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. Postflight examinations revealed a collapsed nose landing gear and firewall damage.
Probable cause
The student pilot’s improper flare during a crosswind landing, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA154
- Event ID
- 20130305X51423
- Case number
- ERA13CA154
- 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. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 3f55249ebc988602e9d733b619b2a0a78820e18b2a61081f24e0130677a0c078; retrieved 2026-09-15T21:02:23.728Z.