CHI07CA296 · Cessna 172 Skyhawk
Cessna 172 Skyhawk · Accident: loss of control on ground/water during landing
From Atkinson Municipal Airport (PTS) to Stockton Municipal Airport (MO3)
Event
- NTSB case
- CHI07CA296
- 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 Skyhawk
- 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
- N12189
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Atkinson Municipal Airport (PTS), Pittsburg, KSTo Stockton Municipal Airport (MO3), Stockton, MO
- 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
- Loss of control on ground/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Aircraft control, not maintained
- Pilot in command › Airspeed, not maintained
- Pilot in command › Recovery from bounced landing, improper
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted terrain following a bounced landing on runway 1 (3,060 feet by 50 feet, asphalt) and subsequent stall. The student pilot was on a solo flight when the accident occurred. She reported that the landing touchdown was hard and the airplane bounced back into the air. She added engine power in an attempt to go-around; however, the airplane veered to the left, off of the runway centerline. Her efforts to regain control of the airplane were unsuccessful. The airport manager stated that he noticed the accident airplane on approach for landing. He noted the pilot appeared to be having difficulty lining up with the runway due to an east crosswind at about 10 knots, with higher gusts. Upon touchdown, the airplane "bounced high into the air" in an approximate 45-degree left bank. After a heading change of approximately 30 degrees to the left, the airplane appeared to stall and subsequently impacted the ground.
Probable cause
The pilot's improper recovery from a bounced landing, her subsequent loss of control of the airplane, and the inadvertent stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA296
- Event ID
- 20071011X01563
- Case number
- CHI07CA296
- 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, 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: 8cd61a18dc0d6695d3c9b251db016b3aaa0958e6e4e4c3b70505cd68ef9b39bd; retrieved 2026-09-21T18:24:08.472Z.