ERA25FA352 · Cirrus Design Corp SR22T
Cirrus Design Corp SR22T · Accident: loss of control in flight on approach
From John C Tune Airport (JWN) to Macon County Airport (1A5)
Event
- NTSB case
- ERA25FA352
- 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
- 3 · 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 SR22T
- 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
- N218VB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From John C Tune Airport (JWN), Nashville, TNTo Macon County Airport (1A5), Franklin, NC
- Aircraft age
- About 9 years (built 2016)
- 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
- Approach · VFR pattern final
- 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
- Substantial
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 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.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25FA352
- Event ID
- 20250918201041
- Case number
- ERA25FA352
- 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: 82ef4266259f76874e1521a7dc42bda0248ae09996f7d68ad07fda0f19cde8c9; retrieved 2026-09-15T09:09:02.141Z.