CHI02FA200 · Piper PA-20
Piper PA-20 · Accident: near collision between aircraft during landing
From Mount Pleasant Municipal Airport (MOP) to Wittman Regional Airport (OSH)
Event
- NTSB case
- CHI02FA200
- 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-20
- Aircraft type
- Piper PA-20
- 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
- N1592A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mount Pleasant Municipal Airport (MOP), Mount Pleasant, MITo Wittman Regional Airport (OSH), Oshkosh, 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
- 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
- Near collision between aircraft
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- 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
- Faa(other/organization) › Visual separation, inadequate
- Pilot in command › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
- Traffic pattern procedure › Congested
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The PA-20 collided with the runway following an abrupt maneuver to avoid another airplane. The accident occurred during EAA AirVenture 2002, at Oshkosh, Wisconsin. The PA-20 pilot was cleared to land on the "orange dot" (1,500 from the threshold) on runway 27. A Cessna 172 was cleared to land on the numbers of runway 27. The PA-20 pilot reported that during his landing flare, he saw the Cessna 172 underneath his airplane. He pulled up and to the right to avoid a collision with the other Cessna 172. He stated he added full throttle and leveled the nose, but a strong wind from the left rolled the airplane to the left and "without enough airspeed for effective aileron" he could not reverse the roll. The airplane stalled and spun into the runway from an altitude of about 120 feet. The pilot of the Cessna 172 reported that there was a fairly strong left crosswind and that his airplane floated a little on the runway before touching down. Neither pilot reported seeing the other. The Cessna 172 pilot reported that he was unaware that an accident had occurred. Winds at the time of the accident were from 230 degrees at 12 knots gusting to 22 knots. As announced on the airport terminal information service (ATIS), the VFR Oshkosh Arrival, Yellow Flow procedures were in effect at the time of the accident. The Yellow Flow instructs pilots to join the other traffic over over a VFR checkpoint. The traffic then travels around the northwest side of the airport, entering a right base leg for either runway 18L or 18R. In addition to landing VFR traffic on runway 18L and 18R, air traffic control (ATC) was landing VFR traffic on runway 27. This was accomplished by having the VFR traffic extend their base leg for the 18 runways, putting them on a right downwind for runway 27. The VFR landings on runway 27 were not outlined as part of the Yellow Flow procedures. The only landings on runway 27 that are a part of the procedure were IFR arrivals approaching the airport from the east and warbirds who were to approach the airport from the southeast. Neither airplane was issued go-around procedures from ATC. The PA-20 pilot reported that his passenger recalled hearing an ATC transmission about an airplane underneath them, but by this time he had already pulled up and it was too late.
T
Probable cause
Inadequate visual lookout by both the accident pilot and the pilot of the other airplane. An additional cause is the arrival procedure used which resulted in a congested traffic pattern and the subsequent inadequate visual separation of the airplanes. Factors associated with the accident are the gusty crosswind, the pilot of the other aircraft landed longer than ATC expected, and the stall/spin encountered during the pilot's attempted remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02FA200
- Event ID
- 20020724X01196
- Case number
- CHI02FA200
- 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: ce53501d6f870579363b5bd7d322ba9e271491e87046f828cff13c2f88387599; retrieved 2026-09-22T10:42:12.478Z.