FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA096 · Piper PA-31-350

24 Dec 2012 · Leesburg, FL, United States

Piper PA-31-350 · Accident: loss of engine power (total) en route

From Eagles Nest Aerodrome (FD44) to Leesburg International Airport (LEE)

Report a problem

Event

NTSB case
ERA13FA096
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
1 · 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-31-350

Aircraft type
Piper PA-31
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
N78WM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eagles Nest Aerodrome (FD44), Crescent City, FLTo Leesburg International Airport (LEE), Leesburg, FL
Aircraft age
Not recorded
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

  • Personnel issues › Task performance

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

NTSB narrative

The pilot and the pilot-rated passenger were flying from their home located at a residential airpark, where no fuel services were available, to an airport located about 37 nautical miles away. Shortly after departing on the flight, the passenger queried the pilot when she noticed the airplane's low fuel state. The pilot responded that one of the fuel gauges always reported a greater quantity of available fuel than the other, and that if necessary they could utilize needed fuel from the tank with the higher reported fuel quantity. About 15 minutes after departure, the pilot advised air traffic control that the airplane was critically low on fuel, and about 5 minutes later the airplane impacted trees and terrain after all fuel had been exhausted and both engines ceased producing power.

Examination of the airframe and engines after the accident confirmed that all of the airplane's fuel tanks were essentially absent of fuel, and that the trace amounts of fuel recovered were absent of contamination. Post-accident testing of the fuel quantity senders showed that both of the applicable units failed to meet the indicated electrical resistance tolerances published in the service manual for the full fuel position, and only one of the units was within the tolerance for the empty position.

Based on the autopsy and toxicology results, the pilot had emphysema, hypertension, dilated cardiomyopathy, and severe coronary artery disease; however, given that the passenger seated in the right seat of the airplane did not report any signs of acute incapacitation, and that the pilot did not communicate any medical issues to air traffic control, it does not appear that these conditions affected his performance on the day of the accident.

The pilot did not report any chronically painful conditions to the FAA in his most recent medical certificate applications, however, the post-accident toxicology identified that the pilot was taking several pain medications (diclofenac, gabapentin, and oxycodone), and one illegal substance (marijuana). Based on the medications' Food and Drug Administration warnings, gabapentin and oxycodone may be individually impairing and sedating; their combined effect may be additive. The effects of the underlying conditions that necessitated the medication could not be determined. It is impossible to determine from the available information what direct effect the marijuana alone may have had on the pilot's judgment and psychomotor functioning; however, the combination of marijuana, oxycodone, and gabapentin likely significantly impaired the pilot's judgment and contributed to his failure to ensure the airplane had sufficient fuel to complete the planned flight.

Probable cause

The pilot's inadequate preflight planning, which resulted in fuel exhaustion and a subsequent total loss of power in both engines during cruise flight. Contributing to the accident was the pilot’s use of prescription and illicit drugs, which likely impaired his judgment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA096
Event ID
20121224X20556
Case number
ERA13FA096
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: 35313297566f253e469bb9fc33222a811af2f053b14f62acb3aad9864f380e0c; retrieved 2026-09-14T15:51:09.143Z.