Malware Alleged to be Contributing Cause of Spanair Flight 5022 Crash

By

Here’s one more thing to add to our “things we wish we didn’t have to worry about” list.

After Spanair flight 5022 crashed seconds after take-off in August of 2008 in Madrid, Spain, killing 154 people and leaving only 18 survivors, Spanish officials began an exhaustive search for the cause of the crash. The plane had been headed for Gran Canaria, the largest island of the Canary Islands. Witnesses observed that seconds after take-off, the plane rolled to the right and crashed near the runway, breaking into at least two parts and subsequently bursting in flames. Investigation determined that when the plane took off, the MD-80’s flaps and slats were retracted, preventing the aircraft from attaining the lift it needed to take off, and that an alarm that should have sounded to make the pilots aware of the situation had malfunctioned. The cause of the crash has been officially designated as pilot error; despite the lack of warning alert, the pilots should have noticed the problem when they went through their check-list.

Further investigation showed that the problem had occurred on two previous occasions with other flights on the same plane in the days before the crash, but that the maintenance system computer had failed to register the events and warn Spanish airport ground personnel. Had authorities been aware of the problems, the plane would have remained grounded at the airline's headquarters in Palma de Mallorca.

The reason the maintenance computer failed to alert ground control, Spanish newspaper El Pais alleged last week, is that the system was infected with malware in the form of a Trojan virus. Three maintenance workers are currently under investigation for manslaughter: two technicians who checked the plane before take-off and the head of maintenance for Spanair at Barajas airport in Madrid. The judge in the case, Juan David Perez, has demanded that Spanair turn over all the entries in the maintenance computer for the days before and after the incident.

If the report turns out to be true, it will be the first confirmed example of malware leading to fatalities. The final report from crash investigators is expected to be in December of this year.


Tracey Schelmetic is a contributing editor for TechZone360. To read more of Tracey's articles, please visit her columnist page.

Edited by Erin Harrison
Get stories like this delivered straight to your inbox. [Free eNews Subscription]

TechZone360 Contributor

SHARE THIS ARTICLE
Related Articles

Your Post-Quantum Readiness Starts at Y2Q Summit

By: TMCnet News    5/27/2026

Y2Q Summit is an executive conference focused on helping enterprises prepare for the coming era of quantum computing disruption, cybersecurity transfo…

Read More

Why Award Marketing Should Be Part of Every B2B Tech Company's Growth Strategy

By: Erik Linask    5/20/2026

Award marketing matters for B2B tech companies because industry recognition can strengthen trust, support sales and partner relationships, improve con…

Read More

Why Email Is Still the Most Underrated Layer of Modern Software Infrastructure

By: Contributing Writer    5/15/2026

Take, for example, the following scenario. A user requests a password reset, waits a few seconds, refreshes their inbox and nothing arrives. They try …

Read More

Jitterbit's Visionary Status Signals a Shift in the iPaaS Market

By: Contributing Writer    4/7/2026

As enterprise ecosystems grow more complex, integration has become less of a backend IT function and more of a strategic driver of business performanc…

Read More

Cyber Extortion over hoax Breach: Lessons from a Fabricated story about IDMERIT

By: Contributing Writer    3/3/2026

Cybercriminals are increasingly staging fake data breaches to launch extortion attempts against KYC-AML companies. Recently, hackers devised a new met…

Read More