WPR09LA214 · Cessna T210M
Cessna T210M · Accident: fuel starvation en route
From North Las Vegas Airport (KVGT) to Nut Tree Airport (KVCB)
Event
- NTSB case
- WPR09LA214
- 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 T210M
- 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
- N6584B
- Operator
- Preston Donald S
- Onboard fatalities
- Unknown
- Route
- From North Las Vegas Airport (KVGT), North Las Vegas, NVTo Nut Tree Airport (KVCB), Vacaville, 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 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While the pilot was descending toward an alternate airport because his fuel level was becoming lower than he was comfortable with, the airplane experienced a total loss of engine power because the selected fuel tank ran dry. Although he tried to restart the engine, the pilot failed to switch tanks during the restart attempt and was therefore unsuccessful. He ultimately made a forced landing in an open field with rough terrain, and one wing came in contact with the surface during the landing roll. It was later determined that the other fuel tank contained about eight gallons of fuel. It was also determined that the pilot had been using the fuel flow charts provided with the airplane at the time of manufacture, instead of the updated charts that should have been used after the engine underwent a Supplemental Type Certificate (STC) performance modification that resulted in higher fuel flows.
Probable cause
A loss of engine power during descent due to fuel starvation as a result of the pilot's improper fuel management. Contributing to the accident was the pilot's failure to use the correct fuel flow performance chart.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA214
- Event ID
- 20090424X12414
- Case number
- WPR09LA214
- 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. 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: 6eb749a74d8c4a46290371326651f79bb4a5a910cadd3e133f1c74b86f102575; retrieved 2026-09-15T10:58:48.065Z.