CHI05CA002 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of control in flight on approach
From Quad City International Airport (MLI) to Marion Airport (C17)
Event
- NTSB case
- CHI05CA002
- 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
Piper PA-28-180
- Aircraft type
- Piper PA-28
- 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
- N7841N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Quad City International Airport (MLI), Moline, ILTo Marion Airport (C17), Marion, IA
- 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
- Approach · VFR go-around
- 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 in flight
- 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 › Aircraft control, not maintained
- Pilot in command › Compensation for wind conditions, inadequate
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 impacted an airport hangar while attempting a go-around. The pilot reported that he elected to go-around after encountering turbulence during landing approach to runway 17. The pilot stated "it felt like a gust of wind went under my right wing & belly and just started pushing me over, to the left. I immediately applied right rudder and aileron as hard as I could and tried to push the nose down but there was no response." The pilot reported he "didn't have a chance to put flaps back up or try to cut power." The pilot stated the airplane went "up and over" to the left and impacted the airport hangar. A nearby weather observing station reported the winds at the time of the accident were 200 degrees true at 15 knots, gusting to 19 knots.
Probable cause
The pilot's inadequate compensation for the gusting wind conditions and his failure to maintain aircraft control. Factors to the accident were the encountered turbulence, the gusting wind conditions and the airport hangar.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05CA002
- Event ID
- 20041105X01776
- Case number
- CHI05CA002
- 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, 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: b46085c387c6a65e136fc9b4a85422e8b1424ba523dbbfe29187f46b9374c056; retrieved 2026-09-21T19:07:34.621Z.