# NTSB ERA25FA352: Cirrus Design SR22T, N218VB, Franklin, NC, September 18, 2025 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: September 18, 2025, 14:56 local (18:56 UTC) - Place: Franklin, NC - Coordinates: 35.226085, -83.418479 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.2261&lon=-83.4185&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 3 fatal - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: Cirrus Aircraft, FAA/FSDO, FAA/NTSB, Continental Aerospace - NTSB case key (mKey): 201041 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25FA352 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201041/pdf - Page: https://openairdocs.org/ntsb/ERA25FA352 ## Preliminary report 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. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cirrus Design SR22T, 8 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2130004), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Aircraft - Registration: [N218VB](https://openairdocs.org/aircraft/N218VB), registered now, S/N 1378, built 2016 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SR22T - Registry model: [Cirrus Design SR22T](https://openairdocs.org/model/cirrus-design-sr22t) (registry code 2130004) (OpenAirDocs) - Registry engine: [Continental TSIO-550-K](https://openairdocs.org/engine/continental-tsio-550-k) (registry code 17410, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 1378 - Year built: 2016 - Damage: Substantial damage - Flight: Personal, Part 91 - Departed: JWN, Nashville, TN - Destination: 1A5, Franklin, NC - Airport: 1A5, Macon County, runway 07/25, 5,002 × 100 ft, asphalt ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 52 °F - Altimeter: 30.07 inHg - Observed at: RHP, 22 nm away - METAR: METAR KRHP 181951Z AUTO 00000KT 10SM CLR 29/11 A3007 RMK AO2 T02890111= ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20250918019439A](https://openairdocs.org/incident/20250918019439A), Sep 18, 2025: Cirrus Design Corp SR22T, Franklin, NC, Substantial damage, 3 fatal. On September 18, 2025, about 1456 eastern daylight time, a Cirrus SR22T was substantially damaged when it was involved in an accident near Franklin, north… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.