Plane crash map Locate crash sites, wreckage and more

N614SK accident description

Utah map... Utah list
Crash location 40.788333°N, 111.977778°W
Nearest city Salt Lake City, UT
40.760779°N, 111.891047°W
4.9 miles away
Tail number N614SK
Accident date 23 Nov 2010
Aircraft type Bombardier Inc CL-600-2C10
Additional details: None

NTSB Factual Report

HISTORY OF FLIGHT

On November 23, 2010, about 2220 mountain standard time, a Bombardier CL-600-2C10 (CRJ), N614SK, operated by SkyWest Airlines as Delta Connection flight 4543, collided with a tow tractor during pushback from gate B4 at Salt Lake City International Airport (SLC), Salt Lake City, Utah. The 2 flight deck crewmembers, 2 flight attendants, 65 passengers, and ground handling crew were not injured. The airplane sustained substantial damage to the lower fuselage skin and multiple belly stringers. The scheduled passenger flight was operating on an instrument flight plan and was destined for Will Rogers World Airport (OKC), Oklahoma City, Oklahoma, under the provisions of 14 Code of Federal Regulations Part 121. Night instrument meteorological conditions prevailed. The flight was delayed prior to the accident, with a scheduled departure time of 2000.

SkyWest Airlines is a regional airline headquartered in St. George, Utah. The airline serves as a feeder airline and operates under contract with various major carriers. The accident flight was performed under a code sharing agreement with Delta Air Lines, Inc. Ground handling duties at the time of the accident were performed by agents from Delta Air Lines, Inc. The airplane was dispatched with the auxiliary power unit (APU) inoperative, a condition which is permissible based on the airplane's Minimum Equipment List (MEL), and which requires that one or both engines be started utilizing an external air-start cart or a precharged air bottle.

The airplane load agent, who was responsible for driving the tow tractor, stated that snow was falling during the loading and pushback sequence. He reported that during loading he observed a member of the flight crew performing an external preflight inspection.

Once the airplane had been loaded, he began to prepare for pushback. He was seated in the tow tractor, which was configured as a pushback tug and connected to the airplane's nose wheel utilizing a tow bar. He was in communication with the flight crew via the interphone, and stated that the crew could see him from their position on the flight deck. The captain requested an, "air-start" at the gate, and reported that he was going to start both engines. The engines were then started and the captain reported that the brakes were released and they were clear to commence the pushback. The driver then began the process of pushing the airplane back, but the wheels of the tug slipped and the airplane would not move. He subsequently informed the flight crew, and he decided to use a larger tug. With the larger tug attached, he began the pushback. The airplane subsequently started moving, and they began to back out of the gate area towards the alleyway. He was about to begin the turn into the alleyway, when the airplane started to skid to the left in the direction of the turn. He reported that the airplane then began to move forward, towards the tug, pushing it to the right side of the airplane. The driver stated that about this time, the captain asked if the airplane was pushing the tug, to which he responded yes. The airplane continued to move forward, subsequently overtaking the tug, which remained connected to the airplane's nose wheel. He further reported that the tug struck the belly of the airplane about the same time as tow bar severed at the nose wheel connection.

The tug driver reported that two wing-walkers were present at the time of the accident, and that neither tug was equipped with snow chains or traction devices.

The captain recounted similar observations regarding the initial pushback attempt. He became concerned that disconnecting the tug with both engines running could cause the airplane to move forward in the slippery conditions. He considered shutting down one or both of the engines; however, when he attempted to communicate his concerns with the driver, he had already departed to get the larger tug. By this time, the air-start equipment had also been removed from the gate area. The airplane appeared to remain firmly in position at the gate, and as such, he decided to keep both engines running.

The driver returned with a larger tow tug, and the airplane was successfully pushed back from the gate. Shortly thereafter, the captain experienced a turning and slipping sensation. He asked the tug driver if he still had control of the airplane, to which he replied in the affirmative. He then observed the tug rotate to the right and felt a collision. He reported that although he did not believe the airplane was moving forward, the events transpired so quickly that it was possible he may have missed any forward motion. As such, he could not definitively confirm if the tug struck the airplane, or if the airplane struck the tug.

