MIA86LA154 · Piper PA-38-112
Phoenix East Aviation Piper PA-38-112 · Accident: loss of engine power en route
From Page Field (FMY) to Daytona Beach International Airport (DAB)
Event
- NTSB case
- MIA86LA154
- 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-38-112
- Aircraft type
- Piper PA-38
- 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
- N4374E
- Operator
- Phoenix East Aviation
- Onboard fatalities
- Unknown
- Route
- From Page Field (FMY), Fort Myers, FLTo Daytona Beach International Airport (DAB), Daytona Beach, 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
- Loss of engine power
- 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
- Wire, static
- 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
- Engine assembly › Undetermined
Approximate · Estimated position: the centre of Daytona Beach, FL, the place the record names. Not the accident site.
NTSB narrative
FLT EXPERIENCED ENGINE FAILURE WHILE DESCENDING FOR LANDING. WHILE APPROACHING A FIELD FOR A FORCED LANDING THE AIRCRAFT STRUCK ELECTRICAL POWER LINES AND THEN CRASHED INTO THE FIELD. THE ENGINE WAS OPERATED TO FULL POWER AFTER THE ACCIDENT WITH NO EVIDENCE OF PRECRASH MECHANICAL FAILURE OR MALFUNCTION. POST CRASH CALCULATIONS REVEALED THE AIRCRAFT SHOULD HAVE HAD 12 GALLONS OF FUEL ONBOARD AT THE TIME OF THE ACCIDENT. THE AIRCRAFT WAS OPERATION UNDER CONDITIONS CONDUCIVE TO SERIOUS CARBURETOR ICING AT GLIDE POWER HOWEVER THE PILOT STATED CARBURETOR HEAT WAS USED THROUGHOUT THE DESCENT. POST CRASH EXAMINATION OF THE CARBURETOR HEAT SYSTEM REVEALED IT TO BE INTACT WITH NO EVIDENCE OF MALFUNCTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA86LA154
- Event ID
- 20001213X33626
- Case number
- MIA86LA154
- 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: 50cf0945f6e0aa31390d4726a49ed32908d49bf7e00d8f9f4c665b46441faf7a; retrieved 2026-09-22T01:26:30.160Z.