Cirrus Design CORP SR22T accident near Franklin, North Carolina, September 18, 2025
On September 18, 2025 at about 6:56 pm local time, a 2016 Cirrus Design CORP SR22T, registered N218VB, was substantially damaged in an accident during approach (VFR pattern final) near Franklin, North Carolina (Macon County airport). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).
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 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 18, 2025 · about 6:56 pm local time
- Place
- Franklin, North Carolina · Macon County · map
- Type
- Accident
- Injuries
- 3 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22T, built 2016
- Registration
- N218VB · registry record · serial 1378
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On September 18, 2025, at 1456 eastern daylight time, a Cirrus SR22T, N218VB, was substantially damaged when it was involved in an accident near Franklin, North Carolina. The private pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Preliminary air traffic control information provided by the Federal Aviation Administration (FAA) indicated that the pilot was on an instrument flight rules flight from John C. Tune Airport (JWN), Nashville, Tennessee to Macon County Airport (1A5) Franklin, North Carolina. As the pilot approached 1A5, he requested a visual approach to runway 07 from air traffic control. The controller approved the request, and at 1448 the pilot reported the airport in sight. The controller then approved a frequency change to the common traffic advisory frequency. Shortly after, the pilot transmitted (while still tuned to the controller’s radio frequency) that he was at 6,800 ft and intended to perform a 360° turn to land on runway 07. The controller then advised the pilot that he was still on the frequency; there were no further transmissions received from the pilot. Review of preliminary ADS-B data showed that shortly after, the airplane began a descending left turn from an altitude of about 6,300 ft mean sea level. It continued through a 360° left turn before it began to approach runway 7 at an altitude of about 3,300 ft (the airport elevation of 1A5 was 2,033 ft). The ADS-B data ended when the airplane was about 0.5 nautical miles from the runway threshold. Surveillance video showed the airplane flying over the runway before initiating a descending left turn. The airplane continued descending in the left turn before entering a tightening spiral and impacting the ground. Multiple witnesses near the accident site reported observing the airplane flying at a low altitude near the airport and over a nearby school playground. The airplane was described as rocking side-to-side, with its wingtips moving up and down, before rolling inverted and descending behind a tree line. The airplane impacted a field about 0.25 miles east of 1A5. The airplane came to rest upright and all major components of the airframe were located at the accident site. All major flight control surfaces were observed and flight control continuity was traced throughout the flight control system. The engine sustained impact damage but remained attached to all four engine mounts. The propeller flange, hub, and one blade remained attached to the engine. During the on-scene examination, the engine was lifted and its crankshaft was rotated, which confirmed crankshaft and camshaft continuity. Borescope examination of all cylinders revealed normal combustion and operating signatures on the piston faces, cylinder walls, and valve heads. The airplane was recovered and 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
- Loss of control in flight during approach (VFR pattern final) defining event
The aircraft
- Seats: 5
- Landing gear: fixed
The flight
- Departed from: JWN Nashville TN at 5:41 pm
- Destination: 1A5 Franklin NC
- Runway 07/2, 5,002 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 84°F (29°C), dew point 52°F (11°C)
- Altimeter: 30.07 inHg
- Observation at 3:51 pm from RHP, 22 miles away
Weather report (METAR): METAR KRHP 181951Z AUTO 00000KT 10SM CLR 29/11 A3007 RMK AO2 T02890111=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
