WPR11LA254 · Cessna 177
Cessna 177 · Accident: fuel exhaustion en route
From San Luis County Regional Airport (SBP) to Van Nuys Airport (VNY)
Event
- NTSB case
- WPR11LA254
- 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
Cessna 177
- Aircraft type
- Cessna 177
- 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
- N2301Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Luis County Regional Airport (SBP), San Luis Obispo, CATo Van Nuys Airport (VNY), Van Nuys, 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 · descent
- Defining eventThe 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
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to the flight, the pilot visually checked the fuel quantity in the fuel tanks and the left fuel tank fuel quantity was within one inch from the filler neck, and the right fuel tank appeared to be half full. As the flight neared the area of the accident site, both the pilot and passenger observed the right fuel gauge indicate zero, followed by the left. While attempting to maneuver around clouds to descend to an airport the pilot saw beneath the clouds, the engine started to sputter. The pilot switched the fuel selector from the both position to the left fuel tank and the engine stopped almost immediately. He then switched to the right fuel tank, but the engine did not restart. The pilot initiated a forced landing onto a road, which resulted in substantial damage to the airplane's wings and horizontal stabilizer. A postaccident examination of the airframe and engine by a Federal Aviation Administration (FAA) Inspector revealed no fuel in either fuel tank and about 1/2 cup of fuel was drained from the fuel strainer. The FAA inspector also observed a placard on the instrument panel which stated "... [the] Tuned Exhaust System installed on this aircraft may cause the aircraft to burn more fuel at certain power settings. It is the Pilot's responsibility to determine what, if any, change in fuel flow exists and to plan accordingly."
Probable cause
The pilot's inadequate preflight verification of the fuel quantity and his inadequate fuel consumption calculations, which resulted in fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA254
- Event ID
- 20110608X23151
- Case number
- WPR11LA254
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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 2011-06-09.
- API snapshot SHA-256: 548795f40f15294057f814dd8baa6ed8116b801033131e8cc3622571e2e8a543; retrieved 2026-09-15T16:15:41.793Z.