ATL92LA133 · Cessna 402B
Jefferson Airplane Cessna 402B · Accident: airframe, component or system failure en route
Event
- NTSB case
- ATL92LA133
- 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
- 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
- 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
- N910WT
- Operator
- Jefferson Airplane
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Airframe, component or system failure
- 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
- Door, emergency exit › Separation
- Unknown › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE WAS BEING FLOWN FOR THE FIRST TIME FOLLOWING REPAINTING. AFTER LEVELING OFF AT CRUISE ALTITUDE, THE PILOT HEARD WIND NOISE FROM THE CABIN & NOTED THAT THE BOTTOM OF THE EMERGENCY EXIT DOOR WAS AJAR. SHORTLY AFTERWARD IT DEPARTED THE FUSELAGE & STRUCK THE LEADING EDGE OF THE HORIZONTAL STABILIZER. AN UNEVENTFUL LANDING WAS COMPLETED. EXAMINATION OF THE AIRPLANE REVEALED THAT THE EXIT HAD BEEN MIS-RIGGED. DURING THE LAST ANNUAL INSPECTION, THE SEAL FOR THE UPPER CABIN DOOR WAS REPLACED BUT, THERE WAS NO INDICATION OF WORK ON THE EMERGENCY EXIT. THE RECORDS FOR THE RECENT REPAINTING OF THE AIRPLANE DID NOT REVEAL ANY WORK THAT REQUIRED THE REMOVAL OF THE EMERGENCY EXIT.
Probable cause
THE IMPROPER INSTALLATION OF THE EMERGENCY EXIT, BY AN UNKNOWN PERSON, WHICH RESULTED IN ITS SEPARATION, IN FLIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92LA133
- Event ID
- 20001211X14782
- Case number
- ATL92LA133
- 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 local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: df11d683cfba10350bda72cf4d83e84961fd463d0375deaa7f9822ec1c78cda9; retrieved 2026-09-23T03:00:06.391Z.