FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13LA019 · Piper PA-23-250

13 Oct 2012 · Charlotte Amalie, United States

Rainbow International Airlines Piper PA-23-250 · Accident: controlled flight into terrain/object (CFIT) en route

From Henry E. Rohlsen Airport (TISX) to Cyril E. King Airport (TIST)

Report a problem

Event

NTSB case
ERA13LA019
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
3 · 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
Visual Meteorological Cond

Piper PA-23-250

Aircraft type
Piper PA-23
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
N5553Y
Onboard fatalities
Unknown
Route
From Henry E. Rohlsen Airport (TISX), ChristianstedTo Cyril E. King Airport (TIST), Charlotte Amali
Aircraft age
Not recorded
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 · descent
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
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The accident airplane departed over water on a dark night and flew toward its destination airport at an altitude of about 1,700 feet above the water. Radar data showed that the airplane began a gradual descent on about the same heading before it leveled off at 200 feet above the water. The airplane continued at 200 feet above the water for another 18 seconds before its radar target disappeared about 5 miles from the destination airport.

The surviving passenger stated that she had flown with the pilot on this flight many times before. She stated that during the en route portion of the accident flight, the pilot flew progressively lower to "get under the weather." The passenger stated that she could see lights on the shore near the destination airport, and could see that it was raining. She recalled light turbulence and observed the pilot make his "usual" radio call. She next remembered the airplane "hitting a wall," and the airplane filled with water. She said that the pilot broke the window on his side of the airplane, and that she and the pilot egressed through it. She did not see any of the other occupants of the airplane after that. When asked if she noticed anything unusual with the flight or if the pilot provided any warning before striking the water, the passenger said no, and indicated that everything was normal.

Examination of the wreckage revealed damage consistent with a high-speed, shallow-angle impact with water, and no evidence of preimpact mechanical anomalies.

Weather data and imagery were consistent with the passenger’s account of flying beneath outer rain bands associated with a developing tropical storm southeast of the accident site. There was little to no illumination from the moon. Based on a search of flight service and commercial vendor records, the pilot did not obtain a weather briefing or file a flight plan before the accident flight.

The destination airport was tower-controlled, but the tower was closed at the time of the accident. The runway was located along the shore, with the approach end surrounded by water on three sides. Multiple instrument approach procedures were available for the airport; however, those instrument approaches were not authorized while the tower was closed. A caution printed in the plan view of the approach charts stated, "CAUTION: Pilots may encounter false illusory indications during night approaches to Runway 10 when using outside visual cues for vertical guidance."

It is likely that the pilot descended the airplane to remain clear of the lowering clouds and descended into the water due to the lack of visual cues.

Probable cause

The pilot's attempted visual flight rules (VFR) flight into marginal VFR conditions on a dark night over water and his failure to maintain sufficient altitude, which resulted in the airplane’s controlled flight into water. Contributing to the accident was the pilot's inadequate preflight weather planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13LA019
Event ID
20121015X92424
Case number
ERA13LA019
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, coordinates. 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: c890995600c4d61f113e0feeaf1285b7d14626b4ccf9727591334ca1e414b647; retrieved 2026-09-14T15:46:06.957Z.