MIA03LA154 · Piper PA-31-310
Piper PA-31-310 · Accident: total loss of engine power (non-mechanical) en route
From Akron Canton Regional Airport (CAK) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- MIA03LA154
- 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
- N876RD
- Operator
- Perry L Fleisher · private individual
- Onboard fatalities
- Unknown
- Route
- From Akron Canton Regional Airport (CAK), Canton, OHTo Fort Lauderdale Executive Airport (FXE), 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 · descent
- 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
- Substantial
Cause areas
- Pilot in command › Planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he and his wife were en route to a medical conference which was to be held aboard a cruise ship that was departing from Fort Lauderdale, Florida, at 1700. He stated that both tanks were full of fuel when he departed the Canton Regional Airport, Canton, Ohio, en route to Fort Lauderdale Executive Airport. According to the pilot, the inboard tanks had been selected for the first hour and a half and the outboard tanks for the following two hours. He said the flight was vectored around thunderstorms, and during the descent, when about 12 miles to the north of Palm Beach International Airport, Palm Beach, Florida, the left engine ceased operating. He said that at this time he noticed that both inboard fuel indicators showed the tanks to be empty, and he switched to the outboard tanks, both of which were shown to be a quarter full. The pilot stated that two minutes later both engines began to surge, and after making an emergency radio communications call, he was advised by the FAA Air Traffic Controller that Tailwinds Airport was located 4 miles to the west. Unable to reach the runway at Tailwinds Airport, the pilot said he made a forced landing in an orange grove. the pilot also said that prior to the accident, there had not been any mechanical failure or malfunctions to the airplane or any of its systems. Examination of the accident site revealed that the airplane had incurred substantial damage, and there was little or no fuel present at the scene. Follow-on examination of the airplane, its fuel system and both engines revealed no anomalies.
Probable cause
The pilot's failure to adequately plan for the flight which resulted in fuel exhaustion, a forced landing, and damage to the airplane during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA154
- Event ID
- 20030813X01318
- Case number
- MIA03LA154
- 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: 8b5fa9c9fbee28e292d4e10e6e59f6b68f71f28e36e21aa04950acb2a4148eb6; retrieved 2026-09-21T19:24:07.253Z.