Mesa Airlines Flight 2705
Bombardier, Inc. CL-600-2B19 · Incident while standing
From Los Angeles International Airport (LAX) to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- LAX07IA191
- 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
- Airline
- 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
Bombardier, Inc. CL-600-2B19
- Aircraft type
- Bombardier 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
- N7264V
- Operator
- Mesa Airlines
- Onboard fatalities
- Unknown
- Route
- From Los Angeles International Airport (LAX), Los Angeles, CATo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- 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 121: Air Carrier
- 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
- Standing · engine(s) not operating
- 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
- Miscellaneous/other
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Door, passenger › Jammed
- Maintenance, adjustment › Improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
At the completion of a flight, the airplane taxied to the arrival gate whereupon the flight attendant attempted to open the airplane's main passenger cabin door. Unable to open the door to allow the passengers to disembark, the flight attendant requested and received assistance from the first officer. He was similarly unable to open the door, which was jammed in the closed position, and a mechanic was summoned. The mechanic entered the airplane via the galley service door. The mechanic manipulated the cabin door opening lever from inside the passenger cabin, and he successfully opened the door. Maintenance personnel subsequently examined the door and found it was out of adjustment (rig), and some internal components were inoperative. Under certain conditions these anomalies rendered the door dysfunctional. Neither the operator's maintenance program, nor the manufacturer's response to the repeated jamming events had adequately resolved the recurring discrepancy.
Probable cause
An out of rig/jammed door. Contributing to the incident was the operator's inadequate maintenance program and the airframe manufacturer's inadequate response to the issue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07IA191
- Event ID
- 20070627X00819
- Case number
- LAX07IA191
- 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, damage. 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: a93461635dfdfe9359c1351c5a0ac31a8ca9c8d7d413eff4f74660470f453ee3; retrieved 2026-09-18T14:43:54.148Z.