FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA90LA157 · Boeing B75N1

21 Jul 1990 · Plant City, FL, United States

Boeing B75N1 · Accident: loss of engine power during initial climb

Report a problem

Event

NTSB case
MIA90LA157
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

Boeing B75N1

Aircraft type
Boeing B75
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
N4429N
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
Initial climb
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

  • Reason for occurrence undetermined

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

NTSB narrative

THE ACFT HAD BEEN FLOWN FOR ABOUT 20 MINUTES PRIOR TO THE ACCIDENT FLT WITH NO PROBLEM. WITH ABOUT 20 GALS OF FUEL ABOARD, THE PLT PREFLIGHTED THE ACFT FOR THE NEXT FLT BUT DID NOT CHECK THE FUEL SYSTEM FOR CONTAMINANTS. THE ENG RUN-UP PRIOR TO DEPARTURE WAS NORMAL. SHORTLY AFTER TAKEOFF AT AN ALT OF ABOUT 300 FT, AFTER THE INITIAL POWER REDUCTION, THE ENG QUIT. UNABLE TO RETURN TO THE ARPT, THE PLT LANDED THE ACFT IN A FIELD, DURING WHICH, IT COLLIDED WITH A FENCE & DITCH. THE COLLISION WITH THE DITCH COLLAPSED THE LANDING GEAR. EXAM OF THE ENG REVEALED NO EVIDENCE OF CATASTROPHIC FAILURE OR MALFUNCTION. THE FUEL WAS TESTED FOR CONTAMINANTS. NONE WERE FOUND. NO FURTHER EXAM WAS CONDUCTED; THEREFORE, NO DETERMINATION COULD BE MADE AS TO THE REASON FOR THE LOSS OF ENG POWER.

Probable cause

ENGINE FAILURE FOR UNDETERMINED REASONS RESULTING IN THE FORCED LANDING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA90LA157
Event ID
20001212X23764
Case number
MIA90LA157
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: c5538d8f9eb5ed338ec85b6e9eaf8fdd8e1daa090269569e30f3759ada6b61b8; retrieved 2026-09-23T05:33:01.577Z.