DEN02LA054 · Cessna TR182
Cessna TR182 · Accident: hard landing
From 2V2 · Longmont, CO to Sumers Airpark (GWS)
Event
- NTSB case
- DEN02LA054
- 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 TR182
- 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
- N333AJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2V2 · Longmont, COTo Sumers Airpark (GWS), Glenwood Sprngs, 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
- Hard landing
- 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
- Stall/mush; Tree(s)
- 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said he was concerned about the airport's elevation and runway length, so he maintained a low approach speed. As the airplane came over the runway, airspeed started to decay. The pilot said he didn't react quickly enough, and the airplane mushed onto the runway, bounced hard twice, and drifted off the left side of the runway. He decided to abort the landing, so he raised the flaps, enrichened the mixture, and added full throttle. The airplane lifted off but its left wing struck a tree, spinning the airplane around 90 degrees. It slid 200 feet, struck some construction equipment, spun around again, and came to a halt.
Probable cause
the pilot's failure to maintain clearance from a tree while conducting an aborted landing. Contributing factors were the pilot’s low approach airspeed, and his failure to maintain directional control during landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN02LA054
- Event ID
- 20020620X00945
- Case number
- DEN02LA054
- 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: 4346f3fcb6d7d86b361cb19bc58027bfca8ae64d1ebe08b78b6c21ca6acc01fc; retrieved 2026-09-21T19:42:06.438Z.