Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: Flavius

not this hogwash again, how many times is this crash going to be blamed on malware????


2 posted on 08/29/2010 5:48:11 PM PDT by driftdiver (I could eat it raw, but why do that when I have a fire.)
[ Post Reply | Private Reply | To 1 | View Replies ]


To: driftdiver

I don’t know.

People seem to want to think the plane itself had malware loaded on it’s computers, and it seems impossible to knock that notion out of their heads...

The crash was due to pilot error.


9 posted on 08/29/2010 7:46:55 PM PDT by ltc8k6
[ Post Reply | Private Reply | To 2 | View Replies ]

To: driftdiver
dailytech poster has explanation as he read report --

[Collapse Comment] Virus Had NOTHING To Do With The Crash
By DougF on 8/24/2010 8:35:04 AM , Rating: 5

quote:

The report indicates that the computer failed to detect three problems (including one issue with the airplane's wing flaps being in the incorrect position for takeoff) in a fail-safe monitoring system and that those problems were brought on by a malicious program that came from the USB thumb drive.

Wrong again. I've read the report and it CLEARLY states that the aircrew had the aircraft in "flight" mode, where the weight on wheels (WOW) switch is overridden in the cockpit. Normally, this is used for ground maintenance troubleshooting, and is NOT an approved part of pre-flight switchology. With the WOW switch in "flight" mode, the temperature probe registered a fault, which was then turned off as it is redundant for flight. With the aircraft in "flight" mode, there would have been NO warning or error logged as part of the takeoff process, as the aircraft already thinks it's in flight. The "problem" is that the aircrew was monkeying around with switches and put themselves and the passengers in grave danger.

The aircrew successfully defeated THREE SAFTEY PROCEDURES: 1) They had the WOW in "flight" mode for takeoff; 2) The aircrew said, but did NOT check the indication for flaps/slats in the cockpit; and 3) The aircrew failed to conduct a MANDATORY visual inspection for the flaps/slats from the cockpit windows.
Those three safety violations killed the aircrew, the passengers, and destroyed the aircraft, NOT a virus on the airline's mainframe. The virus did affect the showing of multiple faults, but that had NOTHING to do with this accident. The enquiry is simply finding additional problems that need to be addressed, they are not saying the virus had anything to do with this crash.

C'mon read the report...


11 posted on 08/29/2010 8:00:26 PM PDT by all_mighty_dollar
[ Post Reply | Private Reply | To 2 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson