Microsoft software implicated in air traffic shutdown

A bug in a Microsoft system compounded by human error was ultimately responsible for a three-hour radio breakdown that left hundreds of aircraft aloft without guidance Tuesday last week, according to a report in the LA Times.

Nearly all of Southern California's airports were shut down, and five incidents where aircraft broke separation guidelines were reported. In one case, a pilot had to take evasive action.

The newspaper said that a Microsoft-based replacement for an older Unix system needed to be reset every thirty days 'to prevent data overload', as a result of problems found when the system was first rolled out. However, a technician failed to perform the reset at the right time, and an internal clock within the system subsequently shut it down. A back-up system also failed.

Richard Riggs, an advisor to the technicians union, said the FAA - the American aviation regulator -- 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.

Microsoft UK was not immediately able to comment.

ZDNet UK's Rupert Goodwins reported from London. For more coverage from ZDNet UK, click here.

Advertisement

Talkback 4 comments

    The FAA are criminally neglige ...Anonymous -- 21/09/04

    The FAA are criminally negligent in using such a buggy system. What happens if there is a mid-air collision as a result. Sue Microsoft ???

    An other example that proofs t ...Anonymous -- 22/09/04

    An other example that proofs that M$ junk should not be used for critical applications ...

    What a ridiculous headline. No ...Anonymous -- 23/09/04

    What a ridiculous headline. No where in the story was actual Microsoft software mentioned as the culprit. In fact, the article implies it was FAA created software (or rather software the FAA contracted) that was to blame. Irresponsible journalism at its worst. If Microsoft products were really to blame, why were they not mentioned by name in the article?

    Hey Chuckle head....the first ...Anonymous -- 06/11/04

    Hey Chuckle head....the first line..in BOLD says
    "A bug in a Microsoft system "

    The BUG is that Windows servers need to be restarted every 49.7 days. This has nothing to do with the FAA component. it is a "Feature" in Windows.

    If this did not exist, there wouldn't have been a problem to begin with.

Add your opinion

Latest Videos

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

  • Chris Duckett Carelessness busts Linux security
    No operating system can ever properly protect a computer from trojans as long as users continue to do silly things. Just because Linux is immune to your standard drive-by viruses it does not mean that it can escape trojan horses.
  • Array Sun shining on Ajnaware
    Graham Dawson talks about the future of iPhone app development and augmented reality.
  • Array Holiday IT to-do lists
    The fast-approaching holiday season is a great time to update your IT systems while everything's quiet.
  • More blogs »

Tags

Back to top

Featured