The smoking gun on the Amtrak crash
By JIM STONE
Now it seems the engineer reports have been supplemented with black box data. For the record, TAKE THIS TO THE BANK, anything else that gets spewed will be an MSM lie because we have the CHECK MATE, which is: The emergency brake on the train was "applied" for a full 4 minutes before the crash, and the entire time the brake was "applied" the train accelerated. Yet in the wreckage, where you can see the brake discs, they are not burned and never got hot, which means they were never applied.
There is ONLY ONE WAY this could have happened, and it is the Stuxnet virus, which did not block the "brakes applied" command log from hitting the black box, but stuxnet DID stop the "brakes applied" signal from showing on the control panel and DID stop the "brakes applied" signal from actually getting to the brakes, which never activated.
Here is another clincher: The engineer did not apply the brakes, UPDATE: Now they are saying the engineer could tell the train was speeding up, but that the speed readout stayed at 50 mph THIS PROVES BEYOND A DOUBT: No matter what the MSM spews about this, the train really was software controlled in that section of the track with the engineer as a supervisor looking out the window knowing it was speeding up and not controlling the speed, SOFTWARE controlled the speed, knew it was too fast and applied the brakes, only to be stopped by STUXNET. There is no other way this can be, it is the absolute ONLY thing that fits.
Additionally, at the same time this Amtrak event was going on, there was a NOW PROVEN HACK CRASH OF THE SUBWAY IN MEXICO CITY. Mexican press said it was the operator's fault. However, the Australian press said the auto pilot jammed and the operator could not disengage it. (then left out all the details, such as autopilot is to prevent crashes, right?) MORE STUXNET, TOO COINCIDENTAL.
By JIM STONE
Now it seems the engineer reports have been supplemented with black box data. For the record, TAKE THIS TO THE BANK, anything else that gets spewed will be an MSM lie because we have the CHECK MATE, which is: The emergency brake on the train was "applied" for a full 4 minutes before the crash, and the entire time the brake was "applied" the train accelerated. Yet in the wreckage, where you can see the brake discs, they are not burned and never got hot, which means they were never applied.
There is ONLY ONE WAY this could have happened, and it is the Stuxnet virus, which did not block the "brakes applied" command log from hitting the black box, but stuxnet DID stop the "brakes applied" signal from showing on the control panel and DID stop the "brakes applied" signal from actually getting to the brakes, which never activated.
Here is another clincher: The engineer did not apply the brakes, UPDATE: Now they are saying the engineer could tell the train was speeding up, but that the speed readout stayed at 50 mph THIS PROVES BEYOND A DOUBT: No matter what the MSM spews about this, the train really was software controlled in that section of the track with the engineer as a supervisor looking out the window knowing it was speeding up and not controlling the speed, SOFTWARE controlled the speed, knew it was too fast and applied the brakes, only to be stopped by STUXNET. There is no other way this can be, it is the absolute ONLY thing that fits.
Additionally, at the same time this Amtrak event was going on, there was a NOW PROVEN HACK CRASH OF THE SUBWAY IN MEXICO CITY. Mexican press said it was the operator's fault. However, the Australian press said the auto pilot jammed and the operator could not disengage it. (then left out all the details, such as autopilot is to prevent crashes, right?) MORE STUXNET, TOO COINCIDENTAL.