15 Jun 2019: Piper PA32 260

15 Jun 2019: Piper PA32 260 (N2750Q) — Unknown operator

No fatalities • Crisfield, MD, United States

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.

— NTSB Determination

Accident 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 complete blood 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.

Contributing factors

  • cause Pilot
  • cause Pilot
  • Pilot

Conditions

Weather
VMC, wind 190/04kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.