Pilatus PC-12/45 N68PK accident near Burlington, North Carolina

Jan 16, 2013 · NTSB number ERA13FA115 · Final report

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 analysis

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.

Text from the NTSB. Open the NTSB docket for ERA13FA115 for the full record.

Event

Date
Jan 16, 2013
Type
Accident
Place
Burlington, North Carolina
Nearest airport
Burlington-Alamance Regional (BUY)
Highest injury
Fatal
Fatal injuries
1
Weather
Instrument (IMC)
Light
Night

Pilatus PC-12/45

N-number
N68PK
Category
Airplane
Year built
1999
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Executive or corporate

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.