FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI86FA200 · Piper PA-28-235

6 Aug 1986 · Shelby, IN, United States

Hall'S Laundries Piper PA-28-235 · Accident: in flight encounter with weather en route

From Chicago Executive Airport (PWK) to Madison Municipal Airport (IMS)

Report a problem

Event

NTSB case
CHI86FA200
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
4 · all aircraft and ground
Ground fatalities
0
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-235

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
N4383X
Onboard fatalities
Unknown
Route
From Chicago Executive Airport (PWK), Wheeling, ILTo Madison Municipal Airport (IMS), Madison, IN
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
En route · cruise
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
In flight encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft handling, not maintained
  • Pilot in command › Design stress limits of aircraft, exceeded
  • Pilot in command › Flight into known adverse weather, attempted
  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › Preflight planning/preparation, improper
  • Pilot in command › Spatial disorientation

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE NON-INSTRUMENT RATED PILOT INITIATED THE VFR FLIGHT FROM WHEELING, IL, TO MADISON, IN, IN MARGINAL WEATHER CONDITIONS. THE WRECKAGE WAS FOUND ON THE AFTERNOON OF THE FOLLOWING DAY ABOUT 26 MILES SOUTH OF GARY, IN. THE AIRCRAFT SUSTAINED AN IN-FLIGHT BREAKUP WHEREIN BOTH WINGS, THE RIGHT STABILATOR AND THE VERTICAL FIN AND RUDDER SEPARATED. INVESTIGATION SHOWED THE BREAKUP OCCURRED BECAUSE OF AERODYNAMIC FORCES THAT EXCEEDED THE DESIGN LIMITATIONS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI86FA200
Event ID
20001213X34416
Case number
CHI86FA200
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: 64e39fec1f7e353b3937d62c7a67d188273745d85a58b01e4fefb88993c80c68; retrieved 2026-09-21T04:27:08.403Z.