FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW87FA183 · Piper PA-24-250

1 Aug 1987 · Kokomo, IN, United States

Piper PA-24-250 · Accident: in flight encounter with weather en route

From Nashville International Airport (BNA) to Elkhart Municipal Airport (EKM)

Report a problem

Event

NTSB case
FTW87FA183
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
1 · 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
Instrument Meteorological Cond

Piper PA-24-250

Aircraft type
Piper PA-24
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
N7841P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Nashville International Airport (BNA), Nashville, TNTo Elkhart Municipal Airport (EKM), Elkhart, 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 › Design stress limits of aircraft, exceeded
  • Pilot in command › Hazardous weather advisory, disregarded
  • Pilot in command › In-flight planning/decision, poor
  • Wing › Failure, total
  • Wing › Overload

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

NTSB narrative

THE PLTS PREFLT WX BRIEFING REVEALED MARGINAL VFR & IFR WX ALONG HIS PROPOSED ROUTE, WITH A PRECAUTION FOR THUNDERSTORMS. AN IFR FLT PLAN WAS FILED AND THE ACFT DEPARTED. LATER DURING FLT THE PLT WAS RADIOED INFO ABOUT A CONVECTIVE SIGMET THAT CONTAINED A LINE OF T-STORMS REACHING 45000 FT ACROSS HIS ROUTE. THE PLT STATED THAT HE WANTED TO CONTINUE ON ROUTE & WOULD CHECK BACK LATER. ABOUT 20 MIN LATER THE PLT WAS WARNED THAT HE WAS ABOUT TO ENTER HEAVY PRECIP AND WAS OFFERED AN ESCAPE ROUTE. HIS LAST TRANSMISSION WAS 'OK FOUR ONE POP.' A FEW MINUTES LATER HIS TRANSPONDER CODE WAS LOST ON RADAR. THE ACFT WAS AT 9000 FT MSL AND EXPERIENCED INFLT SEPARATION OF BOTH WINGS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW87FA183
Event ID
20001213X31798
Case number
FTW87FA183
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: 73a002dac1a3083bb7c2fe658dd8174ea199215291422892511d82af15439773; retrieved 2026-09-21T04:02:59.937Z.