Barken Interl Learjet 35 accident
Learjet 35 · Accident: airframe, component or system failure during initial climb
From an unrecorded airport to Portland International Airport (PDX)
Event
- NTSB case
- SEA83FA121
- 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
- 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
Learjet 35
- Aircraft type
- Learjet 35
- 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
- N1976L
- Operator
- Barken Interl
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Portland International Airport (PDX), Portland, OR
- 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
- 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, passenger › Open
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Visual/aural perception
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT DRAGGED THE RIGHT WING TIP TANK AND RUPTURED IT AFTER THE PASSENGER DOOR OPENED DURING TAKEOFF. DURING THE ABORTED TAKEOFF THE ACFT OSCILLATED RIGHT, LEFT AND RIGHT BEFORE MAKING GROUND CONTACT ON THE RIGHT WING. THE HIGHEST ALT ATTAINED WAS ABOUT 100 FT AGL. BEFORE TAKEOFF A PUROLATOR CARGO HANDLER INTERRUPTED THE CAPTAIN CLOSING THE DOOR TO GIVE HIM A PACKAGE. THE CAPT WENT TO SECURE THIS PACKAGE AND THE CARGO HANDLER CLOSED THE DOOR. AFTER THE CAPT WAS IN HIS SEAT HE AND THE CO-PILOT FAILED TO NOTE THE RED DOOR WARNING LIGHT MENTALLY REGARDING IT AS A MALFUNCTIONING FUEL WARNING EVEN THOUGH THESE LIGHTS ARE SEPARATED BY 3 OTHER LIGHTS. DURING THE TAKEOFF AT ABOUT 110 KTS THE DOOR OPENED AND THE ABORT COMMENCED. THE CARGO HANDLER WAS INTERVIEWED AND ADMITTED CLOSING THE DOOR BUT SAID HE NEVER LATCHED THE DOOR SINCE IT REQUIRES A KEY TO ACTIVATE IT. THIS WAS ALWAYS DONE BY THE CREW.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA83FA121
- Event ID
- 20001214X43522
- Case number
- SEA83FA121
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: fdf50a63b388be01abb5baa079790812e4bc2647ec51a5b91a0e2da4d851896f; retrieved 2026-09-18T20:58:03.871Z.
- The NTSB's operator name is blank for N1976L; the operator shown is the name the NTSB records it doing business as.