# NTSB CEN09CA139: Cessna 172I, N35571, Rockford, IL, January 19, 2009

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: January 19, 2009, 16:45 local (22:45 UTC)
- Place: Rockford, IL
- Coordinates: 42.291667, -89.136108 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=42.2917&lon=-89.1361&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report April 15, 2009
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Federal Aviation Administration - DuPage FSDO
- NTSB case key (mKey): 73263
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09CA139
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73263/pdf
- Page: https://openairdocs.org/ntsb/CEN09CA139

## 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.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Cessna 172I, 3 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072426), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Runway/land/takeoff/taxi surface: snow/slush/ice covered surface](https://openairdocs.org/ntsb-findings/03023015): Environmental issues › Physical environment · Ability to respond/compensate (probable cause); cases with it: [Cessna 172I, 2 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md?model=2072426), [All aircraft, 219 cases](https://openairdocs.org/ntsb-findings/03023015/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Cessna 172I, 6 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=2072426), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md)
- [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172I, 7 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072426), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172I, 1 case](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072426), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md)
- [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172I, 5 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072426), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md)

## Analysis

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.

## Factual 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 (nm) cross-country flight. The pilot located the nearest airport, a snow covered grass runway, and decided to land in lieu of continuing into the deteriorating weather conditions. He circled the airport to identify if the runway had any obstructions. There was a 65 foot wide plowed path in the runway that was bordered by snowdrifts. During landing rollout the airplane veered to the left after encountering a low lying snow bank that was obscured by drifting snow. The pilot attempted to regain directional control, but the nose landing gear separated from the airplane when it impacted a second snow bank. The airplane turned 180 degrees and came to rest in a nose down attitude. The nose landing gear and left wing were damaged during the accident. Prior to departure, the pilot obtained weather information for the planned route of flight using a commercial weather service. According to a Terminal Aerodrome Forecast (TAF), visual flight rules (VFR) conditions were expected for the duration of the accident flight. The nearest weather reporting station to the accident site, located about 6 nm to the south, reported ground visibilities greater than 10 statute miles (sm) and cloud ceilings 15,000 to 20,000 feet above ground level (agl), during the seven hour period before the departure time. However, about 10 minutes after the departure time, the ground visibility and cloud ceiling had dropped to 1-3/4 sm and 3,600 feet agl, respectively. The weather station reported light snow conditions in the area. The lower cloud ceilings and visibilities were not forecast to begin until after the accident flight was planned to reach the intended destination.

## Aircraft

- Registration: [N35571](https://openairdocs.org/deregistered/N35571-2023-10-07), registration cancelled 2023-10-07, S/N 17256842, built 1968 (OpenAirDocs)
- Reported make and model: Cessna 172I
- Registry model: [Cessna 172I](https://openairdocs.org/model/cessna-172i) (registry code 2072426) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17256842
- Airframe hours: 2650
- Engines: Lycoming O-320-E2D 150 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Utility; Standard, Normal
- Last inspection: Annual, October 8, 2008
- Departed: KJVL, Janesville, WI
- Destination: KSQI, Sterling, IL
- Airport: 1C8, Cottonwood Airport, runway 18, 2,540 × 260 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 20; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review September 12, 2007; seat: left; flight hours: 300 total, 200 in this make and model, 235 as pilot in command, 40 in the last 90 days, 2 in the last 30 days

## Weather

- Conditions: Visual (VMC), Dusk
- Wind: 290° at 6 knots
- Visibility: 1.5 statute miles
- Lowest ceiling: 2,200 ft broken
- Temperature: 18 °F, dew point 10 °F
- Altimeter: 29.88 inHg
- Observed at: KRFD, 6 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20090119012479A](https://openairdocs.org/incident/20090119012479A), Jan 19, 2009: Cessna 172I, Rockford, IL, Substantial damage. (-23) Mr. John young departed from southern Wisconsin regional airport, janesville, WI (jvl) on January 19, 2009 at approximately 1545 CST. Mr. Young stated…

## Other investigations on N35571 (3)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA22LA203](https://openairdocs.org/ntsb/ERA22LA203), Apr 22, 2022: Cessna 172 (N35571), Westminster, MD, substantial damage. Probable cause: The student pilot’s failure to attain the proper touchdown point which resulted in a runway overrun.
- [NTSB ERA12LA148](https://openairdocs.org/ntsb/ERA12LA148), Jan 19, 2012: Cessna 172I (N35571), Springfield, TN, substantial damage. Probable cause: The pilot did not apply carburetor heat during approach to landing, which resulted in a total loss of engine power due to carburetor icing.
- [NTSB CHI76FEE51](https://openairdocs.org/ntsb/CHI76FEE51), Apr 11, 1976: Cessna 172I (N35571), Ransom, IL, substantial damage

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.