DEN93LA024 · Cessna 152
Durango Air Service Cessna 152 · Accident: total loss of engine power (non-mechanical) en route
From Durango La Plata County Airport (DRO) to Durango La Plata County Airport (DRO)
Event
- NTSB case
- DEN93LA024
- 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 152
- Aircraft type
- Cessna 152
- 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
- N67492
- Operator
- Durango Air Service
- Onboard fatalities
- Unknown
- Route
- From Durango La Plata County Airport (DRO)To Durango La Plata County Airport (DRO)
- 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 contamination
- 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 › Contamination
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE, WITH AN INSTRUCTOR AND STUDENT PILOT ABOARD, WAS FULL OF FUEL WHEN THEY TOOK OFF FOR AN INSTRUCTIONAL FLIGHT. AFTER 45 MINUTES, THEY TURNED BACK AND WHEN THEY WERE ABOUT 3 MILES FROM THE AIRPORT, THE ENGINE BEGAN TO RUN ROUGH AND RPM DROPPED STEADILY FROM FULL POWER TO A COMPLETE POWER LOSS. ATTEMPTS TO RESTORE POWER WERE UNSUCCESSFUL. A FORCED LANDING WAS MADE IN DEEP SNOW AND THE AIRPLANE NOSED OVER. THE ENGINE WAS LATER FUNCTIONALLY TESTED AND IT OPERATED SATISFACTORILY. THE OPERATOR SAID THE AIRPLANE HAD NOT FLOWN RECENTLY AND THERE HAD BEEN A SUBSTANTIAL SNOW FALL. HE SUSPECTED THE FUEL MAY HAVE BEEN CONTAMINATED WITH WATER.
Probable cause
POWER LOSS DUE TO WATER CONTAMINATED FUEL. A FACTOR WAS: UNSUITABLE TERRAIN FOR A FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN93LA024
- Event ID
- 20001211X11688
- Case number
- DEN93LA024
- 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: 5988201a01cfd319a8cb8867a621cdd3a675a00b51d7cf8d774f43237c76e61e; retrieved 2026-09-23T02:22:01.426Z.