DEN85LA058 · Cessna 210B
Cessna 210B · Accident: loss of engine power en route
From Rialto, CA to Carlsbad, NM
Event
- NTSB case
- DEN85LA058
- 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
- 0
- 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 210B
- 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
- N101PQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rialto, CATo Carlsbad, NM
- 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
- Loss of engine power
- 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 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
- Bleed air system, valve › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PLT STATED THAT DURING THE FLT THE RT FUEL TANK WAS USED UNTIL EMPTY AT WHICH TIME THE LEFT TANK WAS SELECTED. APRX 20 MINUTES AFTER SWITCHING TANKS AND 2 HRS 35 MINUTES AFTER DEPARTURE, THE ENGINE BACKFIRED AND SUBSEQUENTLY QUIT. A FORCED LANDING WAS MADE DURING WHICH TIME ACFT NOSED DOWN AFTER CONTACTING A SAND DOME. INVESTIGATION REVEALED THAT DURING THE 4 MONTHS WHICH THE PLT OWNED THE ACFT HE HAD TO HAVE THE FUEL SYSTEM CLEANED TWICE BECAUSE OF SEDIMENT. INSPECTION OF THE ACFT DISCLOSED SEDIMENT IN THE FUEL PUMPS AND SADDLE TANKS. THE SEDIMENT WAS CLEANED OUT AND THE ENGINE WOULD NOT RUN LONGER THEN APRX 2 MINUTES ON EITHER TANK. THE FUEL SYSTEM WAS THOROUGHLY CHECKED AND THE ONLY DISCREPANCY NOTED WAS EXCESSIVE PLAY IN THE FUEL SELECTOR VALVE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN85LA058
- Event ID
- 20001214X35504
- Case number
- DEN85LA058
- 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: 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: 172ba3870abf9212de0507773c1ebb4526bf7fdf7ce04049baaa318be5ec49d2; retrieved 2026-09-22T02:00:57.986Z.