The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA24FA397 · Preliminary: the investigation is not finished

Cirrus Design CORP SR22 accident near Kill Devil Hills, North Carolina, September 28, 2024

On September 28, 2024 at about 9:18 pm local time, a 2023 Cirrus Design CORP SR22, registered N1281F, was destroyed in an accident during landing near Kill Devil Hills, North Carolina (First Flight airport). It was a personal flight under general aviation rules (Part 91). 5 people were killed. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 28, 2024 · about 9:18 pm local time
Place
Kill Devil Hills, North Carolina · First Flight · map
Type
Accident
Injuries
5 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22, built 2023
Registration
N1281F · registry record · serial 9379
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative preliminary · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area overshoot during landing
  2. Loss of control in flight during landing defining event

The aircraft

  • Airframe total time: 108 hours
  • Last inspection: annual inspection, August 16, 2024; 20 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Fire on the ground
  • Operator: Pantheon Aviation LLC

The flight

  • Departed from: MQI Manteo NC at 9:10 pm
  • Flight plan: none
  • Runway 21, 3,000 ft by 60 ft

Weather at the time

  • Light: daylight
  • Wind: from 170° at 6 knots, gusting 14
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 68°F (20°C)
  • Altimeter: 29.84 inHg
  • Observation at 5:10 pm from FFA

Weather report (METAR): KFFA 282110Z AUTO 17006G14KT 10SM CLR 27/20 A2984 RMK AO2 P0001 T02690201

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

22 documents, released by the NTSB on September 9, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Witness Statements PDF, 5 pages · our copy View Download
2 Flight Instructor Statement PDF, 1 page · our copy View Download
3 Fuel Receipt PDF, 1 page · our copy View Download
4 Memorandum for Record - Video File PDF, 3 pages · our copy View Download
5 Video File video · our copy View Download
6 Pilot Logbooks PDF, 18 pages · our copy View Download
7 Pilot Log (Excerpt) Single Entry PDF, 1 page · our copy View Download
8 Pilot Sr Training Records PDF, 22 pages · our copy View Download
9 Maintenance Records PDF, 20 pages · our copy View Download
10 Flight Track Google Earth Plot map file · our copy Download
11 GPS Track Raw Data spreadsheet · our copy Download
12 Ctaf Audio File audio · our copy View Download
13 Investigative Photos PDF, 5 pages · our copy View Download
14 Wreckage Examination PDF, 15 pages · our copy View Download
15 NTSB Memorandum - Engine Disassembly PDF, 32 pages · our copy View Download
16 Memorandum for Record - Cirrus Emails (Excerpts) PDF, 4 pages · our copy View Download
17 Toxicological Report PDF, 2 pages · our copy View Download
18 Recoverable Data Module - Specialist's Factual REPORT_ERA24FA397 PDF, 19 pages · our copy View Download
19 Attachment 1 to Recoverable Data Module - Specialist's Factual Report_tabular Data data file · our copy Download
20 Certification of Party Representative PDF, 10 pages · our copy View Download
21 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
22 Evidence Control Form PDF, 3 pages · our copy View Download

The same docket at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA24FA397.