CEN23FA239 · Mooney M20R
Mooney M20R · Accident: loss of control in flight en route
From Watertown Municipal Airport (RYV) to Manitowish Waters Airport (D25)
Event
- NTSB case
- CEN23FA239
- 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
- Instrument Meteorological Cond
Mooney M20R
- 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
- N1025C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Watertown Municipal Airport (RYV), Watertown, WITo Manitowish Waters Airport (D25), Manitowish Waters, WI
- Aircraft age
- About 20 years (built 2003)
- 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 · change of cruise level
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Physical
- 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
The instrument-rated pilot was conducting a personal cross-country flight with a passenger. An airport surveillance camera captured the airplane climbing wings level into a 300-ft overcast ceiling shortly after takeoff. Based on a review of recorded flight track data, shortly after the airplane climbed into the clouds it entered a climbing left turn but did not establish a direct course to the intended destination or climb to 3,000 ft mean sea level (msl) as cleared by the air traffic controller before the takeoff. Rather, the airplane flew through the direct course while it climbed and descended before it ultimately entered a steep descending right turn. In the moments before the accident, the airplane exceeded the never exceed airspeed (VNE) as it descended more than 13,500 feet per minute (fpm) while in the steep right turn. A witness reported seeing the airplane descend “nose first” into a grass field and wooded area, which was followed by a large explosion.
The airplane fragmented upon impact with terrain and trees, but a wreckage layout confirmed that all major structural components and flight controls were accounted for at the accident site. Flight control continuity could not be confirmed due to extensive impact-related damage; however, the airplane’s recorded flight path established that the airplane turned left and right and both climbed and descended during the flight. Additionally, a sound spectrum analysis of recorded audio concluded that the engine was operating when the airplane impacted terrain. The recorded flight path was consistent with the pilot experiencing spatial disorientation while flying in instrument meteorological conditions (IMC). The pilot’s recent instrument flight experience could not be adequately assessed with the available logbook evidence.
FAA Forensic Sciences toxicological testing detected ethanol in both lung and muscle tissue of the pilot. The presence of ethanol in both specimens means that the possibility of alcohol consumption could not be excluded. The negative ethanol result from the autopsy toxicology report adds little information due to the relatively high reporting limit used. However, based on the condition of the pilot’s remains and the difference in ethanol levels between lung and muscle tissues, at least some of the detected ethanol likely was from postmortem production. If the pilot consumed ethanol, the ethanol level in lung tissue was not low enough to exclude some impairing effects, particularly in the presence of other potential central nervous system (CNS) depressant substances. Thus, whether ethanol effects contributed to the crash could not be determined.
The pilot’s toxicological results indicated the use of gabapentin. Based on the gabapentin levels measured in tissue, it is likely that the pilot was experiencing some effects from the gabapentin. Specific effects are uncertain; however, it is possible for gabapentin to affect the vestibular system and proprioception, which are important for spatial orientation. Toxicological results also indicated the pilot’s use of codeine. The use of codeine can cause CNS depression as well as increase the risk of gabapentin’s effects on the CNS. The toxicological results also indicated the pilot’s use of delta-8 THC. Delta-8 THC has the potential to alter perception and cause impairment. To what extent the combination of multiple CNS-active substances may have affected, the pilot’s cognitive processing and motor skills is unknown. Thus, based on the available information, it is possible that the pilot was impaired by the use of gabapentin, codeine, and delta-8 THC contributed to the accident. However, notably, the FAA prohibits an individual who uses gabapentin and/or delta-8 THC from acting as pilot-in-command of an aircraft.
The pilot reportedly had obstructive sleep apnea (OSA) treated with a continuous positive airway pressure (CPAP) device. Inadequately treated OSA can contribute to increased sleepiness, diminished attention, and cognition leading to an increased risk of performance errors. The pilot’s medical records regarding his use of a CPAP device were insufficient to determine whether he complied with OSA therapy; however, the pilot’s family reported that he was traveling with his CPAP device. Regardless, without additional information on the pilot’s compliance with OSA therapy, whether the effects of his OSA condition contributed to the accident could not be determined.
Probable cause
The pilot’s loss of control due to spatial disorientation while operating in instrument meteorological conditions. Contributing to the accident was the pilot’s impairment from the prohibited substance; however, the extent of impairment could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA239
- Event ID
- 20230614192369
- Case number
- CEN23FA239
- 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: dcf2e5b955ee44a20ecde295f57ae963fb125eb02ac25c0ae945a2491a886c45; retrieved 2026-09-15T08:01:23.405Z.