NYC99FA163 · Piper PA-31T
Piper PA-31T · Accident: loss of control in flight en route
From Jonesboro Municipal Airport (JBR) to Shenandoah Valley Regional Airport (SHD)
Event
- NTSB case
- NYC99FA163
- 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-31T
- Aircraft type
- Piper PA-31
- 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
- N602RM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jonesboro Municipal Airport (JBR), Jonesboro, ARTo Shenandoah Valley Regional Airport (SHD), WEYER'S CAVE, VA
- 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 · 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
- Loss of control in flight
- 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
- Tree(s)
- 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 control, not maintained
- Pilot in command › Incapacitation(cardiovascular)
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was descending the airplane from 23,000 feet for an instrument approach. All communications were normal until after he acknowledged an instruction to contact approach control, when radio contact was lost. Radar contact ceased at 11,300 feet due to radar signal reception difficulties. Contact was lost almost directly over the eventual impact site, which was on the eastern side of a small valley. Witnesses on the western side of the valley had seen the airplane flying near them, at treetop level, eastbound, and clear of clouds. About the same time, on the eastern side of the valley where the airplane would impact trees, then terrain, there was heavy rain. The commercial pilot had about 1,850 total flight hours, and had completed a 'Wings III' flight proficiency program and an instrument proficiency program about two months earlier. The airplane had been on a continuous maintenance program. At the accident site, all of the airplane's control surfaces were found, and the engines and propellers displayed signatures consistent with being under power at impact. There were insufficient remains to conduct an autopsy or toxicological testing. Previously, the pilot's father, two uncles, and a male cousin had suffered fatal heart attacks.
Probable cause
Loss of control of the airplane due to pilot incapacitation following a heart attack.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99FA163
- Event ID
- 20001212X19328
- Case number
- NYC99FA163
- 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: 2c1f803fd73ba02c5a57738471001947d4e8716a2ffd566e2c015c8489154c20; retrieved 2026-09-20T22:01:29.349Z.