You are here: home   Blogs   The Range Blog   How coal is already congesting Washington's railways
The Range Blog

How coal is already congesting Washington's railways

Document Actions
Tip Jar Donation

Your donation supports independent non-profit journalism from High Country News.

Enter amount:

$
sightline | Oct 26, 2011 06:00 AM

By Eric de Place, Sightline.org

This post is part of the research project: The Dirt on Coal

Washington’s rail system is congested in places. Adding dozens of coal trains each day, without also big new capacity improvements, could cripple the system with gridlock. All that is common knowledge. Less well-known is this: coal shipments are already causing problems.

To understand what’s going on, it’s useful to zero in on the northwest portion of the state’s railway system. Here’s a close look at northwest Washington, the area most directly affected by Cherry Point coal exports:

train map

This Cambridge Systematics map from 2006 is the most recent comprehensive analysis of the state’s rail system. The green on the mainline between Everett and Canada indicates adequate capacity, but the numerous red dots indicate hotspots of local congestion that plague the system.

What’s happening on the ground there now? In May 2011, the regional rail experts at the Cascadia Center produced the “Cross-Border Freight Rail Improvement Study,” for the Whatcom Council of Governments (along with a companion volume “Cross-Border Passenger Rail Improvement Study). It turns out that things in the area are not going smoothly.

There are a variety of reasons, but one reason is coal.

To understand why, it’s helpful to understand the basic configuration of the rail system. Here’s a fragment of BNSF’s regional map, showing more local detail:

Train map closeup

The mainline track extends north-south between New Westminster, BC and Bellingham. Jutting off to the west from the mainline are two branch lines, one north of the border and one south. The Canadian side’s branch line (in yellow) runs to the Westshore coal terminal at Roberts Bank; the American side has a branch line, called the Custer Intalco line, (in orange) to Cherry Point.

Coal shipments on the Canadian branch line to Westshore are already clogging the system, and for a considerable distance. In fact, the Cascadia report notes that:

Increased congestion on the east-west Roberts Bank rail corridor that BNSF uses to deliver coal to the Westshore Coal Terminal are causing the railroad to hold trains south of Bellingham.

In other words, coal trains clogging the branch line are sending ripples of congestion well down the mainline. And the same scenario will play out south of the border if coal exports began to move from Cherry Point, as the Cascadia study points out:

Future cross border shipments of coal and other commodities by BNSF may be greatly influenced by a new facility near the border proposed by SSA Marine… The entrance to the [branch line] has the potential to create an operational bottleneck if the train frequencies expected by the Terminal materialize. Industry switch engines, slowly moving loaded coal trains and the resulting empties could result in volumes of traffic that would tax the mainline and small yard that is located at Custer. With the close proximity of the border to the Custer Intalco line, future congestion may result.

“Future congestion may result” is a good candidate for the understatement of the year. To understand why, let’s do the numbers.

According to Cascadia, BNSF runs an average of 15 trains per day from the Seattle-Everett area up to Vancouver, BC plus 2 Amtrak passenger runs. Yet according to the terminal proponents, the terminal would put up to 18 roundtrip trains on the system. In other words, trains serving Cherry Point would more than double the existing rail traffic in that area. That’s before the region sees any other freight expansions, and before the region gets new passenger rail service.

Now take a closer look at the first map up above. (If it’s not clear, click to enlarge it or see page 29 of this pdf.) The red boxes display the number of trains per day (top number) and the actual practical capacity (bottom number). Between Burlington and the Canadian border there are places where the system’s practical capacity is 14, or even just 7, trains per day. In these places, of course, the system is already congested. Adding 18 trains per day doesn’t seem possible.

Here’s the point: even if we removed every single freight and passenger train—and we did nothing but serve Cherry Point—those shipments alone would swamp the northern portion of the state’s rail system.

To be sure, rail congestion is a fixable problem, at least to an extent. There are a number of infrastructure and technology improvements that would boost capacity in the system. The catch, however, is that these improvements tend to be costly, and the majority of them are likely to get billed to the public. In fact, as we’ll explore in some follow-up posts, there is good reason to worry that taxpayers—not BNSF and not the coal companies—will be asked to expand the state’s railway system to make way for coal.

In the meantime, the biggest loser may be the region’s long-sought high speed rail service. Unless taxpayers are prepared to open their wallets again, it could well turn out that reliable passenger rail in the Northwest will run into the brick wall of Asia-bound coal.

But more on that later.

This post would not have been written without valuable research assistance from Dave Kershner.

Essays in the Range blog are not written by High Country News. The authors are solely responsible for the content.

Originally posted at The Daily Score, a Sightline Institute blog.

Email Newsletter

The West in your Inbox

Follow Us

Follow us on Facebook! Follow us on Twitter! Follow our RSS feeds!
  1. In the field with a Montana couple hunting wolves | Amid bitter controversy over allowing hunters and ...
  2. How right-wing emigrants conquered North Idaho | Conservative transplants largely from California h...
  3. Seeking balance in Oregon's timber country | Can logging towns and old-growth forests both thri...
  4. Save our gauges | Important USGS stream gauges imperiled by austerit...
  5. Rants from the hill: Trapping the bees | What to do when 50,000 honeybees hive up inside th...
  1. Don't mess with the Forest Service | How a determined and feisty Forest Service held of...
  2. How right-wing emigrants conquered North Idaho | Conservative transplants largely from California h...
  3. How technology detected a huge mine landslide before it happened | Employees at a Kennecott copper mine outside Salt ...
  4. Seeking balance in Oregon's timber country | Can logging towns and old-growth forests both thri...
  5. The Forest Service battles placer mining with an obscure law | A little-known 1955 law gives the Forest Service a...
Subscriber Alert
HCN Classifieds
More from Climate & Pollution
Winter: an encore edition The author celebrates the (temporary) return of winter in Montana
Mixed messages on methane And why you shouldn't make too much of any of them -- yet
Mapping your way to better health California is a test-ground for the new field of Geomedicine
All Climate & Pollution
 
© 2013 High Country News, all rights reserved. | privacy policy | terms of use | powered by Plone | site by Groundwire | design by Ryan Foster

HCN Logo High Country News in your inbox!


Sign up now to receive our weekly email newsletter!

• The best weekly collection of Western environmental news

• An at-a-glance look at our latest news and analysis


This box was designed to only appear once. It uses a "cookie" (a small file stored on your computer) to remember that it has shown the box to you.

If you are seeing this box appear multiple times, then something is not allowing the cookie to be stored properly. Browsers can be set to not allow cookies, and some people choose to disallow cookies for security reasons. If your browser is setup this way, please consider adding "www.hcn.org" as an exception to your no-cookies rule. For information about how to do this, just search the Web for "browser cookie exceptions."

If you're sure this isn't the problem, then it could be related to how your browser has stored information from our site in previous visits. Browsers often "cache" images, text and other website content in order to make them appear faster if you ever go back. Sometimes the browser's cache can be corrupted or become outdated. The simplest fix for this is to try reloading the page. If that doesn't fix the problem, it may be necessary to clear your temporary items from your browser. Again, a web search will provide you with lots of options and instructions.

Either way, we're sorry to hear that this box is getting in the way of your enjoyment of the HCN website. If you continue to have trouble, please contact our Subscriber Services team.