FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN07CA162 · Cessna 182Q

20 Sept 2007 · Glenwood Springs, CO, United States

Cessna 182Q · Accident: in flight encounter with weather during landing

From Gunnison Crested Butte Regional Airport (GUC) to Sumers Airpark (GWS)

Report a problem

Event

NTSB case
DEN07CA162
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 182Q

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
N97996
Operator
Terry E. Harland · private individual
Onboard fatalities
Unknown
Route
From Gunnison Crested Butte Regional Airport (GUC), Gunnison, COTo Sumers Airpark (GWS), Glenwood Springs, 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
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 › Go-around, not performed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot was landing the airplane on runway 32 (3,305 feet by 50 feet, dry, asphalt). As the airplane crossed over the runway threshold, the pilot heard a warning for wind shear over the UNICOM. The pilot reported the "wind changed to a tailwind which caused us to float down the runway and [the pilot] had difficulty getting the airplane down." The airplane departed the end of the runway and impacted terrain. During the excursion, the nose landing gear separated from the airframe, and the airplane came to rest upright. Winds at the time of the accident were reported as variable and gusty.

Probable cause

The pilot's failure to go around when it became apparent that he could not land and stop the airplane on the remaining runway. Factors contributing to the accident were the tailwind and the gusts.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN07CA162
Event ID
20071030X01690
Case number
DEN07CA162
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: 45c79ef5eddc39702fba5996e3ad88414f032c5b9900f6fcf0f2f2799a5b2002; retrieved 2026-09-21T18:23:43.848Z.