FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA040 · Piper PA-28 140

25 Nov 2017 · Odessa, FL, United States

Piper PA-28 140 · Accident: loss of engine power (total) en route

From Tampa Executive Airport (VDF) to Tampa Executive Airport (VDF)

Report a problem

Event

NTSB case
WPR18LA040
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28 140

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N57351
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tampa Executive Airport (VDF), Tampa, FLTo Tampa Executive Airport (VDF), Tampa, FL
Aircraft age
About 44 years (built 1973)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA040
Event ID
20171127X13142
Case number
WPR18LA040
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 7511de46ee17ba145defc4caa81cb57056fa0e2a4bf87befe1d8918fcf0267ab; retrieved 2026-09-16T06:02:07.046Z.