WPR20FA108 · Mooney M20K
Mooney M20K · Accident: loss of control in flight on approach
From North Bend, OR to Van Nuys Airport (VNY)
Event
- NTSB case
- WPR20FA108
- 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
- Instrument 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
- N777WP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Bend, ORTo Van Nuys Airport (VNY), Van Nuys, CA
- Aircraft age
- About 37 years (built 1983)
- 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 initial 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
- Substantial
Cause areas
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was at the completion of a cross-country flight during daytime instrument meteorological conditions. A review of air traffic control (ATC) audio recordings and automatic dependent surveillance-broadcast (ADS-B) data showed that the pilot advised ATC he was inbound on the instrument landing system instrument approach, the airplane was established on the localizer to runway 16R, and the air traffic controller cleared the pilot to land. About 1 minute later, as the airplane was near the final approach fix, it began a series of climbing and descending turns to the south and west of the approach course over high terrain. The air traffic controller queried the pilot and provided multiple instructions to both climb and turn to the south. The pilot initially flew to the south as directed but soon began maneuvering to the west and north. The pilot’s final response to ATC instructions occurred when the airplane was at an altitude of about 2,744 ft mean sea level (msl). No further radio communication from the pilot acknowledging the controller’s instructions was received.
The ADS-B data showed that the airplane turned left slightly 23 seconds later, followed by a series of mostly right turns. Throughout the final turn, the airplane’s altitude fluctuated over 400 ft. The last recorded radar target was at an altitude of 2,638 ft msl, within the vicinity of the accident site.
The wreckage was located adjacent to a downed powerline within mountainous terrain at 2,315 ft msl. All major structural components of the airplane were located within the debris path. Postaccident examination of the wreckage revealed no evidence of any preexisting mechanical malfunction that would have precluded normal operation with the airframe or engine.
The pilot’s communications with ATC as the flight deviated from the approach course included delayed response, incomplete readback of instructions, and transmissions consistent with increasing stress. These communications occurred while the airplane’s ground track was off course, both laterally and vertically. The airplane maneuvers were inconsistent with the charted approach and ATC instructions.
The airplane’s altitude and heading deviations on the approach indicate the pilot was not reliably and positively controlling the airplane by reference to instruments. Pilot communications early in this period were nominal. However, as off-course maneuvering continued and became more erratic, the pilot’s communications became distressed, suggesting he recognized the difficulty he was having controlling the airplane. As the restricted visibility conditions and maneuvering were conducive to the development of spatial disorientation, it is likely that the pilot experienced spatial disorientation before losing control of the airplane.
Probable cause
The pilot’s spatial disorientation during an instrument approach in instrument meteorological conditions, which resulted in loss of control of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20FA108
- Event ID
- 20200313X13202
- Case number
- WPR20FA108
- 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, 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: 310f0aebe81b7f3226659c18876aa85b0ff9d011efdd531e5af0ac64a609d25f; retrieved 2026-09-15T07:12:40.878Z.