FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA99FA245 · Beech B-90

3 Sept 1999 · West Palm Beach, FL, United States

Beech B-90 · Accident: total loss of engine power (non-mechanical) on approach

From Oakland County International Airport (PTK) to BCI · BOCA RATION, FL

Report a problem

Event

NTSB case
MIA99FA245
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
8 · 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 B-90

Aircraft type
Beechcraft B-90
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
N338AS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oakland County International Airport (PTK), Pontiac, MITo BCI · BOCA RATION, 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
Approach · VFR pattern final
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)
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
Fuel exhaustion; Wire, static; 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
Destroyed

Cause areas

  • Fluid, fuel › Exhaustion

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

NTSB narrative

At 0314, the pilot reported to the Air Traffic Control (ATC) Tower that he wanted to divert from his destination to land at a closer airport, and was cleared for a visual approach. At 0325, the pilot issued a "Mayday." On final approach the airplane struck a building and wires about 1/2 mile short of the runway. Witnesses that saw the airplane just before impact said that the airplane was low, there was no in-flight fire, and the engine sounds "...appeared to be a fluttering sound as if air [was] passing through the propeller." The pilot had filed for a cruise altitude of 15,000 feet, with a time en route of 5 hours, and fuel on board 6 hours. Weight and balance calculations showed that the pilot was operating about 722 pounds above the maximum gross weight for the takeoff, climb, and maximum cruise power settings. The Pilot Operating Handbook calculations showed that most of the fuel would have been used during the flight. The engine and propeller examinations revealed that both engines were not producing power at impact (windmilling). There were no discrepancies found with the engines or propellers. Examination of the propellers revealed that they were not in the feather position and they were not in beta/reverse position. Line personnel at the departure airport confirmed that all the tanks were topped off (282 gallons added). It took the flight 32 minutes to reach a cruise altitude of 15,000 feet, which calculated to about 293.3 pounds (1 gallon of Jet "A" equals 6.7 pounds), and a flight time of 4.9 hours from takeoff to impact. Sample calculations indicated that the fuel burn rate would have caused the airplane to use 2,649.3 pounds of Jet "A" turbine fuel during the flight. The flight departed with all tanks full 384 gallons usable (2,572.8 pounds), which calculates to insufficient fuel for the completion of the flight. Two gallons of fuel was drained from the right nacelle tank at the crash site, and there was no evidence of in-flight leakage. The sample calculations do not consider performance degradation for operating the airplane above the maximum allowable gross weight, which would cause the fuel consumption to go up because more power was required for the over weight conditions. The pilot's flight plan was for economy cruise, plus the airplane was over gross weight at takeoff, and there are no performance charts for that condition. So, the performance was even poorer than shown on the maximum power chart for climb and cruise. Calculations of the maximum allowable fuel that could be on board the aircraft showed that only 1851 pounds of turbine fuel could be carried to start the flight at the maximum allowable weight, or about 3.2 hours of flight. The en route winds aloft at the airplane's altitude indicated a slight tailwind for half the flight and a headwind of about 15 knots for the remainder of the flight.

Probable cause

a total loss of engine power due to fuel exhaustion. Contributing factors in this accident were the pilot's operation of the airplane in an overweight condition, inadequate pre-flight and in-flight planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA99FA245
Event ID
20001212X19819
Case number
MIA99FA245
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: 936030b78977478a4d8711baffdb73f6237b45c5f081305eca2be798aab87335; retrieved 2026-09-20T21:49:25.277Z.