CHI08LA096 · Cessna 172R
Poplar Grove Airmotive Cessna 172R · Accident: loss of control on ground during landing
From Poplar Grove Airport (C77) to Monroe Municipal Airport (EFT)
Event
- NTSB case
- CHI08LA096
- 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 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
- N724PG
- Operator
- Poplar Grove Airmotive
- Onboard fatalities
- Unknown
- Route
- From Poplar Grove Airport (C77), Poplar Grove, ILTo Monroe Municipal Airport (EFT), Monroe, WI
- 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
- Loss of control on ground
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
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 landed long and bounced during touchdown and then departed the runway. It then nosed over and impacted a snow bank to the right of the runway. There were two skid marks on the runway consistent with left and right main landing gear tires that began about 2,200 feet down the runway. The recorded winds at the airport were 270 degrees at 10 knots with gusts at 17 knots. The airport did not have an air traffic control tower and was equipped with runways 12-30 (5,000 feet by 75 feet, asphalt) and 02-20 (3,000 feet by 75 feet, asphalt). The airplane landed on Runway 02. The airplane's fuselage was wrinkled and both wings were damaged. Inspection of the airplane revealed no mechanical anomalies that would have precluded normal operation.
Probable cause
The pilot's decision to land on the wrong runway for the existing wind conditions and his improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08LA096
- Event ID
- 20081003X41448
- Case number
- CHI08LA096
- 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, 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: 423fc44dffb155acdd1a855896603c00e1c712e3eac6599ad71d10f31c7274bb; retrieved 2026-09-15T10:19:25.118Z.