M2 Aircraft Management British Aerospace BAE JETSTREAM 3101 incident
British Aerospace BAE JETSTREAM 3101 · Incident: part(s) separation from aircraft during initial climb
From Kansas City International Airport (MCI) to Willow Run Airport (YIP)
Event
- NTSB case
- CEN12IA592
- 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
- Incident
- 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
British Aerospace BAE JETSTREAM 3101
- Aircraft type
- British Aerospace BAE JETSTREAM 3101
- 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
- N695MA
- Operator
- M2 Aircraft Management
- Onboard fatalities
- Unknown
- Route
- From Kansas City International Airport (MCI), Kansas City, MOTo Willow Run Airport (YIP), Ypsilanti, MI
- 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
- Initial climb
- 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
- Minor
Cause areas
- Aircraft › Aircraft structures
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight crew reported that they heard a “bang” followed by a caution light for the cargo door. The flight crew diverted the airplane and performed a precautionary landing without incident. Upon landing, it was determined that a section of the cargo door was missing. The pilot subsequently reported that the door latch was not properly fastened. The pilot indicated that there were no mechanical malfunctions and that the door, which was not fastened, came off after takeoff. The missing section was not located.
Probable cause
The flight crew’s failure to ensure that the cargo door was properly fastened before departure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12IA592
- Event ID
- 20120830X14810
- Case number
- CEN12IA592
- 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. 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: 8566c279fa1310f6b0be63f1c7e73d0ff86f986dd29267107ee0e80f4f43434b; retrieved 2026-09-15T19:35:19.938Z.