CHI08CA091 · Cessna 172R
Cessna 172R · Accident: loss of control on ground during landing
From Clermont County Airport (I69) to an unrecorded destination
Event
- NTSB case
- CHI08CA091
- 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 172R
- 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
- N53417
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Clermont County Airport (I69), Batavia, OHTo 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 · 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot stated that she was practicing touch-and-goes on runway 4 (3,568 feet by 75 feet, asphalt) as part of a solo instructional flight when the accident occurred. She noted that the winds were variable and gusty, and it was "choppy" in the pattern. The accident occurred on what was to be the final landing for the day. The pilot reported that the airplane was established on final approach about 65 knots. The airplane was slightly low, but she did not feel the need to correct the glide path. The airplane touched down and its nose suddenly turned to the left. As the nose went to the left, the airplane bounced. She "gently lowered the nose, but the plane bounced again and again." Her efforts to regain control were not successful and the airplane ultimately came to rest in a grass area to the left side of the runway. The nose landing gear collapsed during the accident sequence. A post accident inspection did not reveal any anomalies consistent with a pre-impact failure or malfunction. Archived weather information was not available for the accident airport. Winds recorded at an airport about 10 miles north of the accident airport were from 110 degrees at 9 knots. The pilot reported a total flight time of 97.5 hours. She had accumulated a total of 5.8 hours as pilot-in-command (PIC) and 2.3 hours as PIC in the same make and model aircraft.
Probable cause
The pilot's misjudgment of the landing flare and her inadequate recovery from the bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA091
- Event ID
- 20080411X00457
- Case number
- CHI08CA091
- 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. 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: 19bee7c4081b452874b427d46bae8262d533010c56a714c9bea1165901c0c531; retrieved 2026-09-15T09:31:16.663Z.