FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA061 · Piper PA-23-250

17 Feb 2003 · Miami, FL, United States

Piper PA-23-250 · Accident: in flight encounter with weather en route

From Miami Executive Airport (TMB) to South Bimini Airport (MYBS)

Report a problem

Event

NTSB case
MIA03LA061
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
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
N54835
Operator
Unknown
Onboard fatalities
Unknown
Route
From Miami Executive Airport (TMB), Miami, FLTo South Bimini Airport (MYBS), Bimini
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 · cruise
First occurrenceThe 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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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

  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

On February 17, 2003, about 0859, eastern standard time, the accident airplane, N54835, departed Kendall-Tamiami Executive Airport, Miami, Florida, and was later reported as not having arrived at its destination, Bimini, Bahamas. Instrument meteorological conditions prevailed in the area at the time, and a visual flight rules flight plan had been filed. Search and rescue assets later discovered an oil sheen and light airplane related debris, specific to the missing airplane, floating in the Atlantic Ocean, in the vicinity of geographic position 25 degrees 29 minutes north latitude, 079 degrees 58 minutes west longitude, 8 miles east of the Miami Harbor Entrance, Miami, Florida. The NTSB evaluated radar and other weather data, as well as radar track data for the flight, and the showed that after departure the accident airplane climbed to 4,500 feet, where it remained for about 45 seconds and at 0906:37, began a slow descent. The descent continued until the airplane was lost from radar, approximately 4 minutes later. The pilot of N54835 had received weather information for his intended route of flight from the Miami Automated International Flight Service Station (MIA-AIFSS) on five separate occasions before departing Tamiami. During the pilot's first communication with MIA-AIFSS, the weather briefer informed the pilot that rain showers and thunderstorms were predicted to precede a frontal system across the southern tip of Florida and move out past Nassau, Bahamas, later in the afternoon. The pilot told the briefer that based upon the outlook he did not plan on going but would call back to see if the conditions had improved. The pilot's last communication with MIA-AIFSS prior to departure occurred at 0825. During this conversation, the pilot noted that he had initially filed a flight plan, and had intended to depart at 0815. The briefer then told the pilot that there was activity beginning near Key Largo and extending to the southwest, but that at that time there was nothing significant along his route from Tamiami to Bimini. The briefer further added that the "Key Largo system" was moving slowly to the northeast. A half an hour passed between the end of this brief and the time that N54835 took off, during which time radar data shows that the system progressed to the northeast. The NTSB did not obtain any records to substantiate the pilot having obtained an instrument rating. The NTSB Meteorology Report has been included as an attachment to the factual report.

Probable cause

The non instrument-rated pilot-in-command's improper inflight planning/decision, and continued VFR flight into instrument meteorological conditions, which resulted in a loss of control during descent, and impact with water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA061
Event ID
20030225X00258
Case number
MIA03LA061
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 8d97e8b85a7c238bf2748b9759736d61839e680251f808aad492502be385164a; retrieved 2026-09-20T19:28:06.323Z.