FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA068 · Piper PA-22-160

21 Jan 2002 · Iowa Falls, IA, United States

Piper PA-22-160 · Accident: loss of control on ground/water during landing

From Dubuque Regional Airport (DBQ) to Iowa Falls Municipal Airport (IFA)

Report a problem

Event

NTSB case
CHI02LA068
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-22-160

Aircraft type
Piper PA-22
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
N9248D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Dubuque Regional Airport (DBQ), DuBuque, IATo Iowa Falls Municipal Airport (IFA), Iowa Falls, 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
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
Loss of control on ground/water
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane nosed over following a loss of control during landing. The pilot reported the winds were from 240 degrees at 11 knots and the landing was being made on runway 31. He reported he lowered the left wing and applied right rudder during the approach to compensate for the crosswind. The pilot reported that the airplane bounced during the landing and he did not react quickly enough by once again lowering the wing. He reported the wind lifted the left wing so that the airplane was on the right main gear only. He reported that it seemed the airplane was going to ground loop. He applied right rudder to stop the ground loop, but by that time the airplane was off the side of the runway. The airplane traveled into a plowed bean field where it nosed over and tipped onto the right wing.

Probable cause

The pilot's inadequate compensation for the crosswind condition and the subsequent failure to maintain control of the airplane. Factors associated with the accident were the crosswind and the rough terrain encountered.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA068
Event ID
20020124X00112
Case number
CHI02LA068
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: b9c00ca97aa57fd5800a9c31355cfc5ff49c248bf9dab8117f0513ea15141cef; retrieved 2026-09-22T11:11:17.942Z.