Cirrus SR22T N218VB

Summary

On 18 September 2025 at about 18:56 local time, a Cirrus SR22T registered N218VB was involved in an accident near Franklin, North Carolina, United States. 3 people were on board and 3 died. The aircraft was substantially damaged. No probable cause has been published yet; this accident is still under investigation.

Date

18 September 2025 at 18:56

Classification

Accident

Location

Franklin, North Carolina, United States

Nearest airport

MacOn County (1A5)

Coordinates

35.2261, -83.4185

Aircraft

Cirrus SR22T

Registration

N218VB

Category

Airplane

Year built

2016

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

Nashville → Franklin

Aircraft damage

Substantial

Weather

VMC

Light

Day

NTSB number

ERA25FA352

3 people died.

The NTSB has not published a probable cause for this record. The investigation is still open; a final report usually follows one to two years after the accident.

Nothing about the cause is stated here that is not in the source record.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.