Talk:Amtrak Cascades

A map would be nice
Either static or dynamic... Hobbitschuster (talk) 22:28, 13 July 2017 (UTC)

Amtrak Cascades accident
So according to media coverage there has been an accident on the Amtrak Cascades on its very first run over a new route (boy am I glad that the Nuremberg-Erfurt route "only" had some minor issues with ETCS that while causing delays have not actually hurt anybody). It seems the cause is not yet known but I would presume there are some service disruptions at least until the cause is clear and the issue addressed. We should probably put caution or warning or info boxes in the articles in question. Hobbitschuster (talk) 09:07, 19 December 2017 (UTC)


 * Definitely. It was a horrific accident with several fatalities and a larger number of injuries. Ikan Kekek (talk) 09:53, 19 December 2017 (UTC)


 * Our media is now reporting that someone went around the corner too quickly. I presume we'd only use  in bright red to warn of things which would endanger life or limb for the next hapless voyager to blunder across the 49th parallel. If the impact on *the next voyager* is that the train is not running, then note the disruption in Get around#By train with something less than warningbox. If the impact is that the next visitor who boards Amtrak anywhere will most surely die, then place the warningboxes at once. K7L (talk) 13:43, 19 December 2017 (UTC)


 * Well if those "excessive velocity" reports turn out to be accurate, this becomes yet another entry in the mind-numbingly long list of "Modern train control could have prevented this accident". I mean yes, the hiccups with ETCS on the Nuremberg-Erfurt line are annoying, but we can see what happens if there is no system that puts in an emergency stop if it detects speeds of (and if only because someone put in a wrong diameter for the wheels). Hobbitschuster (talk) 17:06, 19 December 2017 (UTC)


 * As I understand it, Positive Train Control was installed on the new route but not yet active. Powers (talk) 22:39, 23 December 2017 (UTC)