Loss of control Accident Pilatus PC-12/45 N68PK, Wednesday 16 January 2013
ASN logo
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Wednesday 16 January 2013
Type:Silhouette image of generic PC12 model; specific model in this crash may look slightly different    
Pilatus PC-12/45
Owner/operator:Laboratory Corporation Of America Holdings
Registration: N68PK
MSN: 265
Year of manufacture:1999
Total airframe hrs:4637 hours
Engine model:P&W Canada PT6A-67B
Fatalities:Fatalities: 1 / Occupants: 1
Other fatalities:0
Aircraft damage: Destroyed
Location:5 mi NE of Burlington (KBUY), NC -   United States of America
Phase: Initial climb
Departure airport:Burlington, NC (BUY)
Destination airport:Morristown, NJ (MMU)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

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.

Accident investigation:
Investigating agency: NTSB
Report number: ERA13FA115
Status: Investigation completed
Download report: Final report




Revision history:

16-Jan-2013 05:16 gerard57 Added
16-Jan-2013 06:14 gerard57 Updated [Total fatalities, Total occupants, Other fatalities, Phase, Source, Damage, Narrative]
16-Jan-2013 06:48 gerard57 Updated [Aircraft type, Operator, Phase, Departure airport, Destination airport, Source]
16-Jan-2013 06:54 harro Updated [Aircraft type, Registration, Cn, Narrative]
17-Jan-2013 13:23 RobertMB Updated [Time, Registration, Cn, Operator, Source]
17-Jan-2013 13:26 RobertMB Updated [Location, Narrative]
17-Jan-2013 13:27 Loadbob Updated [Time, Registration, Cn, Operator, Source]
17-Jan-2013 13:28 harro Updated [Registration, Cn, Source, Narrative]
17-Jan-2013 14:32 RobertMB Updated [Time, Cn, Operator, Location, Phase, Source, Narrative]
01-Apr-2013 19:05 TB Updated [Operator, Location, Source, Narrative]
20-Jan-2016 17:15 Aerossurance Updated [Source, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
28-Nov-2017 14:05 ASN Update Bot Updated [Operator, Nature, Departure airport, Destination airport, Source, Narrative]
03-Jul-2022 13:46 rvargast17 Updated [Damage]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314