Malware partly blamed for Fatal 2008 Spanair Crash

rated by 0 users
This post has 6 Replies | 2 Followers

Top 10 Contributor
Posts 24,882
Points 1,116,760
Joined: Sep 2007
ForumsAdministrator
News Posted: Sun, Aug 22 2010 2:48 PM
Malware has been implicated as a contributing factor in a Spanair plane crash that killed 154 people two years ago Friday. The crash of Spanair flight JK 5022 occurred just after takeoff, two years ago, on August 20, 2008.

The crash was Spain's deadliest in 25 years. Only 18 of the 172 passengers and crew survived. The plane, a McDonnell Douglas MD-82 aircraft, was taking on from Madrid's Barajas Airport on a scheduled flight to Las Palmas.


While not directly involved in the crash, the malware affected the mainframe that monitors technical problems on the plane, according to the Spanish language paper El Pais. An alarm is supposed to sound if three similar technical problems are registered on a single plane, but it did not go off, as a result of the Trojans infecting the mainframe.

While it was determined that pilot error was reponsible for the crash, as both the slats and flaps were not set properly, the onboard alarm system did not alert the pilots as it should.

Obviously, if the mainframe had not been infected, and its alarm had sounded, lives might have been saved. You can watch video of the actual crash below:

  • | Post Points: 65
Top 10 Contributor
Posts 5,048
Points 60,675
Joined: May 2008
Location: U.S.
Moderator
3vi1 replied on Sun, Aug 22 2010 5:11 PM

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?

++++++++++++[>++++>+++++++++>+++>+<<<<-]>+++.>++++++++++.-------------.+++.>---.>--.

  • | Post Points: 20
Top 75 Contributor
Posts 1,792
Points 28,420
Joined: Feb 2008
Location: South Carolina

Dang what were they running on the PC Windows Mellenium!!Confused

 

 

 

 

  • | Post Points: 5
Top 100 Contributor
Posts 1,099
Points 13,965
Joined: Jun 2010
fat78 replied on Sun, Aug 22 2010 8:42 PM

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

  • | Post Points: 5
Top 75 Contributor
Posts 1,809
Points 18,105
Joined: May 2009
Location: Waikiki

Just like the movie Virus :P

Intel Core i7-875K Quad
Asetek 510LC 120MM
4GB Kingston Hyper-X DDR-3
ASUS P7P55D-E Pro
CyberPower 800 PSU
Kingston 64GB SSD 
2 Hitachi 1-TB HDD'S
FirePro V8800
8X Blu-Ray DVD±R/±RW
HPw2207 22" LCD
Cintiq 21UX
CoolerMaster 690II Advance
Win 7 Pro 64 bit
Special thanks to HotHardware.com!
  • | Post Points: 5
Not Ranked
Posts 1
Points 20
Joined: Aug 2010
Location: Online

If this is real true, then the military should use this kind of tactics to bring down jet fighters and drones.

  • | Post Points: 20
Top 100 Contributor
Posts 1,099
Points 13,965
Joined: Jun 2010
fat78 replied on Mon, Aug 23 2010 2:41 PM

Flaps arnt controlled by the computers, they are just monitored by it. pilot didnt get the warning that the flaps were set incorrectly

  • | Post Points: 5
Page 1 of 1 (7 items) | RSS