CEN20FA049 · Mooney M20S
Mooney M20S · Accident: loss of control in flight during takeoff
From Johnson County Executive Airport (OJC) to North Little Rock Municipal Airport (ORK)
Event
- NTSB case
- CEN20FA049
- 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
- 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
Mooney M20S
- 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
- N602TF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Johnson County Executive Airport (OJC), Olathe, KSTo North Little Rock Municipal Airport (ORK), North Little Rock, AR
- Aircraft age
- About 19 years (built 2000)
- 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
- Takeoff
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and a passenger were departing from the airport to return to their home base airport. A witness reported that nothing was out of the ordinary on the airplane’s initial rollout. However, the airplane rotated at a much slower speed than would be expected and immediately started to climb at a very high pitch attitude. The witness reported that as the airplane gained altitude, it appeared to fly slower to the point that the left wing stalled, causing the airplane to nose over and continue its trajectory straight into the ground just east of the runway. The witness stated that the engine power was “on” throughout the entire flight. Videos recorded near the accident site and the accident airplane’s engine monitor data were consistent with the witness description of the accident flight. The airplane did not exhibit any in-flight fire or smoke in the videos, and a ground fire was observed after impact.
The pilot had purchased the airplane about 1 month before the accident and, according to his flight instructor, had accumulated 6.8 hours of instructional flight time.
A disassembly examination of the engine revealed no preimpact anomalies that would have precluded normal operation. Review of photographs of an exemplar trim jack screw and the accident airplane’s jack screw revealed that the airplane’s trim system components exhibited a setting consistent with a full nose-up trim. The before takeoff checklist for the airplane make and model includes the step, “Elevator Trim….TAKEOFF SETTING.”
The autopsy did not detect any significant natural disease. Toxicology testing detected a muscle relaxant and an antinausea medication in the pilot’s liver and muscle tissue samples; it was unknown why the pilot was using these impairing medications. The witness who saw the pilot before he took off observed nothing out of the ordinary in the pilot’s behavior and “no red flags” with respect to the pilot‘s actions. Thus, it could not be determined if effects from the pilot’s use of a muscle relaxant and an antinausea medication were factors in this accident.
A low level of carbon monoxide was detected in the pilot’s blood. The concentration would not be at a level to cause impairment and thus was determined not to be a factor in the accident.
Given the available information, it is likely the pilot departed with the elevator trim set to a full nose-up setting as opposed to the takeoff setting, which resulted in the airplane pitching up steeply after liftoff and the subsequent aerodynamic stall.
Probable cause
The pilot’s failure to set the elevator trim properly for takeoff, which resulted in an exceedance of the airplane’s critical angle of attack during climb out, an aerodynamic stall, and the subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20FA049
- Event ID
- 20191231X83852
- Case number
- CEN20FA049
- 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. 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: b508f54bbf4e0722fbc588b6b8175904da95ad679cda12ff2fb0ecf1f669241d; retrieved 2026-09-15T07:10:05.262Z.