LAX Center No Comm, 5 airproxes?

[Shore Guy]

FAA radio outage halts flights in West
About 800 planes were in the air at time of breakdown

WASHINGTON (CNN) -- A breakdown of a radio system linking air traffic controllers to high-altitude planes over Southern California forced federal officials to halt outgoing flights for three hours Tuesday evening at several airports, including Los Angeles International.

Some planes were being allowed to land at affected airports, but departing planes were held on the runways until a failed radio communications system could be repaired at Los Angeles Center, a remote facility in the desert north of the city.

The center links air traffic controllers with high-altitude planes.

Federal Aviation Administration spokesman Mike Fergus said controllers lost radio communications with aircraft within a 200-mile radius of the facility about 5 p.m. (8 p.m. ET), but takeoffs were allowed to resume by 8 p.m. (11 p.m. ET).

The airports affected included at least four in the Los Angeles area -- Los Angeles International, Burbank, Long Beach and Ontario, according to officials at those airfields. Airports at Oakland, California, and Las Vegas, Nevada, were likewise affected.

Some incoming flights were diverted to San Francisco International Airport.

The agency also halted all air traffic bound for Los Angeles and San Diego before the planes could take off.

About 800 airplanes were in the affected airspace at the time the communications system collapsed, the FAA said.

FAA officials said the problem did not present a danger for the planes or their passengers.

But the agency said it would force officials to establish alternative ways of communicating with planes destined for Los Angeles and San Diego airports.

The FAA said it instructed airline dispatch centers to contact their planes and have them communicate directly with the terminal radar controllers as they entered airspace closer to their destinations.

"We want to stress there are no safety issues, just delays, because control over the air space has been turned over to other air traffic facilities," Gaby Pacheco, a spokeswoman for Los Angeles International Airport, told The Associated Press.

It was the second time in 10 days that operations were interrupted at the airport known as LAX to air travelers.

On September 4, Labor Day weekend travelers were evacuated from four terminals for three hours after two incidents -- in one a flashlight battery exploded, in the other a man ran past security officers.

The LAX Web site says the airport is ranked fifth in the world for volume of passengers per year.

[mr Q]

http:/September 16, 2004 E-mail story
Human Errors Silenced Airports
A controllers union official describes 'harrowing' incidents in the sky, but the FAA insists the radio system failure posed no threat.
A Reeling King/Drew Receives Huge Blow


By Ricardo Alonso-Zaldivar, Eric Malnic and Jennifer Oldham, Times Staff Writers


Two separate human errors caused a breakdown in radio communications that brought Southern California's major airports to a near-stop Tuesday and led to at least five instances in which planes came too close, Federal Aviation Administration officials said.

"A loss of communication is a serious matter, and it should not have occurred," Rick Day, a senior FAA official, said Wednesday.
On Tuesday, FAA officials had insisted that the more than three-hour system shutdown posed no safety risks. But they acknowledged Wednesday that they were investigating five incidents in which planes lost the required separation distance during the first 15 minutes of the communications breakdown.

In two cases, large airliners — a UPS cargo plane and a Northwest Airlines flight bound for Southern California airports — came much closer to small corporate jets than federal guidelines allow, requiring at least one pilot to take corrective action. FAA officials repeated Wednesday that they did not believe lives were ever at risk.

The agency's radio system in Palmdale shut itself down Tuesday afternoon because a technician failed to reset an internal clock — a routine maintenance procedure required every 30 days by the FAA. Then a backup system failed, also as a result of technician error, officials said.

The radar system in Palmdale, contrary to what some FAA and union officials had said Tuesday, did not shut down.

The radio system that crashed about 4:30 p.m. Tuesday at the Los Angeles Air Route Traffic Control Center in Palmdale is a high-tech touch-screen tool that allows air traffic controllers to quickly communicate with planes in transit. Controllers at the Palmdale facility communicate with cruise-altitude air traffic across Southern California and most of Arizona and Nevada, an area of about 178,000 square miles.

FAA officials said they had known for more than a year that a software glitch could shut down radio communications and were in the process of fixing it. In the meantime, they required manual resetting of the communications system — a process they described as similar to rebooting a personal computer.

The problem so far has been corrected only in Seattle, one of 21 FAA regional air-traffic control centers that have used the system since the mid-1990s.

The radio failure rippled throughout the nation's airports, grounding hundreds of commercial flights and forcing controllers working from other centers to divert hundreds more to locations outside Southern California.

Los Angeles International Airport officials said about 30,000 passengers were affected, with 500 or 600 spending the night in the terminals. The backlog of incoming flights was not cleared until 3 a.m. Wednesday. At LAX, 450 flights were diverted or canceled and another 150 were delayed. An additional 32 were canceled Wednesday morning because the aircraft did not arrive Tuesday night.

Other airports — Ontario, Bob Hope, John Wayne, Long Beach and Palm Springs, as well as San Diego — experienced significant delays, and airports throughout the West took diverted flights.

