CHI04CA209 · Cessna 172M
Cessna 172M · Accident: loss of control in flight during landing
From Sublette Municipal Airport (19S) to Sublette Municipal Airport (19S)
Event
- NTSB case
- CHI04CA209
- 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 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
- N105PD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sublette Municipal Airport (19S), Sublette, KSTo Sublette Municipal Airport (19S), Sublette, KS
- 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 in flight
- 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 › Recovery from bounced landing, not successful
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 departed the runway and nosed over during the student pilot's first solo flight. The pilot stated that the local winds resulted in a five knot left crosswind. The pilot reported that she flew a left traffic pattern for runway 17 and while on final approach had to "compensate with right rudder" for the crosswind. The pilot stated the airplane touched-down a few feet off the runway centerline with a "very slight bounce." The pilot reported the airplane "veered to the right" and that she was "unable to apply left rudder in time to keep [the airplane] from going off the runway." The pilot stated the right main landing gear contacted soft terrain and the airplane nosed over.
Probable cause
The student pilot's inadequate compensation for the crosswind condition, and her failure to maintain aircraft control during landing. Factors contributing to the accident included the student pilot's unsuccessful recovery from the bounced landings and the soft terrain conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA209
- Event ID
- 20040823X01269
- Case number
- CHI04CA209
- 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: dda6e11c36ee8763d503be2399cbb6d89bb5bf4d686237dbdc240d62e331d935; retrieved 2026-09-21T19:11:00.649Z.