CHI97LA250 · Cessna 172M
Cessna 172M · Accident: hard landing
From Ottumwa Regional Airport (OTM) to Keokuk Municipal Airport (EOK)
Event
- NTSB case
- CHI97LA250
- 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
- N13353
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ottumwa Regional Airport (OTM), Ottumwa, IATo Keokuk Municipal Airport (EOK)
- 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
- Hard landing
- 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 › Flare, improper
- Pilot in command › Porpoise/pilot-induced oscillation, inadvertent
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that on final approach to the runway, the airplane was high on the glide slope, so he increased the flap setting to 40 degrees. He stated that he flew past the numbers and fixed distance marker, then initiated a flare. Also, the pilot reported, 'Flared high, banged hard on the two main wheels. Bounced up and came down again. Bounced about 5 more times.' On the fifth bounce the nose gear broke off. The pilot reported that the airplane veered off the prepared runway surface, crossed a taxiway, into a grass section between the taxiway and runway 8. After reaching the grass section, the airplane nosed over and came to rest inverted.
Probable cause
the pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise, failure (collapse) of the nose gear, and a subsequent nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97LA250
- Event ID
- 20001208X08579
- Case number
- CHI97LA250
- 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: 0db5ef6a4bd8e8b4accd44f362e469a18031e97770d9bf654816ac86223a4871; retrieved 2026-09-22T18:52:45.943Z.