FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN21FA360 · Mooney M20M

7 Aug 2021 · Victoria, MN, United States

Mooney M20M · Accident: loss of control in flight on approach

From Chandler Field (AXN) to Flying Cloud Airport (FCM)

Report a problem

Event

NTSB case
CEN21FA360
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
3 · 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
Instrument Meteorological Cond

Mooney M20M

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
N9156Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chandler Field (AXN), Alexandria, MNTo Flying Cloud Airport (FCM), Minneapolis, MN
Aircraft age
About 29 years (built 1992)
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 · IFR final approach
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 structures
  • 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 pilot and two passengers (one of whom was a student pilot) departed on a personal flight. The pilot was cleared by air traffic control (ATC) to fly an instrument landing system (ILS) approach in instrument meteorological conditions (IMC). About 10 miles from the runway while on final approach, the airplane slowed to 80 knots, tracked left of the approach course, accelerated to about 140 knots, and descended about 300 ft. The airplane subsequently turned right and descended below the designated altitude for the approach, which triggered a low-altitude alert that the controller transmitted, and the pilot acknowledged. The airplane then abruptly turned left and entered a steep descent. The airplane continued in a left-turning spiral and descended below an overcast ceiling. The airplane subsequently impacted the ground upright about 8 miles west of the destination airport. Both wings and the right stabilizer were deflected upward in a vertical position. No preaccident mechanical failures or malfunctions were found with the airframe and engine that would have precluded normal operation. The airplane debris on the ground—the left horizontal stabilizer, left elevator, and part of the main wing spar upper cap splice plate--showed that an inflight breakup occurred during the final seconds of flight. The performance study for this accident revealed that the airplane exceeded its maximum positive load factor during the spiral descent. As the airplane descended below the overcast ceiling, a rapid groundspeed increase and heading change occurred, which were consistent with the pilot (or possibly the student pilot) attempting to recover the airplane from a nose-low attitude after seeing the ground. The spiral descent and attempted recovery overstressed the airplane, which caused the in-flight breakup. The left horizontal stabilizer, left elevator, and spar cap were found southwest of the accident site. Postaccident examinations of the airplane revealed that both wing main spars and both sides of the horizontal stabilizer had fractured due to overstress. The wings fractured first, and the horizontal stabilizer, elevator, and spar cap fractured immediately afterward. While the pilot was flying the final approach, several of his radio transmissions to ATC were either delayed or disjointed, indicating that the pilot was task-saturated. The performance study showed that, when the airplane made the series of turns while on final approach, erratic altitude and airspeed fluctuations occurred. These airspeed and altitude fluctuations and the tight spiraling turn that began afterward were consistent with the pilot becoming spatially disoriented due to the lack of visual references while the airplane was operating in IMC. The pilot’s spatial disorientation led to his loss of airplane control. A friend of the accident pilot stated that the pilot had adopted an instrument flying habit in the Mooney airplane that involved making turns on approach primarily with the rudder and adjusting pitch attitude with the pitch trim. If the pilot controlled the airplane in such a manner during the accident flight, especially in response to the controller’s lowaltitude alert, the application of rudder could have exacerbated the pilot’s erratic airplane control inputs while on approach. The pilot’s electronic logbook did not show any logged instrument approach procedures in 2021, and the accident pilot did not fly with his usual safety pilot during 2021. The pilot’s last flight review, in October 2020, did not include any instrument approach procedures. Neither the safety pilot nor the accident pilot’s flight instructor knew whether the accident pilot had flown with another safety pilot to log instrument time. As a result, the investigation was unable to determine if the accident pilot met the Federal Aviation Administration’s regulatory requirements for instrument experience. Diphenhydramine (commonly marketed as Benadryl) was detected in the pilot’s liver and heart tissue; no blood specimen was available to assess therapeutic levels. Diphenhydramine causes sedation and can slow psychomotor responses and reaction times, which can contribute to susceptibility to spatial disorientation. However, without a diphenhydramine blood level, the investigation was unable to determine whether the effects of the pilot’s use of diphenhydramine contributed to this accident.

Probable cause

The pilot’s loss of airplane control due to spatial disorientation during final approach, which led to a spiral dive that overstressed the airplane and resulted in an in-flight breakup.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN21FA360
Event ID
20210807103651
Case number
CEN21FA360
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: a33d4b62927b73e86ea696017e57b9430300d009215b1ac6640ab127ebb1710b; retrieved 2026-09-15T07:32:52.551Z.