Empire Builder Summer Blues Started Early this year

[trainman74]

PUT?

I assume that's supposed to be "Portland Union Terminal." Although it's not much of a terminal, given all those run-through tracks. Seems like more of a station -- oh, wait, that's exactly what it says in giant letters on the clock tower.

 

[Eric S]

PUT?

I assume that's supposed to be "Portland Union Terminal." Although it's not much of a terminal, given all those run-through tracks. Seems like more of a station -- oh, wait, that's exactly what it says in giant letters on the clock tower.

That's sort of what I figured he meant. But I thought that perhaps there was something else he was trying to refer to.

And thanks for the photo, I always liked how Portland (PDX, PUS, PUT) and Denver (DEN, DUS, DUT) have signage promoting train travel.

 

[Swadian Hardcore]

I just like calling it PUT. I've always thought PDX was transplated from the airport code. PUT was orignally a ground transport code and has always been one, so I just use that instead.

It is actually an official code:

PUT PORTLAND, OR

 

[Eric S]

An official code for what? (For what mode of transport, or service provider, or transportation terminal?)

 

[Swadian Hardcore]

An official code for what? (For what mode of transport, or service provider, or transportation terminal?)

Oh come on, you know what! :giggle: I am Swadian after all. But I will not risk getting busted by an Admin again!

 

[Swadian Hardcore]

Anyways, no more PUT-debates, please! Let's look at some delays instead. 7 (22) is over three hours late, that's no good but it's through the worst section so hopefully things will get better. At least it's making up a few minutes at every station.

8 (22) is screwed over though, 3:42 late and it's just out of Williston! Then it's gonna lose more throughout North Dakota! Expect a 8:30 PM arrival tommorow in CHI. No good. Pax will miss everything except the LSL. Summer may be over, but the delays sure aren't!

Also, take a look at 1 (23), it's an hour early into SAS! Great performance for the Sun Belter. It might not run every day, it might not carry nearly as much pax as the EB, it might cover very little of its costs, but the SL sure is reliable! I remember back when it was the one horrendously late every time and the EB was very punctual back then. Seeing the flip, happening everywhere.

 

[jebr]

Hopefully some of these EB trains won't get caught up in work in Minnesota that starts at 8:30. It seems that in order to avoid them the train can't be more than about two hours late hitting the Minnesota stretch, which rarely happens. (I'm sure some people on the train on Saturday would've liked that early of a train...it was running over four hours late and one of the passengers needed to be in Winona by noon!)

 

[Steve4031]

What's hAppening west of Spokane to cause 7 to lose time. This is happening today and 1 or 2 other days.

 

[Swadian Hardcore]

What's hAppening west of Spokane to cause 7 to lose time. This is happening today and 1 or 2 other days.

I can think of two reasons: either train congestion or slow turnaround at SEA/PUT after a late arrival from CHI.

8 (22) is in trouble. 5 hours late, it'll arrive in CHI at about 8:50 PM. For some reason it lost an extra hour CBS-MKE. The 30 and 50 both left already, more heavy loads on the LSL.

 

[NW cannonball]

Now, 7(24) lost 2 hours 50 minutes near SCD -- wonder what happened there?

 

[aurbo]

The lead engine conked out between MSP and SCD. They had to set out the bad engine and replace it with a BNSF engine.

 

[Linda T]

What's hAppening west of Spokane to cause 7 to lose time. This is happening today and 1 or 2 other days.

I can think of two reasons: either train congestion or slow turnaround at SEA/PUT after a late arrival from CHI.

8 (22) is in trouble. 5 hours late, it'll arrive in CHI at about 8:50 PM. For some reason it lost an extra hour CBS-MKE. The 30 and 50 both left already, more heavy loads on the LSL.

I take it the 8 (22), the 22 means it left SEA on Sunday? The #7 broke down and it took 5 hours to repair. It arrived late and of course needed prepped to become the 8. We were all given Subway lunch boxes, and then still got supper on the train. Three cheers for the crew keeping announcements going concerning delays. We went through most of the track work unaffected, but it was having lost our slot that made us lose 40+ minutes late due to having to wait a while for a freight.

The #50 was ontime from CHI to HUN (where I got off), so instead of busing us to IND, they had to bus us to CIN. Oh well... because I read AU I knew what was gonna happen even before my trip started.

 

[Ryan]

I take it the 8 (22), the 22 means it left SEA on Sunday?

Correct.

 

[gn2276]

