WPR11FA002 · Cessna 310
Cessna 310 · Accident: fuel starvation during initial climb
From Catalina Airport (AVX) to San Luis County Regional Airport (SBP)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR11FA002
- 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
- Instrument Meteorological Cond
Cessna 310
- Aircraft type
- Cessna 310
- 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
- N310XX
- Operator
- Sabovich and Sons
- Onboard fatalities
- Unknown
- Route
- From Catalina Airport (AVX), Avalon, CATo San Luis County Regional Airport (SBP), San Luis Obispo, 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
- Initial climb
- 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 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The non-instrument rated owner/pilot of the twin engine airplane dropped off his two passengers on the island and then flew to the mainland, where he remained overnight. The next day he returned to the island a few hours late due to weather on the mainland, and he and his friends ate lunch. While dining, the pilot noticed that the weather was deteriorating rapidly and suggested that they depart before instrument meteorological conditions prevailed. After boarding the airplane and starting the engine, the pilot conducted an abbreviated engine run-up during the taxi. The takeoff roll was normal, but about 2 to 3 seconds after liftoff, the left engine failed, and the airplane veered to the left. The pilot pushed the nose down to maintain airspeed, and the airplane entered a cloud/fog bank, impacted terrain, and was engulfed by fire.
Postaccident examination of the left engine and propeller did not reveal any mechanical malfunctions or failures that would have precluded normal operation. On scene, the fuel selector valve for the left engine was found set between "OFF" and its normal takeoff setting. The mechanical configuration of the selector valve and linkage made it unlikely that the valve setting was altered by impact forces, particularly since the surrounding airplane structure remained intact. The left engine was tested at the engine manufacturer's facility where it operated normally and developed full-rated takeoff power. Testing of the left fuel selector valve revealed that, in its as-found position, it was incapable of delivering the required fuel flow to the engine at takeoff power. The pilot stated that it was his habit to shut off both fuel selector valves after each flight and that he did so after the previous landing. Residual fuel in the lines, gascolator, and carburetor, combined with the limited flow capability of the mis-set selector valve, permitted the engine to be started and operated normally at low rpm. However, the high fuel flow demand of the engine operating at full power could not be maintained by the mis-set valve, and the engine failed in the initial climb due to fuel starvation.
The pilot's decision to attempt the departure with the rapidly deteriorating weather caused him to hasten his activities. Had the pilot not been in a rush, it is likely that he would have properly set the left engine fuel selector valve. He also would have conducted a full and/or longer engine run-up, which would have failed the engine before the takeoff attempt if he hadn’t properly reset the left engine fuel selector valve. While the pilot took the initiative to create a personal checklist, he missed the opportunity to improve upon the existing manufacturer's checklist. The pilot's personal checklist appeared visually and functionally inferior to the manufacturer's checklist, and it did not include any double checks of such flight-critical items as fuel selector valve position.
Probable cause
The pilot's improper setting of the left engine fuel selector valve, which resulted in fuel starvation of the left engine immediately after takeoff. Contributing to the accident was the pilot's decision to try to depart ahead of developing weather, which resulted in his hastened departure procedures and likely led to his failure to recognize the incorrect fuel selector positioning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11FA002
- Event ID
- 20101003X04946
- Case number
- WPR11FA002
- 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: investigation status, coordinates. 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: 55f8d12b1144364dd9906bf890dad8b59368d264145cbc580e08c04099319db7; retrieved 2026-09-15T15:26:40.397Z.