FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19LA026 · Piper PA31T

25 Oct 2018 · Atlantic Ocean, AO, United States

Bulldog Flying Club Piper PA31T · Accident: inflight upset en route

From Andrews, SC (private airstrip) to Governor's Harbour Airport (MYEM)

Report a problem

Event

NTSB case
ERA19LA026
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
5 · 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
Visual Meteorological Cond

Piper PA31T

Aircraft type
Piper PA31
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
N555PM
Onboard fatalities
Unknown
Route
From Andrews, SC (private airstrip)To Governor's Harbour Airport (MYEM), Governors Hrbr.
Aircraft age
About 42 years (built 1976)
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 · climb to cruise
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
Inflight upset
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

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The two pilots and three passengers were conducting a cross-country flight over the ocean from South Carolina to the Bahamas. About 30 minutes into the flight, while climbing through 24,300 ft to 25,000 ft about 95 miles beyond the coast, the pilot made a garbled radio transmission indicating an emergency and intent to return. At the time of the transmission the airplane had drifted slightly right of course. The airplane then began a descent and returned on course. After the controller requested several times for the pilot to repeat the radio transmission, the pilot replied, "we're descending." About 15 seconds later, at an altitude of about 23,500 ft, the airplane turned sharply toward the left, and the descent rate increased to greater than 4,000 ft per minute, consistent with a loss of control. Attempts by the air traffic controller to clarify the nature of the emergency and the pilot's intentions were unsuccessful. About 1 minute after the sharp left turn and increased descent, the pilot again declared an emergency. No further communications were received. Search efforts coordinated by the U.S. Coast Guard observed an oil slick and some debris on the water in the vicinity of where the airplane was last observed via radar, however the debris was not identified or recovered. According to recorded weather information, a shallow layer favorable for light rime icing was present at 23,000 ft. However, because the airplane was not recovered, the investigation could not determine whether airframe icing or any other more-specific issues contributed to the loss of control.

One air traffic control communication audio recording intermittently captured the sound of an emergency locator transmitter (ELT) "homing" signal for about 45 minutes, beginning near the time of takeoff, and ending about 5 minutes after radar contact was lost. Due to the intermittent nature of the signal, and the duration of the recording, it could not be determined if the ELT signal had begun transmitting before or ceased transmitting after these times. Because ELT homing signals sound the same for all airplanes, the source could not be determined. However, the ELT sound was recorded by only the second of two geographic areas that the airplane flew through and began before the airplane arrived near either of those areas. Had the accident airplane's ELT been activated near the start of the flight, it is unlikely that it would be detected in the second area and not the first. Additionally, the intermittent nature of the ELT signal is more consistent with an ELT located on the ground, rather than an airborne activation. An airborne ELT is more likely to have a direct line-of-sight to one or more of the ground based receiving antennas, particularly at higher altitudes, resulting in more consistent reception.

The pilot's initial emergency and subsequent radio transmissions contained notably louder background noise compared to the previous transmissions. The source or reason for the for the increase in noise could not be determined.

Probable cause

An in-flight loss of control, which resulted in an impact with water, for reasons that could not be determined because the airplane was not recovered.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19LA026
Event ID
20181025X55256
Case number
ERA19LA026
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. 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: 70ed165f360b1d5560227f46e8335d8b04157edab519638d75876284533707e0; retrieved 2026-09-15T06:50:01.333Z.