FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA068 · Cessna T210L

14 Jan 2005 · Yuba City, CA, United States

Cessna T210L · Accident: total loss of engine power (non-mechanical) en route

From Chico Regional Airport (CIC) to Sutter County Airport (O52)

Report a problem

Event

NTSB case
LAX05LA068
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 T210L

Aircraft type
Cessna 210
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
N5177V
Operator
Doug Snider
Onboard fatalities
Unknown
Route
From Chico Regional Airport (CIC), Chico, CATo Sutter County Airport (O52), Yuba City, 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

  • Fluid, fuel › Exhaustion
  • Pilot in command › Fuel supply, not verified
  • Pilot in command › Preflight planning/preparation, inadequate
  • Pilot in command › Refueling, not performed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During a 20-minute flight, the engine lost power due to fuel exhaustion, and the pilot forced landed the airplane in a river. Prior to departure, the pilot noted that the left fuel tank gauge indicated less than 1/4 tank and the right fuel tank gauge indicated 1/4 tank of fuel. The pilot did not visually verify the fuel quantity in the tanks and departed using the right tank. The pilot climbed the airplane to 5,500 feet mean seal level and set the manifold pressure and rpm at 25 inches and 2,500 rpm, respectively. He then leaned the mixture to 30 degrees, lean of peak. During cruise flight, the pilot felt a drop in power and noticed a fluctuating fuel flow indication and almost 1/4 tank of fuel indicated on the right gauge. He switched to the left fuel tank, power was restored, and the fuel flow stabilized. While approaching to land at the nearest airport, the pilot extended the gear and set the flaps to the approach setting. Then, the engine began to lose power again and the fuel flow was fluctuating. He applied a full rich mixture, full forward on the throttle and the propeller. He also switched the fuel selector to the right tank and pitched the airplane's attitude for best glide speed. Because the airplane was about 1,500 feet above ground level and nearing the approach end of the runway, the pilot elected to perform a 360-degree turn in order to dissipate the airplane's altitude. As the airplane came through 270 degrees, he noted that the airplane was too low to land on the runway. After assessing his other landing options, the pilot elected to land the airplane in the river. He raised the gear and slowed the airplane to 80 miles per hour. Upon landing, the pilot egressed the airplane and swam to shore. The pilot felt that he should not have departed without refueling the airplane. The airplane had accumulated about 5 1/2 hours since its last refueling. The pilot said that he was planning on obtaining fuel from another airport in his city; however, a family member called requesting a ride from a nearby airport and he decided to refuel there instead. Performance calculations indicated that the usable fuel level would have been nearly depleted based on the flight profiles and times since the last refueling of the airplane.

Probable cause

the pilot's inadequate preflight preparation and failure to verify the fuel supply, which resulted in fuel exhaustion and subsequent loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA068
Event ID
20050209X00161
Case number
LAX05LA068
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-01-15.
  • API snapshot SHA-256: ec1906f6a4e79e6fb4d164b3920f09b806dd4496eced2a49277a342b8b6bf351; retrieved 2026-09-22T06:21:59.772Z.