FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11FA125 · Beech 95-B55 (T42A)

7 Feb 2011 · San Bernardino, CA, United States

Beech 95-B55 (T42A) · Accident: fuel starvation on approach

From San Luis County Regional Airport (SBP) to San Bernardino International Airport (SBD)

Report a problem

Event

NTSB case
WPR11FA125
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 (T42A)

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
N225DH
Operator
Unknown
Onboard fatalities
Unknown
Route
From San Luis County Regional Airport (SBP), San Luis Obispo, CATo San Bernardino International Airport (SBD), San Bernardino, 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 · VFR go-around
Defining eventThe 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
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

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

During the initial climb, the landing gear warning horn sounded. The pilot diagnosed the problem and determined that the landing gear had retracted successfully and that the indication system was in error. He continued the flight with the horn intermittently sounding. During the descent phase, the pilot was given an unexpected direct route to the airport, and, as a result, he rushed through the descent checklist items. The pilot decided to perform a low pass over the arrival runway to confirm that the landing gear had extended. The pilot said that during the low pass he started to have difficulty controlling the airplane. An onboard engine monitoring system recorded a total loss of engine power to the right engine at that time. The pilot did not recognize that his difficulty in maintaining altitude and airplane control was a result of a loss of engine power to one engine; he subsequently lost control of the airplane, which collided with a storage facility in a nose-down inverted attitude. Witness reports, photographic evidence, and a postaccident examination revealed that the pilot did not retract the landing gear and flaps after the loss of power, as instructed in the airplane's operating instructions for a go-around with one engine inoperative.

The airplane's operating instructions recommend that the main fuel tanks be selected during descent and while landing. The pilot stated that he customarily uses the auxiliary fuel tanks during cruise flight and the main tanks while climbing and descending; however, both fuel selector valves were found in the auxiliary tank position at the accident site. The airplane's fuel tanks were serviced to capacity about 2.5 flight hours before the accident. Calculations of fuel consumption for the flights since the last fueling would have resulted in the use of a quantity of fuel that would have either been equal to or slightly exceeded the capacity of the auxiliary fuel tanks. Damage to the fuel system precluded an accurate assessment of the quantity and distribution of the remaining fuel onboard at the time of the accident. The engine monitoring system recorded a small rise in exhaust gas temperatures just before the loss of power; this rise is consistent with a lean fuel/air mixture, which would be present in a fuel starvation or exhaustion event. The postaccident examination did not reveal any anomalies with the airframe or engine that would have precluded normal operation.

The pilot's increased workload, due to the unexpected routing and possible problem with the landing gear, during the abbreviated final approach clearance and subsequent low pass could have resulted in a task overload, which resulted in his mismanagement of the fuel system during the landing phase.

Probable cause

The pilot did not recognize the loss of power in the right engine and did not execute the proper procedures for a go-around with one engine inoperative, likely due to increased workload. Contributing to the accident was the pilot's improper in-flight fuel management, which resulted in fuel starvation of the right engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11FA125
Event ID
20110207X62442
Case number
WPR11FA125
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 55f37c4f8204989a864456d879234fb9fb8695d770eeb35aa73eae2a532722d8; retrieved 2026-09-15T15:46:31.821Z.