Train 8 getting into Seattle today got in 39 mins early. Should be an on time departure out of Seattle today.

 

[Swadian Hardcore]

Train 8 getting into Seattle today got in 39 mins early. Should be an on time departure out of Seattle today.

You mean Train 7 right? Indeed, 8 (25) departed on time today. So is the 28. 7 (24) is nowhere near as lucky, it's 6:39 late and getting wrose at every stop! The train may still need to get through some construction before battling train congestion. Definately will be an afternoon arrival in SEA/PUT. Passengers may miss connections to the Coast Starlight.

 

[JayPea]

As late as 7 is, it's more likely it will be annulled in Spokane and passengers bused to points west.

 

[Swadian Hardcore]

As late as 7 is, it's more likely it will be annulled in Spokane and passengers bused to points west.

We'll see what happens.

 

[montana mike]

Now that 7 is well over 7 hours behind in MT I would say the odds are high that it turns in SPK. #8 isn';t doing a lot better-4 hours behind in ND-with the worst delays ahead of it. This has not been a good september for timekeeping on the EBs

 

[Fan_Trains]

7(25) Had departed CHI on time, Arrived GLN, 4 min early, departed on time, Arrived MKE 6 min early, Departed on time, Arrived CBS 4 min early, Departed 1 min late, Arrived POG 2 min Late, Departed 4 min late, Arrived WDL 1 min Late, Departed2 min late, Arrived TOH 4 min Late, Departed 9 min late, Arrived LSE 1 min Late, Departed 4 min Late, Arrived WIN 20 min Late, Departed 19 min Late, Arrived RDW 17 min Late, Departed 19 min Late, Arrived MSP 11 min Early, and Departed 0n time.

 

[AmtrakBlue]

Train 8 getting into Seattle today got in 39 mins early. Should be an on time departure out of Seattle today.

You mean Train 7 right? Indeed, 8 (25) departed on time today. So is the 28. 7 (24) is nowhere near as lucky, it's 6:39 late and getting wrose at every stop! The train may still need to get through some construction before battling train congestion. Definately will be an afternoon arrival in SEA/PUT. Passengers may miss connections to the Coast Starlight.

This is an Amtrak forum, please use Amtrak station codes, not Greyhound's.And I wish you would change your signature because I think it is inappropriate for a train forum. I feel like you're trying to sell tickets for Greyhound.

 

[jebr]

Train 8 getting into Seattle today got in 39 mins early. Should be an on time departure out of Seattle today.

You mean Train 7 right? Indeed, 8 (25) departed on time today. So is the 28. 7 (24) is nowhere near as lucky, it's 6:39 late and getting wrose at every stop! The train may still need to get through some construction before battling train congestion. Definately will be an afternoon arrival in SEA/PUT. Passengers may miss connections to the Coast Starlight.

This is an Amtrak forum, please use Amtrak station codes, not Greyhound's.And I wish you would change your signature because I think it is inappropriate for a train forum. I feel like you're trying to sell tickets for Greyhound.

Most passengers wouldn't even know the station code. I never knew the station codes for where I was going on Greyhound...they do not use them on any public-facing media as far as I could tell. Even internal documentation (that I can find) usually uses the full town name whenever possible. (I've traveled Greyhound before, and until now I didn't know they had station codes!)
As for the signature, if it doesn't meet guidelines, I would report it to the admins. (I'm not reporting it because, in my personal opinion, it meets guidelines.)

 

[jebr]

It looks like 7(24) is no longer losing time, though a turn in Spokane seems very likely. 7(25) is only 51 minutes down in Devil's Lake, so that's promising, though 8(24) was just as far behind hitting the construction zone and is now 7 hr. and 29 min. behind Not looking good!

 

[EB_OBS]

As late as 7 is, it's more likely it will be annulled in Spokane and passengers bused to points west.

We'll see what happens.

No buses available. It's running thru.

 

[amtrakmichigan]

#7 pulled into Sandpoint, Id 8hr 40min late. Looks like it lost a locomotive somewhere along the way. Lead unit was a BNSF loco followed by a Amtrak P42

 

[Bob Dylan]

#7 pulled into Sandpoint, Id 8hr 40min late. Looks like it lost a locomotive somewhere along the way. Lead unit was a BNSF loco followed by a Amtrak P42

Railfans would say that you get to see Idaho and Eastern Washington in Daylight! ^_^ Poor Empire Builder, it's Inherited the Curse of the Old Sunset East: Terrible OTP!