Slashdot Mirror


Feds Order Amtrak To Turn On System That Would've Prevented Crash

McGruber writes: Last Tuesday evening, northbound Amtrak Northeast Regional train No. 188 derailed on a curve in Philadelphia, killing eight passengers. The train was traveling in excess of 100 mph, while the curve had a passenger-train speed limit of 50 mph. In response, the Federal Railroad Administration (FRA) is issuing formal emergency orders that will require Amtrak to make sure automatic train control systems work Northbound through Philadelphia at and near the site of the derailment. The FRA is also requiring that Amtrak assess the risk of all curves along the NEC and increase the amount and frequency of speed limit signs along the railroad. FRA's emergency order is newsworthy because Amtrak's existing signal system could have been configured to prevent a train from exceeding speed limits, according to the Wall Street Journal.

5 of 393 comments (clear)

  1. No self driving trains? by Anonymous Coward · · Score: 5, Insightful

    I'm baffled that we just might get self driving cars before self driving trains.

    Do I really have to state the obvious? It's on *rails*.

    1. Re:No self driving trains? by fisted · · Score: 5, Funny

      It's on *rails*.

      So what? Ruby is, and still it crashes all the time, too.

  2. Re:and dog eats tail by Shakrai · · Score: 5, Interesting

    This headline is misleading. We don't yet know what caused the crash, so it's a leap to say PTC could have prevented it. We do know that the train was traveling at a high rate of speed but not the reasons why it was doing that. If it was a systems failure then it's entirely possible that PTC would have been irrelevant. This is just like the rush to judgment against the engineer, who everyone was ready to lynch after the accident; all we know for sure about him at this juncture is his cell phone was turned off and his drug/alcohol test came back clean.

    Do some reading about PTC when you have a few minutes; like most Federal mandates it was:

    1) Unfunded.
    2) Ignored existing technology that could do the job nearly as well for a fraction of the cost.
    3) Ineffective, in that there have only been two train accounts in the last 20 years (three if this one is confirmed) that it would have prevented.

    --
    I want peace on earth and goodwill toward man.
    We are the United States Government! We don't do that sort of thing.
  3. Lobbying Against PTC by Anonymous Coward · · Score: 5, Informative

    Wall Street Analyst Encouraged Rail Company to Lobby Against Train Safety Rules
    https://firstlook.org/theintercept/2015/05/15/wall-street-analyst-demanded-rail-industry-invest-lobbying-train-speed-safety-regulations/
    By Lee Fang (@lhfang)
    05/15/2015 11:26 AM

    Positive Train Control, a technology system used to monitor trains and automatically keep them from reaching unsafe speeds, would likely have prevented the tragic Amtrak derailment earlier this week and many other train crashes in recent years, according to the National Transportation Safety Board and train safety experts.

    But ever since Congress passed a law in 2008 requiring train companies to implement PTC by the end of 2015, the railroad industry has mounted a ferocious lobbying campaign to delay the rule.

    Amtrak, like many other railroads, has been slow to comply. The federal government has been accommodating. And most recently, senators have been fighting primarily over how long an extension should be granted.

    Train companies did not want to invest the needed funds to upgrade their systems. But they may have been feeling direct pressure from Wall Street, as well.

    In one revealing exchange during an investor call in 2009, Jason Seidl, then a financial analyst with the Dahlman Rose & Co. investment bank, asked Wick Moorman, the chief executive of Norfolk Southern Corp., what “you guys can do in terms of lobbying” on the PTC. And given the costs of complying with the PTC rule, the analyst wanted to know how future investments might be impacted.

    Moorman said he and other rail executives were busy working to “educate members of Congress as to what the implications of this legislation are.” Seidl encouraged Moorman to “further educate” them.

    Lobbying and other government records show the rail industry extensively sought to influence the Federal Railroad Administration and Congress on the PTC rules. Individual rail companies, including Norfolk Southern, Union Pacific, CSX, Canada National Railway Company, among others, hired a small army of lobbyists.

    But the largest and most prominent lobbying group to work to delay and weaken the PTC rule was the American Association of Railroads, which employed a veritable who’s who of D.C. consultants and lobbyists, including:

    — Linda Daschle, the wife of former Democratic Senate Leader Tom Daschle, was paid to lobby on the PTC on behalf of the Association of American Railroads.

    — The bipartisan lobbying duo of Max Sandlin and Vin Weber, both former congressmen, are registered with the American Association of Railroads to lobby on the PTC. Weber, an advisor to Jeb Bush, is also on the board of the American Action Network, a GOP dark money group that spends millions on election campaigns.

    — Another bipartisan lobbying team, including former Sen. John Breaux, D-La., and former Sen. Trent Lott, R-Miss., is registered to lobby on behalf of the American Association of Railroads on PTC.

    — The tax returns for the American Association of Railroads lists SKDKnickerbocker as a consultant for public relations and advertising throughout 2011 and 2012. SKDK is a public affairs firm led by senior Democratic staffers including former White House communications director Anita Dunn and CNN contributor Hilary Rosen. SKDK did not return a call requesting information about what services the firm provided for AAR, or if they continue to count AAR as a client.

    — Former National Transportation Safety Board Kathryn Higgins was registered on behalf of AAR to lobby on the PTC.

    — Former Rep. William Lipinski, D-Ill., was registered on behalf of the AAR to lobby on PTC. Lipinski’s son Dan is now a member of Congress who serves on the House Transportation Committee.

    Engineers have complained about the influence of the train

    1. Re:Lobbying Against PTC by Anonymous Coward · · Score: 5, Informative

      Replying as anonymous for business reasons...

      I worked on the PTC a few years ago with Lockheed Martin and Norfolk Southern. The LM folks were very committed to the program, but NS kept reducing funding. I wont make you read between the lines here, the program was a absolute disaster.

      Technologically the solution evolved GPS/Radio units in every train and maintenance vehicle that reported back to a bunker, data center, the trains approximate location, direction, and speed. However because of accuracy issues it was really hard to tell EXACTLY which track a train was on, especially in high density rail yards. So train GPS was supplemented by track circuits which in theory tell you if a train is on a section of track. Which is good in theory, but it can't tell you which train, nor distinguish between maintenance vehicles and trains, nor can it tell you how fast or long a train is.

      Knowing how long a train is became important for guaranteeing safe spacing between vehicles, as well as knowing safe times to switch track selectors.

      And don't get me started on the software, if anything were ever written by a room full of monkeys it was the PTC software. I recall one function in particular that controlled logic for determining which track a train was likely to be on; when printing out was over 30 foot long. To give you a since of how convoluted that code was, that single function had a McCabe complexity of over 1.5 million.

      Now I don't care how brilliant you THINK you are as a programmer, but thinking that you could understand that function only proved to me you were an idiot. 1.5 million possible paths through that one function (yes I know that we didn't account for similar condition statements that artificially inflate that number). That one function is absolutely guaranteed to kill your program, and we stressed that until we were released from the program. Just by odds alone, you are likely to add 5-10 defects while trying to fix a bug in it. And for two solid years that is exactly what happened, the defect count literally oscillated like a sin-wave function.

      I'm not telling you this as a slight at the programmers, nor the management. I'm telling you this because a project like PTC is HARD, its like the traveling salesman problem but with 50 salesman who can't be at the same place at the same time, but can pass each-other as needed, are likely going in opposite directions, and you have to recompute the whole mess every 30 seconds and resolve conflicts when a previous solution made the train "jump". Let me tell you there is nothing worse than watching a train make it's way through a switch yard then suddenly jump 10 lanes halfway through on the display.