ERA19LA197

NTSB accident investigation · Piper PA32 · Crisfield, MD · June 15, 2019

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
June 15, 2019, 04:15 local (08:15 UTC)
Place
Crisfield, MD
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2750QPiper PA32
Defining event
Approach-VFR pattern final: Miscellaneous/other
Weather
Visual (VMC) · Night
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20190615007029A
Case key
99671

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's sudden incapacitation from an undiagnosed cardiac arrhythmia while on final approach, which resulted in descent and collision with trees and terrain.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot departed with the intention of remaining in the traffic pattern to perform one full-stop night landing before proceeding on a planned instrument flight rules cross-country flight. After takeoff, he remained in the traffic pattern and turned onto the final approach leg. He last recalled being about 1 mile from the runway threshold, then had a brief recollection of trees being in the cockpit. He awoke several hours later, exited the wreckage of the airplane, and walked to his house, where help was summoned. He reported that, to the best of his knowledge, there was no preimpact mechanical failure or malfunction. The pilot's description was consistent with unwitnessed temporary loss of consciousness during the landing approach. While there was no toxicology to support an alternative cause, a cardiac evaluation 2 months after the accident revealed that the pilot had intermittent complete heart block with prolonged pauses between heartbeats, which can lead to fainting. Additional cardiac tests showed normal coronary arteries but revealed that the pilot had cardiac sarcoidosis. The pilot denied having syncopal events prior to the accident and reported no symptoms before losing consciousness. His medical records contained no mention of any sarcoid disease. Given the natural course of cardiac sarcoidosis, the pilot's sudden incapacitation from complete heart block would not have been predicted. Thus, it is likely that the pilot experienced sudden incapacitation from an undiagnosed arrhythmia.

Factual narrative

On June 15, 2019, about 0415 eastern daylight time, a Piper PA-32-260, N2750Q, impacted trees and terrain while on approach to Crisfield-Somerset County Airport (W41), Crisfield, Maryland. The private pilot sustained minor injuries. The airplane was operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time and no flight plan was filed for the flight that originated about 5 minutes earlier from W41. In statements provided to the Federal Aviation Administration (FAA), Maryland State Police, and also National Transportation Safety Board (NTSB), the pilot reported that he intended to perform one full-stop night landing in advance of a flight planned to depart W41 at 0430. Very light winds favored runway 32 which had an inoperative precision approach path indicator (PAPI). He departed and remained in the airport traffic pattern for runway 32. The crosswind and downwind legs of the airport traffic pattern were uneventful with the airport lights "crystal clear and fully illuminated." Shortly after turning onto the base leg of the airport traffic pattern, the airplane's altitude was between 550 and 600 ft above ground level and he had the airport in sight. He announced turning onto the final leg of the airport traffic pattern for runway 32 and was lined up perfectly with the runway with the airplane landing lights on, and the runway in sight in front of him. While on the final approach of the airport traffic pattern at what appeared to be normal altitude he "last recalled" being 1 mile from the runway 32 threshold and he had 1 flash memory that sometime between his final call and waking up in the crashed airplane, seeing red lights, and "major limbs in the cabin", adding that, "…all [of a] sudden trees came through the cabin (unseen until the impact)." The pilot regained consciousness during daylight, climbed out of the wreckage and walked to his home. The pilot indicated on the submitted NTSB Pilot/Operator Aircraft Accident/Incident Report that to the best of his knowledge there was no preimpact mechanical failure or malfunction. The FAA inspector who examined the wreckage the same day reported the fuselage was resting on its left side in a ditch with the left wing separated and in close proximity among trees, while the right wing remained attached by control cables. The ditch was adjacent to trees at the southern end of an open field, with the accident site located about 1,830 ft southeast of the runway 32 threshold. In an e-mail from the pilot to NTSB on September 12, 2019, he provided information regarding a medical finding that was significant to the investigation. He was asked for and provided the requested medical information. 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. The emergency room records revealed the completeblood count and metabolic panel were not concerning and no drug panel was ordered. On his first visit to the internist about 1 month after the accident, which appeared to be his routine 6-month follow-up from an earlier exam, the pilot reported the circumstances of the accident and denied falling asleep before the crash, and stated he still had some dizziness since the crash. An electrocardiogram (EKG) at this visit showed a first degree heart block and the internist ordered a cardiac work-up that included a stress echocardiogram and a 24-hour halter monitor for the pilot. On August 15, 2019, the 24-hour halter monitor showed first degree heart block and multiple episodes of complete heart block, notably at least one episode with a 3.5 second pause between heartbeats. For additional information please see the Medical Factual Report contained in the NTSB's public docket for this investigation.

Aircraft

Registration
N2750Q
Reported as
Piper PA32 (260)
Category
Airplane
Serial number
32-7700014
Built
1977
Airframe hours
6,153.8
Engine
Lycoming O-540-E4B5, 260 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · November 12, 2018
Departed
W41 · Crisfield, MD
Destination
W41 · Crisfield, MD
Airport
W41 · Crisfield-Somerset County Arpt, runway 32, 2,397 × 75 ft, asphalt
Equipment
Handheld GPS, Onboard weather, Stall warning system, ADS-B, Auto-pilot, Electronic flight bag or handheld device

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
65
Injuries
Minor
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
June 4, 2019
Seat
Left
Restraint
3-point
Flight hours
1,253.5 total · 193.8 in this make and model · 1,127 as pilot in command · 33.7 in the last 90 days · 18 in the last 30 days · 0.1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night
Wind
190° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
57 °F, dew point 54 °F
Altimeter
30.15 inHg
Observed at
MFV, 22 nm away

Docket · 6

The files NTSB released with the investigation on October 9, 2020, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.2 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.