FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA397 · Cirrus Design Corp SR22

28 Sept 2024 · Kill Devil Hills, NC, United States

Pantheon Aviation Cirrus Design Corp SR22 · Accident: loss of control in flight during landing

From Dare County Regional Airport (MQI) to an unrecorded destination

Report a problem

Event

NTSB case
ERA24FA397
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
Ongoing
API-reported fatalities
5 · all aircraft and ground
Ground fatalities
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
Visual Meteorological Cond

Cirrus Design Corp SR22

Aircraft type
Cirrus SR22
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
N1281F
Onboard fatalities
Unknown
Route
From Dare County Regional Airport (MQI), Manteo, NCTo not recorded
Aircraft age
About 1 year (built 2023)
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
Landing
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On September 28, 2024, at 1718 eastern daylight time, a Cirrus Design Corp SR22, N1281F, was destroyed when it was involved in an accident near Kill Devil Hills, North Carolina. The private pilot and four passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot departed from Moore County Airport (SOP), Carthage, North Carolina, on a multileg flight with stops in Ocracoke Island Airport (W95) and Dare County Regional Airport (MQI) before continuing to First Flight Airport (FFA), Kill Devil Hills, North Carolina. The accident flight departed from MQI at 1710 and was airborne for 8 minutes prior to the accident. Preliminary Automatic Dependent Surveillance-Broadcast (ADS-B) data provided by the Federal Aviation Administration (FAA) showed that after departing MQI, the pilot flew to FFA and entered the left traffic pattern for runway 21. The published airport traffic pattern for runway 21 was a right-hand pattern. The pilot descended and flew above the runway. He then climbed to traffic pattern altitude and rejoined the traffic pattern using left turns. The pilot approached runway 21 a second time, and according to witnesses, was high and fast during the approach. As the airplane passed the midway point of the runway, it made a steep left turn and impacted the top of 50-foot-tall trees (see figure 1). The airplane subsequently impacted additional trees before coming to rest 300 ft east of the runway in heavily wooded terrain, where a significant postimpact fire ensued.

Figure 1- Preliminary ADS-B data showing the airplane’s flight track during the accident approach (green line) and the previous approach to runway 21 (yellow line). Preliminary review of recorded audio communications on the common traffic advisory frequency (CTAF) did not reveal any distress calls from the pilot. The wind reported at FFA about the time of the accident was 170° at 6 knots, gusting to 14 knots. The airplane’s left wing impacted 50-foot-tall trees near the edge of the left side of runway 21 before the airplane contacted the ground approximately 135 ft from that initial contact point. The airplane came to rest in wooded terrain on an approximate 222° heading. The airplane was mostly consumed by a postimpact fire. All major portions of the airplane were accounted for at the accident site. The main wreckage area contained the fuselage, engine, empennage, right wing, and a majority of the left wing. The empennage remained partially attached to the fuselage and was mostly consumed by postimpact fire. The empennage structure was twisted 180°. Rudder and elevator control cable continuity was established from their respective flight control surfaces to the cockpit. The Cirrus Recoverable Data Module (RDM-300) was located within the empennage and removed for data recovery and analysis. The right wing remained with the fuselage structure. The inboard portion of the wing was mostly consumed by fire. The outboard portion and wing tip were intact and displayed thermal damage. The left wing tip was separated from the main wreckage and was found in a tall tree at the initial impact point. The navigation lighting wiring remained with the wing tip and was wrapped around the tree. The left aileron and other miscellaneous portions of the left wing were found approximately halfway from the initial contact point and the main wreckage. The remainder of the left wing remained with the fuselage and was consumed by fire, along with the flaps. The flap actuator was found within the fuselage debris and indicated that the flaps were at the 100% position. The cockpit was consumed by postimpact fire. The airplane was equipped with Garmin G1000 displays, which were destroyed. The secure digital (SD) cards for the G1000 system were found in their respective card slots but were melted in place. The engine control levers were destroyed. The fuel selector position could not be determined due to thermal damage. The pilot purchased 44 gallons of fuel prior to departure from MQI. The fuel selector position could not be determined. The fuel pump switch was not located. Fuel blighting was evident on the leaves of trees between the initial impact point and the main wreckage. The airplane was equipped with a Cirrus Airframe Parachute System (CAPS). A portion of the rocket motor was found adjacent to the empennage, and was damaged consistent with postimpact thermal exposure. The harness, suspension lines, and canopy were all contained within the deployment bag and remained restrained within the empennage in a packed state. The engine remained attached to the airplane firewall. The engine and its accessories were exposed to the postcrash fire. The fuel pump was removed, and the drive coupling shaft was found intact. The top spark plugs were removed and displayed coloration consistent with normal engine operation. The engine was rotated and thumb compression was attained on all six cylinders. The crankshaft and camshaft continuity were confirmed throughout the engine. The magnetos could not be tested due to thermal damage. The airplane was equipped with a 3-bladed Hartzell propeller. Propeller strike marks were observed on a large diameter tree directly in front of the engine with slash signatures measuring approximately 8 to 12” apart on the tree trunk. A large 12” section of the tree trunk was severed. The three composite material propeller blades were liberated from the propeller hub assembly. One blade was found approximately 10 ft forward of the hub assembly in one piece. A second blade was found below the hub assembly in the soil but was fractured in half from impact forces. The third propeller blade was not recovered. The wreckage was retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA24FA397
Event ID
20240928195219
Case number
ERA24FA397
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. 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.
  • API snapshot SHA-256: 005709f1a866f17a4048718245a74552d1a32d2387c60d18fb86cfc2ee290fdf; retrieved 2026-09-15T08:58:36.851Z.