FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA91LA044 · Beech F33A

15 Dec 1990 · Lakeland, FL, United States

Globe Aero Beech F33A · Accident: total loss of engine power (non-mechanical) en route

From an unrecorded airport to Bangor International Airport (BGR)

Report a problem

Event

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

Beech F33A

Aircraft type
Beechcraft 33
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
N81562
Operator
Globe Aero
Onboard fatalities
Unknown
Route
From not recordedTo Bangor International Airport (BGR), Bangor, ME
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 · 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
Total loss of engine power (non-mechanical)
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, piston › Seized
  • Fluid, oil › Exhaustion

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

NTSB narrative

BEFORE DEPARTURE, THE PLT PREFLIGHTED THE ACFT & PERFORMED AN ENG RUN-UP WITH NO DISCREPANCIES NOTED. AFTER DEPARTURE WHILE CLIMBING THROUGH 5,500 FT, THE ENG QUIT. THE PLT RESTARTED THE ENG BUT OBSERVED THE OIL PRESSURE WAS ZERO. THE ENG QUIT AGAIN & HE WAS UNABLE TO RESTART IT. DURING THE FORCED LANDING IN A FIELD, THE ACFT COLLIDED WITH A TREE. EXAM OF THE ACFT REVEALED OIL COATING THE BOTTOM OF THE FUSELAGE. THE ENG COMPARTMENT WAS NOT CONTAMINATED. THE ENG WAS REMOVED & EXAM OF IT REVEALED THAT THE NO'S 1,2,5, & 6 PISTONS SCORED THE CYLINDER WALLS. NO'S 3 & 4 PISTONS WERE NORMAL. DUE TO THE DAMAGE, NO DIMENSIONAL ANALYSIS OF THE FAILED PISTONS & CYLINDERS COULD BE MADE. THE ENG DRIVEN OIL PUMP WAS EXAM & FOUND TO BE FREE OF FAILURE OR MALFUNCTION. NO DETERMINATION COULD BE MADE AS TO THE REASONS FOR THE LOSS OF ENG OIL RESULTING IN THE TOTAL LOSS OF ENG POWER DUE TO SEIZURE OF THE NO'S 1,2,5, & 6 PISTONS IN THE CYLINDERS. THE ACFT & ENG HAD ACCUMULATED 16.1 HRS SINCE MANUFACTURE.

Probable cause

TOTAL LOSS OF ENGINE POWER DUE TO OIL EXHAUSTION FOR UNDETERMINED REASONS. THIS CAUSED THE PISTONS TO SEIZE IN THE CYLINDERS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA91LA044
Event ID
20001212X24790
Case number
MIA91LA044
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: f168516a6a13ef319d9fe48abf5bbcc1298f55d81d87b6c4f5b36cd38ef2543f; retrieved 2026-09-23T05:01:48.525Z.