Jfyhkgu

United Airlines Flight 2860

A United Airlines Douglas DC-8-54AF, similar to the one involved.
Accident
Date	December 18, 1977 1:38 a.m. MST
Summary	Controlled flight into terrain, ATC error, pilot error
Site	Davis County, Utah, U.S. near Farmington 41°01′41″N 111°52′30″W / 41.028°N 111.875°W / 41.028; -111.875Coordinates: 41°01′41″N 111°52′30″W / 41.028°N 111.875°W / 41.028; -111.875
Aircraft type	McDonnell Douglas DC-8-54AF
Operator	United Airlines
Registration	N8047U
Flight origin	San Francisco International Airport, San Francisco, California, U.S.
Stopover	Salt Lake City International Airport, Salt Lake City, Utah
Destination	O'Hare International Airport, Chicago, Illinois
Passengers	0
Crew	3
Fatalities	3
Injuries	0
Survivors	0

San Francisco

Salt Lake City

Locations in the western United States

United Airlines Flight 2860 was a scheduled domestic cargo flight in the United States from San Francisco, California, to Chicago, Illinois, with an intermediate stop added at Salt Lake City, Utah. On December 18, 1977, operated by one of the airline's McDonnell Douglas DC-8-54AF Jet Traders, registration N8047U,^[1] the flight was in a holding pattern in Utah and crashed into a mountain in the Wasatch Range near Kaysville. All three crew members, the only occupants of the plane, were killed in the accident.^[2][3][4][5]

Summary of events

Late on Saturday, December 17, 1977, United Airlines Flight 2860 departed from San Francisco at 11:17 p.m. PST (12:17 a.m. MST). The intermediate stopover in Salt Lake City had been added several hours earlier. When the flight was near Salt Lake City less than an hour later at 1:11 a.m. MST, the crew radioed the airport that they were having electrical trouble, and requested holding clearance to give them time to communicate with company maintenance. Clearance was approved, and the flight entered a holding pattern.^[6]

For the next seven-and-a-half minutes, while in a holding pattern, the flight was absent from the approach control frequency, and entered an area of hazardous terrain. The flight contacted maintenance, and informed they were having electrical trouble, and that several landing gear lights were inoperative. After discussing the problems with maintenance, and deciding to contact the tower to get the emergency equipment ready, they re-established contact with the tower in Salt Lake City.^[6]

The controller on duty noticed Flight 2860's predicament, but was unable to contact the flight until it re-entered the approach frequency. The controller immediately told Flight 2860 it was close to terrain on its right, and to institute an immediate left turn. Not receiving a response, the controller repeated his instructions, which Flight 2860 responded to. Fifteen seconds later, the same controller told Flight 2860 to climb to 8,000 feet (2,440 m). The flight reported it was climbing to 8,000 from 6,000 feet (1,830 m). Eleven seconds later at 1:38 a.m., the flight crashed into a 7,665-foot (2,336 m) mountain ridge at 7,200 feet (2,195 m).^[6]

The sheriff's office in Farmington reported the sound of an explosion and subsequent rumbling felt in the ground. The dispatcher called the airport to ask if an airplane had gone missing. The first answer was no. More questions revealed that it was a cargo plane. The sheriff's office organized a rescue team that found the bodies and debris. The rescue team reported that no part of the airplane bigger than a briefcase survived the crash. The "echo" of the crash could be seen on the mountainside for several years afterward.

Witnesses in Kaysville and Fruit Heights saw an airplane flying low overhead. Shortly thereafter, all saw an orange glow to the east, which continued for three to four seconds. All witnesses reported rain in the area, and several reported it as heavy.^[6] All three occupants of the flight were killed, and the aircraft was destroyed.

Cause

The NTSB deduced that the cause of the accident was the "controller's issuance and the flight crew's subsequent acceptance of an incomplete and ambiguous holding clearance". The flight crew was cited for their failure to adhere to established lack-of-communication guidelines, and lack of adherence to established holding procedures. The aircraft's electrical problems were cited as a contributing factor.

In addition, the flight's cockpit voice recorder was found to be inoperative, preventing the accident investigation from identifying any contributing factors in the cockpit.^[7]

References

External links

• Aviation Safety Network for United 2860


• 
  Photos of N8047U at Airliners.net