FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Island Air Charters Piper PA31 350 accident

19 Sept 2020 · Fort Lauderdale, FL, United States

Piper PA31 350 · Accident: fuel exhaustion on approach

From Grand Bahama International Airport (FPO) to an unrecorded destination

Report a problem

Event

NTSB case
ERA20LA331
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
Event fatalities
Unknown
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
Charter & commuter
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 PA31 350

Aircraft type
Piper PA31
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
N257SH
Onboard fatalities
Unknown
Route
From Grand Bahama International Airport (FPO), FreeportTo not recorded
Aircraft age
About 40 years (built 1980)
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 135: Air Taxi & Commuter
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
Approach · VFR pattern base
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 exhaustion
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 of the on-demand passenger flight about 10 to 15 miles from the destination when the twin-engine airplane’s left engine stopped producing power. The pilot opened the fuel cross-feed valve, switched on both fuel boost pumps, and restored power to the left engine. The pilot continued to the original destination rather than land at a closer airport because he believed that the right engine fuel gauge indicated adequate fuel to complete the flight. When the airplane was on a left base leg for landing, both engines lost total power. The pilot made a forced landing on the grass between the runway and a taxiway, during which the airplane was substantially damaged. Postaccident examination of the airplane found that all of the fuel tanks were intact and empty of useable fuel. When the fuel system was tested, no leaks or other mechanical deficiencies were observed that would have precluded normal operation at the time of the accident. The airplane’s inboard fuel tanks had most recently been topped off 3 days before the accident (the outboard tanks were kept empty for weight reasons), after which the pilot performed a round trip passenger flight. Before the accident flight, the pilot did not visually check the fuel level in fuel tanks as prescribed by the preflight checklist. He stated that the fuel gauges, which he did not believe were accurate, indicated that the inboard tanks were more than half full. Based on his previous experience with the airplane’s typical fuel consumption, he estimated that he had about 2 hours of fuel remaining onboard the airplane to complete the planned round-trip flight, plus a 30-minute reserve. Following the accident, the pilot stated that he was “stubbornly overconfident” that there was enough fuel to complete the flight and, based on his extensive experience flying the airplane, he calculated a fuel consumption of 40 gallons per hour (gph); but he admitted that he should have calculated a fuel consumption of 50 gph. Based on the lack of fuel in the fuel tanks after the accident, as well as the confirmed postaccident integrity of the fuel system, it is likely that the pilot’s failure to verify the quantity of fuel onboard the airplane prior to the flight and his miscalculation of the airplane’s fuel consumption rate resulted in fuel exhaustion and the subsequent total loss of engine power. The accident likely also could have been avoided if the pilot landed immediately after the first loss of engine power rather than continuing to the originally planned destination. Based on available medical and operational evidence, it is unlikely that the pilot’s diagnosed tremors or other medical conditions contributed to the accident. There was no evidence that the pilot’s use of medications or alcohol contributed to the accident; however, available evidence was limited and did not include postaccident toxicology results.

Probable cause

The pilot’s improper preflight fuel planning, which resulted in a total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot’s decision to continue to the destination following the loss of engine power to the first engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA331
Event ID
20200919X42745
Case number
ERA20LA331
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, cause areas. 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: 7052e77a7614d9a231ded995e5a42309969e23dd0a46691a63a880e17b7881fe; retrieved 2026-09-16T13:04:02.514Z.