WPR14LA056 · Cessna T210 - F
Cessna T210 - F · Accident: fuel exhaustion en route
From Gillespie Field (SEE) to Jack Northrop Field Hawthorne Municipal Airport (HHR)
Event
- NTSB case
- WPR14LA056
- 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 T210 - F
- 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
- N6186R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gillespie Field (SEE), San Diego, CATo Jack Northrop Field Hawthorne Municipal Airport (HHR), Hawthorne, CA
- Aircraft age
- About 47 years (built 1966)
- 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 · climb to cruise
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On the morning of the accident, the owner/pilot determined that the airplane had about 18 (out of a total capacity of 65) gallons of fuel on board by referring to the installed fuel totalizer, which calculated the fuel remaining using a pilot-entered initial fuel quantity and a sensed fuel flow rate. As was his habit, he relied solely on the fuel totalizer indication and did not verify fuel quantity by looking in or "sticking" the fuel tanks or using the airplane's fuel quantity gauges. The pilot, with one passenger onboard flew to an airport about 20 miles away to pick up another passenger and then flew to a third airport about 26 miles away, where the pilot purchased about 15 to 20 gallons of fuel. The pilot and passengers then flew to and landed at three other airports, with a cumulative straight-line distance of about 110 additional miles. Although it was available, no fuel was purchased at any of the three airports. After dark, the pilot and passengers departed for the home airport about 100 miles away. About 15 minutes after takeoff, when the airplane was at an altitude of about 3,500 ft, the engine "sputtered," and the pilot determined that the right tank was empty. He switched to the left tank, which he believed contained about 18 gallons of fuel. Shortly thereafter, the engine sustained a complete loss of power. The pilot turned the airplane toward the nearest GPS-indicated airport, which was a military facility. Although he attempted to contact air traffic control tower personnel, the tower was not operating at the time. The runway lights came on while the airplane was still airborne but too late to allow the pilot to align the airplane with the runway. The airplane touched down on a ramp area, crossed into an unpaved area, and struck a berm.
Postaccident examination recovered a total of about 2.5 gallons of fuel from the undamaged fuel tanks; the manufacturer's information indicated that each of the two fuel tanks had an unusable fuel quantity of 2.5 gallons. Using the pilot's estimates of the fuel on board at the beginning of the day and the fuel purchased en route, the pilot had flown at least 250 miles and conducted 6 takeoffs on 33 to 38 gallons of fuel. Review of the airplane manufacturer's performance data indicated that a minimum of about 36 to 40 gallons would have been required and that the actual required quantity could have been significantly greater than that, depending on power settings, engine leaning, and actual flight times and distances.
Probable cause
The pilot's failure to determine the actual onboard fuel quantity before beginning the flight, which resulted in a complete loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot's habitual reliance solely on the cockpit fuel flow/totalizer unit to determine fuel quantity rather than measuring the actual amount.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14LA056
- Event ID
- 20131121X72932
- Case number
- WPR14LA056
- 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 2013-11-17.
- API snapshot SHA-256: bc7fb185ddb1ffeb23da0e2e00dd2cf581637a34764a25fbcb063caf307c350a; retrieved 2026-09-15T23:08:18.892Z.