LAX89LA228 · Cessna 150
Cessna 150 · Accident: total loss of engine power (non-mechanical) en route
From Lampson Field (1O2) to 1O2
Event
- NTSB case
- LAX89LA228
- 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
Cessna 150
- Aircraft type
- Cessna 150
- 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
- N5712E
- Operator
- Tom Watson
- Onboard fatalities
- Unknown
- Route
- From Lampson Field (1O2), Lakeport, CATo 1O2
- 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
- En route · cruise
- 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 exhaustion
- 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 › Exhaustion
- Pilot in command › Fuel consumption calculations, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT SAID HE CHECKED THE FUEL TANKS BY DIPPING THEM AND VISUALLY LOOKING IN THEM. HE DETERMINED HE HAD 6 TO 7 GALLONS, THAT HE THOUGHT WOULD BE GOOD FOR APPROXIMATELY AN HOUR OR MORE. THE AIRPLANE DEPARTED ON THE FLIGHT AT 2008 PDT AND CRASHED AT 2050 PDT. THE PILOT SAID THE ENGINE STARTED TO SPUTTER AND HE WAS UNABLE TO CORRECT THE ENGINE PROBLEM SO HE MADE A FORCED LANDING IN A PASTURE. DURING THE ROLLOUT, THE LEFT WING IMPACTED A FENCE POST. POST ACCIDENT INSPECTION INDICATED NO FUEL IN THE RIGHT FUEL TANK AND APPROXIMATELY 2 GALLONS OF FUEL IN THE LEFT FUEL TANK. A CONSERVATION FUEL CONSUMPTION FIGURE FOR THIS TYPE FLIGHT IS FIVE GPH ACCORDING TO THE FLIGHT MANUAL. THE FLIGHT MANUAL ALSO LISTS THE LAST 3 TO 3.5 GALLONS OF FUEL AS UNUSABLE.
Probable cause
INADEQUATE PREFLIGHT PLANNING/PREPARATIONS AND THE IMPROPER FUEL CONSUMPTION CALCULATIONS BY THE PILOT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89LA228
- Event ID
- 20001213X28860
- Case number
- LAX89LA228
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-07-02.
- API snapshot SHA-256: 608c2a0185e2dc6a238b3b3806ab604d793f2ab60b876e1ec8550c5e505588cf; retrieved 2026-09-23T07:26:34.237Z.