FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA130 · Mooney M20C

14 Mar 2019 · Cashiers, NC, United States

Mooney M20C · Accident: loss of control in flight en route

From Knoxville Downtown Island Airport (DKX) to Aiken Regional Airport (AIK)

Report a problem

Event

NTSB case
ERA19FA130
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
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
Unknown

Mooney M20C

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
N6075Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Knoxville Downtown Island Airport (DKX), Knoxville, TNTo Aiken Regional Airport (AIK), Aiken, SC
Aircraft age
About 54 years (built 1965)
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 · cruise
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
  • Aircraft › Aircraft systems
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot obtained a weather briefing and filed his instrument flight rules flight plan the night before the cross-country flight. About 30 minutes after departure, an air traffic controller advised the pilot that he had overcorrected a turn. Shortly after, the pilot advised the controller that his attitude indicator was not functioning. The controller asked the pilot if he was in the clouds, and the pilot responded that he was in instrument meteorological conditions. The controller attempted to help the pilot get to clearer air, but the pilot continued to have difficulty controlling the airplane and maintaining an assigned course. Radar contact and radio contact were lost shortly thereafter. The wreckage was located in mountainous terrain, and all major components and control surfaces were accounted for at the accident site. Various parts of the airplane were scattered through the treetops and the wreckage debris field. While the airplane’s attitude indicator was not recovered, the directional gyroscope and vacuum pump were, and they were each examined in detail. Examination of the vacuum pump revealed that the shear coupling that connected the driveshaft between the engine accessory drive gear and the vacuum pump driveshaft assembly likely fractured before impact. The condition of the fractured shear coupling was consistent with the drive side rotating after fracture while in contact with the separated (and hence, stationary) driven side. A transverse fracture as observed through the shear coupling would have disengaged the two-piece driveshaft, which would not have allowed the pump to rotate. Additionally, all six of the vacuum pump’s vanes were intact but the rotor was fragmented into four relatively large pieces, and a relatively small area had fragmentated into smaller pieces. Given this information, the vacuum pump was likely not rotating at impact, as a greater degree of fragmentation would be expected if the pump were rotating. The interior surface vacuum pump housing displayed wear consistent with vane impact, dragging, and debris contamination within the housing at some point during the pump’s operational lifetime. One of the vanes exhibited heat tinting, and portions of the rotor’s exterior circumference also exhibited wear scarring. These observations were all consistent with the presence of forces resisting the pump’s normal rotation. It is likely that these resistive forces ultimately resulted in the failure of the rotor or the shear coupling. Additionally, examination of the directional gyroscope revealed that the rotor and its housing displayed signatures consistent with ingestion of dirt particles or foreign debris during operation, though none of the signatures conclusively supported its operational status at the time of the accident. Given these observations, it is likely that the vacuum pump ceased operating during the flight, which would have rendered the airplane’s vacuum-driven attitude indicator and directional gyroscope inoperative. A definitive cause for this failure could not be determined, though it is possible that the system had been contaminated with debris, which may have contributed to the failure. Because the operational status of the directional gyroscope was inconclusive, it could not be determined whether the pilot attempted to use the airplane’s standby vacuum system or whether that system was functional at the time of the accident. Because the pilot was operating the airplane under instrument flight rules and in instrument meteorological conditions, he would have primarily relied on the airplane’s instruments to maintain control and orientation of the airplane. It is likely that following the inflight failure of the vacuum pump, the pilot’s ability to control the airplane continually degraded, based on his communications with air traffic control and the airplane’s flight track as observed by the air traffic controller. While the pilot might have used the airplane’s standby vacuum system or attempted to maintain control of the airplane using partial instrument techniques, this would have been difficult given his lack of recent instrument flight experience. Ultimately, it is likely that the pilot succumbed to spatial disorientation and lost control of the airplane. While toxicological testing of specimens collected from the pilot’s remains following the accident were positive for the presence of ethanol, there was no evidence available to suggest that it was the result of ingestion rather than post-mortem production.

Probable cause

The pilot's loss of airplane control due to spatial disorientation while flying in instrument meteorological conditions. Contributing to the accident was the failure of the vacuum pump and its associated instruments.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA130
Event ID
20190315X92308
Case number
ERA19FA130
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: dae83a6e8a37a4d2d08cfcb99b982d789af81942b99897eae7176538f0379daa; retrieved 2026-09-15T06:55:37.389Z.