WPR17LA090 · Cessna T210N N
Cessna T210N N · Accident: loss of engine power (total) en route
From Deming Municipal Airport (DMN) to Corona Municipal Airport (AJO)
Event
- NTSB case
- WPR17LA090
- 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 T210N N
- 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
- N6218Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Deming Municipal Airport (DMN), Deming, NMTo Corona Municipal Airport (AJO), Corona, CA
- Aircraft age
- About 36 years (built 1981)
- 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
- 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
- Loss of engine power (total)
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a flight from New Mexico to California in the single engine airplane. About 35 miles short of his destination, in day visual meteorological conditions, the pilot reported that the engine experienced a power problem, and he then attempted to land at a nearby airport. The airport attendant reported hearing the pilot announce over the common traffic advisory frequency that the airplane had experienced a "massive power failure." He saw the airplane on the right downwind leg of the traffic pattern, and again on final, and both times he thought that it was positioned for a normal landing. Shortly thereafter, he saw a cloud of dust near the end of the runway. The airplane touched down about 180 ft short of the runway and sustained substantial damage.
The pilot was initially detained by law enforcement personnel, and subsequently incarcerated for reasons unrelated to the accident, which prevented him from being interviewed by investigation personnel. As a result, the exact nature of the engine power loss, the location and altitude of the airplane when the power loss occurred, and the pilot's actions subsequent to the power loss were all unable to be determined.
Examination of the wreckage did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded continued flight. The right fuel tank contained sufficient fuel for continued flight, but the left fuel tank was empty. A lack of fuel in a segment of the airplane fuel system downstream of the fuel selector valve was consistent with fuel starvation. However, the fuel selector valve was found in the OFF position, and the investigation was unable to determine when, or by whom, the valve was placed in that position.
Despite the fact that the pilot experienced some degree of engine power loss, he opted to fly a normal traffic pattern, instead of a more direct approach that would better ensure a landing on the runway. As a result, the airplane touched down short of the runway. The short landing demonstrated that the approach was not conducted in accordance with FAA guidance to allow sufficient margin to enable corrections for errors on final approach during an emergency landing. Although the investigation was unable to determine the specific reasons for the short landing, the underlying cause was improper energy management by the pilot during the approach; the pilot's execution of an apparently normal traffic pattern, in combination with the strong headwinds on the final approach leg, left the airplane with insufficient energy to reach the runway.
Probable cause
The pilot's improper energy management during an emergency landing approach that was prompted by an engine power loss. The specific reason(s) for the power loss and the improper energy management could not be determined based on available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR17LA090
- Event ID
- 20170425X32611
- Case number
- WPR17LA090
- 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: 11498599871e9a21a92dd59a7fc83d3ca433619e1948ccbe20b7b29b2a4daf8f; retrieved 2026-09-16T05:12:01.144Z.