Mesa Airlines Flight 2763
Bombardier CL600 2D24 - 900 · Accident: ground collision during pushback
From San Antonio International Airport (SAT) to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- CEN14LA430
- 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
- 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 CL600 2D24 - 900
- Aircraft type
- Bombardier CL600
- 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
- N943LR
- Operator
- Mesa Airlines
- Onboard fatalities
- Unknown
- Route
- From San Antonio International Airport (SAT), San Antonio, TXTo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- Aircraft age
- About 8 years (built 2006)
- 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
- Pushback/towing
- 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
- Ground collision
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During pushback from the gate, the tug positioned the airplane on the taxiway. Before disconnecting, the tug reversed and the airplane rolled forward while still attached to the tug. As the airplane rolled past the tug, the tug impacted the left side of the fuselage. The tow bar pin was found sheared, but it could not be determined if the pin failed before or during the tow operation. Further, the operator did not have an immediate means of communicating with the flight crew the need to apply the brakes while the tug was still attached.
The tug operator's postaccident urine test was positive for marijuana, which indicated prior use. However, it could not be determined whether the tug operator was impaired by the effects of marijuana at the time of the event.
Probable cause
Failure of the tow bar shear pin, which resulted in the tug operator’s loss of control of the airplane during pushback operations. Contributing to the accident was the tug operator’s inability to communicate to the flight crew to apply the airplane’s brakes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA430
- Event ID
- 20140814X52213
- Case number
- CEN14LA430
- 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: e50f1eb201e1c138b2f4be8b634bde54859d2d897ca4e11419c429ef0591c1d1; retrieved 2026-09-16T01:38:30.092Z.