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

Cirrus Design CORP SR22 accident near Lafayette, Tennessee, July 2, 2026

On July 2, 2026 at about 3:32 pm local time, a 2011 Cirrus Design CORP SR22, registered N127DC, was substantially damaged in an accident during enroute near Lafayette, Tennessee. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. 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
July 2, 2026 · about 3:32 pm local time
Place
Lafayette, Tennessee · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22, built 2011
Registration
N127DC · registry record · serial 3802
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On July 2, 2026, at 1032 central daylight time, a Cirrus Design Corp SR22, N127DC, was substantially damaged when it was involved in an accident near Lafayette, Tennessee. The pilot and passenger sustained no injuries. The airplane was operated as a Title 14 Code of Federal Regulation Part 91 personal flight. The pilot reported that following the completion of an annual inspection, he was returning a ferry pilot to Owensboro/Davis County Regional Airport (OWB), Owensboro, Kentucky. About 20 minutes into the flight, while at an altitude of 6,500 feet mean sea level, the engine completely lost power. The pilot initially attempted to divert to the nearest airport, which was about 12 miles away, but then determined they would be unable to reach the airport. The pilot then made a distress call to air traffic control and decided to activate the airplane’s whole airframe parachute system at an altitude of 1,975 feet. The parachute successfully deployed and the airplane came to rest in a tree within an urban neighborhood. The airplane sustained substantial damage to the empennage, fuselage, and wings. 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

  1. Loss of engine power (total) during enroute defining event

The aircraft

  • Maximum gross weight: 3,600 lb
  • Seats: 4
  • Landing gear: fixed

The flight

  • Departed from: CSV Crossville TN at 2:07 pm
  • Destination: OWB Owensboro KY
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 120° at 7 knots
  • Visibility: 10 statute miles
  • Sky: scat at 4,200 ft
  • Temperature: 97°F (36°C), dew point 72°F (22°C)
  • Altimeter: 30.14 inHg
  • Observation at 12:00 pm from BNA, 43 miles away

Weather report (METAR): METAR KBNA 021653Z 12007KT 10SM SCT042TCU 36/22 A3014 RMK AO2 SLP197 TCU S-W-NW T03560222 $

Injuries

FatalSeriousMinorNone
Flig1
Passengers1

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 docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site 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 ERA26LA257.