The computer glitch that snarled air traffic was first discovered more than a year ago in Atlanta after the FAA upgraded its computers.

"That's why we built in strict maintenance procedures and protocols," said FAA spokesman Greg Martin. He said his agency is aggressively pursuing the reason why the routine and simple procedure was skipped at the Palmdale air traffic center.

Tuesday's communications failure marks the first time that the backup system has failed when the radio system shut down, Martin said.

The backup's failure left controllers with no way to communicate with other FAA centers or the high-altitude flights displayed on their radar screens.

Hamid Ghaffari, a union official at the Palmdale facility, described a scene of high tension Tuesday evening as controllers tried to use personal cellphones to warn controllers at other facilities and watched close calls unfold without being able to alert the pilots.

Martin called the remarks "wildly overstated" and said "none of these incidents under our definition would be considered near midair collisions."

Ghaffari said three controllers had filed job injury claims as a result of the stress, but said none of them would speak to the media.

"You can see planes getting close together, but you can't talk to them," said Ghaffari, describing conditions Tuesday evening.

"That's what made it particularly harrowing."

Once the Palmdale radio system failed, controllers at other FAA facilities, following contingency plans, took over communication with scores of airborne flights.

"En route aircraft were safely handed off to other air traffic control facilities, as designed," Martin said.

Controllers said they believed at least two of the incidents were dangerous, and FAA officials acknowledged those two were the most serious.

"I can't comprehend where the government can come out and say safety was never compromised," said Ghaffari, whose union has long complained about being understaffed.

Ghaffari, who has reviewed the radar tapes, described the two incidents.

In one, he said a Citation jet headed northwest from Phoenix to Monterey and a UPS cargo jet headed southwest from Louisville to Orange County's John Wayne Airport came within two miles of each other horizontally at 35,000 feet over Twentynine Palms. The vertical separation at that time was 100 feet.

Planes flying above 29,000 feet are required to be separated by nearly six miles horizontally and 2,000 feet vertically.

A spokesman for UPS confirmed that the pilot of Flight 1292 took evasive action after receiving an alert from the plane's collision-avoidance system, but said the incident was not serious.

"The pilot received a warning and took minor corrective action," said spokesman Mark Giuffre. "He climbed about 1,000 feet and they did see a business jet going by. The flight continued without event, but we are investigating it to find out what happened."

In the other incident, Ghaffari said a chartered Gulfstream III jet headed east from Long Beach to Dulles airport near Washington, D.C., was climbing to 41,000 feet over Needles. It came within less than a mile horizontally of a Northwest Airlines jetliner that was headed southwest from Detroit to San Diego at 39,000 feet.

The radar indicates that the Gulfstream halted its climb momentarily, possibly in an evasive action. The pilot of the Gulfstream leveled off about 900 feet the below Northwest Flight 277, Ghaffari said, to avoid coming any closer.

"They practically went right over one another," he said.

But Northwest spokeswoman Mary Stanik said there were no reports of problems on Flight 277. "All there was was a delayed descent to San Diego," she said.

Of the three other incidents, FAA officials said one involved a passenger jetliner and two involved cargo jets. They provided no additional information, other than to say one incident involved separation that was only slightly below the required 5 3/4 miles.

Officials from Professional Airways Systems Specialists, the union that represents FAA technicians, acknowledged Wednesday that an improperly trained employee failed to reset the Palmdale radio system.

But they said the quirk in the system, known as Voice Switching and Control System, is a "design anomaly" that should have been corrected after it was discovered last year in Atlanta.

As originally designed, the VSCS system used computers that ran on an operating system known as Unix, said Ray Baggett, vice president for the union's western region.

The VSCS system was built for the FAA by Harris Corp. of Melbourne, Fla., at a cost of more than $1.5 billion.

When the system was upgraded about a year ago, the original computers were replaced by Dell computers using Microsoft software. Baggett said the Microsoft software contained an internal clock designed to shut the system down after 49.7 days to prevent it from becoming overloaded with data.

Software analysts say a shutdown mechanism is preferable to allowing an overloaded system to keep running and potentially give controllers wrong information about flights.

Richard Riggs, an advisor to the technicians union, said the FAA had been planning to fix the program for some time. "They should have done it before they fielded the system," he said.

To prevent a reoccurrence of the problem before the software glitch is fixed, Laura Brown, an FAA spokeswoman, said the agency plans to install a system that would issue a warning well before shutdown.

Martin, the chief FAA spokesman in Washington, said the failure was not an indication of the reliability of the radio communications system itself, which he described as "nearly perfect."
Times staff writers Megan Garvey and Andrew Blankstein contributed to this report.
LATIMES.COM

[747FOCAL]

5 pairs of planes came too close, FAA admits
San Francisco Chronicle 09/16/04
author: Michael Cabanatuan
(Copyright 2004)

