VFR into IMC · NTSB ERA13FA115

PILATUS PC-12/45 — Burlington, NC

1 fatal High-time pilotNightIMC
DateJanuary 16, 2013
LocationBurlington, NC
AircraftPILATUS PC-12/45
Purpose of flightExecutive/Corporate
ConditionsNight · Instrument Meteorological Cond
Phase / occurrenceUncontrolled descent Collision with terr/obj (non-CFIT)
Pilot age57
Pilot total time6,369 hrs · High time
Time in type315 hrs
Fatalities1

Probable cause

The pilot's failure to maintain airplane control due to spatial disorientation during the initial climb after takeoff in night instrument flight rules conditions.

NTSB findings

  • Personnel issues-Psychological-Perception/orientation/illusion-Spatial disorientation-Pilot - C
  • Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • Aircraft-Aircraft oper/perf/capability-Performance/control parameters-(general)-Not attained/maintained - C
  • Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Effect on personnel - C
  • Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-Clouds-Effect on personnel - C
  • Aircraft-Aircraft systems-Auto flight system-Autopilot system-Not specified

What happened

The pilot departed in night instrument flight rules (IFR) conditions on a medical specimen transport flight. During the climb, an air traffic controller told the pilot that the transponder code he had selected (2501) was incorrect and instructed him to reset the transponder to a different code (2531). Shortly thereafter, the airplane reached a maximum altitude of about 3,300 ft and then entered a descending right turn. The airplane's enhanced ground proximity warning system recorded a descent rate of 11,245 ft per minute, which triggered two "sink rate, pull up" warnings. The airplane subsequently climbed from an altitude of about 1,400 ft to about 2,000 ft before it entered another turning descent and impacted the ground about 5 miles northeast of the departure airport. The airplane was fragmented and strewn along a debris path that measured about 800-ft long and 300-ft wide.

Postaccident examination of the airplane did not reveal any preimpact mechanical malfunctions that would have precluded the pilot from controlling the airplane. The engine did not display any evidence of preimpact anomalies that would have precluded normal operation. An open resistor was found in the flight computer that controlled the autopilot. It could not be determined if the open resistor condition existed during the flight or occurred during the impact. If the resistor was in an open condition at the time of autopilot engagement, the autopilot would appear to engage with a mode annunciation indicating engagement, but the pitch and roll servos would not engage. The before taxiing checklist included checks of the autopilot system to verify autopilot function before takeoff. It could not be determined if the pilot performed the autopilot check before the accident flight or if the autopilot was engaged at the time of the accident.

The circumstances of the accident are consistent with the known effects of spatial disorientation. Dark night IFR conditions prevailed, and the track of the airplane suggests a loss of attitude awareness. Although the pilot was experienced in night instrument conditions, it is possible that an attempt to reset the transponder served as an operational distraction that contributed to a breakdown in his instrument scan. Similarly, if the autopilot's resistor was in an open condition and the autopilot had been engaged, the pilot's failure to detect an autopilot malfunction in a timely manner could have contributed to spatial disorientation and the resultant loss of control.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →