N79NX

HISTORY OF FLIGHTOn February 13, 2022, about 1402 eastern standard time, a Pilatus PC-12, N79NX, was destroyed when it was involved in an accident near Beaufort, North Carolina. The commercial pilot, and 7 passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

Earlier on the day of the accident, the airplane departed Pitt-Greenville Airport (PGV), Greenville, North Carolina, about 1235, and landed at Hyde County Airport (7W6), Engelhard, North Carolina, at 1255.

According to data recovered from the airplane’s combination flight data and cockpit voice recorder, before departing on the accident flight, when the passengers were boarding the airplane, the pilot was instructing the student pilot-rated passenger, who was seated in the right front seat of the airplane, on how to enter the flight plan information into the avionics. At one point, the passenger was told to enter W95 (Ocracoke Island Airport, Ocracoke, North Carolina) into the flight plan; however, he seemed unsure if he entered the information correctly. The pilot responded and stated that “we’ll get it later.” The passenger proceeded to insert Michael J. Smith Field Airport (MRH), Beaufort, North Carolina, into the flight plan, and then activate it. The data recorder data showed that the engine was started at 1329, and after taxi, the engine power was advanced for takeoff at 1334. The autopilot was engaged shortly after takeoff and the airplane climbed and leveled at the selected target altitude of 3,500 ft. The airspeed then stabilized around 220 knots from about 1337 to about 1343. Figure 1 depicts the airplane’s flight track for the entirety of the accident flight overlayed onto a visual flight rules sectional chart.

Figure 1. View of the airplane’s flight track (red) overlayed onto a visual flight rules sectional chart. The airplane’s position at various 5 minute time increments is also labeled.

After departure, the pilot and passenger spent several minutes amending and activating a flight plan into the airplane’s integrated flight management system before the pilot contacted air traffic control and reported they were going to level off at 3,500 ft mean sea level (msl). He requested VFR flight following as well as an IFR clearance to MRH. At 1338, the controller advised the pilot that a nearby restricted airspace was active, and the pilot confirmed that they would remain clear of the airspace and fly to the east. After that, while still attempting to program the autopilot flight plan, he stated, “I don’t know what I need to do. Just I almost [want] to take it all out and start from scratch.”

According to air traffic control data, at 1341, the controller called the pilot and indicated that they were about to enter the restricted airspace. After multiple calls with no response from the accident pilot, the controller instructed the military aircraft that were operating in the restricted airspace to remain above 4,000 ft msl. Although the pilot never responded to the controller, the cockpit voice recorder indicated that the pilot and passenger continued to try and program the flight plan into the flight management system. The pilot expressed concern to the passenger about entering the restricted area, and at one point the pilot stated, “what in the [expletive] am I doing?”

From 1341 to 1347, the pilot continued his attempts to program the flight plan into the integrated flight management system. At 1342:55 the selected altitude decreased to 3,000 ft and pitch control mode changed from altitude hold to vertical speed. The airplane began to descend, and the airspeed accelerated to 240 knots by 1343:42. Upon reaching 240 knots an overspeed warning was recorded. The “speed” (overspeed) alert sounded twice from the crew alerting system (CAS) and the pilot continued to enter waypoints into the integrated flight management system. After the first “speed” alert, the cockpit area microphone recorded a sound similar to a reduction in engine power, which correlated with the flight data recorder data that indicated the engine torque was reduced, and the airplane leveled at 3,000 ft. The torque setting remained unchanged until 1355. With the reduced torque setting, the airspeed stabilized at 147 knots. At 1346, the pilot stated, “I have – I have [got to] get a fricken flight plan in this thing.” At 1347, the pilot verbalized the weather conditions at the destination airport.

At 1348, the pilot called the controller and requested the RNAV approach to runway 26 but was denied the request because of the active restricted airspace. The controller then queried the pilot as to why he did not respond to the earlier radio calls, and the pilot responded that he “was trying to get out” and was unable to receive the radio transmissions. The controller offered an approach to runway 8 or runway 3, and the pilot chose runway 8. After that, the pilot talked about programing the avionics, and even mentioned “I’ve got to get my iPad out…. this is not good this way – I’m way behind the eight ball – [expletive] I hate it – I hate it when that happens.” The pilot asked the passenger to “bring up” runway 08 [instrument approach procedure], the passenger responded “here I got you” and “there you go,” to which the pilot stated, “I [do not have] my dang gone glasses either – there we go the lights help.”

