Re: FRA issues E.O. 29 to MNCR
Author: SP5103
Date: 12-06-2013 - 23:21

It would be interesting to know the rest of the story on this. Is this due to political pressure, or is the FRA unhappy with Metro-North? The FRA generally doesn't issue an Emergency Order against a railroad without something specific in mind.

To my knowledge, Metro-North's pratices of cab car and single enginer is common practice for many Amtrak and commuter agencies, and as far as I know a dead man is still legal. But the EO basically forces them to run an engineer and a second qualified person in the cab until they modify their ATC to provide for speed restrictions or complete PTC installation, assuming anyone will be able to comply with the PTC deadline. In addition to supply issues, I heard that the FCC is refusing to grant permits for most PTC towers, and the railroads were having trouble getting frequencies in urban areas.

Somehow Metro-North has royally pissed off the FRA or something else is involved. The FRA references the other incidents in the last year - apparently one was a track defect, another a dispatcher error, and the CSX garbage train they claim is undetermined - yet none of them suggest another excess speed or fatigue issue. The order doesn't mention Amtrak or CSX as being subject to the same rules, but if they are operatiing over Metro-North's track wouldn't they be?

This is a wierd Emergency Order in my opinion. If overspeed events such as this are truly a widespread issue, why doesn't the EO apply to all US railroads? Anybody else think either Metro-North is being punished or the "all accidents are preventable so are therefor outlawed regardless of cost or reason" applies here? Can we now expect a new EO after every major incident?

Everything reasonable should be done to prevent deaths and injuries in the rail industry, but let's think smarter on effective ways to make a real difference. I personally agree that a second qualified person should be in the cab, but note that the FRA is willing to accept electronic oversight which comes with its own potential design and maintenance flaws.



Subject Written By Date/Time (PST)
  FRA issues E.O. 29 to MNCR OPRRMS 12-06-2013 - 20:29
  Re: FRA issues E.O. 29 to MNCR SP5103 12-06-2013 - 23:21
  Re: FRA issues E.O. 29 to MNCR Graham Buxton 12-07-2013 - 04:30
  Re: FRA issues E.O. 29 to MNCR J 12-07-2013 - 05:22
  Re: FRA issues E.O. 29 to MNCR Rich Hunn 12-07-2013 - 08:31
  Re: FRA issues E.O. 29 to MNCR--Not PTC ex-BN 12-07-2013 - 09:31
  Re: FRA issues E.O. 29 to MNCR--Not PTC Mark 12-07-2013 - 13:08
  Re: FRA issues E.O. 29 to MNCR--Not PTC ex-BN 12-07-2013 - 13:48
  Re: FRA issues E.O. 29 to MNCR--Not PTC The Unprofessional Iconoclast 12-07-2013 - 14:06
  Re: FRA issues E.O. 29 to MNCR--Not PTC Mark 12-07-2013 - 16:27
  Re: FRA issues E.O. 29 to MNCR--Not PTC mook 12-07-2013 - 16:40
  Re: FRA issues E.O. 29 to MNCR--Not PTC mook 12-07-2013 - 16:42
  Re: FRA issues E.O. 29 to MNCR--Not PTC Rich Hunn 12-07-2013 - 18:18


Go to: Message ListSearch
Subject: 
Your Name: 
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically.
 **    **   ******    *******   ********  **     ** 
  **  **   **    **  **     **     **     ***   *** 
   ****    **        **            **     **** **** 
    **     **        ********      **     ** *** ** 
    **     **        **     **     **     **     ** 
    **     **    **  **     **     **     **     ** 
    **      ******    *******      **     **     ** 
This message board is maintained by:Altamont Press
You can send us an email at altamontpress1@gmail.com