FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW06CA176 · Cessna 210A

7 Jul 2006 · Denver City, TX, United States

Cessna 210A · Accident: loss of engine power on approach

From Tulsa Riverside Airport (RVS) to Denver City Airport (E57)

Report a problem

Event

NTSB case
DFW06CA176
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 210A

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
N9419X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tulsa Riverside Airport (RVS), Tulsa, OKTo Denver City Airport (E57), Denver City, TX
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
Approach · VFR pattern final
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
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

  • Reason for occurrence undetermined

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

NTSB narrative

A 2,350-hour commercial pilot completed a 393-nautical mile cross-country flight, and was preparing to land at his destination airport when he experienced a total loss of engine power while on final approach. The single-engine airplane landed short of the 3,960-foot long runway, slid, and came to rest about 100 feet short of the runway threshold. An FAA inspector, who examined the airplane, reported that the engine firewall was wrinkled and confirmed that there was fuel present in the left fuel tank. He added that witnesses reported observing fuel draining from the right wing after the accident. The pilot reported that the power loss was the result of a faulty fuel pump. Examination of the fuel pump and engine by an airframe and power plant mechanic did not reveal any anomalies or mechanical deficiencies. The reason for the loss of engine power could not be determined.

Probable cause

The loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW06CA176
Event ID
20060809X01117
Case number
DFW06CA176
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, 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: 4e06cecdb48055f61e0cb6004c9d6d8dd46a1796a2efb80d2838d85a6cb71f85; retrieved 2026-09-22T04:41:47.381Z.