:angry:And the construction efforts in MT and ND have ramped up big time. My BNSF guy said the 5-6 hour delays being seen this week thru this area should be likely much of the summer until late October.
:-(
I'll bring snacks.
:angry:And the construction efforts in MT and ND have ramped up big time. My BNSF guy said the 5-6 hour delays being seen this week thru this area should be likely much of the summer until late October.
:-(
so how longs will amtrak keep the reestablished connection of eb 27 to cs 11 in pdx?And the construction efforts in MT and ND have ramped up big time. My BNSF guy said the 5-6 hour delays being seen this week thru this area should be likely much of the summer until late October.
:-(
It's a myth. They are not. I have it first hand from the District Manager that Amtrak is not footing the bill for missed connections in PDX. Every effort is being made to ensure that all passengers with a connection understand this.so how longs will amtrak keep the reestablished connection of eb 27 to cs 11 in pdx?And the construction efforts in MT and ND have ramped up big time. My BNSF guy said the 5-6 hour delays being seen this week thru this area should be likely much of the summer until late October.
:-(
ok, hold on a minute. amtrak will book the connection of 27 to 11. but it's not a guaranteed connection? as of last week, we booked an october trip with the connection and were told we could no longer book and overnight in pdx(it's an agr redemption)so we booked spk-lax without the overnight in pdx.. what sort of bs is this? EB_OBS, you are the pride of amtrak but your bosses are self serving bs artistsIt's a myth. They are not. I have it first hand from the District Manager that Amtrak is not footing the bill for missed connections in PDX. Every effort is being made to ensure that all passengers with a connection understand this.so how longs will amtrak keep the reestablished connection of eb 27 to cs 11 in pdx?And the construction efforts in MT and ND have ramped up big time. My BNSF guy said the 5-6 hour delays being seen this week thru this area should be likely much of the summer until late October.
:-(
i just called amtrak and spoke with an agent, asked her if 27 to 11 was a guaranteed connection and what that meant, and was told it meant amtrak would do whatever it took to get you to your destination and if that included overnight lodging in pdx that amtrak would cover itok, hold on a minute. amtrak will book the connection of 27 to 11. but it's not a guaranteed connection? as of last week, we booked an october trip with the connection and were told we could no longer book and overnight in pdx(it's an agr redemption)so we booked spk-lax without the overnight in pdx.. what sort of bs is this? EB_OBS, you are the pride of amtrak but your bosses are self serving bs artistsIt's a myth. They are not. I have it first hand from the District Manager that Amtrak is not footing the bill for missed connections in PDX. Every effort is being made to ensure that all passengers with a connection understand this.so how longs will amtrak keep the reestablished connection of eb 27 to cs 11 in pdx?And the construction efforts in MT and ND have ramped up big time. My BNSF guy said the 5-6 hour delays being seen this week thru this area should be likely much of the summer until late October.
:-(
One left on our one-way trip on the EB to PDX in July.On ours, it's the same out, return home, there's 2 room left.Strangely enough, for my upcoming trip the EB sleepers are entirely sold out, but there are 8 or more roomettes on the CS during the same time frame.
yeah, but as i understood the above post of EB_OBS, who, imho, ought to know amtrak is not on the hook for a night in pdx. i put much more confidence in what he has to say than a random agentWith average arrival delays into PDX well over 3 hours over the past month or so this could be a challenge making the connection, but if Amtrak is still on the hook for a night in Portland, other than arriving a day late at your destination I guess things could be worse.
![]()
Over 4 hours and the train hadn't made it through Cheney yet? :blink: I can walk that distance that fast! Of course it helps that it's downhill between Spokane and Cheney.BNSF track gang had a construction window and with #7 so late, #27 missed it and had to bus to PDX.Does anyone know what the "service disruption" is for #27 that was supposed to arrive in Portland on Wednesday morning? Amtrak's status map still shows it parked somewhere north of Pasco.Empire Builder "troubles" back to the normal SNAFUs this AM- #8 just under 6 hours behind in MN, #7 in WA over 5 hours late and #27 suffering a service disruption. Bummer.
The equipment finally left SPK at 2:15pm. At 6:30pm it hadn't even made it thru Cheney, WA. Finally arrived into PDX 4:08am.
There's a lot of construction and expansion going on right now between SPK and PSC.
The derailment has also caused cancellation of Northstar Commuter Rail service today, which runs on BNSF tracks between Minneapolis and Big Lake.Well another derailment, this time east of St. Cloud, MN. ETO, 8:00PM CT.
#7 had already made it west of there before the derailment. Unfortunately #8 will have to hold 'til the tracks open.
If they have any food left!I was worried about getting dinner on 7 ,,, maybe I will be getting breakfast as well,,,,, before it rolls into GPK
Via the Empire Builder group on Facebook:looks like 8 is taking the Wilmar route - however is currently stopped south of Morehead, as of 0940am.
BNSF derailed a freight between Elk River and Ramsey, MN this morning. Both mains on the Staples Sub are blocked. All North star trains canceled this morning.
Yep, just waiting for BNSF pilots on-duty and expect to take up to 5-6 additional hours according to BNSF.looks like 8 is taking the Wilmar route - however is currently stopped south of Morehead, as of 0940am.
right. also are you interested in the brooklyn bridge or some prime land in florida?Back to the issue of "guaranteed connections"...
It seems like some agents are saying that many EB connections are guaranteed, and that some are not. I thought that any connection to (the EB or any other train) booked as one ticket was a guaranteed connection. If you want to book a connection that is too short, Amtrak requires you to book two tickets.
They've made exceptions to this - allegedly contacting everyone who had valid connections to tell them that their connections were no longer valid. So, it seems like if you bought a ticket for that connection, and Amtrak hasn't called you to tell you that your connection isn't valid, then the responsibility is on them, right?
Bummer to have no lounge on such a long trip but KFC and Subway Chow is better than most of the stuff sold @ New York Prices in the Cafe!OH, and did I forget to mention that #8(12) had to set out its lounge car last night at SPK due to a broken brake pipe? Subway and KFC all the way to CHI.
What's next?