MIA84FA126 · Cessna 402B
Associated Air Service Cessna 402B · Accident: missing aircraft
From Fort Lauderdale Hollywood International Airport (FLL) to South Bimini Airport (MYBS)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- MIA84FA126
- 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
- 6 · 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
- Unknown
Cessna 402B
- Aircraft type
- Cessna 402
- 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
- N44NC
- Operator
- Associated Air Service
- Onboard fatalities
- Unknown
- Route
- From Fort Lauderdale Hollywood International Airport (FLL), Fort Lauderdale, 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
- Unknown
- 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
- Missing aircraft
- 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
- Reason for occurrence undetermined
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THIS ACFT DISAPPEARED ON A FLT FROM FT LAUDERDALE, FL TO BIMINI, BAHAMAS. AFTER DEPARTURE, THE ACFT FLT PLAN WAS ACTIVATED BY RADIO. THIS WAS THE LAST COMMUNICATION WITH THE ACFT. AN ITAP RADAR READOUT REVEALED AN ACFT FLT THAT DEPARTED AT THE APPROPRIATE TIME. THIS TARGET HEADED FOR BIMINI, & AFTER ABOUT 10 MIN, SLOWED TO 90 KTS AIRSPEED. ABOUT 4 MINUTES LATER THE TARGET ENTERED A 5400 FPM RATE OF DESCENT AND DISAPPEARED OFF RADAR. TWO WITNESSES SAW AN ACFT CRASH INTO THE WATER NEAR BIMINI BETWEEN 0830 AND 0900 ON 3/31. THE MISSING ACFT DEPARTED FT LANDERDALE AT 0823 ON 3/31/84. THE INJURY INDEX & ACFT DAMAGE ARE PRESUMED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA84FA126
- Event ID
- 20001214X39093
- Case number
- MIA84FA126
- 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. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: a8b962a15f145daf47a84f56720dcfc664612ba803d9d6773ae42433718ca8b6; retrieved 2026-09-21T05:35:51.087Z.