ERA24LA389 · Cessna 150 J
Fundamentals Flight Training Cessna 150 J · Accident: hard landing
Event
- NTSB case
- ERA24LA389
- 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
- 0
- 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 150 J
- Aircraft type
- Cessna 150
- 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
- N61232
- Operator
- Fundamentals Flight Training
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 55 years (built 1969)
- 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
- Hard landing
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported the purpose of the flight was to train the student pilot on landings and go-arounds. After completing one touch-and-go landing and two go-arounds without incident, the flight instructor recounted that the student pilot flew the airplane through the traffic pattern and final approach leg at the appropriate speeds, altitudes, and descent rates. During the landing, the student pilot flared high and the airplane subsequently impacted the runway hard and flat. This led to a short bounce resulting in the airplane touching down a second time in a side-loaded and nose-down attitude. Upon the second touchdown the nose landing gear collapsed, and the right wing struck the runway resulting in substantial damage to the right wing and lower fuselage. The flight instructor did not report any preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The student pilot’s improper landing flare and subsequent improper recovery from a bounced landing and the flight instructor’s inadequate remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA389
- Event ID
- 20240923195160
- Case number
- ERA24LA389
- 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, cause areas. 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: 62b4a8f1dfaa2f168f9f1ff03d9e7ba3760da3a98d66a7ddb0ab97346bf40ba3; retrieved 2026-09-16T19:17:43.263Z.