CEN09CA139 · Cessna 172I
Cessna 172I · Accident: collision during takeoff/landing
From Southern Wisconsin Regional Airport (KJVL) to Whiteside County Airport - Joseph H Bittorf Field (KSQI)
Event
- NTSB case
- CEN09CA139
- 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 172I
- 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
- N35571
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Southern Wisconsin Regional Airport (KJVL), Janesville, WITo Whiteside County Airport - Joseph H Bittorf Field (KSQI), Sterling, IL
- 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
- 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
- Collision during takeoff/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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated pilot reported that the cloud ceiling and visibility began to deteriorate about 10 minutes after his departure on a 60-nautical-mile cross-country flight. He located the nearest airport, a snow-covered grass runway, and decided to land in lieu of continuing into the deteriorating weather conditions. There was a 65-foot-wide plowed path in the runway that was bordered by snowdrifts. During landing, the airplane struck a low-lying snow bank that was obscured by drifting snow. The airplane then veered left and struck a second snow bank causing substantial damage to the left wing. Prior to departure, the pilot obtained weather information for the planned route of flight using a commercial weather service. The lower cloud ceilings and visibilities were not forecast to begin until after the accident flight was planned to reach the intended destination.
Probable cause
The pilot's inability to maintain directional control during the landing roll after contacting a low-lying snow bank that was obscured by drifting snow.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA139
- Event ID
- 20090122X01552
- Case number
- CEN09CA139
- 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: c021521d9649155415c6127036bedbe30752cf2a7cc6b0ebf86b62ecc1b5d12e; retrieved 2026-09-15T10:42:28.206Z.