DEN04LA045 · Cessna 172N
Cessna 172N · Accident: total loss of engine power (non-mechanical) en route
From Double Eagle II Airport (AEG) to Cedar City Regional Airport (CDC)
Event
- NTSB case
- DEN04LA045
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N9892J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Double Eagle II Airport (AEG), Albuquerque, NMTo Cedar City Regional Airport (CDC), Cedar City, UT
- 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
- Total loss of engine power (non-mechanical)
- 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
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he topped-off the airplane with fuel, and departed to the west on a long cross-country flight. After flying for several hours, he saw the "glow of [city] lights" and thought it was his destination. He attempted to contact the airport by radio, but did not receive a response. He stated that, at that time, he was unable to pick up the VOR. At that point he realized that he must have drifted north and off of his intended heading. He said he adjusted his heading to the southwest, and climbed to a higher altitude. Shortly thereafter, he located his destination, and through radio contact, turned on the runway lights. As he flew over the airport, the airplane's engine began to lose power and then it "cut out." He circled around the airport as he descended and set up for a forced landing on runway 22. On the final approach, he realized that he wasn't going to make the runway. He said that he "increased the [airplane's] angle of attack," but the airplane fell short of the runway. The airplane's right wing struck a fence post and the airplane impacted the terrain approximately 50 yards short of the runway threshold. The airplane's right wing spar was bent outboard of the wing strut, and the nose landing gear was separated from the gear fork. An on-site examination of the airplane revealed that both wing fuel tanks were empty.
Probable cause
the pilot's in-flight decision/planning which resulted in fuel exhaustion. The fence and night conditions were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN04LA045
- Event ID
- 20040220X00209
- Case number
- DEN04LA045
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-02-13.
- API snapshot SHA-256: 05340b7ce5fa16113fce49173da6dc084d25ddb8aa38d660b079c94d2de79195; retrieved 2026-09-22T07:57:47.392Z.