FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI90LA227 · Beech BE 95

12 Aug 1990 · Faribault, MN, United States

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

From South Bend International Airport (SBN) to an unrecorded destination

Report a problem

Event

NTSB case
CHI90LA227
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 BE 95

Aircraft type
Beechcraft BE-95
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
N9906R
Operator
Unknown
Onboard fatalities
Unknown
Route
From South Bend International Airport (SBN), South Bend, INTo 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
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 starvation
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

  • Pilot in command › Emergency procedure, improper
  • Pilot in command › In-flight planning/decision, improper

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

NTSB narrative

THE TWIN-ENGINE AIRPLANE LOST RIGHT ENGINE POWER AT 200 FEET ON FINAL APPROACH. THE PILOT RETRACTED LANDING GEAR AND ATTEMPTED TO GO AROUND SINGLE ENGINE. THE AIRPLANE STRUCK GROUND WITH ITS RIGHT WINGTIP AND CARTWHEELED. PILOT STATED HE EXPERIENCED LATERAL CONTROL DIFFICULTY. NO MECHANICAL DISCREPANCY WAS FOUND WITH FLIGHT CONTROLS, RIGHT ENGINE OR FUEL SYSTEM. AUXILLIARY FUEL CELLS CONTAINED 3.2 GALLONS RIGHT AND 0.4 GALLONS LEFT. THE AIRPLANE OWNER'S MANUAL STATES AUXILLIARY TANK FUEL BELOW 3 GALLONS ON EITHER SIDE IS UNUSEABLE. MAIN FUEL TANKS WERE FULL. THE FUEL QUANTITY GAGE SELECTOR WAS FOUND IN THE AUX POSITION. THE PILOT STATED HE TURNED THE FUEL TANK SELECTOR OFF AFTER THE CRASH BUT HAD SELECTED MAIN TANKS PRIOR TO LANDING.

Probable cause

THE PILOT'S IMPROPER INFLIGHT DECISION AND HIS IMPROPER EXECUTION OF THE CHOSEN EMERGENCY PROCEDURE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI90LA227
Event ID
20001212X23949
Case number
CHI90LA227
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: 77f9b585ecf4d91ec892ef304ec1f23a2fd71238ec150926f83245843bc5abbb; retrieved 2026-09-21T23:46:27.794Z.