ERA16FA289 · Piper PA 31 325
Piper PA 31 325 · Accident: fuel starvation en route
From Kissimmee Gateway Airport (ISM) to University Oxford Airport (UOX)
Event
- NTSB case
- ERA16FA289
- 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
- 6 · 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 325
- 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
- N447SA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kissimmee Gateway Airport (ISM), Orlando, FLTo University Oxford Airport (UOX), Oxford, MS
- Aircraft age
- About 32 years (built 1984)
- 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
- Fuel starvation
- 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 private pilot and five passengers departed on a day instrument flight rules cross-country flight in the multiengine airplane. Before departure, the airplane was serviced to capacity with fuel, which corresponded to an endurance of about 5 hours. About 1 hour 45 minutes after reaching the flight's cruise altitude of 12,000 ft mean sea level, the pilot reported a failure of the right engine fuel pump and requested to divert to the nearest airport. About 7 minutes later, the pilot reported that he "lost both fuel pumps" and stated that the airplane had no engine power. The pilot continued toward the diversion airport and the airplane descended until it impacted trees about 1,650 ft short of the approach end of the runway; a postimpact fire ensued.
Postaccident examination of the airframe and engines revealed no preimpact failures or malfunctions that would have precluded normal operation. The propellers of both engines were found in the unfeathered position. All six of the fuel pumps on the airplane were functionally tested or disassembled, and none exhibited any anomalies that would have precluded normal operation before the accident. Corrosion was noted in the right fuel boost pump, which was likely the result of water contamination during firefighting efforts by first responders.
The airplane was equipped with 4 fuel tanks, comprising an outboard and an inboard fuel tank in each wing. The left and right engine fuel selector valves and corresponding fuel selector handles were found in the outboard tank positions. Given the airplane's fuel state upon departure and review of fuel consumption notes in the flight log from the day of the accident, the airplane's outboard tanks contained sufficient fuel for about 1 hour 45 minutes of flight, which corresponds to when the pilot first reported a fuel pump anomaly to air traffic control. The data downloaded from the engine data monitor was consistent with both engines losing fuel pressure due to fuel starvation.
According to the pilot's operating handbook, after reaching cruise flight, fuel should be consumed from the outboard tanks before switching to the inboard tanks. Two fuel quantity gauges were located in the cockpit overhead switch panel to help identify when the pilot should return the fuel selectors from the outboard fuel tanks to the inboard fuel tanks. A flight instructor who previously flew with the pilot stated that this was their normal practice. He also stated that the pilot had not received any training in the accident airplane to include single-engine operations and emergency procedures. It is likely that the pilot failed to return the fuel selectors from the outboard to the inboard tank positions once the outboard tanks were exhausted of fuel; however, the pilot misdiagnosed the situation as a fuel pump anomaly.
Probable cause
A total loss of power in both engines due to fuel starvation as a result of the pilot's fuel mismanagement, and his subsequent failure to follow the emergency checklist. Contributing to the pilot's failure to follow the emergency checklist was his lack of emergency procedures training in the accident airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA289
- Event ID
- 20160814X40011
- Case number
- ERA16FA289
- 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: 868145f36afe1b566e025c887638894aa8ed41b017c1122c07ed104a210d240b; retrieved 2026-09-14T21:58:35.436Z.