FAA Computer Glitch Causes Widespread Airline Delays
seven of five writes with this excerpt from an Associated Press report: "A problem with the FAA system that collects airlines' flight plans caused widespread flight cancellations and delays nationwide Thursday. It was the second time in 15 months that a glitch in the flight plan system caused delays. The FAA said in a statement that it is having a problem processing flight plan information. 'We are investigating the cause of the problem,' the agency said. 'We are processing flight plans manually and expect some delays. We have radar coverage and communications with planes.'"
Some one messed up their $2,000,000 excel macro that list morning.
I only changed one little line of code! It wasn't even important enough to test!
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
I just read a post on Facebook by an Air traffic controller I know. They had to e-mail or fax all icao flight plans to the FAA. The FAA manually typed in every flight plan for every flight in the country.
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
Given that the FAA is responsible for the lives of thousands of people who travel by air every day, not to mention cargo planes which represent billions of dollars in economic activity, I'd be extremely alarmed if they were constantly switching to the latest and greatest technology without testing each and every line of code in the entire software stack, up to and including the bare metal. Change is slow in organizations like that because it has to be. Improper testing can easily lead to lost lives, or at the very least huge delays like these ones that can cost millions in lost productivity.
"That's it, you're all grounded!"
I am officially gone from
It could be worse. You could be stuck in Lodi (again).
This guy's the limit!
That bug just flew in under the radar...
**ducks**
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
"First things first -- but not necessarily in that order"
-- The Doctor, "Doctor
Sorry, this is flight planning/scheduling software. This is the system by which airliners are told what route they are to take when they finally get their flight clearance.
The primary reason this has not received "oh my god the sky is falling" priority is because, well, it isn't. Nor are shiny metal tubes blasting through the sky at 500 miles an hour going to smash into each other because of this. People will be inconvenienced and that's regrettable and needs to be fixed, but this is not a safety issue.
- Radar control systems: Unaffected.
- Air Traffic control: Unaffected.
- Communications: Unaffected.
- Landings: Unaffected.
- Any flights already in progress: Unaffected.
- Ground control: Unaffected.
- Passenger Safety: Unaffected.
This only delays the granting of flight clearance. The planes that are inconvenienced by this are safely on the ground, and the effect is that they stay on the ground longer than they should. Again, this is regrettable, but not fatal. There is no plausible scenario that would lead from this to a failure of traffic control. In fact, with fewer planes in the sky, you could argue that flying is actually safer (for those people who are lucky enough to have gotten clearance, of course!).
In the medical field, this would be a failure of the system that the receptionist uses to schedule your next appointment. In the automotive analogy, this would be a failure of your garage door opener. In the heart monitor analogy, there isn't even an analogy because heart monitors don't have (as far as I know) any non-critical systems.
"This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
Considering that this did not affect the development of flight plans, only delayed them, I'd rip this back out of the category of "safety critical".
Online development of flight plans is much faster than offline. But that's precisely what makes the offline ones safe - as you delay the development of flight plans you also reduce the number of planes being cleared for takeoff at the same time. Once the flight planning software goes back online, you can start granting flight plans quickly again and get traffic volumes back to normal.
And it's a bit of a stretch to assume a risk of a collision even in the complete absence of flight planning. ATC, Radar, airplane internal collision avoidance, and pilot eyeballs are all unaffected by this. The only thing this could possibly do is put two planes in the vicinity of each other, but even that is unlikely as the sky isn't "the wild west" - it's carved up into clearly-defined highways with speed limits and defined routes which are all used in flight planning. So if you have two planes in the vicinity of each other, they are going in the same direction at roughly the same speed, so there's TONS of time to react.
And the first precaution, as we've seen here, is to reduce the number of clearances. Arguably, this makes the actual flying safer, since there are fewer planes up there for ATC to have to track and communicate with.
"This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
Yea, these are the guys (the feds) I want building cars, taking over health care...thanks god they are not building the planes. I'm just trying to think one government run organization that works as well as any private one. Any idea?
Well, I work w/ the FAA right now, and they're becoming relatively platform agnostic actually. ERAM, for instance, was written by Lockheed Martin to run on top of some flavor of IBM UNIX or Linux (forget which). In the old days, everything ran on custom, purpose-built hardware and OSes, but that really turned out to be a maintenance nightmare. Using COTS Hardware/Software means upgrading systems or providing new capabilities can be pretty easy.
I think ASDE-X runs on top of some sort of POSIX type OS as well... I know its data stream is standard UDP over Ethernet type stuff.
Maxim: People cannot follow directions.
Increases in truth directly with the length of time spent explaining them