FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA356 · Canadair Ltd CL-600-2B16

23 May 2012 · Hallandale, FL, United States

Majestic Jet Canadair Ltd CL-600-2B16 · Accident: part(s) separation from aircraft en route

From Miami-Opa Locka Executive Airport (OPF) to Pompano Beach, FL

Report a problem

Event

NTSB case
ERA12LA356
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
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

Canadair Ltd CL-600-2B16

Aircraft type
Canadair CL-600
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
N207JB
Operator
Majestic Jet
Onboard fatalities
Unknown
Route
From Miami-Opa Locka Executive Airport (OPF), Opa Locka, FLTo Pompano Beach, 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 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
Part(s) separation from aircraft
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 structures
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

About 3 minutes into the positioning flight, at 3,000 feet, the flight crew heard a "loud bang" and became aware that the main passenger door had separated from the airplane. The pilot declared an emergency, diverted to a nearby airport, and landed without further incident. The separated passenger door was subsequently found on a nearby golf course.

The co-pilot reported in a written statement that he closed the main passenger door and checked for a green light to ensure that it was secure. In a subsequent interview, he reported that he "believed" that the door warning lights were working, but he could not positively recall seeing the "Door Safe" light illuminated after closing the door. He also did not remember activating the "Recall" switch before takeoff.

Ramp security video showed that the main passenger door appeared to close; it then re-opened momentarily and closed again before the airplane taxied out of the ramp area. The co-pilot reported that he re-closed the door because it did not secure on the first attempt. An examination of the recovered door and the door frame did not reveal evidence of a pre-existing mechanical malfunction or failure that would have precluded normal operation. The top half of the door was crushed from the impact with the ground, which prevented establishing the condition of door rigging before the accident. An examination of the fuselage revealed a skin puncture that matched the location of the door pull-out handle and is consistent with the door being in the open position when the puncture occurred. Although the door's external handle was found in the closed position, smudging on the fuselage was consistent with the handle's movement from the open to the closed position during impact with the fuselage.

Although it is apparent from the cockpit voice recording that the flight crew referenced the pilot checklist at some stages during ground operations, crew challenge and response items were sporadically mentioned. After the sound of the passenger door closing, neither crewmember mentioned the door warning lights. At no point during ground operations through the takeoff sequence were the doors, door warning lights, or master caution system mentioned. The co-pilot mentioned the "Annunciator" check in the Before Takeoff checklist; however, no "Recall" response was noted on the recording. Activating the recall switch would have alerted the flight crew to an unsecured door before takeoff.

Probable cause

The failure of the co-pilot to properly close and latch the passenger door before departure, and the flight crew's failure to ensure that the door was secure by using the door warning system. Contributing to the accident was the flight crew's inadequate use of checklists.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA356
Event ID
20120523X04047
Case number
ERA12LA356
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: 977ae5ed17dc52a42bd492f475ad33353aa940fcdbd2d4ee2c431f9b3e60ed74; retrieved 2026-09-15T18:13:50.129Z.