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

Piper PA-28 accident near Odessa, Florida, November 25, 2017

On November 25, 2017 at about 7:20 pm local time, a 1973 Piper PA-28, registered N57351, was substantially damaged in an accident during enroute (cruise) near Odessa, Florida. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of engine power due to fuel starvation as a result of the pilot's inadequate planning and in-flight fuel management. Contributing to the accident was the pilot’s failure to follow proper procedures after the 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
November 25, 2017 · about 7:20 pm local time
Place
Odessa, Florida · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28 140, built 1973 · all PA-28s on the register
Registration
N57351 · no longer on the register · serial 28-7425097
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot indicated that about 3 weeks before the accident flight, he had topped off the airplane's two fuel tanks and flown the airplane once; the flight lasted about 1 1/2 hours and was conducted using fuel from the left tank only. During his preflight inspection before the accident flight, the pilot noted that the right tank was full and the left tank was "just under half." The pilot departed on the personal flight, which had a planned duration of 2 hours, and was again using fuel from the left tank only. After about 40 minutes to 1 hour of flight time, while the airplane was at an altitude of about 2,500 ft above mean sea level, the pilot reversed course to return to the departure airport; shortly thereafter, the engine lost total power. The pilot turned on the electric fuel pump and ran it for about 10 seconds before he switched to the right tank. The engine did not start, and the pilot switched back to the left tank. The pilot's attempts to restore engine power were unsuccessful, and he did not refer to the engine failure checklist in the cockpit. He chose to conduct a forced landing; the airplane landed in a field and was substantially damaged when the right wing struck a power line pole. Postaccident examination of the airplane revealed that the left tank was empty, the right tank was full, and the fuel selector was set to the left tank. Each tank had a usable fuel capacity of 24 gallons, and performance information from the airplane manufacturer's pilot's operating manual indicated that it was possible for the airplane to burn 24 gallons of fuel in the 2 1/2 hours flown by the pilot since fueling. Examination of the airframe and engine did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation, and the engine was successfully test run. Because there was no evidence of an engine malfunction or failure and there was sufficient fuel on board, it is likely that the engine lost total power due to fuel starvation as a result of the pilot's continued operation using the left fuel tank only. The pilot's actions after the engine lost power likely contributed to his inability to restore engine power. The manufacturer's emergency procedures checklist cited switching fuel tanks before activating the electric fuel pump; however, the pilot activated the electric pump, ran it for about 10 seconds on the empty left tank, switched to the full right tank, and then switched back to the empty left tank. Although it could not be determined how long the pilot kept the fuel selector valve set to the right tank before he switched it back to the left tank, it is likely that there was insufficient time for the engine to restart once the fuel selector was switched to the right tank, particularly if he did not activate the electric fuel pump at that time.

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 (cruise) 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

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
  • cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
  • factor Personnel issues › Action/decision › Action › Incorrect action sequence › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 149 hours in all; 142 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 4,722 hours
  • Last inspection: annual inspection, June 1, 2017; 10 hours since
  • Maximum gross weight: 2,150 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 4,722 hours total

The flight

  • Departed from: VDF Tampa FL at 6:40 pm
  • Destination: VDF Tampa FL
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 240° at 7 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 23,000 ft
  • Temperature: 73°F (23°C), dew point 57°F (14°C)
  • Altimeter: 29.98 inHg
  • Observation at 11:53 pm from TPA, 12 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

9 documents, released by the NTSB on February 4, 2020. 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.

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.