
At 7:51 on the evening of February 16, 2000, witnesses in Rancho Cordova, California, watched a Douglas DC-8 cargo jet descend at an impossible angle toward an automobile salvage yard east of Sacramento. The aircraft's left wing struck a concrete and steel support column on a two-story building, and the plane tore through rows of junked cars, igniting what one observer described as "a hellish scene of smoke, flames and exploding cars" visible for miles. All three crew members aboard Emery Worldwide Airlines Flight 17 were killed. The flight had been airborne for less than two minutes.
The DC-8 that crashed in Rancho Cordova had already lived several careers by the time it reached Emery Worldwide's fleet. Built in 1968 as a Douglas DC-8-71, registration N8079U, the aircraft first flew passengers for United Airlines for more than two decades. In 1990, it transferred to Lineas Aereas Paraguayas, the Paraguayan national carrier, where it served until 1994. Somewhere along the way, the airplane was converted from a passenger jet to a freighter, its cabin stripped of seats and refitted with cargo rails and bulkheads. In July 1983, its original Pratt & Whitney JT3D engines were replaced with more efficient CFM International CFM56 turbofans, upgrading it from a DC-8-60 series to a 70 series. By the time of the crash, N8079U had accumulated approximately 84,447 flight hours across 33,395 flight cycles, a workhorse by any measure, the kind of airframe that freight carriers depended on for the unglamorous overnight runs that kept supply chains moving.
Flight 17 was a routine cargo run, the kind that fills the night skies over America: Reno to Dayton, Ohio, with an intermediate stop at Sacramento Mather Airport. The crew that evening consisted of Captain Kevin Stables, 43, a veteran with 13,329 flight hours and more than 2,100 hours in the DC-8; First Officer George Land, 35, who had logged 4,511 hours with 2,080 in type; and Flight Engineer Russell Hicks, 38, with 9,775 hours of experience. These were not inexperienced pilots groping through an unfamiliar cockpit. They were professionals who knew the DC-8 intimately, men who had spent thousands of hours managing the four-engine jet's systems, quirks, and demands. Their competence would make what happened next all the more troubling.
Shortly after takeoff from Mather Airport, the crew reported control problems. The aircraft, loaded with cargo and climbing into the darkening Sacramento sky, was not responding normally to pitch inputs. Something was wrong with the elevator, the control surface on the tail that governs whether an airplane climbs or descends. The crew fought to stabilize the jet as it began swaying left and right, the kind of oscillation that tells a pilot the airplane is on the edge of controllability. They attempted to return to Mather, turning the DC-8 on a northwesterly heading back toward the field. But the aircraft was losing altitude, and the ground proximity warning system began sounding its urgent alarm. The crew was running out of sky. At 19:51 local time, the left wing caught the support column of that two-story building at the edge of the salvage yard, and the aircraft came apart.
The National Transportation Safety Board's investigation, which concluded in August 2003, traced the accident to the aircraft's right elevator control tab. The NTSB's findings pointed to failures in maintenance procedures and design vulnerabilities that had gone unaddressed for decades. The board's safety recommendations addressed the DC-8's elevator position indicator installation and usage, the adequacy of DC-8 maintenance work cards for required inspection items, and the design of the DC-8 elevator control tab itself. The parallels were haunting: thirty years earlier, Trans International Airlines Flight 863, another DC-8 freighter, had crashed due to problems with the same right elevator system. The lessons of that earlier accident had not been fully absorbed into maintenance practices and regulatory oversight. Three decades of flying had not closed the gap between what was known about the DC-8's elevator vulnerabilities and what was done about them.
The crash site in Rancho Cordova, an unincorporated community east of Sacramento that would not incorporate as a city until 2003, was an automobile salvage yard, a landscape of stacked and crushed cars that erupted into a secondary inferno when the DC-8's fuel ignited among them. No one on the ground was killed, a piece of luck in a disaster that otherwise offered none. Sacramento Mather Airport, from which Flight 17 departed, was itself a place of transition: a former military installation, Mather Air Force Base had closed in 1993 and been converted to civilian use. The accident left its mark on aviation safety regulation, but the salvage yard was rebuilt, the runway continued operating, and the cargo flights resumed their nightly crossings. What remains is the memory of three crew members who died doing work most people never think about, the invisible freight runs that move goods across the continent while the rest of the country sleeps.
Crash site located at 38.561N, 121.251W in Rancho Cordova, California, east of Sacramento. Sacramento Mather Airport (KMHR), the departure point, is approximately 2 nm southwest of the crash site. Sacramento Executive Airport (KSAC) lies approximately 12 nm west. The crash occurred shortly after takeoff from Runway 22L at Mather. The salvage yard site is in flat Central Valley terrain with few obstructions. From the air, Mather Airport's runways and the surrounding suburban development of Rancho Cordova are clearly visible. Best observed at 3,000-5,000 ft AGL to understand the spatial relationship between the airport and crash site.