ERA16FA001 · Piper PA32R 301
Piper PA32R 301 · Accident: aircraft structural failure during an uncontrolled descent
From Warsaw Municipal Airport (ASW) to Oconee County Regional Airport (CEU)
Event
- NTSB case
- ERA16FA001
- 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
- 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
- Instrument Meteorological Cond
Piper PA32R 301
- Aircraft type
- Piper PA32
- 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
- N782TM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Warsaw Municipal Airport (ASW), Warsaw, INTo Oconee County Regional Airport (CEU), Clemson, SC
- Aircraft age
- About 31 years (built 1984)
- 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
- Defining eventThe 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
- Aircraft structural 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
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Nearing the conclusion of a cross-country, instrument flight rules flight in instrument meteorological conditions, the private pilot was entering a procedure turn in advance of conducting an instrument approach to the destination airport. The pilot reported to air traffic control that he was outbound on the procedure turn but did not subsequently report when the airplane was inbound. Shortly thereafter, a military flight on the frequency reported hearing a "mayday" call and that the airplane was "going down." No further communications were received from the accident airplane. Radar and GPS data showed the airplane in a right, rapidly descending spiral. Witness statements and the distribution of the wreckage indicated that the airplane experienced an in-flight breakup. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Fractures to the right wing and stabilator were consistent with overstress and likely occurred during an attempted recovery from the descending spiral.
The pilot's autopsy revealed severe atherosclerosis in the vasculature of the brain and heart. There was near-total occlusion of the right frontal and middle cerebral arteries. In the heart, the left anterior descending coronary had 80% occlusion, while both the right and circumflex coronary arteries showed 40% atheromatous occlusion. In addition, the myocardium displayed indications that the pilot had experienced a previous heart attack. The pilot's wife was unaware of a previous heart attack or heart condition, and the pilot had not reported any heart issues to the Federal Aviation Administration.
The pilot had very low levels of pseudoephedrine in his system at the time of the accident. Although his use of this powerful vasoconstrictor may have further increased his risk of an acute cardio- or cerebro-vascular event, given the low levels, it is unlikely that any direct psychoactive effect of the drug contributed to the accident. Finally, the pilot had 0.06 ug/ml of chlorpheniramine, a sedating antihistamine, in his postmortem blood. Although the pilot lost control of the airplane, there was no evidence of impaired behavior or decision-making before the loss of control. Therefore, it is unlikely that the sedating effects of the chlorpheniramine contributed to this accident.
Given the circumstances of the accident and pilot's cardiac conditions, it is possible that he became acutely incapacitated by a sudden cardio- or cerebro-vascular event and that could have resulted in the loss of airplane control. Because the pilot suffered fatal blunt force injuries within a few minutes after symptoms began, no findings indicating the acute event would be expected to be visible on autopsy, and none were found; thus, it could not be determined whether the loss of control was the result of incapacitation or if there was another reason that the airplane departed controlled flight and the pilot was unable to regain control.
Probable cause
The pilot's loss of airplane control for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA001
- Event ID
- 20151002X84211
- Case number
- ERA16FA001
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: f4a6fd9382250d145c0b740f37448bc9a773c49bd988c95dc936e7eee036b6fa; retrieved 2026-09-14T21:31:53.722Z.