No fatalities

15 Jun 2019: Piper PA32 260 (N2750Q) — Crisfield, MD

Crisfield, MD, United States

On 15 Jun 2019, a Piper PA32 260 (registration N2750Q) was involved in an aviation accident near Crisfield, MD. No fatalities were reported. Investigators recorded the probable cause as: The pilot's sudden incapacitation from an undiagnosed cardiac arrhythmia while on final approach, which resulted in descent and collision with trees and terrain. This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

A Piper PA-32-260 impacted trees while on approach to Crisfield-Somerset County Airport on June 15, 2019. The private pilot sustained minor injuries. No preimpact mechanical failure was reported.

Accident

On June 15, 2019, about 0415 eastern daylight time, a Piper PA-32-260, registration N2750Q, struck trees and terrain while on approach to Crisfield-Somerset County Airport (W41), Crisfield, Maryland. The private pilot, who was the sole occupant, sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed, and no flight plan was filed. The flight had originated from W41 about 5 minutes earlier.

Pilot Account

The pilot reported that he intended to perform a full-stop night landing before a planned departure at 0430. Very light winds favored runway 32, which had an inoperative precision approach path indicator (PAPI). After departing, he remained in the airport traffic pattern for runway 32. The crosswind and downwind legs were uneventful, with airport lights "crystal clear and fully illuminated." Shortly after turning onto the base leg, the airplane was at an altitude between 550 and 600 ft above ground level, and the airport was in sight. He announced turning onto the final leg for runway 32, with the airplane lined up perfectly and the runway visible. On final approach at what appeared to be a normal altitude, he "last recalled" being 1 mile from the runway 32 threshold. He then had a flash memory of waking up in the crashed airplane, seeing red lights and "major limbs in the cabin," adding that trees came through the cabin unseen until impact. The pilot regained consciousness during daylight, climbed out of the wreckage, and walked home. He indicated no preimpact mechanical failure or malfunction.

Aircraft and Site

An FAA inspector examined the wreckage the same day. The fuselage was resting on its left side in a ditch, with the left wing separated and in close proximity among trees. The right wing remained attached by control cables. The ditch was adjacent to trees at the southern end of an open field, and the accident site was located about 1,830 ft southeast of the runway 32 threshold.

Medical Information

In an email to the NTSB on September 12, 2019, the pilot provided information about a medical finding significant to the investigation. According to the NTSB Medical Factual Report, emergency room records and post-accident medical records through December 27, 2019 were obtained from the pilot's internist and cardiologist. Emergency room records showed the complete blood count and metabolic panel were not concerning, and no drug panel was ordered. On a visit to the internist about one month after the accident, the pilot reported the circumstances and denied falling asleep before the crash, but noted some dizziness since the crash. An electrocardiogram (EKG) showed a first-degree heart block, leading to a cardiac work-up including a stress echocardiogram and a 24-hour Holter monitor. On August 15, 2019, the Holter monitor revealed first-degree heart block and multiple episodes of complete heart block, notably at least one episode with a 3.5-second pause between heartbeats. Additional details are contained in the NTSB's public docket.

Contributing factors

Pilot