LAX97LA020 · Beech S35
Beech S35 · Accident: total loss of engine power (non-mechanical) on approach
From Jacqueline Cochran Regional Airport (TRM) to Palo Alto Airport (PAO)
Event
- NTSB case
- LAX97LA020
- 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 S35
- Aircraft type
- Beechcraft 35
- 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
- N5642K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jacqueline Cochran Regional Airport (TRM), Thermal, CATo Palo Alto Airport (PAO)
- 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
- 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 pilot reported that he calculated that 60 gallons of fuel were onboard his airplane before taking off on the flight, and that fuel was located in the main and auxiliary tanks. En route, the pilot transferred all of the fuel from the tip tanks into the main tanks, and alternated using fuel from the main tanks. The pilot additionally reported that approaching Palo Alto, he repositioned the fuel selector toward the fullest tank. On final approach, all engine power was lost, and the pilot made a forced landing in a marsh area of the San Francisco Bay. The FAA coordinator reported that during examination of the airplane and surrounding marshland, no evidence of any oil or fuel leakage was found. The airplane was recovered, and its fuel tanks were found intact. The quantity of fuel observed in the left wing tip tank and the left main tank was 0.25 and 11.0 gallons, respectively. The quantity of fuel observed in the right wing tip tank and the right main tank was 0.75 and 0.50 gallons, respectively. During examination of the engine, no evidence of preimpact damage was found, and the engine was successfully test run.
Probable cause
fuel starvation, due to the pilot's improper positioning of the fuel tank selector to an empty tank. Swampy terrain in the emergency landing area was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA020
- Event ID
- 20001208X06929
- Case number
- LAX97LA020
- 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: b059deef69aec70d0d79ccb233930d3e6801db048ec515c0ed20c40b35156cbc; retrieved 2026-09-22T20:56:34.259Z.