Back to Search

NTSB investigation record

ERA13FA115

Completed

Pilatus Pc-12/45· N68PK

Date
January 16, 2013
Location
Burlington, NC
Conditions
IMC
Record
Published September 25, 2020

Primary finding

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.

Investigator assessment

Analysis narrative

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.

Source record

Factual narrative

HISTORY OF FLIGHT On January 16, 2013, about 0556 eastern standard time, a Pilatus PC-12/45, N68PK, operated by LabCorp, Inc., as Skylab 53 (SKQ53), was substantially damaged when it impacted terrain shortly after takeoff from Burlington-Alamance Regional Airport (BUY), Burlington, North Carolina. The airline transport pilot was fatally injured. Instrument meteorological conditions prevailed and an instrument flight rules (IFR) flight plan had been filed for the flight destined for the Morristown Municipal Airport (MMU), Morristown, New Jersey. The corporate flight was transporting medical specimens and was conducted under the provisions of 14 Code of Federal Regulations Part 91. Review of Federal Aviation Administration (FAA) air traffic control (ATC) audio data revealed that at 0541, the pilot contacted Greensboro (GSO) clearance delivery, while on the ground at BUY, and requested an IFR clearance to MMU. The pilot was advised that there was no flight plan stored in the ATC system. His original flight plan had a proposed departure time of 0315 and the flight plan was only good for 2 hours. The pilot subsequently requested to file an IFR flight plan and provided the routing details. At 0550, GSO ATC provided an IFR clearance to SKQ53 from BUY to MMU, which included an initial altitude of 3,000 feet. ATC subsequently provided a transponder code of 2531, an altimeter setting of 30.01, an initial vector of a left turn to 360 degrees after takeoff, and a clearance void time of 0600, at 0551:30. The pilot acknowledged, read back the assigned transponder code as 2501, and stated that he would be airborne in about 30 seconds. At 0554, the pilot advised GSO ATC that he was "climbing through thirty." The pilot was asked to "ident" and responded that he was turning to a heading of 360 degrees at 3,000 feet. The pilot was then directed to reset his transponder to code 2531, which he acknowledged with "531." At 0555, ATC advised the pilot that his transponder indicated a code of 2501 at an altitude of 2,000 feet. The pilot did not respond and ATC made numerous attempts to contact SKQ53 without success. The airplane was not radar identified by ATC. The airplane was subsequently found fragmented in an athletic field that was located about 5 miles northeast of BUY. PERSONNEL INFORMATION According to FAA and company records, the pilot, age 57, held an airline transport pilot and flight instructor certificates, with ratings for airplane single-engine land, airplane multiengine land, and instrument airplane. The pilot's most recent FAA second-class medical certificate was issued on November 19, 2012. According to the pilot's most recent logbook entry, as of January 11, 2013, he had accumulated about 6,370 hours of total flight experience, which included about 315 hours in the same make and model as the accident airplane. He had also logged about 600 hours of flight experience in actual instrument meteorological conditions, and about 3,245 hours as night flight experience. In addition, he had accumulated about 45 hours in the same make and model as the accident airplane during the 90 days preceding the accident, which included about 25, and 20 hours logged in night and actual meteorological conditions; respectively. According to the company chief pilot, the accident pilot had been flying the PC12 approximately 4 days per week since September 2012. His current schedule called for morning flights with "show times" at 0330. On the day prior to the accident, the pilot flew from BUY to Charleston, West Virginia (CRW). He took a nap at CRW before flying to Columbus, Ohio (OSU), and returned to BUY about 0940. His duty time ended at 1015, on January 15, 2013. According to company records, in November 2012, the chief pilot arranged for an evaluation flight for the accident pilot in a Pilatus PC12. The chief pilot asked the instructor pilot conducting the evaluation flight to not allow the accident pilot to use the autopilot and preferred that the flight be conducted without flight director programming. Following the evaluation flight, the flight instructor noted that the accident pilot seemed to get behind the airplane because of lack of trim usage. This was usually masked when using the autopilot, which would input the correct trim for the airplane and was magnified when only using, or not using at all, the flight director. The instructor pilot made some suggestions to the accident pilot that included engine power settings and trim verification, which markedly improved his handling of the airplane. The instructor pilot added that the last two-thirds of the evaluation flight were satisfactory to FAA standards for an instrument rating and commercial pilot single-engine land privileges. AIRCRAFT INFORMATION According to FAA records, the low wing, T-tail, retractable-gear airplane, serial number 265, was issued an airworthiness certificate on July 6, 1999. It was constructed primarily of aluminum and powered by a Pratt & Whitney Canada PT6A-67B, turboprop engine, with a takeoff power rating of 1,200 shaft horsepower that was equipped with a Hartzell four-bladed hydraulically actuated, constant-speed propeller assembly. According to the airplane flight manual, the flight control system utilized push-pull rods and carbon steel cables and were equipped with electric trim systems. Each wing contained a single piece fowler-type flap that was electrically actuated. The airplane was also equipped with a stick shaker-pusher system to improve handling in the low speed flight regime by preventing the airplane from inadvertently entering a stall condition. According to maintenance records, the airplane's most recent inspection was a "300-hour mini inspection" that was performed on January 14, 2013, at a total airframe time of 4,637 hours. A crack on the underside of the left flap was repaired on January 15, 2013. At the time of the accident, the airplane had been operated for about 4,650 total hours. METEOROLOGICAL INFORMATION The 0554 recorded weather observation at BUY included wind from 040 degrees at 4 knots, visibility 10 statute miles, broken cloud celling at 700 feet, overcast at 1,700 feet, temperature 4 degrees Celsius (C), dew point 3 degrees C; and an altimeter setting of 30.02 inches of mercury. The 0700 Greensboro-High Point, North Carolina upper air sounding depicted a frontal inversion extending immediately about the surface to 3,533 feet agl. While the surface temperature was 4 degrees C, the freezing level was identified at 11,553 feet. No icing was indicated on the sounding due to the frontal inversion. AERODROME INFORMATION Burlington-Alamance Regional Airport was a non-tower-controlled airport with a common traffic advisory. It was equipped with single runway designated as runway 06/24. Runway 06/24 was constructed of asphalt, 6,405-feet-long, and 100-feet-wide. The field elevation for the airport was 616 feet above mean sea level (msl). FLIGHT RECORDERS The airplane was not equipped, nor was it required to be equipped with a cockpit voice recorder or flight data recorder. WRECKAGE AND IMPACT INFORMATION The elevation at the accident site was 531 feet msl and the majority of the wreckage was located strewn in a field. All major portions of the airplane, including all flight control surfaces and associated counterweights were located at the accident site. A debris path that was about 800 feet long, and 300 feet wide, was observed on a magnetic heading about 140 degrees. The right wing pitot tube was located about 10 feet from the initial impact point. Various sizes of wing spar segments were located in an impact crater. The crater was located on a berm, extended about 50 feet, and varied in depth to about 3 feet. The propeller hub, two propeller blades and the front reduction gear box were located in the crater. The third propeller blade was located about 200 feet along the debris path. The spin

Continue research

Find similar accidents

Continue with the strongest shared characteristics.