The U.S. aircraft register, updated daily
Accidents · NTSB WPR20FA108 · Final report

Mooney M20K accident near Sylmar, California, March 13, 2020

On March 13, 2020 at about 9:47 pm local time, a 1983 Mooney M20K, registered N777WP, was substantially damaged in an accident during approach (IFR initial approach) near Sylmar, California (Van Nuys airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s spatial disorientation during an instrument approach in instrument meteorological conditions, which resulted in loss of control of the airplane.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 13, 2020 · about 9:47 pm local time · cases in 2020
Place
Sylmar, California · Van Nuys · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Mooney M20K No Series, built 1983 · all M20Ks on the register
Registration
N777WP · no longer on the register · serial 25-0738
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during approach (IFR initial approach) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during approach (IFR initial approach)

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 4,594 hours in all; 3,560 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,532.5 hours
  • Last inspection: annual inspection, July 24, 2019
  • Maximum gross weight: 3,131 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Continental TSIO-360-LB1 (piston); 3,890 hours total

The flight

  • Departed from: North Bend OR at 5:40 pm
  • Destination: VNY Van Nuys CA
  • Flight plan: IFR
  • Runway 16R, 8,001 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 150° at 4 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 900 ft
  • Temperature: 55°F (13°C), dew point 52°F (11°C)
  • Altimeter: 29.92 inHg
  • Observation at 9:56 pm from KVNY, 7 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 10 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

13 documents, released by the NTSB on April 22, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Record of Conversation - Son of the Pilot PDF, 1 page · our copy View Download
2 Record of Conversation - Co Owner PDF, 1 page · our copy View Download
3 ADS-B Data Kmz File map file · our copy Download
4 Opsview Kmz File map file · our copy Download
5 Air Traffic Control Communication Summary PDF, 2 pages · our copy View Download
6 Accident Site, Airframe, and Engine Examination Summary Report PDF, 9 pages · our copy View Download
7 Pilot Report Memo PDF, 1 page · our copy View Download
8 Pilot 72-HOUR History Summary from Family PDF, 2 pages · our copy View Download
9 Portion of an Insurance Application PDF, 1 page · our copy View Download
10 Autopsy Memo PDF, 1 page · our copy View Download
11 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
12 Toxicological Report PDF, 1 page · our copy View Download
13 Photo Array PDF, 10 pages · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR20FA108.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.