FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA165 · Piper PA-31-310

28 Jan 2012 · Palm Beach, FL, United States

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

From San Salvador International Airport (MYSM) to Treasure Coast International Airport (FPR)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA12LA165
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-31-310

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
N30DC
Onboard fatalities
Unknown
Route Possible conflict
From San Salvador International Airport (MYSM), San Salvador, AOTo Treasure Coast International Airport (FPR), Fort Pierce, 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 · descent
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 › Action/decision

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

NTSB narrative

On the morning of the accident, the pilot had the airplane topped off with 22 gallons of fuel, which he visually confirmed. The pilot flew the airplane to an offshore island that did not have fuel, deplaned passengers, and was returning to the mainland. The pilot planned for 4.6 hours of round trip operation and had previously flown similar flights to the same destination with durations of 4.6 to 5.1 hours. The outbound leg was completed without any anomalies noted; the pilot reported that the preflight inspection, start, taxi, runup and takeoff checks for the returning accident flight were "normal." Throughout the climb after takeoff, the pilot noted less manifold pressure on the left engine, and, by the time the airplane reached a cruising altitude of 10,500 feet, the engine was unable to maintain more than 55 percent power at 2,200 rpm and 26 inches of manifold pressure. The pilot matched the right engine power setting to the left and switched from the main fuel tanks to the outboard tanks at the top of the climb.

He consulted the pilot operating handbook, which indicated a 4 gallon-per-hour reduction in fuel consumption at that power setting. En route, the left outboard tank emptied about 15 minutes before the right tank, which the pilot later reported was unusual because both engines normally burned evenly. About 60 nautical miles (nm) from the destination, the pilot initiated a descent, and about 55 nm from the destination, the left engine began surging. According to the pilot, the fuel gauges at the time indicated just below 1/4 full on the left main fuel tank and above 1/4 full on the right main fuel tank. The pilot turned on the emergency boost pump and selected fuel crossflow, which restored power to the left engine.

The pilot then turned the airplane toward the nearest mainland airport, about 32 nm away, and contacted approach control. Shortly thereafter, the left engine surged, then lost power, followed closely by the right engine. The pilot turned on the emergency boost pumps, switched to the outboard and inboard fuel tanks sequentially (separately and with cross flow) but was unable to restore engine power. With the airplane descending through about 7,500 feet, the pilot completed the feathering procedure for both engines and established a best glide attitude, eventually landing the airplane on a beach.

On-scene examination of the airplane did not reveal the presence of fuel, and no evidence of fuel leakage. The investigation did not reveal any mechanical malfunctions or failures that would have precluded normal operation, and the pilot did not note any preexisting anomalies with the fuel quantity indicators. Insufficient and contradictory information precluded a determination as to why the airplane ran out of fuel. The pilot had previously flown the same route with ample fuel remaining, but couldn't for this flight. The left engine would not produce normal power, so the pilot reduced right engine power, which should have resulted in more en route flight time, but didn't. Lower power settings should have resulted in a longer time to destination, yet based on provided flight times, it didn't. The left outboard fuel tank ran out of fuel sooner than normal, indicating that either the left engine was utilizing an excessive amount of fuel, or the fuel tank had not been filled completely or fuel was drained from it at the intermediate stop. Also, when the left engine stopped the first time, the fuel gauge, which had not been previously been noted as inaccurate, reportedly still indicated the presence of fuel at just under 1/4 tank.

A direct line plot from the departure airport for the accident flight to the intended destination indicated the airplane overflew an island airport with fuel facilities about 105 nm from the destination and about 50 nm before the left engine began to surge. It is unknown if the pilot had sufficient information at that point to properly judge whether he should bypass an available en route fuel stop. However, with the information he did have, he judged that he had adequate fuel to complete his flight, which ultimately proved to be incorrect.

Probable cause

The pilot’s in-flight misjudgment of fuel remaining resulting in fuel exhaustion and a total loss of engine power. Contributing to the accident was an inadequate fuel quantity for the flight for reasons that could not be determined during postaccident investigation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA165
Event ID
20120130X60836
Case number
ERA12LA165
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: df7b99d00d83d45a48739608ac9e35823473c977719f216d6ecb4023f21501ef; retrieved 2026-09-15T17:08:08.186Z.