FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA154 · Mooney M20K

25 Mar 2024 · St. Augustine, FL, United States

Mooney M20K · Accident: loss of control in flight on approach

From Northeast Florida Regional Airport (SGJ) to Miami Homestead General Aviation Airport (X51)

Report a problem

Event

NTSB case
ERA24FA154
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
2 · 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

Mooney M20K

Aircraft type
Mooney M20
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
N4387W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Northeast Florida Regional Airport (SGJ), St. Augustine, FLTo Miami Homestead General Aviation Airport (X51), Homestead, FL
Aircraft age
About 37 years (built 1987)
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
Approach · VFR pattern base
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
  • Aircraft › Aircraft structures
  • Personnel issues › Psychological
  • 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

Shortly after takeoff, the pilot reported to the air traffic controller that he had a door that had “popped open,” and the controller cleared the flight to return for landing. A review of ADS-B data and surveillance video revealed that, while the airplane was on the base leg for the approach back to the departure airport, it entered a steep, nose-down descent while rolling to the right, consistent with an aerodynamic stall/spin. Postaccident examination of the airplane revealed that both of the airplane’s doors (the rear baggage door and the main cabin door) remained attached to the airframe. Examination of the rear baggage door revealed damage consistent with it having been closed and latched at the time of impact; this included damage on the door latch pins (which were found extended) and striker plates indicating that the rear baggage door latch pins had been forced past the striker plates during the impact sequence. Examination of the main cabin door upper and aft center latch components revealed no damage to the latch pins and striker plates, indicating that the door was likely not closed and latched at the time of impact. Because the examination of the door lock and latching mechanisms did not reveal any mechanical failure or malfunction that would have precluded normal operation, the door was likely not closed properly before takeoff. The examination of the remainder of the airframe and the engine did not reveal any mechanical malfunction or failure that would have precluded normal operation. According to the airplane’s Pilot’s Operating Handbook (POH), if the main cabin door is not properly closed, it may come unlatched in flight but will not affect the airplane’s flight characteristics. The POH prescribed either returning to the field and landing normally or climbing the airplane to a safe altitude to perform the procedures for shutting and latching the door. The airplane was equipped with an engine data monitor that recorded various engine data parameters for the entire accident flight. A review of the engine data revealed that, at the time that the monitor stopped recording, all readings were consistent with normal engine operation and a high power setting. Based on these data, it is likely that, during the aerodynamic stall/spin, the pilot added full power to the engine in an attempt to recover from the aerodynamic stall/spin. According to the POH, to recover from a spin, it is necessary to bring the engine back to idle; however, the POH also stated that stalls at low altitude are extremely critical and that up to 2,000 ft of altitude may be lost during a one-turn spin and recovery. Thus, due to the airplane being below traffic pattern altitude when it entered the aerodynamic stall/spin, it is unlikely that the pilot could have recovered even if he had properly conducted the spin recovery items.

Probable cause

The pilot’s failure to maintain adequate airspeed of the airplane while in the traffic pattern, which resulted in an aerodynamic stall/spin. Contributing was the pilot’s distraction due to the in-flight opening of the main cabin door, which resulted from the incorrect closure of the door before takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA154
Event ID
20240325193984
Case number
ERA24FA154
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: ccbd803d8492af9470bcef61f3316bb63c445559eb6197b20268b5f02c762edf; retrieved 2026-09-15T08:11:56.567Z.