CHI99LA103 · Cessna 172R
Cessna 172R · Accident: hard landing
From Battle Creek Executive Airport at Kellogg Field (BTL) to an unrecorded destination
Event
- NTSB case
- CHI99LA103
- 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 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
- N983AV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Battle Creek Executive Airport at Kellogg Field (BTL)To 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
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that during the flare/touchdown she experienced, '... a little bit of turbulence... . ' She reported that two or three seconds after touchdown the airplane started to slide to the left. The pilot stated that she applied full right rudder to compensate for the drift, but the aircraft continued to slide. The pilot reported that the aircraft impacted a snowbank, on the left side of the runway, and the aircraft came to rest in an upright orientation. Examination of the runway showed a series of propeller impact marks along the centerline of the runway. Inspection of the wreckage revealed no anomalies with the airframe, flight controls, or engine. The pilot had a total time of 15.1 hours, with 14.6 hours as dual instruction and .5 hours as pilot-in-command.
Probable cause
The pilot's improper flare and failure to maintain directional control. Related factors were the snowbank and lack of total experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA103
- Event ID
- 20001205X00280
- Case number
- CHI99LA103
- 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: 4d0f17efb217d55083b0fc88483fbd91b21d4822f4adac345502440ec37d2ec9; retrieved 2026-09-22T15:44:10.192Z.