# NTSB WPR20FA108: Mooney M20K, N777WP, Sylmar, CA, March 13, 2020 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: March 13, 2020, 14:47 local (21:47 UTC) - Place: Sylmar, CA - Coordinates: 34.330554, -118.52639 - Nearby events: https://openairdocs.org/map.md?lat=34.3306&lon=-118.5264&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-IFR initial approach: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 101073 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20FA108 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101073/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101073 - Page: https://openairdocs.org/ntsb/WPR20FA108 ## Probable cause The pilot’s spatial disorientation during an instrument approach in instrument meteorological conditions, which resulted in loss of control of the airplane. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Mooney M20K, 4 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=5870220), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Perception/orientation/illusion: spatial disorientation](https://openairdocs.org/ntsb-findings/02022025): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Mooney M20K, 3 cases](https://openairdocs.org/ntsb-findings/02022025/cases.md?model=5870220), [All aircraft, 358 cases](https://openairdocs.org/ntsb-findings/02022025/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Mooney M20K, 15 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=5870220), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Ceiling/visibility/precip: low visibility](https://openairdocs.org/ntsb-findings/03035015): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Mooney M20K, 3 cases](https://openairdocs.org/ntsb-findings/03035015/cases.md?model=5870220), [All aircraft, 175 cases](https://openairdocs.org/ntsb-findings/03035015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-IFR initial approach: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Mooney M20K, 9 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=5870220), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Approach-IFR initial approach: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mooney M20K, 28 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5870220), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative The FAA Civil Aeromedical Institute's publication, "Introduction to Aviation Physiology," defines spatial disorientation as a “loss of proper bearings; state of mental confusion as to position, location, or movement relative to the position of the earth.” Factors contributing to spatial disorientation include changes in acceleration, flight in IFR conditions, frequent transfer between visual flight rules and IFR conditions, and unperceived changes in aircraft attitude. Van Nuys Airport is a public airport operating under class-Delta airspace. The airport is equipped with an air traffic control tower and features multiple instrument approaches. Runway 16R, has two instrument landing system (ILS) approaches, ILS 16R Y, and ILS 16R Z. On March 13, 2020, about 1447 Pacific daylight time, a Mooney M20K, N777WP, was substantially damaged when it was involved in an accident near Sylmar, California. The private pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The cross-country flight departed Soutwest Oregon Regional Airport (OTH), Oregon, about 1040 and was destined for Van Nuys Airport (VNY), California. Review of automatic dependent surveillance-broadcast (ADS-B) data and air traffic control communications between the pilot and the Van Nuys Air Traffic Control Tower controller revealed that, the pilot initially advised the controller he was inbound on the instrument landing system (ILS) at 1443:22. The airplane was aligned on the localizer course to runway 16R at that time (see figure 1). Between 1443:24 and 1444:39, the track shifted right and left of the localizer course, while descending from 4,281 ft mean sea level (msl) to 3,563 ft msl. The controller cleared the pilot to land on runway 16R, and reported wind from 140°, at 7 knots. At 1444:44, the data showed that while in the vicinity of the final approach fix, a right turn to a west-southwesterly heading, until 1445:02, when a left turn to southerly heading was made, at an altitude of 3,163 ft msl. At 1445:02, the controller queried the pilot, advising them they were deviating to the west and at a low altitude, to which the pilot responded they were on course and level. About 14 seconds later, the data showed a right turn to a westerly heading at an altitude of 3,419 ft msl. About 4 seconds later, the controller alerted the pilot that they were right of. The pilot responded shortly after that they were turning. At 1445:54, the controller issued the pilot instructions to fly heading 160°, climb and maintain 5,000 ft, to which the pilot acknowledged the altitude only. The controller responded to the pilot’s acknowledgement and instructed to the pilot to fly a 160° heading and climb to 5,000 ft, which the pilot acknowledged the altitude only a second time. About 2 seconds later, the controller asked the pilot to ensure they were on a 160° heading, which went unanswered by the pilot. About 7 seconds later thecontroller repeated that they need to climb to 5,000 ft, and a 160° heading. At 1446:30 the pilot replied “copy, 7WP.” Despite further attempts, no further radio communication acknowledging the controller’s instructions was received from the pilot. At 1446: 45, the data showed a right turn to a southerly heading, at an altitude of 3,106 ft msl. The airplane continued on a southerly heading until 1447:03, when a right 270° turn was observed. Throughout the turn, altitude fluctuated between 2,288 ft msl and 2,700 ft msl. The last recorded radar target was at 1447:14, at an altitude of 2,638 ft msl, within the vicinity of the accident site. Figure 1: Radar Data Overlay over ILS Runway 16R -Z Approach Plate At 1451, the automated weather observation station at Van Nuys Airport, Van Nuys, California, located about 8.5 miles south of the accident site reported wind from 160° at 6 knots, visibility 10 statute miles, few clouds at 700 ft, scattered cloud layer at 1,100 ft, overcast cloud layer at 1,800 ft, temperature 12°C, dew point 11°C, and an altimeter setting of 29.92 inches of mercury. At 1456, an Aviation Selected Special Weather Report (SPECI) was issued at VNY, reporting, wind from 150° at 4 knots, visibility 7 statute miles, broken cloud layer at 900 ft, overcast cloud layer at 1,800 ft, temperature 13°C, dew point 11°C, and an altimeter setting of 29.92 inches of mercury. About 20 minutes prior to the accident, pilot reports indicated that cloud tops varied from 7,500 ft to 5,500 ft mean sea level over the Burbank and Los Angeles areas. The pilot’s most recent logbook was not located during the investigation. However, on an insurance application, dated February 5, 2020, the pilot reported he had accumulated 4,594 hours total flight time, of which 3,560 hours were in the accident make/model airplane. It could not be determined how much instrument flight time the pilot had accumulated, or if the pilot had maintained their instrument proficiency. Examination of the accident site revealed that the airplane impacted power lines, which were about 50 ft in height, on a heading of about 064° before impacting terrain about 250 ft east and downslope of the powerlines. The fuselage came to rest inverted on heading of about 014° magnetic in a canyon surrounded by mountainous tree covered terrain, at an elevation of about 2,315 ft mean sea level (msl). The wreckage debris path was measured about 260 ft in length, oriented on a heading of about 064° magnetic and contained all major structural components of the airplane. Examination of the recovered wreckage established flight control continuity was able to be established from the cockpit to all primary flight controls. Numerous separations were noted within the control system and were found consistent with being cut by wreckage recovery personnel or they exhibited signatures consistent with overload separation. No evidence of any preexisting mechanical malfunction with the airframe or engine, including thevacuum system were found that would have precluded normal operation. ## Aircraft - Registration: [N777WP](https://openairdocs.org/deregistered/N777WP-2020-11-06), registration cancelled 2020-11-06, S/N 25-0738 (OpenAirDocs) - Reported make and model: Mooney M20K (No Series) - Registry model: [Mooney M20K](https://openairdocs.org/model/mooney-m20k) (registry code 5870220) (OpenAirDocs) - Registry engine: [Continental TSIO-360 series](https://openairdocs.org/engine/continental-tsio-360-series) (registry code 17019, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 25-0738 - Year built: 1983 - Airframe hours: 4532.5 - Engines: Continental TSIO-360-LB1 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 24, 2019 - Departed: North Bend, OR - Destination: VNY, Van Nuys, CA - Flight plan: IFR - Airport: VNY, Van Nuys, runway 16R, 8,001 × 150 ft, asphalt - Equipment: Stall warning system, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 77; injuries: fatal; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; toxicology performed; flight hours: 4,594 total, 3,560 in this make and model ## Weather - Conditions: Instrument (IMC), Day - Wind: 150° at 4 knots - Visibility: 7 statute miles - Lowest ceiling: 900 ft broken - Temperature: 55 °F, dew point 52 °F - Altimeter: 29.92 inHg - Icing: Unknown - Turbulence: Unknown - Observed at: KVNY, 7 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20200313005369A](https://openairdocs.org/incident/20200313005369A), Mar 13, 2020: Mooney Aircraft Corp. M20K, Sylmar, CA, Destroyed, 2 fatal. On March 13, 2020, about 1447 pacific daylight time, a Mooney M20K, N777WP, was destroye when it was involved in an accident near Sylmar, California. The… ## Docket (13 files) The files NTSB released with the investigation on April 22, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101073. 11.0 MB in all. - Record of conversation - son of the pilot (item 1, PDF, 1 page, 121 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13386828&FileExtension=pdf&FileName=Record%20of%20Conversation%20%20Son-Rel.pdf - Record of conversation - co owner (item 2, PDF, 1 page, 127 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387040&FileExtension=pdf&FileName=Record%20of%20Conversation%20co%20owner-Rel.pdf - ADS-B data kmz file (item 3, KMZ, 225 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13386666&FileExtension=kmz&FileName=ADSB%20Data-Rel.kmz - Opsview kmz file (item 4, KMZ, 165 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387254&FileExtension=kmz&FileName=Opsview%20Data-Rel.kmz - Air traffic control communication summary (item 5, PDF, 2 pages, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387050&FileExtension=pdf&FileName=ATC%20Communication%20Memo-Rel.pdf - Accident site, airframe, and engine examination summary report (item 6, PDF, 9 pages, 7 photos, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13391258&FileExtension=pdf&FileName=Airframe%20and%20Engine%20Examination-Rel.pdf - Pilot report memo (item 7, PDF, 1 page, 175 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387264&FileExtension=pdf&FileName=Pireps%20Memo-Rel.pdf - Pilot 72-hour history summary from family (item 8, PDF, 2 pages, 135 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387244&FileExtension=pdf&FileName=72%20hour%20history-Rel.pdf - Portion of an insurance application (item 9, PDF, 1 page, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387274&FileExtension=pdf&FileName=insurance%20application_Redacted-Rel.pdf - Autopsy memo (item 10, PDF, 1 page, 104 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13386606&FileExtension=pdf&FileName=Autopsy%20Memo-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 11, PDF, 1 page, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13386696&FileExtension=pdf&FileName=n777wp%20wreckage_releasedocs_Redacted-Rel.pdf - Toxicological report (item 12, PDF, 1 page, 382 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13387060&FileExtension=pdf&FileName=tox_Redacted-Rel.pdf - Photo array (item 13, PDF, 10 pages, 5.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13388800&FileExtension=pdf&FileName=Photo%201-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.