FTW00FA053 · Mooney M20K
Mooney M20K · Accident: loss of control in flight en route
From Mc Alester Regional Airport (MLC) to Altus Quartz Mountain Regional Airport (AXS)
Event
- NTSB case
- FTW00FA053
- 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
- 1 · 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
- N5697N
- Operator
- John P. Mcdaniel · private individual
- Onboard fatalities
- Unknown
- Route
- From Mc Alester Regional Airport (MLC)To Altus Quartz Mountain Regional Airport (AXS), Altus, OK
- 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
- En route · climb to cruise
- 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
- Loss of control in flight
- 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
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane impacted heavily wooded and rocky terrain during an uncontrolled descent from cruise climb in night visual meteorological conditions. Toxicological tests were positive for tramadol at therapeutic concentrations, and phenobarbital, nordiazepam, chlorepheniramine, pseudoephedrine, and phenylpropanolamine. The pilot had a history of substance abuse. It is reasonable to conclude that the pilot was impaired by the use of or withdrawal from the effects of such medications at the time of the accident. The airplane's left wing speed brake was found in the stowed position, and the right wing speed brake was found deployed. FAA verified that flight test results provided by the speed brake manufacturer indicated no significant effect on handling qualities with one speed brake deployed. No evidence of an in-flight fire was found at the accident site. No evidence of uncorrected discrepancies was found in the maintenance records. No evidence of an in-flight mechanical and/or flight control malfunction was found that would have rendered the airplane uncontrollable prior to the impact.
Probable cause
The pilot's failure to maintain aircraft control. Factors were the pilot's impairment (drugs), the deployed right speed brake, and the night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00FA053
- Event ID
- 20001212X20236
- Case number
- FTW00FA053
- 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. 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: 0299bba0d081b74a59b20cebbfb4940c9d926bda9ea772e80babc06f14bf018a; retrieved 2026-09-20T21:32:58.272Z.