BOMBARDIER INC CL-600-2C10SKYWEST AIRLINES INC
What the docket says, assembled. No language model is involved, so nothing on this page can be invented — every line traces to a recorder, a report page or the Board's own record.
Ask the docket
passages, not paraphrasesEvery answer is a passage of the docket with the page it came from, or the words “not in the docket”. Nothing is summarised or reasoned for you — read the source.
One timeline
0 timed factsthe recorder events from the FDR report, with the transcript's warnings, callouts, the words nearest each event and the final seconds — on one clock, as printed in each reportNo timed facts: this docket has no extracted recorder sequence and no transcript.
- approximately 2150 mountain standard timeDelta Connection flight 4543, a Bombardier CL-600-2C10, N614SK, collided with a tug during push-back from the gate at Salt Lake City International Airport, Salt Lake City, Utah.
- Prior to flight: Sys/Comp malf/fail (non-power)→
- Pushback/towing: Ground handling event
Precedents
8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded- Airbus A320 · Frontier AirlinesDenver, CO
- ●Personnel issues › Task performance › (general)
Ground handling event - BEECH 1900DSt. Louis, MO
- ●Organizational issues › Management › Policy/procedure
- ●Personnel issues › Task performance › (general)
- MCDONNELL DOUGLAS AIRCRAFT CO MD-88 · DELTA AIR LINES INCAtlanta, GAGround handling event
- BOEING 757-222 · United AirlinesLos Angeles, CAGround handling event
- BOMBARDIER CL600 2D24 - 900 · MESA AIRLINES INCSan Antonio, TXmatched on what happened, as the Board wrote it · same aircraft family
- BOMBARDIER DHC8 · Piedmont AirlinesNewark, NJ
- ●Organizational issues › Management › Policy/procedure
Sys/Comp malf/fail (non-power) - BOEING 737-3H4 · SOUTHWEST AIRLINES COLos Angeles, CAGround handling event
- Bombardier, Inc. CL-600-2C10 · United ExpressSan Francisco, CA
- ●Organizational issues › Management › Policy/procedure
What the record says
a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable cause- 3 of 8Personnel issues › Task performance › Communication (personnel)
- 3 of 8Personnel issues › Task performance › Use of equip/info
- 2 of 8Personnel issues › Task performance › (general)cited here too
- 2 of 8Organizational issues › Management › Policy/procedurecited here too
- 2 of 8Personnel issues › Action/decision › Action
- 4 of 8Ground handling event
- 3 of 8Ground collision
- Management › Policy/procedure
- Task performance › (general)
- —
- Action/decision › Action
- Task performance › Communication (personnel)
- Task performance › Use of equip/info
A teaching device, not a verdict: what the record would have looked at, next to what the Board found.
- DCA19CA0792019-01-28 · Airbus A320 · Frontier Airlines
loss of control of the tug by the driver during pushback operations as a result of the contaminated ramp, angle of the towbar, and the airplane engines being at idle thrust.
- DEN08LA1512008-09-07 · BEECH 1900D
The ground crew's failure to ensure airplane clearance from the building while parking the airplane. Contributing to the accident was the flight crew's unprofessional behavior and the lack of marshaling procedures for the ground crew.
- ERA12CA0382011-10-07 · MCDONNELL DOUGLAS AIRCRAFT CO MD-88 · DELTA AIR LINES INC
The tug driver's inadequate control of the tug while maneuvering the airplane during pushback.
- WPR11LA3002011-05-31 · BOEING 757-222 · United Airlines
The ground crewmembers’ failure to follow proper procedures for removing a stuck or jammed tow bar, which resulted in a ground crew injury.
- CEN14LA4302014-08-09 · BOMBARDIER CL600 2D24 - 900 · MESA AIRLINES INC
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.
This is the pattern in the NTSB’s own record across similar accidents — which findings it cited, what it coded, what it recommended. It is drawn from the record, not written about this case, and it never assigns blame: investigations exist to prevent the next accident (ICAO Annex 13).