MIA03CA041 · Cessna 150K
Cessna 150K · Accident: hard landing
From Naples Municipal Airport (APF) to Everglades Airpark (X01)
Event
- NTSB case
- MIA03CA041
- 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 150K
- 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
- N5629G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Naples Municipal Airport (APF), Naples, FLTo Everglades Airpark (X01), Everglades City, FL
- 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
- 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
- Stall/spin
- 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) › Airspeed(vs), not maintained
- Pilot in command(cfi) › Go-around, continued
- Pilot in command(cfi) › Supervision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The instructor stated that the student was on a stable approach to runway 33, and when crossing the runway threshold the student brought the power to idle and immediately entered the landing flare. The airplane contacted the runway and bounced. The student advanced the throttle to initiate a go-around, and the airplane pitched up and banked approximately 10 degrees to the left. At this time the instructor took control of the aircraft and with both the student and instructor on the controls, the airplane banked right toward the runway. The student then let go of the controls. The aircraft continued to the right off the runway and impacted runway edge lights. He continued the go-around, raised the wing flaps, and checked that the carburetor heat was off. The airplane was airborne off the end of the runway but performance was poor. To avoid trees beyond the water inlet off the departure end, the instructor initiated a shallow left turn and ditched the airplane in the water. The right wheel impacted the water and rotated the airplane about 180 degrees. The dual student stated he was in the left seat. They approached runway 33 and landed hard. The airplane then ended up in the grass and the instructor took control of the airplane. The instructor got the airplane flying again and they climbed to about 100 feet. The engine was at full power. The airplane stalled, rolled to the right, and nosed down. The airplane then hit the water left wing and left side first. Witnesses stated the airplane landed hard and bounced into the air. The airplane touched down again while in a nose high attitude and full engine power was added. The airplane then ran off the right side of the runway and collided with runway lights and a sign. The elevator remained in the full nose up position and engine power remained at full power. The airplane lifted off and climbed to about 60-100 feet. The airplane then stalled and entered a spin to the right. After about 1/4 turn in a spin, the airplane crashed into the water. The instructor stated they had no mechanical diffilculties with the airplane.
Probable cause
The instructor's failure to maintain airspeed during climb after lift off from an aborted landing, resulting in the airplane stalling, entering a spin, and crashing into water at the departure end of the runway. Contributing to the accident was the instructor's improper monitoring of the dual student and the instructor's failure to abort an attempted go around when directional control was lost.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03CA041
- Event ID
- 20030115X00066
- Case number
- MIA03CA041
- 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: 918811f486ebbbc5c0a508e9f8e4aedf2c0e15096d8afe8307d4adabfe572aa9; retrieved 2026-09-21T09:31:57.465Z.