DEN83LA073 · Cessna 172M
Cessna 172M · Accident: loss of control on ground/water during landing
From Fremont County Airport (1V6) to LKV · Leadville, CO
Event
- NTSB case
- DEN83LA073
- 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 172M
- Aircraft type
- Cessna 172
- 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
- N13620
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fremont County Airport (1V6), Canon City, COTo LKV · Leadville, 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
- Loss of control on ground/water
- 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 › Directional control, not maintained
- Pilot in command › Flight controls, improper use of
- Pilot in command › Go-around, not corrected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE CESSNA 172 COLLIDED WITH A SNOWBANK DURING LANDING AND NOSED OVER. THE WEATHER WAS VMC WITH LIGHT WINDS FROM 20 DEGREES AT 3 KTS. ONE INCH OF FRESH SNOW WAS COVERING THE RUNWAY. THE PILOT SAID HE FLEW THE APPROACH TO RUNWAY 34 WITH 20 DEGREES OF FLAPS AND TOUCHED DOWN 150 YARDS PAST THE NUMBERS. AFTER TOUCHDOWN THE ACFT SKIDDED TO THE LEFT FOR ABOUT 100 YARDS. ACCORDING TO THE PILOT HE APPLIED BRAKES AND RIGHT RUDDER TO NO AVAIL. WHEN HE APPLIED POWER THE ACFT STRAIGHTENED BUT IT WAS TOO LATE. THE LEFT LANDING GEAR WENT INTO A SNOW BANK AND THE ACFT NOSED OVER THE PILOT RECEIVED HIS PRIVATE CERTIFICATE 3 MONTHS BEFORE THE ACCIDENT AND HAD ABOUT 90 HOURS OF FLIGHT TIME.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN83LA073
- Event ID
- 20001214X42401
- Case number
- DEN83LA073
- 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: 13c8d5b14b38308340c2b3302be7c8e2cd09cf4d4e9120dbcf2dfa8f3ea69b06; retrieved 2026-09-23T22:53:10.751Z.