ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

History of the Spokane Portland and Seattle Railway

Updated on October 4, 2016

Northwest's Own Railway

The Northwest's own Railway was literally a pawn in the railroad game in the very early 1900s. James J Hill and E H Herriman (owner of the Union Pacific Railroad) were in a bitter feud in the Northwest. Hill had gained control of the Northern Pacific Railroad in the Depression of 1893, and thus he had a monopoly in the Pacific Northwest. Herriman intended to build a line from Salt Lake City to Portland and then paralleling the Northern Pacific to Seattle. Hill didn't want that to happen so the Spokane Portland and Seattle was built.

Starting from Vancouver Washington (with trackage rights into portland over the Northern Pacific) the SP&S built east along the Columbia River from Vancouver to Pasco. This author has railfanned and has take a number of trips through the Columbia River gorge, which is very beautiful. Anyway, at Pasco, the line turns North east and follows the Snake River a tributary of the Columbia to south of Kahlous Wash. At this point it heads inland to the third largest city in Washington, Spokane.

The SP&S operated its first train over the entire railroad in 1909, opening a direct link for its parents the Great Northern and Northern Pacific a direct link to Portland. At a little town of Wishram, the SP&S built a spectacular bridge that wyed on the north end so trains coming from the south could head east or west. This line was built south to Bend Oregon. Timber lands as well as a connection with the Western Pacific Railroad was the catalyst for building the Oregon Trunk, a wholly own subsidiary of the SP&S. Hill had always dreamed of getting to California, and in 1931 he made it, from Bend though Klamath Falls the Great Northern built again and on over the syskiyous to a town called Bieber California. It was at this town that the Western Pacifi c built to, from Keddie California A distance of 112 miles to meet the Great Northern and have a direct connection to the Northwest.

The SP&S didn't stop the Union Pacific from reaching the Northwest. They bought the Oregon Railroad and Navigation Company (OR&N) which had built a line on the south side of the Columbia River. This railroad linked with the UP in Salt Lake City.

The SP&S operated as a separate railroad but was under the direction of the Parent roads, as each had members on the SP&S Board of directors. They tacked on to parent locomotive orders, and that is how they gained the 700 class of Northerns that look identical to the Northern Pacific's 4-8-4s. They alternated every ten years the use of the GN and NP rail yards in Spokane and thus kept costs down.

The line itself was so well built with slight grade that it can handle anything. James J Hill believed it was to well built, however it stands in testimony today as one of the heaviest used BNSF routes in the Pacific Northwest, with export grain and coal loads trans-versing it daily, along with intermodal trains. It is one of three crossings of the cascades and has proven itself useful day in and day out.

In 1970 the SP&S joined it's parents Great Northern and Northern Pacific merged with the Chicago Burlington & Quincy to create the Burlington Northern Railroad. Today, Amtrak's train 27 and 28 the Portland section of the Empire Builder transverses the line that it has since the 1930s.

Wishram WA Railroad Bridge

Former SP&S Bridge, looking north. Notice how the bridge forms two legs of the wye.
Former SP&S Bridge, looking north. Notice how the bridge forms two legs of the wye. | Source

Passenger Trains

The SP&S had three sets of passenger trains operating over its line in the 40s-60s. These were Trains 1 and 2, the westbound and eastbound Great Northern's Empire Builder, and the Northern Pacific's North Coast Limited. Trains 3 and 4 were the Great Northern's Western Star and the Northern Pacific's Mainstreeter. Trains 5 and 6 were locals operated by the SP$S providing service to the towns that the streamliners skipped.

Trains 1 and 2 were numbered like the parents crack passenger trains until they changed in 1952. The SP&S kept those numbers until the very end (and that goes for 3 and 4 as well). The Great Northern, added a Portland section to their Empire Builder (Mid 30s) and Western Star (1952). These trains split in Spokane and would have a consist looking like this:

E7 Locomotive: 750 and occasionally F3 #800 or 801

SPS Baggage Car

2 GN Coaches

SPS Diner

2-3 GN Sleeping cars

The break up (westbound) or make up (eastbound) of the Empire Builder took place around midnight on a nightly basis. The Streamliner (#1) as it was known as, would leave while the Builder was being reassembled and by about 3 am, the Streamliner was in Pasco at the Northern Pacific station repeating the ritual with the North Coast Limited. The combined train would follow rthe Columbia River and reach Portland around 9:30 am.

Trains 3 and 4 were the secondary trains of the GN and NP were the work horses of the line, carrying the mail and packages. They had working RPOs and carried passengers. Both of these trains would carry tour groups to the national parks.

Trains 5 and 6 was the workhorse of the SP&S. It was a local that traveled the same lines, as the 1-2,3 and 4 but stopped at every little hamlet along the way.


Freight trains operated from Portland across the Columbia River to Vancouver WA then east to Spokane. At roughly the midway point is Wishram, a small railroad town about 100 east of Portland, from there they diverged to the south over the Inside Gateway or continued east to Spokane where they were then split into other trains heading east, Mostly over the parent roads of the Great Northern or Northern Pacific. In Spokane, the agreement was made that every ten years the SP&S would share the yard of each parent railroad. It is the only agreement that I know of where a railroad changes facilities every few years.

The SP&S primary reason was to forward the freight for the parent roads and to serve the communities along the Columbia River. It also was built to compete with the Union Pacific that was building on the Southern bank of the Columbia River directly to Portland.

Looks like SP&S #2 getting ready in  Portland OR.  This train left portland about 3 pm arriving in Spokane at 11:30.
Looks like SP&S #2 getting ready in Portland OR. This train left portland about 3 pm arriving in Spokane at 11:30. | Source


There are a number of places that you can find information on the Spokane Portland and Seattle:

The North Bank Road: The Spokane Portland and Seattle John T. Gaertner Washington State University Press 1990

The best book I've come across is this one:

SP&S The Spokane Portland and Seattle Railway Ed Austin & Tom Dill Pacific Fast Mail 1996.

This book has Maps, diagrams and history, giving one of the most complete picture of the history of the SP&S Railway


    0 of 8192 characters used
    Post Comment

    • profile image

      R. Shewbert 

      6 months ago

      I lived in wishram washington, from 1960 to 1977

    • bn9900 profile imageAUTHOR

      Clayton Hartford 

      5 years ago from Alger WA

      Thank you for the kind comments, this line is roughly 300 miles end to end and he Main Cities on the line are Vancouver WA, Wishram, Pasco, and Spokane. Best of Luck with the layout.

    • alocsin profile image


      5 years ago from Orange County, CA

      Nice to meet another railroad buff here on Hubpages. I was not aware of this line and was thinking it might be self-contained enough to model in HO scale. Voting this Up and Useful.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)