DEN02LA066 · Cessna 172M
Cessna 172M · Accident: total loss of engine power (non-mechanical) en route
From 1V5 · Boulder, CO to Cal Black Memorial Airport (U96)
Event
- NTSB case
- DEN02LA066
- 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 172M
- 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
- N725EC
- Operator
- David L. Metzger · private individual
- Onboard fatalities
- Unknown
- Route
- From 1V5 · Boulder, COTo Cal Black Memorial Airport (U96), Halls Crossing, 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)
- 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 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
- Fluid, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was about 30 miles away from the airport when the airplane's engine lost power. He said he tried to find a place to land. The pilot said, "I found a very small dirt road, so I turned base and then final for it. We had a big tailwind at this point and we overshot the road. I then turned to the right and set it down in the middle of the desert. The landing was soft until we ran out of room and hit a ditch. We almost stopped and the front tire dug in, and it lifted us straight up and then we rolled over slowly on to the top of the plane." In his statement to a Federal Aviation Administration Inspector, the pilot said that he ran out of fuel. An examination of the airplane's fuel system showed no fuel in the tanks. No other pre-impact anomalies were found.
Probable cause
the pilot's improper in-flight planning resulting in fuel exhaustion. A factor relating to the accident was the unsuitable terrain encountered during the forced landing attempt.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN02LA066
- Event ID
- 20020708X01058
- Case number
- DEN02LA066
- 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: d6f7221a42dbab4301d84ef03d7c2aae0279e16827382be1dd5f34445357870b; retrieved 2026-09-22T10:47:13.945Z.