Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
1–10 of 311 posts
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#2Well, 3600 billionths of a meter IS kinda close...just sayin'
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#3Good news: the system successfully detected an error and didn't send bad data to air traffic controllers.
Bad News: the system can't recover from an error in an individual flight plan, bringing the whole system down with it (along with the backup system since it was running the same code).
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#4Well, 3600 billionths of a meter IS kinda close...just sayin'
I read it the same way….
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#5Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#6Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#7People posting on this forum saying "ah well software's failure case isn't as bad"
> This forced controllers to revert to manual processing, leading to more than 1,500 flight cancellations and delaying hundreds of services which did operate.
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#8Title should be nmi
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#9FYI: nm = nautical miles, not nanometers.
Re: Air traffic failure caused by two locations 3600nm apart sharing 3-letter code
#10People posting on this forum saying "ah well software's failure case isn't as bad" > This forced controllers to revert to manual processing, leading to more than 1,500 flight cancellations and delaying hundreds of services which did operate.
Zero fatalities though. You could do a lot worse for a massive air traffic control failure.