ERA20FA101 · Mooney M20J
Mooney M20J · Accident: abrupt maneuver on approach
From Spruce Creek Airport (7FL6) to Bartow Executive Airport (BOW)
Event
- NTSB case
- ERA20FA101
- 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 M20J
- 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
- N1149T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Spruce Creek Airport (7FL6), Daytona Beach, FLTo Bartow Executive Airport (BOW), Bartow, FL
- Aircraft age
- About 39 years (built 1981)
- 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 final
- 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
- Abrupt maneuver
- 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 › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident pilot and his wife were assigned the No. 4 position in a formation flight. Flight data indicate that, throughout the flight, the accident airplane’s path, altitude, and speed closely followed those of the lead airplane. Approaching the landing airport, the flight-lead instructed the other pilots in the formation to “Go extended trail,” and all complied and were in-trail behind the flight lead to enter the traffic pattern. Subsequently, the accident airplane’s flightpath became irregular when, about 1,500 ft past the lead airplane’s turn, the accident airplane began a turn from downwind to base leg during which the bank angle varied from 5° to 20°. It leveled off on the base leg, then turned sharply right toward the runway, passing through the runway heading before turning left and steeply descending. Witnesses at the airport reported seeing the accident airplane “closing in” on airplane No. 3 before making a sharp right turn. The airplane impacted the ground about .6 nautical mile from the runway threshold. Examination of the airplane revealed that the landing gear was in the UP position and the flaps were extended to 10°, which is not consistent with normal landing configuration upon the completion of the landing checklist, which should be performed on the downwind leg of the traffic pattern. No preimpact anomalies or malfunctions were identified during the examination that would have prevented normal operation. Airplane manufacturer lift data indicated that for a no-flaps configuration, lift dropped off just before 15° angle of attack. The airplane’s calculated angle of attack increased to more than 14° immediately before the airplane descended rapidly to the ground. Although the airplane’s flap setting was likely 10°, the final seconds of the airplane’s flightpath were consistent with an aerodynamic stall and an entry phase of a spin at an altitude too low to recover. Review of six detailed flight notebooks maintained by the pilot’s wife showed a multi-year history of in-flight notations of the times for every radio call, configuration change, entry in the traffic pattern, and turns within the traffic pattern. Given the failure of the pilot’s wife to note the time of entry into the downwind leg of the traffic pattern and the irregularity of the flightpath that commenced on the downwind leg of the traffic pattern, it is likely that there was a distraction in the cockpit around this time; however, the reason for the distraction could not be determined. The distraction likely led to his failure to lower his landing gear and flight control inputs that allowed the airplane to exceed its critical angle of attack, leading to an aerodynamic stall at low altitude. Review of the pilot’s medical history and medications revealed that the upset was unlikely to have been an effect of any of his medical conditions or his use of fluoxetine.
Probable cause
The pilot’s exceedance of the airplane's critical angle of attack and subsequent aerodynamic stall and spin at low altitude due to a possible distraction in the cockpit for which the reason was undetermined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20FA101
- Event ID
- 20200213X55547
- Case number
- ERA20FA101
- 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, 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: a3dae8d7616b354382fb8bdd3475048308052d10c9af66f06a71e7fbc8a5eca7; retrieved 2026-09-15T07:11:55.097Z.