With regard to starting both engines instead of one in lieu of a functioning APU, the captain stated that he made a judgment call based on a concern that if he started one engine only, he would encounter control problems taxing in the slippery conditions. He reported that he could also have attempted to start the second engine in the alleyway after pushback using a cross-bleed start. However, he was concerned that attempting such a start would require increasing the power to the running engine and could be disruptive to ground personnel and other traffic within the alleyway.

With regard to weather, the captain stated that although snow was falling at the time, the ramp area at the gate was plowed and mostly clear, and that the alleyway was contaminated with snow and ice. His view was not obscured by precipitation during the maneuver, and he could see the tug.

Examination of a photograph taken following the accident revealed that the airplane's nose gear had become canted to the right over-steer limits, with the tow bar bracket remaining partially attached to the left side of the wheel by the axle engagement pins. The bracket separated from the tow bar at its shank, which remained within the tow bar collar. The tow bar remained attached to the tug, which had come to rest impinged against the right forward fuselage, and opposite the direction of travel. Tire-shaped snow tracks were observed in the snow behind the nose wheel, the tracks continued in a sweeping arc aft towards the left side of the airplane. No snow disruption was present forward of the nose wheel.

METEOROLOGICAL INFORMATION

A special automated surface weather observation for SLC was issued at 2222. It indicated winds from 020 degrees at 6 knots; 2 miles visibility, with light snow and mist, a broken cloud ceiling at 1,600 feet, scattered clouds at 700 feet and overcast at 6,000 feet; temperature minus 7 degrees C; dew point minus 9 degrees C; and an altimeter setting of 29.81 inches of mercury.

FLIGHT RECORDERS

The airplane was equipped with both a Flight Data Recorder (FDR), and a Cockpit Voice Recorder (CVR). Both units were sent to the NTSB Office of Research and Engineering for data extraction. Examination of the CVR revealed that the unit was not de-energized subsequent to the collision, and as such, the accident sequence had become overwritten.

The FDR recorded about 77 hours of data, including the accident sequence. The data revealed that both engines were started about 2158 and powered to an N1 (Fan rpm) speed of 25% rpm while the airplane remained on a heading of 142 degrees magnetic. At 2220, the heading decreased until it reached 57 degrees, 45 seconds later, with a coincident jump in lateral and longitudinal acceleration of 0.07 and -0.08 g, respectively. The brake pedals were not applied until about 2 seconds after the acceleration event.

ADDITIONAL INFORMATION

SkyWest CRJ Standard Operating Procedures (SOP), in part, required the following prior to commencing the pushback:

"When ramp surface conditions would prevent adequate traction for ground equipment, engine start will be delayed until pushback is complete, and the pushback crew is clear of the aircraft. The pushback operator is responsible to notify the captain accordingly."

The corresponding SkyWest "Below-Wing Stations Operating Manual" made the following reference with regard to pushback/dispatch procedures with the tow bar and tow unit:

"WARNING - WHEN RAMP SURFACE CONDITIONS PREVENT ADEQUATE PUSHBACK UNIT TRACTION, ENGINE START MUST BE DELAYED UNTIL PUSHBACK IS COMPLETE. THE PUSHBACK OPERATOR IS RESPONSIBLE TO NOTIFY THE PIC ACCORDINGLY."

Neither the SOP nor the Below-Wing Operations Manual provided guidance for pushback procedures with an inoperative APU during low traction ramp conditions.

Subsequent to this accident, SkyWest issued a Ground Operations Bulletin, and Delta issued an Immediate Action Bulletin requiring that when ramp surface conditions prevent adequate pushback unit traction, only one engine may be started prior to pushing back a regional jet aircraft.

NTSB Probable Cause

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.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.