connecting from Empire Builder to Coast Starlight in Seattle

Amtrak Unlimited Discussion Forum

Help Support Amtrak Unlimited Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Joined
Oct 30, 2015
Messages
3
Hi all,

I was just trying to book a trip connecting from the Builder to the Starlight. I wanted to connect in Seattle 1) to get some time off the train 2) to avoid having to take a bus, possibly, in the middle of the night if the Builder is running very late and 3) to see some of Seattle during the layover. This used to be allowed and I did just that about 5 yrs ago or so. Does anyone know why this is no longer a published route? Is there any way to get it added as a published route before the new system kicks in?

Thanks!
 
There are plenty of options that aren't scheduled as an overnight connection. Sure the 4 hour connection in Portland can be an issue if the EB is late, but it's still four hours and not overnight.
 
As BCL points out, there is a same day connection in Portland, that is the standard connection point for the westbound Builder to the southbound Starlight for points south of Portland and has been for a long, long, long time. The only reason for having it would be to reach points between Seattle and Vancouver, WA, and there are same day Cascades trains that provide that service. There is no logic in having it as a published route, which isn't primarily to suit AGR awards, but to make logical connection options easily and transparently available for general booking.

I doubt that AGR would push to have a published route added at this late date, especially one that isn't logical. You can always go over to FlyerTalk and PM AGR Insider, though. Can't hurt to ask.
 
Last edited by a moderator:
As BCL points out, there is a same day connection in Portland, that is the standard connection point for the westbound Builder to the southbound Starlight for points south of Portland and has been for a long, long, long time. The only reason for having it would be to reach points between Seattle and Vancouver, WA, and there are same day Cascades trains that provide that service. There is no logic in having it as a published route, which isn't primarily to suit AGR awards, but to make logical connection options easily and transparently available for general booking.
There's no particular logic to some of the routes I see for (let's say) Chicago to Davis. I picked a random date and got the CZ straight to Davis, the CZ and CC with a 2 hour stopover in Sacramento, EB and CS with a transfer in Portland, Southwest Chief to LA with a bus/train/bus to Davis, and Southwest Chief to LA to transfer to the CS. Of those routes the only one that makes any sense to me from a transportation standpoint is straight to Davis on the California Zephyr. It's the cheapest and fastest route.
 
Those really should be, they are major cities (although from Albuquerque, Chicago -St. Paul would be by overnight bus according to a KCY-MSP test booking, the Southwest Chief and Builder don't connect). It isn't really an excuse but all the "published" connecting routes are entered manually, so many low-demand logical routings are missed.
 
Last edited by a moderator:
I was just trying to book a trip connecting from the Builder to the Starlight. I wanted to connect in Seattle 1) to get some time off the train 2) to avoid having to take a bus, possibly, in the middle of the night if the Builder is running very late and 3) to see some of Seattle during the layover.
So much to see and do in Seattle. Why not spend the day, and take the Starlight the following morning. That way all three of your objectives would be met, and with no worries or hassles.
 
Last edited by a moderator:
Back
Top