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

Cessna 310 accident near Fayetteville, Tennessee, June 24, 2025

On June 24, 2025 at about 5:30 pm local time, a 1968 Cessna 310, registered N5045Q, was substantially damaged in an accident during takeoff (rejected takeoff) near Fayetteville, Tennessee (Fayetteville Muni airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was 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
June 24, 2025 · about 5:30 pm local time
Place
Fayetteville, Tennessee · Fayetteville Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 310 N, built 1968 · all 310s on the register
Registration
N5045Q · registry record · serial 310N-0145
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

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

On June 24, 2025, about 12:30 central daylight time, a Cessna 310N, N5045Q, was substantially damaged when it was involved in an accident near Fayetteville, Tennessee. The commercial pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight. The pilot reported that, during an engine, run-up the right engine experienced a drop of about 250 rpm during the magneto check but returned to 1,800 rpm when the magneto switch was placed in the both position. After rotation the pilot reported the airplane “seemed very sluggish.” He attempted to adjust the mixture but upon enriching the mixture both engines lost power. The pilot lowered the nose and attempted to land on the remaining runway but touched down to the left of the runway, hard, which resulted in the landing gear separating. The airplane’s right wing and fuselage were substantially damaged during the accident sequence. The pilot reported that the airplane had about 70 gallons of 100LL aviation fuel aboard. The airplane was 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 (partial) during takeoff (rejected takeoff) defining event

The aircraft

  • Last inspection: annual inspection, February 29, 2008
  • Maximum gross weight: 5,200 lb
  • Seats: 2
  • Landing gear: retractable

The flight

  • Destination: UOS Sewanee TN
  • Flight plan: none
  • Runway 20, 5,900 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 4 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 6,000 ft; scat at 4,500 ft
  • Temperature: 90°F (32°C), dew point 70°F (21°C)
  • Altimeter: 30.26 inHg
  • Observation at 12:15 pm from MDQ, 12 miles away

Weather report (METAR): KMDQ 241715Z AUTO 01004KT 10SM SCT045 BKN060 BKN070 32/21 A3026 RMK A02 T03190212

Injuries

FatalSeriousMinorNone
Flig1

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 ERA25LA238.