DEN93LA073 · Cessna 177
Cessna 177 · Accident: loss of control on ground/water during landing
From Sterling Municipal Airport (STK) to an unrecorded destination
Event
- NTSB case
- DEN93LA073
- 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 177
- Aircraft type
- Cessna 177
- 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
- N30248
- Operator
- Peterson, Richard L. · private individual
- Onboard fatalities
- Unknown
- Route
- From Sterling Municipal Airport (STK), Sterling, COTo not recorded
- 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 · aborted
- 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 › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AN AIRPORT ADVISORY INDICATED THE WINDS WERE FROM 230 DEGREES AT 20 KNOTS AND GUSTING. THE PILOT MADE HIS LANDING APPROACH TO RUNWAY 29, USING A SLIP TECHNIQUE. UPON TOUCHDOWN THE AIRPLANE BOUNCED AND THE PILOT ATTEMPTED TO RECOVER. THE PILOT WAS UNABLE TO MAINTAIN RUNWAY ALIGNMENT AND THE AIRPLANE DRIFTED OFF TO THE RIGHT SIDE OF THE RUNWAY. THE PILOT ATTEMPTED TO GO AROUND BUT WAS NOT SUCCESSFUL. WHILE FLYING IN GROUND EFFECT, THE AIRPLANE STRUCK A RUNWAY LIGHT, WENT DOWN A HILL AND THROUGH A BARBED WIRE FENCE, AND CAME TO REST ON A SERVICE ROAD.
Probable cause
THE PILOT'S INADEQUATE COMPENSATION FOR WIND CONDITIONS. FACTORS WERE: THE PILOT'S FAILURE TO INITIATE A GO AROUND IN A MORE TIMELY MANNER, AND GUSTY CROSSWINDS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN93LA073
- Event ID
- 20001211X12887
- Case number
- DEN93LA073
- 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: e02561ea15942ead2750775a7da831ba4e062c39a52582e251e5cd3d644923b0; retrieved 2026-09-23T01:54:43.734Z.