Jump to content




Photo

Empire Builder #8: Departing SEA on June 16, 2017


  • Please log in to reply
7 replies to this topic

#1 Dakota 400

Dakota 400

    OBS Chief

  • Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male

Posted 17 June 2017 - 02:49 PM

I see on the Real Time Status Map that #8 left Seattle 1 hour and 54 minutes late on Friday.  I have been following the schedule recently since I will be aboard in July and this late departure is unusual.  The train almost always leaves on time.  Any information as to why the train left so late on Friday?



#2 Thirdrail7

Thirdrail7

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 1,944 posts

Posted 17 June 2017 - 02:58 PM

It looks they added extra equipment.


They say laughter is the best medicine. Obviously they never posted on AU.


#3 Dakota 400

Dakota 400

    OBS Chief

  • Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male

Posted 17 June 2017 - 04:15 PM

It looks they added extra equipment.

 

Thanks for your reply.  How do you know this?  There must be a web site with this information about which I am not aware.



#4 OBS

OBS

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 1,099 posts
  • Gender:Male

Posted 17 June 2017 - 06:07 PM

 

It looks they added extra equipment.

 

Thanks for your reply.  How do you know this?  There must be a web site with this information about which I am not aware.

 

He is an Amtrak employee...



#5 AmtrakBlue

AmtrakBlue

    Engineer

  • Gathering Committee Member
  • PipPipPipPipPipPip
  • 9,103 posts
  • Gender:Female
  • Location:Delaware

Posted 17 June 2017 - 06:08 PM

 

 

It looks they added extra equipment.

 

Thanks for your reply.  How do you know this?  There must be a web site with this information about which I am not aware.

 

He is an Amtrak employee...

 

Aw, you gave it away.   I was going to say he has a crystal ball.  :D


2011: Jun: WIL=>WAS=>WIL (NER) // Nov: WIL=>WAS=>CHI=>PRO (NER=>CL=>CZ)
2012: Apr: WIL=>WAS=>WIL (NER) // May(NTD): WIL=>PHL=>WIL (NER) / PHL=>PAO=>PHL (Keystone) // Aug: WIL=>WAS (NER) / BWI=>WIL (NER) // Oct(Gathering): PHL=>WIL (NER) / PHL=>HAR=>PHL (Keystone) / SEPTA, NJT, PATCO, River Line, Princeton Dinky
2013: May(NTD): WIL=>WAS=>WIL (NER)  // Oct (Gathering): WIL=>CHI (Card) / CHI=>MKE=>GLN=>CHI() / CHI=>JOL=>CHI () / CHI=>WIL(CL=>NER) / CTA, Metra. SEPTA (WIL=>NRK) // Nov:  PHL=>PHL (Autumn Express) 
2014: May(NTD):  WIL=>PHL=>WIL(NER) // May:  WIL=>BOS=>WIL(NER) day trip

2014: Oct(Gathering): WIL=>NYP=>TOL(pd-NER=>LSL) / TOL=>CHI=>LAX=>EMY(pts-LSL=>SWC=>CS) / EMY=>CHI=>TOL (pts-CZ-CL) / TOL=>WAS=>WIL(pd-CL=>NER)
2015: May: CHI=>CIN(pd-Card) / CIN=>WIL(pts Card)
2015;  Oct(Gathering):  WIL=>WAS(Acela) / ALX=>WAS(NER) / WAS=>BAL(Acela) / WAS=>WIL(NER)

2016: Mar: WIL=>WAS=>WIL (NER)  // Oct:  WIL=>NYP=>NYP=>WIL (Autumn Express) 


#6 Dakota 400

Dakota 400

    OBS Chief

  • Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male

Posted 17 June 2017 - 07:14 PM

I appreciate the information, but why should this this lead to such a delay for the train's departure?



#7 AmtrakBlue

AmtrakBlue

    Engineer

  • Gathering Committee Member
  • PipPipPipPipPipPip
  • 9,103 posts
  • Gender:Female
  • Location:Delaware

Posted 17 June 2017 - 07:30 PM

Just a wild, uneducated guess as to why it can take so long.  And I have no idea what Seattle is like as I've never been there.

 

EB is on track 1, extra equipment is on track 3.  Switcher engine goes to get extra equipment...it takes time to hook up cars to engine.  Switcher engine is ready to move cars from track 3 to track one, but wait, here comes a long freight on track 2.  Then when it finally gets onto track 1, it takes time to hook up the cars to the EB and unhook the switcher engine.  

 

And to add to the delay, the extra equipment may have been added to the middle of the consist, so you have to separate cars and put the additional cars in, etc, etc.


2011: Jun: WIL=>WAS=>WIL (NER) // Nov: WIL=>WAS=>CHI=>PRO (NER=>CL=>CZ)
2012: Apr: WIL=>WAS=>WIL (NER) // May(NTD): WIL=>PHL=>WIL (NER) / PHL=>PAO=>PHL (Keystone) // Aug: WIL=>WAS (NER) / BWI=>WIL (NER) // Oct(Gathering): PHL=>WIL (NER) / PHL=>HAR=>PHL (Keystone) / SEPTA, NJT, PATCO, River Line, Princeton Dinky
2013: May(NTD): WIL=>WAS=>WIL (NER)  // Oct (Gathering): WIL=>CHI (Card) / CHI=>MKE=>GLN=>CHI() / CHI=>JOL=>CHI () / CHI=>WIL(CL=>NER) / CTA, Metra. SEPTA (WIL=>NRK) // Nov:  PHL=>PHL (Autumn Express) 
2014: May(NTD):  WIL=>PHL=>WIL(NER) // May:  WIL=>BOS=>WIL(NER) day trip

2014: Oct(Gathering): WIL=>NYP=>TOL(pd-NER=>LSL) / TOL=>CHI=>LAX=>EMY(pts-LSL=>SWC=>CS) / EMY=>CHI=>TOL (pts-CZ-CL) / TOL=>WAS=>WIL(pd-CL=>NER)
2015: May: CHI=>CIN(pd-Card) / CIN=>WIL(pts Card)
2015;  Oct(Gathering):  WIL=>WAS(Acela) / ALX=>WAS(NER) / WAS=>BAL(Acela) / WAS=>WIL(NER)

2016: Mar: WIL=>WAS=>WIL (NER)  // Oct:  WIL=>NYP=>NYP=>WIL (Autumn Express) 


#8 Thirdrail7

Thirdrail7

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 1,944 posts

Posted 17 June 2017 - 07:31 PM

Sometimes, orders come down later than others. You find out that because of a situation elsewhere, you have to add equipment that will get set off (like in SPK as an example). So, now you have to wait for the equipment, get it serviced and added into both ends of your train so it can get cut off enroute.

 

This is something that happens quite often across the system. A perfect example is yesterday, when a train was held (just as it was ready to depart)  so they could add additional equipment to accommodate displaced passengers from another train that was delayed by a trespasser strike.


Edited by Thirdrail7, 17 June 2017 - 07:32 PM.

They say laughter is the best medicine. Obviously they never posted on AU.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users