FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA003 · Piper PA-30

8 Oct 2002 · Immokalee, FL, United States

Piper PA-30 · Accident: loss of engine power during takeoff

From Immokalee Regional Airport (KIMM) to Fort Lauderdale Executive Airport (KFXE)

Report a problem

Event

NTSB case
MIA03LA003
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-30

Aircraft type
Piper PA-30
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
N7014Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Immokalee Regional Airport (KIMM), Immokalee, FLTo Fort Lauderdale Executive Airport (KFXE), 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
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
Loss of engine power
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

After the fourth touch and go landing, the student applied full power, and accelerated to takeoff. Just after liftoff and at an altitude of about 20 to 30 feet above the ground, the instructor pilot said the airplane's left engine lost power. The airplane veered left, the takeoff was aborted, the airplane departed the runway, and impacted with shrubs. Both pilots stated that although this was a training flight, simulated engine out procedures were not in progress at the time of the engine power loss. The left engine and propeller were placed on a test stand to facilitate a test run. The run was conducted with all of the engine's original parts. The engine and propeller were run with no discrepancies noted.

Probable cause

A loss of engine power on takeoff for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA003
Event ID
20021010X05314
Case number
MIA03LA003
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: fd106bc5282dceca50e33c99fe46ad9fe785558f9c0960e663aee98b25b6f7f7; retrieved 2026-09-22T10:07:22.758Z.