FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05LA011 · Piper PA-31-350

21 Oct 2004 · Pompano Beach, FL, United States

Twin Town Leasing Piper PA-31-350 · Accident: total loss of engine power (non-mechanical) en route

From Exuma International Airport (MYEF) to Fort Lauderdale Hollywood International Airport (KFLL)

Report a problem

Event

NTSB case
MIA05LA011
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-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
N61518
Onboard fatalities
Unknown
Route
From Exuma International Airport (MYEF), Moss TownTo Fort Lauderdale Hollywood International Airport (KFLL), Fort Lauderdale, 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
First occurrenceThe 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
Total loss of engine power (non-mechanical)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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
Destroyed

Cause areas

  • Pilot in command › Aircraft handling, inadequate
  • Pilot in command › Fuel consumption calculations, improper
  • Pilot in command › Instructions, written/verbal, not followed
  • Pilot in command › Refueling, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Before the start of the trip, the pilot was reportedly given $500.00 cash by the operator to purchase fuel. The pilot stated that the first leg of the flight from KFLL to MYEF departed with the main fuel tanks full and approximately 10 gallons in each of the auxiliary fuel tanks. There were no deviations en-route, and the uneventful flight lasted a reported 1 hour 40 minutes. After landing in Exuma International Airport, the main fuel tanks contained slightly more than 1/2 fuel capacity. Ten gallons of fuel were added to each of the two auxiliary fuel tanks at MYEF, no additional fuel was purchased. The flight departed for KFLL, and during the climb to 10,000 feet, he leaned the fuel/air mixture. During the cruise portion of the flight, the fuel in the auxiliary fuel tanks was consumed then he switched to the main fuel tanks to supply fuel to the engines. The flight crossed the DEKAL intersection at 4,000 feet, which is about 31 nautical miles southeast of KFLL, continued, and the right engine manifold pressure decreased, the cylinder head temperature reached red line indication, and the engine sputtered. He declared an emergency with air traffic control and the controller provided vectors to KFLL which he verbally acknowledged but did not comply with. While operating single engine, with the engine operating at full power, he reported no discrepancies with the left engine. He reported he could reach KFLL but was concerned about flying over a populated area at a low altitude, and was losing altitude. Contrary to the statement made by the pilot that he was not able to maintain altitude while flying single-engine, the airplane was capable of a rate of climb greater than 170 feet-per-minute if flown properly. He elected to ditch the airplane in the Atlantic Ocean; the airplane was not recovered. The operator was asked repeatedly by NTSB for historical fuel receipts and flight hours for N61518 but did not comply. NTSB review of fuel consumption calculations performed by the Federal Aviation Administration (FAA) Inspector-In-Charge revealed the aircraft would have experienced fuel exhaustion at the approximate location and time when the pilot declared an emergency with ATC following failure of the right engine. The NTSB did not receive the NTSB requested detailed, signed, dated statement from the pilot.

Probable cause

The pilot's inadequate in-flight planning/decision, which resulted in fuel exhaustion and the loss of engine power in one engine. Contributing factors were the pilot's inadequate handling of the aircraft following failure of the right engine for his failure to extract maximum single engine performance, and his failure to properly refuel the aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05LA011
Event ID
20041027X01705
Case number
MIA05LA011
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: d5d4f797334aaa32d15f27152c0aa26d03483e78d12421be81ef52438a50aff1; retrieved 2026-09-21T19:07:03.187Z.