The U.S. aircraft register, updated daily
Accidents · NTSB WPR11LA058 · Final report

Bombardier INC CL-600-2C10 accident near Salt Lake City, Utah, November 24, 2010

On November 24, 2010 at about 5:20 am local time, a Bombardier INC CL-600-2C10, registered N614SK, was substantially damaged in an accident during pushback/towing near Salt Lake City, Utah (Salt Lake City airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 69 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The tug driver’s loss of airplane control during pushback due to a loss of traction in slippery conditions on the ramp. Contributing to the accident was the ground crews’ and airline operators’ inadequate guidance with regard to pushback procedures during low ground traction conditions with an inoperative airplane auxiliary power unit.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 24, 2010 · about 5:20 am local time
Place
Salt Lake City, Utah · Salt Lake City · map
Type
Accident
Injuries
No one was hurt; 69 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Bombardier INC CL-600-2C10
Registration
N614SK · registry record · serial 10051
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

The airplane was operating 2 hours behind schedule and had been dispatched with its auxiliary power unit (APU) inoperative, a condition that was permissible based on the approved Minimum Equipment List. The ramp area was covered in snow and ice, and it was snowing during aircraft loading and the subsequent pushback attempt. The captain started both engines while the airplane was at the gate, utilizing an external air-start cart in lieu of the APU. The captain stated that he started both engines due to a concern that, by starting one engine only, he would encounter control problems taxiing in the slippery conditions. He recognized that he could also have attempted to start the second engine in the alleyway after pushback using a cross-bleed engine start, but was concerned that attempting such a start would require increased engine thrust on the operating engine and could be disruptive to ground personnel and other traffic within the alleyway. During pushback, the tug was unable to gain enough traction to move the airplane and was subsequently replaced with a larger tug. The larger tug was able to push back the airplane; however, a short time later the thrust from the airplane's engines, which were running at idle, exceeded the traction available to the tug. The captain, seated in the left seat, experienced a sensation of unusual movement as the airplane began to overpower the tug, and he asked the tug driver if the driver still had control of the airplane. The tug driver confirmed that he had control; however, the airplane subsequently moved forward while still attached to the tug, which rotated to the right striking the airplane's fuselage. According to ground personnel and flight crew guidance, if the ramp surface conditions were such that adequate traction was not available, engine start should have been delayed until the pushback was complete. However, an engine start was required prior to pushback due to the inoperative APU. No guidance existed for either the flight or ground crew regarding pushback procedures in low traction ramp conditions with an inoperative APU.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during prior to flight
  2. Ground handling event during pushback/towing defining event

The NTSB's findings

  • Aircraft › Aircraft systems › Airborne APU system › (general) › Inoperative
  • cause Personnel issues › Task performance › (general) › (general) › Ground crew
  • factor Organizational issues › Management › Policy/procedure › Adequacy of policy/proc › Operator
  • factor Organizational issues › Management › Policy/procedure › Adequacy of policy/proc › Not specified
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Snow/slush/ice covered › Effect on equipment

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
  • Flight time: 10,066 hours in all; 6,846 in this make and model; 5,135 as pilot in command
  • Last flight review: July 25, 2010
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 3,317 hours in all; 2,135 in this make and model
  • Last flight review: January 7, 2009
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 20,574 hours
  • Last inspection: continuous airworthiness programme, November 22, 2010
  • Maximum gross weight: 75,000 lb
  • Seats: 69
  • Landing gear: retractable
  • Engine 1: General Electric CF34-8C5B1 (turbofan); 0 hours total
  • Engine 2: General Electric CF34-8C5B1 (turbofan); 0 hours total
  • Operator: Skywest Airlines INC

The flight

  • Departed from: SLC Salt Lake City UT at 4:50 am
  • Destination: OKC Oklahoma City OK
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 010° at 5 knots
  • Visibility: 2 statute miles
  • Sky: broken clouds at 1,600 ft; scat at 700 ft
  • Temperature: 19°F (-7°C), dew point 16°F (-9°C)
  • Altimeter: 29.80 inHg
  • Observation at 5:22 am from SLC

Injuries

FatalSeriousMinorNone
Cabi2
Flight crew67

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.