CEN24LA123 · Cessna 172 I
Cessna 172 I · Accident: loss of control on ground during landing
From Council Bluffs Municipal Airport (CBF) to an unrecorded destination
Event
- NTSB case
- CEN24LA123
- 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 172 I
- 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
- N35719
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Council Bluffs Municipal Airport (CBF), Council Bluffs, IATo not recorded
- Aircraft age
- About 56 years (built 1968)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during landing at the destination airport, with the left and right main landing gear on the runway and the nose wheel elevated for the flare, she felt a gust of wind that “push[ed] the airplane suddenly to the right.” The pilot attempted to perform a go-around, however the airplane bounced twice, exited the runway to the right, impacted a dirt field, nosed over, and came to rest inverted. The airplane sustained substantial damage to the fuselage, both wings, and the empennage. The pilot reported there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
At the time of the accident, the pilot was landing on runway 31 with wind 270° at 23 knots, and with gusts from 30 to 35 knots.
The pilot further reported that the accident could have been prevented by having “better situational awareness” of the wind conditions at the destination airport.
Probable cause
The pilot’s failure to maintain directional control during the landing flare in a crosswind with gusts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA123
- Event ID
- 20240227193850
- Case number
- CEN24LA123
- 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, cause areas. 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: a77df4e68da246ce1a38581751ac83895d486a9f74be46d9e043b028a1d97c61; retrieved 2026-09-16T18:32:46.354Z.