DEN05CA067 · Cessna 182M
Cessna 182M · Accident: in flight encounter with weather during landing
From Scottsdale Airport (SDL) to Cortez Municipal Airport (CEZ)
Event
- NTSB case
- DEN05CA067
- 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 182M
- 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
- N92112
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Scottsdale Airport (SDL), Scottsdale, AZTo Cortez Municipal Airport (CEZ), Cortez, CO
- 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
- Landing · flare/touchdown
- 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 encounter with weather
- 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 › Aircraft control, 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 pilot encountered windshear during the landing flare to runway 21. The pilot reported that he added power as he descended; however, the airplane continued to descend "rapidly." The airplane impacted the runway, bounced several times, and departed the runway to the right. During the impact, the nose landing gear assembly collapsed and the propeller struck the runway, causing substantial damage. An examination of the airplanes systems revealed no anomalies. According to the METAR (routine aviation weather report) the winds at the time of the accident were reported as 170 degrees at 19 knots with gusts to 25 knots. The crosswind component calculated for the time of the accident ranged from 12 to 16 knots.
Probable cause
the pilot's failure to maintain aircraft control during the landing flare. Contributing factors include the pilot's improper in-flight planning/decision making, the crosswind and the gusty surface winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05CA067
- Event ID
- 20050426X00504
- Case number
- DEN05CA067
- 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: ac2a06c7b6d7dcbc82b84643f9afec555333033736e65770d033d539850bd032; retrieved 2026-09-22T06:06:15.221Z.