Re: UP collision in Kansas this morning.
Author: ex-BN
Date: 07-17-2013 - 22:07

Thank you. That's not how we do it. We report "Switches normal" when releasing the TW. Then all trains still approach prepared to stop. Its a favorite test for the TM's. Perhaps UP will follow suit after this wreck.

Leaving a mainline switch open should strike the fear that running a red block does yet for some reason it happens much too often. My policy has always been to line the switch, test the lock, look at the target, walk away, turn and inspect the switch from a distance. And I don't think I could show my face at work after having left one open--even in signalled track. I don't believe in the "fear" method of railroading these days (think safety glasses, vests etc.) but certain deadly operating rules should scare the hell out of an employee if not followed.

Of course this case in Kansas may have been vandalism--I'm speaking in general terms.


OPRRMS Wrote:
-------------------------------------------------------
> ex-BN Wrote:
> --------------------------------------------------
> -----
> > I am familiar with territory (dark) where it is
> > still required to approach facing point
> swithches
> > prepared to stop even though they have been
> > reported "lined for the main track". I thought
> > this was an FRA requirement.
> >
> > Is this track partially signalled for switches?
>
> > Or do the rules not require being prepared to
> > stop?
>
> OK, I'll expand my response to your question about
> this yesterday.
>
> The crew of the local had verbally informed the
> dispatcher that all switches used had been
> re-lined and locked for mainline movement (GCOR
> 8.3 and 14.7), then they released their Track
> Warrant. Any subsequent trains would thus be
> operating at Maximum Authorized Speed and not be
> required to be prepared to stop short of switches.
> Crew members are still required to observe the
> position of switches (GCOR 8.2), but not slow down
> for them in anticipation.



Subject Written By Date/Time (PST)
  UP collision in Kansas this morning. OPRRMS 07-16-2013 - 10:02
  Re: UP collision in Kansas this morning. ex-BN 07-16-2013 - 10:08
  Re: UP collision in Kansas this morning. OPRRMS 07-16-2013 - 11:19
  Re: UP collision in Kansas this morning. Sir Nigel Gresley 07-16-2013 - 13:51
  Re: UP collision in Kansas this morning. Mark 07-16-2013 - 15:03
  Re: UP collision in Kansas this morning. Dr Dreg 07-16-2013 - 15:14
  Re: UP collision in Kansas this morning. Sir Nigel Gresley 07-17-2013 - 01:42
  Re: UP collision in Kansas this morning. Heritage Hunter 07-16-2013 - 15:25
  Re: UP collision in Kansas this morning. RWS 07-16-2013 - 23:05
  Re: UP collision in Kansas this morning. Movie Critic 07-17-2013 - 01:49
  Re: UP collision in Kansas this morning. E 07-17-2013 - 09:05
  Re: UP collision in Kansas this morning. ex-BN 07-17-2013 - 09:48
  Re: UP collision in Kansas this morning. OPRRMS 07-17-2013 - 12:36
  Re: UP collision in Kansas this morning. ex-BN 07-17-2013 - 22:07
  Re: UP collision in Kansas this morning. SPAF 07-17-2013 - 23:36
  Re: UP collision in Kansas this morning. OPRRMS 07-18-2013 - 09:54
  Re: UP collision in Kansas this morning. Dr Zarkoff 07-18-2013 - 16:58
  Re: UP collision in Kansas this morning. Shortline Sammie 07-18-2013 - 21:04
  Re: UP collision in Kansas this morning. ron 07-16-2013 - 15:14


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