At 1352, the controller reported that the restricted airspace was not active anymore and asked if the pilot wanted the RNAV approach to runway 26 instead. The pilot responded that he would appreciate that, and the controller cleared the pilot direct to CIGOR, the initial approach fix for the RNAV 26 approach. The pilot spent the next 3 minutes attempting to program the route of flight into the flight management system, and mentioned, “I can’t get [nothing] on this thing that I want.” On one occasion, the pilot asked the controller to clarify the name of the fix that they had been cleared to fly to in order to begin the approach (CIGOR or CIBAG), and on another occasion he asked the same question of the passenger. The passenger mentioned that he thought the correct waypoint was CIGOR.

At 1355, the controller called the pilot and asked to verify if they were proceeding direct to CIGOR because the airplane was still on a southwesterly track. The pilot responded “roger” and the controller said the pilot could proceed direct to CIGOR, to cross the waypoint at or above 1,900 ft msl, and was cleared for the runway 26 RNAV approach. The pilot read back the instructions correctly and then the passenger stated to the pilot, “should we get [them] to spell CIGOR and just insert it.” The pilot continued to program, delete, and activate waypoints. At 1356:14, the vertical speed mode was engaged again, and the airplane descended to a new selected altitude of 1,800 ft, at 1357:33. During the descent, the engine torque was reduced slightly from its previous setting. After capturing the altitude, airspeed began to decrease at a rate of about 1 knot per second and pitch began a gradual increase of about 0.1 degree per second. Engine torque was reduced again during the slow decay of airspeed while the airplane’s pitch and angle of attack slowly increased.

At 1358, the controller contacted the pilot and issued a heading to CIGOR, but then indicated that he had observed that the airplane was “correcting now.” At 1358:46, the controller called the pilot and issued the local altimeter setting (the airplane was flying at 1,700 ft msl, but the pilot had been instructed to maintain 1,900 ft msl). The pilot read back the altimeter setting correctly, which was the last transmission from the pilot. At 1358:56, the airplane’s barometric altimeter setting changed from 29.98 inHg to 29.96 inHg. At that time, the pitch increased to 10° nose up, while the airspeed had decayed to 109 knots. At 1359:12, the “stall” alert sounded from the CAS, the stick shaker activated, and the autopilot automatically disengaged. The airspeed reached a low of 93 knots and the autopilot remained disconnected for the rest of the recording. At 1359:13, the engine torque increased, which was also correlated with a sound consistent with the engine power increasing. The autopilot disconnect warning sounded continuously at 1359:15 and over the next 2 minutes until the end of the recording. During this time the pilot also continued to make comments about the airplane’s navigation system including, “what are we doin’,” “it’ll navigate,” and “activate vectors.” At 1359:40, the passenger stated, “we’re sideways.” Following the stick shaker activation, at 1359:50, the engine power was increased to nearly full power, the stall alert sounded 8 times, the airspeed decayed to 83 knots and the pitch increased to 31.7° when the stick shaker and pusher activated again. At 1401:21, the sink rate alert sounded, and the terrain avoidance warning system announced “pull up” and “speed” before the recording ended at 1401:29. In the final moments of flight, the airplane rolled to a bank of more than 90° to the right and pitched more than 50° nose down. Figure 2 depicts the airplane’s horizontal and vertical flight track during the final 2 ½ minutes of the flight.

Figure 2. View of altitude variation during the final 2 ½ minutes of the flight.

At 1401, the controller attempted to contact the pilot to inquire about the airplane’s altitude (the airplane was at 4,700 ft msl and climbing quickly). There was no response.

Radar contact with the airplane was lost about 1402 and an ALNOT was issued by air traffic control at 1429. PERSONNEL INFORMATIONAccording to Federal Aviation Administration (FAA) airman records, the pilot held a commercial pilot certificate with ratings for airplane multiengine land, airplane single-engine land, and instrument airplane. In addition, he held a ground instructor certificate and held a mechanic certificate with airframe and powerplant ratings. His most recen...