MIA02LA105 · Cessna 150M
Cessna 150M · Accident: in flight collision with object during initial climb
From Ormond Beach Municipal Airport (OMN) to Osmanabad Airport (OMN)
Event
- NTSB case
- MIA02LA105
- 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
- N63591
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ormond Beach Municipal Airport (OMN), Ormond Beach, FLTo Osmanabad Airport (OMN)
- 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
- Initial climb
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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(cfi) › Remedial action, delayed
- Pilot in command(cfi) › Supervision, inadequate
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 stated that the takeoff and initial climb were uneventful, with the engine developing full power, and that during the climb the student pitched up excessively, and the airspeed decayed to near the stall speed. He said he then took control of the aircraft to avert a departure stall, and tried to clear trees at the end of the runway, steering the aircraft toward an area of lower trees, and extending the flaps to forty degrees in an attempt to balloon over the trees, but the left main landing gear became entangled in a tree, and the aircraft crashed incurring substantial damage. An FAA Inspector conducted a postaccident examination of the aircraft and stated that he did not find evidence of any preaccident failures or malfunctions to the aircraft or any of its systems which would have caused the accident.
Probable cause
The flight instructor's inadequate supervision of the dual student and failure to take prompt remedial action, resulting in a collision with a tree, a subsequent loss of control, and collision with the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02LA105
- Event ID
- 20020606X00816
- Case number
- MIA02LA105
- 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, coordinates. 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: 6177a69dc8ba3cb8bb1ee0d3b14c0bbe4d145313e7f7acdad2fb523d2379bf5d; retrieved 2026-09-21T19:42:28.253Z.