CEN20CA094 · Cessna 172 S
Rocky Mountain Flight Consultants Cessna 172 S · Accident: loss of control on ground during landing
From Boulder Municipal Airport (BDU) to Boulder Municipal Airport (BDU)
Event
- NTSB case
- CEN20CA094
- 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 172 S
- 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
- N370SP
- Onboard fatalities
- Unknown
- Route
- From Boulder Municipal Airport (BDU), Boulder, COTo Boulder Municipal Airport (BDU), Boulder, CO
- Aircraft age
- About 17 years (built 2003)
- 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 · landing roll
- Defining eventThe 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
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 departed from a snow-packed runway, flew locally for about 2 hours, and then returned to land. The pilot stated that, while in the traffic pattern preparing to land, the runway still appeared to be snow-packed like it was during the departure. However, the runway was actually slush covered with patches of ice due to the morning sun melting the previously hard snow, and the airplane veered left during the landing roll. The pilot was unable to maintain directional control, and the airplane subsequently impacted a snowbank on the edge of the runway and nosed over, which resulted in substantial damage to both wings and the vertical stabilizer.
Probable cause
The pilot's loss of directional control during the landing roll on the slush-covered runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA094
- Event ID
- 20200220X82852
- Case number
- CEN20CA094
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: bca9ebe11f60be81238dfdd8a8ed999e5c9ea0a99660515cf16fe2a5ffe90f66; retrieved 2026-09-16T11:08:58.929Z.