FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX07FA049 · Beech B36TC

26 Nov 2006 · Buena Park, CA, United States

Beech B36TC · Accident: loss of engine power on approach

From Benton Field (O85) to Fullerton Municipal Airport (FUL)

Report a problem

Event

NTSB case
LAX07FA049
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 B36TC

Aircraft type
Beechcraft 36
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
N3144D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Benton Field (O85), Redding, CATo Fullerton Municipal Airport (FUL), Fullerton, 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 pattern downwind
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
Loss of engine power
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 management, inadequate
  • Pilot in command › Fuel supply, not selected
  • Pilot in command › Fuel tank selector position, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane experienced a loss of engine power and descended into a single family residence 0.3 miles from the destination airport. The pilot estimated a total flight time en route of 2 hours 38 minutes, with the total fuel on board equating to 4 hours 53 minutes. While in traffic pattern, the engine experienced a loss of power and the pilot declared an emergency. A witness stated that he noticed the accident airplane flying low and the propeller appeared as though it was not producing power. Fueling records at the departure airport disclosed that the aircraft was last fueled immediately prior to departure with the addition of 45 gallons of 100LL aviation fuel. According to the pilot, the addition of the fuel filled the aircraft tanks to a total of 90 gallons (45 in each tank). The fueler was contacted several days after the accident. He indicated that he did not fill each tank to the maximum capacity, rather he evenly distributed the 45 gallons of fuel to each side. Each wing's total fuel capacity was 54 gallons, of which 3 gallons were unusable. Each wing was equipped with a fuel quantity sight gage that reads within the calibrated area of 25 to 30 gallons. The right wing was impact damaged with numerous perforations. The inboard fuel bladder was drained via the bottom sump and found to have about 1 gallon of fuel. The left wing was separated from the fuselage. Removal of the inspection panels on the left wing revealed that the fuel bladders were intact. There appeared to be only several ounces of fuel within the outboard bladder; no other fluid was found in the left wing. The fuel selector was found in the "OFF" position and had been turned to OFF by a first responder. The engine was examined and test run; no mechanical malfunctions or failures were found with the engine that would have precluded it from operating normally. The non-volatile memory of an engine data management system revealed that the accident flight encompassed a duration of 3.66 hours. The total fuel used during the last flight was 64.3 gallons. Shortly before the accident, the engine's fuel flow dropped from 15.9 to 7.1 gallons per hour. Thereafter, the fuel flow was between .3 and 6.2 gallons per hour. The battery voltage remained fairly constant, consistent with the electrical system operating normally. The pre-crash integrity of the fuel system could not be verified due to the extent of airplane damage incurred during the accident.

Probable cause

a fuel starvation induced loss of engine power due to pilot's inadequate fuel system management.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07FA049
Event ID
20061204X01729
Case number
LAX07FA049
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2006-11-27.
  • API snapshot SHA-256: f565907cf4934484eee97107193c642a43248079781f8f865c7c040f962e0abe; retrieved 2026-09-21T08:52:31.888Z.