MIA01LA230 · Cessna 150M
Cessna 150M · Accident: hard landing
From Ormond Beach Municipal Airport (OMN) to an unrecorded destination
Event
- NTSB case
- MIA01LA230
- 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 150M
- 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
- N704KK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ormond Beach Municipal Airport (OMN), Ormond Beach, FLTo not recorded
- 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
- First occurrenceThe 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
- Pilot in command › Flare, improper
Approximate · Estimated position: the centre of Ormond Beach, FL, the place the record names. Not the accident site.
NTSB narrative
The student pilot was performing a soft field landing during a supervised solo flight, and she said that during the landing the aircraft bounced. She said she tried to recover by keeping the nose up, and then putting the nose down, but the aircraft bounced three times, and during the third bounce the nose came down, and the aircraft stopped. The flight instructor stated that he had showed the student soft field landings with both 20 and 40 degrees of flaps, and told her to perform them with 20 degrees of flaps, since he felt that she would not be able to handle the airplane with 40 degrees of flaps. The FAA inspector who conducted the postaccident examination of the aircraft said that during the landing, the landing gear failed, and was bent under the aircraft, bringing it to an abrupt halt. As a result, the firewall was damaged, and the forward fuselage wrinkled.
Probable cause
the student pilot's improper landing flare/touchdown while attempting to make a soft field landing during a supervised solo flight which resulted in substantial damage to the aircraft
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA230
- Event ID
- 20011001X02019
- Case number
- MIA01LA230
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 5c00efe0d71fa793b10f92502d0de0be3101c9981f36435dbc645c8bb14b3f7a; retrieved 2026-09-22T11:35:03.743Z.