LAX93LA268 · Cessna 172
Tradewinds Aviation Cessna 172 · Accident: total loss of engine power (non-mechanical) en route
From Watts Woodland Airport (O41) to Mineta San Jose International Airport (SJC)
Event
- NTSB case
- LAX93LA268
- 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 172
- Aircraft type
- Cessna 172
- 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
- N2791U
- Operator
- Tradewinds Aviation
- Onboard fatalities
- Unknown
- Route
- From Watts Woodland Airport (O41), Woodland, CATo Mineta San Jose International Airport (SJC), San Jose, 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
- 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
- Pilot in command › Fuel consumption calculations, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
BEFORE DEPARTING ON THE ACCIDENT FLIGHT THE PILOT REPORTED THAT THE FUEL TANKS WERE FULL AND CALCULATED THE TOTAL FUEL ON BOARD WAS EQUIVALENT TO 4.2 HOURS. THE INVESTIGATION REVEALED THAT SINCE THE LAST REFUELING, THE AIRPLANE FLEW 0.8 HOURS. THE PILOT FLEW TO TWO DIFFERENT AIRPORTS BEFORE RETURNING TO THE HOME BASE. HE ALSO PERFORMED TWO OR THREE TAKEOFFS AND LANDINGS AT THE ITINERARY AIRPORTS. ABOUT 30 MINUTES AFTER DEPARTING THE LAST ITINERARY AIRPORT THE ENGINE SUSTAINED A TOTAL LOSS OF POWER. THE AIRPLANE COLLIDED WITH A VEHICLE DURING THE ENSUING EMERGENCY LANDING. THE WRECKAGE EXAMINATION DISCLOSED THE AIRPLANE CONTAINED ABOUT 1 3/4 GALLONS OF FUEL IN THE LEFT WING TANK. THE RIGHT WING TANK WAS EMPTY.
Probable cause
THE PILOT'S POOR FUEL CONSUMPTION CALCULATIONS. CONTRIBUTING TO THIS ACCIDENT WAS THE DOWNSLOPING TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA268
- Event ID
- 20001211X12664
- Case number
- LAX93LA268
- 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: 987468299c02cde5908bfd4f0589d6b8fae7efb3b2b11cf1438705b2467617ef; retrieved 2026-09-21T22:54:14.557Z.