WPR20FA108

NTSB accident investigation · Mooney M20K · Sylmar, CA · March 13, 2020

Accident · FatalClass 3 · FieldFinal report
Date
March 13, 2020, 14:47 local (21:47 UTC)
Place
Sylmar, CA
Injuries
2 fatal
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N777WPMooney M20K
Defining event
Approach-IFR initial approach: Loss of control in flight
Weather
Instrument (IMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20200313005369A
Case key
101073

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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 · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotMooney M20K: 4 casesAll aircraft: 1,391 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotMooney M20K: 15 casesAll aircraft: 9,295 casesProbable cause
Ceiling/visibility/precip: low visibilityEnvironmental issues › Conditions/weather/phenomena · Effect on operationMooney M20K: 3 casesAll aircraft: 175 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Mooney M20K (No Series)
Category
Airplane
Serial number
25-0738
Built
1983
Airframe hours
4,532.5
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
77
Injuries
Fatal
Certificate
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

Docket · 13

The files NTSB released with the investigation on April 22, 2022, on NTSB’s docket system: statements, records, photos and specialists’ reports. 11.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.