At least five pairs of planes came closer than federal aviation standards allow during Tuesday's failure of a critical air-traffic control communications system covering the southwestern United States, officials with the Federal Aviation Administration acknowledged Wednesday.

FAA officials also admitted that the shutdown of the system, which prevented controllers from talking to pilots flying high-altitude routes, was caused by a failure to perform routine maintenance at the busy Los Angeles control center in Palmdale.

Representatives of the National Air Traffic Controllers Association called three of the five incidents near misses, and said all were serious violations of standards designed to keep aircraft safely separated.

"Three pairs (of planes) were so close that on-board collision avoidance systems were activated,'' said Mark Sherry, regional vice president of the union and a controller in the San Francisco tower. "We had three controllers who couldn't do anything but watch their screens as two dots merged into one, then wait five or six seconds and hope that two came back out.''

But FAA officials said none of the incidents could be classified as near misses, and wouldn't even be considered violations under new, laxer international standards to be adopted in January.

"The union's claims are wildly overstated,'' said Greg Martin, chief spokesman for the FAA. He labeled the claims "a misrepresentation and inaccurate.''

Tuesday's computer failure, and the subsequent failure of a backup system, shut down voice communications between air-traffic controllers at the Los Angeles Air Route Traffic Control Center and pilots in the skies above Southern California, Arizona, southern Nevada and parts of Utah. About 400 flights were being managed by the center at the time of the shutdown, Martin said.

The outage, which occurred about 4:40 p.m., grounded flights throughout the Southwest for more than three hours. The FAA shifted air-traffic control to other centers, including Oakland, during the outage.

Federal aviation standards require aircraft flying below 29,000 feet to be separated by 1,000 feet in altitude or 5 miles in horizontal distance. Above 29,000 feet, planes are supposed be at least 2,000 feet apart in altitude or 5 miles distant horizontally. In January, Martin said, the FAA will adopt an existing international standard that allows a 1,000-foot or 5- mile separation at all altitudes.

Union and FAA officials disagreed on just how close the aircraft in two incidents came to each other. In the closest call, Sherry said, a Northwest Airlines 757 flying from Detroit to San Diego and a Gulfstream 3 bound for Washington's Dulles Airport from Long Beach were within 0.8 miles and just 900 feet apart in altitude. Rick Day, FAA vice president for en-route and oceanic air traffic control, said the planes were 0.9 miles and 1,400 vertical feet apart.

In what air traffic controllers called a second near-miss, a United Parcel Service 757 flying from Louisville, Ky., to Santa Ana and a Cessna Citation bound for Monterey from Phoenix came within 1.7 miles and 1,000 feet, Sherry said. Day said the planes were 1.9 miles and 1,100 feet apart.

The FAA declined to release identifying information on the three other incidents, saying their investigation is continuing.

Investigators did discover that the shutdown was the result of failure to perform a monthly maintenance routine that Martin likened to rebooting a computer. Investigators were looking into why the maintenance hadn't been performed and why a backup system also failed.

[dudduddud]

UNIX: 1
MICROSOFT: 0

[LGB]

(Stolen right off the 'net:http://soli.inav.net/~catalyst/Humor/gm.htm)

At a recent computer expo (COMDEX), Bill Gates reportedly compared the computer industry with the auto industry and stated: "If GM had kept up with technology like the computer industry has, we would be driving twenty-five dollar cars that got 1000 miles to the gallon."

In response to Bill's comments, GM issued a press release stating (by Mr. Welch himself):

If GM had developed technology like Microsoft, we would be driving cars with the following characteristics:

1. For no reason whatsoever your car would crash twice a day.

2. Every time they repainted the lines on the road you would have to buy a new car.

3. Occasionally your car would die on the freeway for no reason, and you would just accept this, restart and drive on.

4. Occasionally, executing a maneuver such as a left turn, would cause your car to shut down and refuse to restart, in which case you would have to reinstall the engine.

5. Only one person at a time could use the car, unless you bought "Car95" or "CarNT." But then you have would have to buy more seats.

6. Macintosh would make a car that was powered by the sun, reliable, five times as fast, and twice as easy to drive, but would only run on five percent of the roads.

7. The oil, water temperature and alternator warning lights would be replaced by a single "general car default" warning light.

8. New seats would force everyone to have the same size butt.

9. The airbag system would say "Are you sure?" before going off.

10. Occasionally for no reason whatsoever, your car would lock you out and refuse to let you in until you simultaneously lifted the door handle, turned the key, and grab hold of the radio antenna.

11. GM would require all car buyers to also purchase a deluxe set of Rand McNally road maps (now a GM subsidiary), even though they neither need them nor want them. Attempting to delete this option would immediately cause the car's performance to diminish by 50% or more. Moreover, GM would become a target for investigation by the Justice Department.

12. Every time GM introduced a new model car buyers would have to learn how to drive all over again because none the controls would operate in the same manner as the old car.

13. You'd press the "start" button to shut off the engine.