CHI83FA148 · Piper PA-32R-300
Piper PA-32R-300 · Accident: airframe, component or system failure during an uncontrolled descent
From Fort Worth Meacham International Airport (FTW) to University of Illinois Willard Airport (CMI)
Event
- NTSB case
- CHI83FA148
- 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
- Visual Meteorological Cond
Piper PA-32R-300
- Aircraft type
- Piper PA-32
- 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
- N1057Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Worth Meacham International Airport (FTW), FT. WORTH, TXTo University of Illinois Willard Airport (CMI), Champaign
- 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
- Uncontrolled descent
- 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
- Airframe, component or system failure
- 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 › Incapacitation(cardiovascular)
- Wing › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT EXPERIENCED AN IN-FLT BREAK-UP DURING DESCENT. THE PILOT HAD REPORTED ON THE RADIO TO KANSAS CITY ARTCC THAT HEWAS HAVING SEVERE CHEST PAINS AND SHORTNESS OF BREATH. RADAR CONTACT WITH THE PLANE WAS LOST AT 1425 CST. THE PILOT HAD REPORTED HE WAS MANUALLY FLYING THE ACFT. WITNESSES SAW THE ACFT COME OUT OF THE CLOUDS IN A SPIN. THEY SAW SEPARATE PIECES OF THE ACFT FALLING AFTER THE MAIN PORTIONS HAD DESCENDED. THEY HAD HEARD THE ENGINE SOUNDS WHICH MADE THE IMPRESSION THAT THE ACFT WAS DOING STUNTS. THE AUTOPSY REPORT STATED THAT THE CAUSE OF DEATH OF THE PILOT WAS ATHEROSCLEROTIC CORONARY ARTERY HEART DISEASE. THE PILOT HAD BEEN HOPITALIZED IN 10/92 DUE TO CHEST PAINS. HE WAS TESTED FOR CORONARY PROBLEMS. NO EVIDENCE OF CORONARY DISEASE WAS FOUND. HE WAS TREATED FOR HYPERTENSION BUT REPORTEDLY WOULD NOT TAKE HIS MEDICINE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI83FA148
- Event ID
- 20001214X42356
- Case number
- CHI83FA148
- 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: a49a691170b3d1fb13378733f51b53a98f94379cf70b7be37f69c04c0cd08655; retrieved 2026-09-21T07:02:11.277Z.