Burlington - Morristown
Flight / Schedule
Burlington - Morristown
Aircraft
Pilatus PC-12Registration
N68PK
MSN
265
Year of Manufacture
1998
Date
January 16, 2013 at 05:56 AM
Type
CRASHFlight Type
Executive/Corporate/Business
Flight Phase
Takeoff (climb)
Crash Site
Airport (less than 10 km from airport)
Crash Location
Burlington-Alamance North Carolina
Region
North America • United States of America
Coordinates
36.0957°, -79.4378°
Crash Cause
Human factor
Narrative Report
On January 16, 2013 at 05:56 AM, Burlington - Morristown experienced a crash involving Pilatus PC-12, operated by LabCorp - Laboratory Corporation of America, with the event recorded near Burlington-Alamance North Carolina.
The flight was categorized as executive/corporate/business and the reported phase was takeoff (climb) at a airport (less than 10 km from airport) crash site.
1 people were known to be on board, 1 fatalities were recorded, 0 survivors were identified or estimated. This corresponds to an estimated fatality rate of 100.0%.
Crew on board: 1, crew fatalities: 1, passengers on board: 0, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. 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.
Aircraft reference details include registration N68PK, MSN 265, year of manufacture 1998.
Geospatial coordinates for this crash are approximately 36.0957°, -79.4378°.
Fatalities
Total
1
Crew
1
Passengers
0
Other
0
Crash Summary
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.
Cause: Human factor
Occupants & Outcome
Crew On Board
1
Passengers On Board
0
Estimated Survivors
0
Fatality Rate
100.0%
Known people on board: 1
Operational Details
Schedule / Flight
Burlington - Morristown
Flight Type
Executive/Corporate/Business
Flight Phase
Takeoff (climb)
Crash Site
Airport (less than 10 km from airport)
Region / Country
North America • United States of America
