FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02LA076 · Beech 95-B55

3 Feb 2002 · Joshua Tree, CA, United States

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

From Santa Monica Municipal Airport (SMO) to L80 · Joshua Tree, CA

Report a problem

Event

NTSB case
LAX02LA076
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
Unknown
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 95-B55

Aircraft type
Beechcraft 55
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
N9DD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Monica Municipal Airport (SMO), Santa Monica, CATo L80 · Joshua Tree, CA
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
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

  • Fluid, fuel › Starvation
  • Pilot in command › Fuel tank selector position, improper

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

NTSB narrative

The twin-engine airplane lost power in both engines while approaching the uncontrolled airport for landing and landed short of the runway in an unprepared field. The airplane was equipped with four fuel tanks; left main and left auxiliary tanks and right main and right auxiliary tanks. Two fuel quantity gauges indicated fuel quantity in either the main tanks or the auxiliary tanks based upon the position selected on a separate switch on the pilot's sub-panel. Approaching the airport the pilot completed the pre-landing checklist and confirmed the fuel selectors were on the main tanks. He had not changed the fuel selector valve handle positions since before takeoff, 45 minutes earlier, and believed he had been feeding fuel from the main tanks the entire flight. He turned on the fuel boost pumps to the "low" position and confirmed the fuel quantity gauge select switch was also set to indicate fuel quantity in the main tanks. As the airplane entered the landing pattern on crosswind leg, 1/2 to 1 mile from the departure end of the runway, the left engine began to "surge." The fuel gauges read 1/3 tank and the pilot, believing fuel supply was not the problem, elected to feather the left propeller and secure the left engine. Continuing the approach, the pilot extended the downwind leg and turned onto base leg about 1.5 miles from the landing runway threshold. As the airplane was turning onto final approach he lowered the landing gear and, as the gear was extending, the right engine began to surge. He then believed he did have a fuel starvation problem and attempted to unfeather and restart the left engine. The airplane was settling rapidly and he realized he wouldn't be able to reach the runway or restart the engines. He located a clearing beyond some houses and landed the airplane there. The person who recovered the wreckage reported draining 23 gallons of fuel from each main tank , 1/2-gallon from the left auxiliary tank and 1 cup of fuel from the right auxiliary tank. The fuel selector valve handles were in the main tank position and the fuel quantity gauge selector switch was in the main tank position. It is possible on this model airplane to select the fuel quantity gauges to indicate fuel quantity in the main tanks while the engines are, in fact, receiving fuel from the auxiliary tanks. Both engines were subsequently installed on a test stand and operated satisfactorily. No mechanical defects were noted on the airframe or engines.

Probable cause

The pilot's inadvertent missetting of the fuel selector position on the auxiliary fuel tanks (versus the main tanks) resulting in fuel starvation of the engines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02LA076
Event ID
20020206X00192
Case number
LAX02LA076
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: c6129fcac3fa0b58a344b7faa98b615d6782fd00aaaf5d8f7b1d8977f82968ce; retrieved 2026-09-22T11:08:32.315Z.