Bimini Island Air Cessna 402B accident
Cessna 402B · Accident: system/component malfunction/failure (non-power) during landing
From Grand Bahama International Airport (MYGF) to Fort Lauderdale Executive Airport (KFXE)
Event
- NTSB case
- MIA08LA079
- 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
- 0 · 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
- Charter & commuter
- 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
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
- N300SH
- Operator
- Bimini Island Air
- Onboard fatalities
- Unknown
- Route
- From Grand Bahama International Airport (MYGF), FreeportTo Fort Lauderdale Executive Airport (KFXE), Fort Lauderdale, FL
- 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 135: Air Taxi & Commuter
- 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
- Landing · landing roll
- 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
- System/component malfunction/failure (non-power)
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during approach, he observed only two down and locked indications for the nose and left main landing gear. The pilot's attempts to get the right main landing gear down and locked indication were unsuccessful, and a visual inspection of the landing gear by an air traffic controller revealed that the landing gear appeared to be down and locked. During the landing, the right main landing gear collapsed. Examination of the airplane revealed that the right main landing gear down lock micro switch was loose and not fully closed. Review of the operator's records and interviews of the operator's maintenance personnel revealed that several days prior to the accident, they made an improper adjustment to the right "side brace lock link," which was beyond the manufacturer's specifications, and prevented the right main gear to lock in the down position. In addition, after the adjustment, the maintenance personnel did not perform functional checks as required by the manufacturer's instructions.
Probable cause
The improper adjustment of the right main landing gear down lock by maintenance personnel resulting in the gear collapse during the landing roll..
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08LA079
- Event ID
- 20080408X00438
- Case number
- MIA08LA079
- 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: eec35dcbaced6da590cee7b31aa83d3e9bbb61c6136be6082cb9034ccd840bba; retrieved 2026-09-15T09:30:34.007Z.