FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA82FKT09 · Piper PA-36

2 Apr 1982 · Delray Beach, FL, United States

Piper PA-36 · Accident: partial loss of engine power (mechanical failure) en route

From BASSO, FL to BASSO, FL

Report a problem

Event

NTSB case
MIA82FKT09
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
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-36

Aircraft type
Piper PA-36
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
N57750
Onboard fatalities
Unknown
Route
From BASSO, FLTo BASSO, 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 137: Agricultural
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 · climb to 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
Partial loss of engine power (mechanical failure)
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
Tree(s)
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

  • Fluid, fuel › Leak
  • Fuel system › Undetermined

Approximate · Estimated position: the centre of Delray Beach, FL, the place the record names. Not the accident site.

NTSB narrative

WHILE CLIMBING AFTER TAKEOFF, THE PILOT NOTED A PARTIAL LOSS OF POWER. HE THOUGHT HE COULD SMELL SMOKE AND TURNED THE MASTER AND ALTERNATOR SWITCHES OFF. THE ENGINE CONTINUED TO LOSE POWER AND THE PILOT DUMPED THE LOAD. HE ELECTED TO LAND IN A CANAL. AS HE WAS LANDING, THE PILOT NOTED THAT THE WHOLE RIGHT SIDE OF THE ENGINE WAS ON FIRE. THE RIGHT WING OF THE AIRCRAFT STRUCK A TREE AND THE AIRCRAFT CRASHED INTO THE CANAL. THE PILOT REPORTED THAT THERE WAS FIRE EVERYWHERE. HE JUMPED INTO THE CANAL AND SWAN AWAY FROM THE FIRE AND TO THE SHORE. AN INVESTIGATION REVEALED THE NO. 3 INTAKE PIPE, PN 75113, HAD SPLIT OPEN AT THE TOP. AN EXAMINATION OF THE FIRE DAMAGE INDICATED THAT THERE HAD BEEN A BLOW TORCH EFFECT COMING FROM THE AREA OF THE NO. 3 CYLINDER.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA82FKT09
Event ID
20020917X02412
Case number
MIA82FKT09
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: 67af3e752ac904d3d13f178673413825dd57aa4c2f128318ee134484991c7895; retrieved 2026-09-22T03:08:21.178Z.