FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA98FA200 · Piper PA-31-310

17 Jul 1998 · Miami, FL, United States

Piper PA-31-310 · Accident: partial loss of engine power (mechanical failure) during takeoff

From Miami Executive Airport (TMB) to an unrecorded destination

Report a problem

Event

NTSB case
MIA98FA200
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
1 · all aircraft and ground
Ground fatalities
0
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
N7578L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Miami Executive Airport (TMB)To not recorded
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
Takeoff
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
Partial loss of engine power (mechanical failure)
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 › Airspeed(vmc), not maintained
  • Pilot in command › Preflight planning/preparation, inadequate

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

NTSB narrative

An aircraft mechanic working abeam of the point on the runway that the airplane lifted off was attracted by the sound of engine roughness, and observed black smoke trailing from the left engine. The airplane continued to climb to about 150 feet above ground level, entered a series of shallow left turns at about the airport's east boundary at a slow speed, and then entered a rapid left roll and pitched down. The pilot transmitted an unreadable call on FAA tower frequency, but the words, 'we got a..' and 'engine' were clearly discernable. The airplane crashed in dense brush about 1.25 miles northeast of the airport. Contamination was found in the left engine fuel system. Post crash testing of the left fuel servo revealed it would not sustain a steady state fuel flow above about one half throttle due to contamination.

Probable cause

The pilot's inadequate preflight inspection which led to fuel contamination and subsequent loss of engine power. Also causal was the pilot's failure to maintain single engine flying speed (VMC).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA98FA200
Event ID
20001211X10651
Case number
MIA98FA200
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. 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: 0eae7b462b0cc4576a01d567f5933abc6c107f4a0d97e88611317f45e38f50fc; retrieved 2026-09-20T22:30:17.606Z.