LAX96LA302 · Beech B23
Beech B23 · Accident: total loss of engine power (non-mechanical) on approach
From Santa Monica Municipal Airport (SMO) to Modesto City Co-Harry Sham Field (MOD)
Event
- NTSB case
- LAX96LA302
- 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 B23
- Aircraft type
- Beechcraft 23
- 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
- N6087N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Modesto City Co-Harry Sham Field (MOD)
- 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
- 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; Wire, transmission
- 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 › Starvation
- Pilot in command › Fuel management, inadequate
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the two 28.8 gallon capacity fuel tanks were both full upon takeoff for her participation in the Palms-to-Pines air race. After flying for 2:10 hours the pilot arrived at Modesto, and she made a low pass over the field for timing purposes. During the go-around, all engine power was suddenly lost and the pilot attempted to land on a street. On approach, the airplane collided with power lines. The airplane impacted the street, and a fuel-fed fire erupted as the airplane slid to a stop. The pilot reported that she anticipated the fuel burn off rate during the flight was about 11.9 gallons per hour. She did not recall switching fuel tanks during the flight. No mechanical malfunctions were found during the postimpact engine examination.
Probable cause
fuel starvation due to the pilot's inadequate fuel management and failure to reposition the fuel selector to a tank containing adequate fuel. The power lines were a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA302
- Event ID
- 20001208X06549
- Case number
- LAX96LA302
- 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: 76bcc54341849517021409357b2bb47717705d2862d23d6ece173acf6f3b7e2e; retrieved 2026-09-22T21:32:19.650Z.