DEN06FA028 · Cessna 182D
Cessna 182D · Accident: in flight collision with terrain/water en route
From Durango La Plata County Airport (DRO) to Scottsdale Airport (SDL)
Event
- NTSB case
- DEN06FA028
- 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
- 1 · 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 182D
- Aircraft type
- Cessna 182
- 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
- N182GV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Durango La Plata County Airport (DRO), Durango, COTo Scottsdale Airport (SDL), Scottsdale, AZ
- 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
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was the subject of an (alert notification) ALNOT issued January 1, 2006.The accident site was located in a forested area at an elevation of 7,050 feet msl and the airplane impacted on a heading of 220 degrees. The wreckage was scattered 580 feet. Sunset was recorded at 1726 and the end of civil twilight was 1754. The moon rose at 0825 and set at 1807 on the day of the accident. The moon was waxing crescent with one percent of its visible disk illuminated. An examination of the airframe, airplane's systems, and power plant revealed no anomalies that would have precluded normal and correct operation prior to impact. According to flight records, the pilot had logged 3 hours of night flight experience.
Probable cause
the pilot's failure to maintain altitude/clearance from terrain. Contributing factors included the pilot's lack of night flying experience and the dark night.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN06FA028
- Event ID
- 20060112X00060
- Case number
- DEN06FA028
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-01-01.
- API snapshot SHA-256: d89c61a8310298e4cfbd6de163e1674ef073b33b8168bb906e04707349ba292e; retrieved 2026-09-20T17:39:10.536Z.