CHI99LA104 · Cessna 172P
Cessna 172P · Accident: loss of control on ground/water during landing
From 1C5 to 1C5
Event
- NTSB case
- CHI99LA104
- 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 172P
- 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
- N65192
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 1C5To 1C5
- 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 · landing roll
- 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
- 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 › Directional control, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot of the accident airplane said that he maintained 65 knots and was lined up with the Runway 36 while on final approach. Just above the runway he stated he pulled back on the yoke to reduce airspeed. The stall horn sounded before touchdown. The airplane touched down a third of the way down the runway and between the centerline and the left edge of the runway. The pilot stated he felt the airplane being pushed left and the left main wheel exiting the runway. The airplane exited the left edge of the runway. The pilot stated that the airplane impacted a snow bank, tipped on its nose, and came to rest facing eastward. The student's instructor stated that winds were from 070 degrees at 5 knots. The student's logbook showed 4.8 hours total time in C-172's. The student was endorsed to solo a C-172 after 2.7 hours of flight instruction and 6 landings in a C-172. The student had accumulated 4 solo landings and 1.6 solo hours of flight in C-172's including the accident flight.
Probable cause
the pilot's inadequate directional control during landing roll. A factor was the snow bank.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA104
- Event ID
- 20001205X00281
- Case number
- CHI99LA104
- 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: 2a2866685993a4cf78c18f139fce5f625c5fd72bad25f2371c06ce11d472377e; retrieved 2026-09-22T15:44:27.808Z.