It was not a mainframe. The use of the word "mainframe" has since been attributed to bad translation. Planes don't need to talk to a mainframe to determine if they should throw an alarm over flap positions, nor were any other planes affected by this.
The real problem, as usual, was Windows. A Windows PC used by the mechanics was running too slow, due to malware, which caused them to not enter incidents into the maintenance logs. The flight would have been grounded due to three incidents in the logs, as there were two the previous day... but the one on the day of the crash wasn't entered yet because of the malware.
The failure of the alarm about the flaps was unrelated and is not directly attributable to malware. But, that won't stop everyone from saying a virus crashed this plane, apparently.
What part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn" don't you understand?
Dang what were they running on the PC Windows Mellenium!!
Were the flaps and slats not leveled togather? Because the path the plane took on wiki, shows it going off the sides of the runway
Just like the movie Virus :P
If this is real true, then the military should use this kind of tactics to bring down jet fighters and drones.
Flaps arnt controlled by the computers, they are just monitored by it. pilot didnt get the warning that the flaps were set incorrectly
NEWS TIPS |
This site is intended for informational and entertainment purposes only. The contents are the views and opinion of the author and/or hisassociates. All products and trademarks are the property of their respective owners. All content and graphical elements areCopyright © 1999 - 2013 David Altavilla and HotHardware.com, LLC. All rights reserved. Privacy and Terms