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

Piper PA32RT accident near Nashville, Tennessee, March 5, 2024

On March 5, 2024 at about 1:43 am local time, a 1978 Piper PA32RT, registered CFBWH, was substantially damaged in an accident during approach (VFR go-around) near Nashville, Tennessee (John C Tune airport). It was a personal flight under general aviation rules (Part 91). 5 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to ensure the proper placement of the fuel selector during the approach and landing, which resulted in fuel starvation and a subsequent total loss of engine power.

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

What the record shows

Date
March 5, 2024 · about 1:43 am local time
Place
Nashville, Tennessee · John C Tune · map
Type
Accident
Injuries
5 people were killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA32RT 300T, built 1978 · all PA32RTs on the register
Registration
CFBWH · no longer on the register · serial PA32-7887126
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was approaching the destination airport in night visual meteorological conditions at the conclusion of a visual flight rules cross-country flight. As the pilot descended the airplane from 10,500 ft mean sea level (msl), he was communicating with the approach controller and transitioning through Class C airspace toward his destination airport, which was located in underlying Class D airspace. The approach controller handed the pilot off to the destination airport tower controller. The pilot contacted the tower controller about 8 miles north of the airport, and again about 5 miles north of the airport as instructed. The pilot was subsequently cleared to land on runway 20 with a request to confirm the airplane type; the pilot responded with the airplane type, but did not read back the landing clearance. The airplane’s flight track was aligned with the runway centerline during the 3-nautical-mile final approach, but one mile from the runway, the airplane remained at an altitude about 2,400 ft msl, and the pilot subsequently informed the tower controller that he wanted to overfly the airport at 2,500 ft msl and come back to land on runway 20. The reason the pilot did not land could not be determined, and the controller did not inquire about the reason, but instructed the pilot to contact the approach controller again. Residential video/audio cameras captured the sound of the airplane’s engine as it overflew the airport. Analysis of the audio revealed that the engine was operating at nearly full continuous power of about 2,650 rpm before the engine sound became abnormal, and the audio contained several “popping” noises before the sound of engine noise ended. When the airplane was south of the airport, the approach controller asked if the pilot still had the airport in sight. The pilot stated that his engine had “turned off,” and that he would be landing, but he did not know where. The controller declared an emergency and repeatedly cleared the pilot to land on runway 2. The pilot responded that he had the runway in sight, but was too far away to reach it. Shortly after, the airplane impacted terrain adjacent to an interstate 2 nautical miles south of the runway and a significant postimpact fire ensued. Postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation. Examination of the fuel system revealed that the fuel selector was between the off and left main tank positions. This setting would starve the engine of fuel and was likely the result of the pilot changing the fuel selector handle in preparation for landing. The first step of the manufacturer’s approach and landing checklist was, “Fuel Selector Proper Tank.” Given the lack of other mechanical anomalies found during the examination, it is likely that the pilot moved the fuel selector at some point during the overflight and approach, but failed to fully seat the selector in position, resulting in a restricted fuel flow that was less than that needed to sustain engine power. Following the loss of engine power, the remaining altitude was insufficient to provide gliding distance to the runway.

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. Fuel starvation during approach (VFR go-around) defining event
  2. Off-field or emergency landing during landing
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • Aircraft › Fluids/misc hardware › Fluids › Fuel › Incorrect use/operation
  • Aircraft › Aircraft systems › Fuel system › Fuel distribution › Incorrect use/operation
  • Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 200 hours in all; 75 in this make and model
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

Passenger

  • Seat: rgt
  • Injury: fatal

Passenger

  • Seat: rear
  • Injury: fatal

Passenger

  • Seat: rear
  • Injury: fatal

Passenger

  • Seat: rear
  • Injury: fatal

The aircraft

  • Airframe total time: 4,064 hours
  • Last inspection: annual inspection, May 21, 2023; 10 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming TIO-540-S1AD (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: IOB Mount Sterling KY
  • Flight plan: VFR
  • Runway 02/2, 6,001 ft by 100 ft

Weather at the time

  • Light: night
  • Wind: from 150° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 66°F (19°C), dew point 59°F (15°C)
  • Altimeter: 29.98 inHg
  • Observation at 7:50 pm from JWN, 3 miles away

Weather report (METAR): KJWN 050150Z 15008KT 10SM CLR 19/15 A2998

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers4

Photographs from the investigation 8 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

18 documents, released by the NTSB on March 5, 2025. 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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.