No One Is Quite Sure If a U-2 Spy Plane Shut Down LAX Last Week

Last week, hundreds of flights were canceled or delayed along the West Coast went ground control computers connected to several major airports went haywire. 

This article is from the archive of our partner .

Last week, hundreds of flights were canceled or delayed along the West Coast went ground control computers connected to several major airports went haywire. According to NBC News, the problem arose because a Cold War-era spy plane flying through California airspace wreaked havoc with the system. Unfortunately, the U.S. Air Force doesn't agree with that interpretation of events. 

NBC News, citing anonymous sources, reports that the Lockheed U-2 passed through airspace monitored by L.A. Air Route Traffic Control Center in Palmdale, California, on Wednesday afternoon and confused the ERAM computer system that air traffic controllers use to make sure flights don't collide. Per NBC:

The U-2 was flying at 60,000 feet, but the computers were attempting to keep it from colliding with planes that were actually miles beneath it. Though the exact technical causes are not known, the spy plane’s altitude and route apparently overloaded a computer system called ERAM, which generates display data for air-traffic controllers. Back-up computer systems also failed.

The chain of events started with a flight plan that resulted in an improper computer code for the U-2's flight, according to one person, apparently prompting malfunctions that overwhelmed the computer system. The system ultimately went into overload and shut itself down as a precautionary measure.

On Wednesday, Los Angeles International Airport (LAX) diverted ten incoming flights and grounded a number of others as a result of the computer malfunction. LAX spokeswoman Nancy Suey Castles told CNN at the time that "Airlines at LAX are reporting an estimated 10 cancellations and 110 departure delays throughout tonight." John Wayne Airport in Orange County, Bob Hope Airport in Burbank, and Bay Area airports were also affected, as were airports in Las Vegas and Salt Lake City. Officials reported at the time that the confusion was caused by technical glitches.
The type of spy plane that caused all the trouble was commonly used in the 1950s to carry out Pentagon reconnaissance missions over the then-Soviet Union. According to the Wall Street Journal, the Air Force still operates a fleet of about 30 "Dragon Ladies," though they are finally being phased out.
It's still not clear why the U-2 flew into the L.A. Center's airspace, or why it didn't give advance warning of the flight, as per usual. According to NBC News, the nearby Edwards Air Force Base and NASA's Neil A. Armstrong Flight Research Center (located at Edwards) "have been known to host U-2s." But an Edwards rep said no such planes are assigned to Edwards, and a NASA rep said that none of their U-2 planes were flying on Wednesday.
The U.S. Air Force, on the other hand, confirmed that it had sent out a U-2 plane that day — but denied to that the spy plane caused the airport confusion. The Air Force Times has more:

Pentagon spokesman Army Col. Steve Warren confirmed that there was a U-2 operating in the area. The Air Force “filed all the proper flight plan paperwork … in accordance with all FAA regulations” and was conducting a routine training operation, Warren said. The FAA has issued a statement saying technicians have “resolved the specific issue that triggered the problem,” but the agency did not say what the problem was. FAA spokeswoman Laura Brown declined to comment about whether the U-2 was connected to the computer problems at the control center.

For what it's worth, testing of the plane is the official reason why the government says it built Area 51. So the truth is out there. Somewhere.

This article is from the archive of our partner The Wire.