FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17FA181 · Mitsubishi MU2B 40

15 May 2017 · Eleuthera, Bahamas

Mitsubishi MU2B 40 · Accident: loss of control in flight en route

From Rafael Hernández International Airport (TJBQ) to Space Coast Regional Airport (TIX)

Report a problem

Event

NTSB case
ERA17FA181
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
4 · all aircraft and ground
Ground fatalities
Unknown
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

Mitsubishi MU2B 40

Aircraft type
Mitsubishi MU2
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
N220N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rafael Hernández International Airport (TJBQ), Aguadilla, PRTo Space Coast Regional Airport (TIX), Titusville, FL
Aircraft age
About 36 years (built 1981)
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 · 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
Loss of control in flight
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

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

NTSB narrative

The commercial pilot and three passengers were making a personal cross-country flight over ocean waters in the MU-2B airplane. During cruise flight at flight level (FL) 240, the airplane maintained the same relative heading, airspeed, and altitude for about 2.5 hours before radar contact was lost. While the airplane was in flight, a significant meteorological information notice was issued that warned of frequent thunderstorms with tops to FL440 in the accident area at the accident time. Satellite imagery showed cloud tops in the area were up to FL400. Moderate or greater icing conditions and supercooled large drops (SLD) were likely near or over the accident area at the accident time. Although the wreckage was not located for examination, the loss of the airplane's radar target followed by the identification of debris and a fuel sheen on the water below the last radar target location suggests that the airplane entered an uncontrolled descent after encountering adverse weather and impacted the water.

Before beginning training in the airplane about 4 months before the accident, the pilot had 21 hours of multiengine experience accumulated during sporadic flights over 9 years. Per a special federal aviation regulation, a pilot must complete specific ground and flight training and log a minimum of 100 flight hours as pilot-in-command (PIC) in multiengine airplanes before acting as PIC of a MU-2B airplane. Once the pilot began training in the airplane, he appeared to attempt to reach the 100-hour threshold quickly, flying about 50 hours in 1 month. These 50 hours included about 40 hours of long, cross-country flights that the flight instructor who was flying with the pilot described as "familiarization flights" for the pilot and "demonstration flights" for the airplane's owner. The pilot successfully completed the training required for the MU-2B, and at the time of the accident, he had accumulated an estimated 120 hours of multiengine flight experience of which 100 hours were in the MU-2B. Although an MU-2B instructor described the pilot as a good, attentive student, it cannot be determined if his training was ingrained enough for him to effectively apply it in an operational environment without an instructor present. Although available evidence about the pilot's activities suggested he may not have obtained adequate restorative sleep during the night before the accident, there was insufficient evidence to determine the extent to which fatigue played a role in his decision-making or the sequence of events.

The pilot's last known weather briefing occurred about 8 hours before the airplane departed, and it is not known if the pilot obtained any updated weather information before or during the flight. Sufficient weather information (including a hazardous weather advisory provided by an air traffic control broadcast message about 25 minutes before the accident) was available for the pilot to expect convective activity and the potential for icing along the accident flight's route; however, there is no evidence from the airplane's radar track or the pilot's communications with air traffic controllers that he recognized or attempted to avoid the convective conditions or exit icing conditions.

Probable cause

The pilot's intentional flight into an area of known icing and convective thunderstorm activity, which resulted in a loss of control of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA181
Event ID
20170517X95558
Case number
ERA17FA181
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: c396d7f2b0fd5546fb65885ae6149d085fc225d8e4df3e5423f5d4b719eac1b8; retrieved 2026-09-15T06:02:36.279Z.