CEN24LA321 · Cessna A185 F
Cessna A185 F · Accident: loss of control on ground during landing
From Rocky Mountain Metropolitan Airport (BJC) to an unrecorded destination
Event
- NTSB case
- CEN24LA321
- 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 A185 F
- Aircraft type
- Cessna 185
- 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
- N4490R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo not recorded
- Aircraft age
- About 48 years (built 1976)
- 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
- 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
- Personnel issues › Action/decision
- Personnel issues › Psychological
- 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
Before the landing, the pilot told the flight instructor that he “wasn’t real comfortable” with the landing, as he had never landed to the particular runway before, which he classified as shorter and narrower. The flight instructor said the landing would be “okay,” and the pilot completed the before landing checklist with the tailwheel unlocked and full flaps applied for the three-point landing. After touchdown, the airplane bounced and immediately after the second touchdown, the airplane ground looped and departed the runway to the left. The right main landing gear collapsed, and the right wing and the empennage impacted the ground. The airplane came to rest upright on a grass field next to the runway and the three occupants were able to egress from the airplane without further incident.
The airplane sustained substantial damaged to the fuselage, the right wing, and the empennage. The pilot reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The pilot further reported that a ground loop had occurred “very fast,” and the cause of the accident was “human error.”
Probable cause
The pilot’s failure to maintain directional control during the landing, that resulted in a ground loop and a runway excursion. Contributing to the accident was the flight instructor’s delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA321
- Event ID
- 20240821194973
- Case number
- CEN24LA321
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-08-20.
- API snapshot SHA-256: 8670e115e8fc41895d572d7c1609eeb5f766f4ad7b45c64c287cd05801c9f7ce; retrieved 2026-09-16T19:11:37.703Z.