FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2022 Pilatus PC-12 crash

13 Feb 2022 · In the Atlantic Ocean, 6 km east of Drum Inlet in North Carolina, United States.

Edp Management Group Pilatus Aircraft Ltd PC-12/47E · Aircraft crashed into the sea while en route; under investigation

From Hyde County Airport (7W6) to Michael J. Smith Field (MRH)

Report a problem

Event

NTSB case
ERA22LA120
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
8 · all aircraft and ground
Ground fatalities
Unknown
Occupants
Unknown
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Pilatus Aircraft Ltd PC-12/47E

Aircraft type
Pilatus PC-12
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N79NX
Onboard fatalities
Unknown
Route
From Hyde County Airport (7W6), Engelhard, NCTo Michael J. Smith Field (MRH), Beaufort, NC
Aircraft age
About 5 years (built 2017)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

From the Wikipedia article

The 2022 Pilatus PC-12 crash was an aviation event that occurred on the afternoon of Sunday, 13 February of that year when a Pilatus PC-12 aircraft of the private company EDP Management Group LLC disappeared in the Atlantic Ocean 6.5 km (4 miles) east of Drum Inlet, which is 28 km (17 miles) northeast of Michael J. Smith Field airport in the town of Beaufort, North Carolina, United States. Eight people were on board, of whom two bodies have been found so far. It is believed that there is no chance of finding survivors.

Investigation and cause

Investigation

The NTSB and the FAA will be responsible for examining the wreckage of the aircraft and will begin the investigation into what may have caused the disaster.

Translated into English with AI assistance from the Spanish Wikipedia article “Accidente del Pilatus PC-12 de 2022” (revision 173222483, retrieved 2026-09-19) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out; the translation may contain errors, and long articles were cut to their first 700 words. Read the article

NTSB narrative

Before departing on the flight, the pilot of the turbo-propeller-equipped, single-engine airplane and student pilot-rated passenger seated in the right front seat of the airplane attempted to enter a flight plan into the airplane’s integrated flight management system. They ultimately did not complete this task prior to takeoff with the pilot remarking, “we’ll get to it later.” The pilot subsequently departed and climbed into instrument meteorological conditions (IMC) without an instrument flight rules (IFR) flight plan. After entering IMC, he contacted air traffic control and asked for visual flight rules (VFR) flight following services and an IFR clearance to the destination airport. From shortly after when the airplane leveled after takeoff through the final seconds of the flight, the pilot attempted to program, delete, reprogram, and activate a flight plan into the airplane’s flight management system as evidenced by his comments recorded on the airplane’s cockpit voice recorder (CVR). After departing, the pilot also attempted to navigate around restricted airspace that the airplane had flown into. The CVR audio showed that during the final 10 minutes of the flight, the pilot was unsure of the spelling of the fix he should have been navigating to in order to begin the instrument approach at the destination airport, and more generally expressed frustration and confusion while attempting to program the integrated flight management system. As the pilot continued to fixate on programming the airplane’s flight management system and change the altimeter setting, the airplane’s pitch attitude increased to 10° nose up, while the airspeed had decayed to 109 knots. As a result of his inattention to this airspeed decay, the stall warning system activated and the autopilot disconnected. During this time the airplane began climbing and turning to the right and then to the left before entering a steep descending right turn that continued until the airplane impacted the ocean. For the final 2 and 1/2 minutes of the flight, the pilot was provided with stall warnings, stick shaker activations, autopilot disconnect warnings, and terrain avoidance warning system alerts. The airplane impacted the ocean about 3 miles from the coast. Examination of the recovered sections of the airplane did not reveal evidence of any mechanical failures or malfunctions of the airframe or engine that would have precluded normal operation. The instrument meteorological conditions present in the area at the time of the accident were conducive to the development of spatial disorientation. The airplane’s erratic flight track in the final 2 minutes of flight, culminating in the final rapidly descending right turn, were consistent with the known effects of spatial disorientation. It is likely that the pilot’s inadequate preflight planning, and his subsequent distraction while he unsuccessfully attempted to program the airplane’s flight management system during the flight resulted in his failure to adequately monitor the airplane’s speed. This led to the activation of the airplane’s stall protection and warning systems as the airplane approached and entered an aerodynamic stall. The resulting sudden deactivation of the autopilot, combined with his inattention to the airplane’s flight attitude and speed, likely surprised the pilot. Ultimately, the pilot failed to regain control of the airplane following the aerodynamic stall, likely due to spatial disorientation. The pilot had a history of mantle cell lymphoma that was in remission and his maintenance treatment with a rituximab infusion was over 60 days prior to the accident. The pilot also had a history of back pain and had received steroid injections and nonsteroidal anti-inflammatory drugs. By self-report, he had taken oxycodone for pain management; it is unknown how frequently he used this medication or if he had used the medication on the day of the accident. While oxycodone can result in fatigue and dizziness, and may interfere with reaction time, given the information from the CVR, it could not be determined if the pilot had these side effects. A few weeks prior to the accident, the pilot reported having COVID-19 and receiving a 5-day treatment course of hydroxychloroquine and ivermectin. While there are some impairing side effects associated with the use of those medications, enough time had elapsed that no adverse effects would be expected. There is an increased risk of a sudden incapacitating cardiovascular event such as a dysrhythmia, stroke, or pulmonary embolism in people who have recovered from their COVID-19 infection. The risk is slight for those not hospitalized for the infection. The pilot did not have an underlying cardiovascular disease that would pose an increased risk for a sudden incapacitating event and the CVR did not provide evidence of a sudden incapacitating event occurring. Thus, it could not be determined if the pilot’s medical conditions of mantle cell lymphoma, back pain, and recent history of COVID-19 and the medications used to treat these conditions, including rituximab, oxycodone, hydroxychloroquine, and ivermectin, were contributing factors to this accident.

Probable cause

The pilot’s inadequate preflight planning, inadequate inflight monitoring of the airplane’s flight parameters, and his failure to regain control of the airplane following entry into an inadvertent aerodynamic stall. The pilot’s likely spatial disorientation following the aerodynamic stall also contributed to the outcome.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

Spanish Wikipedia article: Accidente del Pilatus PC-12 de 2022
Article
Accidente del Pilatus PC-12 de 2022
Translation
Into English with AI assistance; names of linked operators and aircraft types from Wikidata. It may contain errors.
Revision
173222483 · 2026-04-29 · retrieved 2026-09-19
Wikidata
Q110972884
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record ERA22LA120
Event ID
20220214104634
Case number
ERA22LA120
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
es Wikipedia article "Accidente del Pilatus PC-12 de 2022" (page 10165241, revision 173222483), translated into English with AI assistance; merged with NTSB case ERA22LA120 (events / aircraft)
Date
NTSB record ERA22LA120: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
Place and country
Wikipedia infobox: site; country from NTSB record ERA22LA120
Map position
NTSB record ERA22LA120: NTSB API eventLatitude/eventLongitude
Aircraft, operator and route
NTSB record ERA22LA120: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record ERA22LA120: operated under Part 91: General Aviation
Fatalities
NTSB record ERA22LA120: NTSB API totalFatal
Ground fatalities
NTSB record ERA22LA120: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "2022 Pilatus PC-12 crash" and NTSB case ERA22LA120, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.