The U.S. aircraft register, updated daily
Accidents · NTSB ERA25LA238 · Final report

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 initial climb near Fayetteville, Tennessee (Fayetteville Muni airport). It was a personal 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).

The NTSB's probable cause their words, unchanged

The pilot’s decision to operate the airplane with known discrepancies.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 24, 2025 · about 5:30 pm local time · cases in 2025
Place
Fayetteville, Tennessee · Fayetteville Muni · cases near this airport · 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
Personal flight · general aviation rules (Part 91)

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

The pilot, who was also a mechanic, purchased the twin-engine airplane nearly one year prior to the accident flight. Between the time of purchase and the accident flight he had performed some maintenance of the airplane’s engines; however, the airplane had not undergone an annual inspection at any point during the preceding 15 years, nor had the pilot obtained a special flight (ferry) permit for the accident flight. Prior to departing, the pilot performed an engine runup and noted a substantial rpm drop during the right engine magneto check. He also described that he leaned both engines’ mixture controls for takeoff due to the density altitude, and because both engines would “flood out” and not run with the mixture controls in the fully forward position. During initial climb the pilot reported the airplane seemed “sluggish,” so he advanced the mixture controls forward, after which both engines lost partial power. The pilot then decreased the airplane’s pitch attitude and landed in the grass next to the runway, which resulted in substantial damage to both wings and the fuselage. A postaccident examination of the airplane’s engines found contamination in the fuel system for the right engine. The fuel manifold valve was corroded and the fuel servo inlet screen and fuel manifold screen for the right engine were partially obstructed. Multiple spark plugs installed in the right engine exhibited corrosion, lead, and carbon fouling, and severe wear. The right engine air intake hose was found disconnected from the airbox. This condition would have likely resulted in the engine ingesting warm, unfiltered air from the cowling instead of cooler, filtered ram air. The combination of these issues likely resulted in the feeling of diminished performance the pilot reported. The examination otherwise found no evidence of any preaccident mechanical malfunctions or failures of the left engine or the airframe that would have precluded normal operation. Given the pilot’s statement that the engines would “flood out” and would not run with the mixture controls in the full forward position, it is likely that when the pilot advanced the mixture controls during initial climb the increased fuel flow resulted in the partial loss of power the pilot reported. Because this abnormal condition was known prior to the accident flight, the pilot should not have undertaken the flight without performing additional troubleshooting steps to fully understand and resolve the underlying issue(s).

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 initial climb defining event
  2. Off-field or emergency landing during initial climb
  3. Aircraft maintenance event during prior to flight

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Not serviced/maintained other cases naming the engine
  • Personnel issues › Task performance › Maintenance › (general) › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,344.2 hours in all; 6 in this make and model; 8.9 in the last 90 days; 6.3 in the last 30 days; 2,344.2 as pilot in command
  • Last flight review: November 11, 2024
  • Medical certificate: BasicMed (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection, February 29, 2008
  • Maximum gross weight: 5,200 lb
  • Seats: 2
  • Landing gear: retractable
  • Engine 1: Continental IO-470V09 (piston); 87 hours total
  • Engine 2: Continental IO-470 (piston); 1,389 hours total

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
Flight crew1

Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

11 documents, released by the NTSB on October 21, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA25LA238.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.