Published: February 25, 2026
Colorado’s passenger-rail conversation is often framed as two separate stories: a Front Range “spine” along I-25, and a harder, longer-term quest to offer real alternatives to the I-70 mountain drive. The Western Rail Coalition (WRC) sits squarely in the second camp. It is not a state agency or an operator; it’s a coalition of elected officials, transportation advocates, business voices, and engaged residents working to build momentum for passenger rail west of the Front Range—especially in the I-70 mountain corridor.
What makes the WRC worth watching is that its agenda overlaps with a project that is moving through the public process: CDOT’s “Colorado Mountain Rail” (often shortened to Mountain Rail)—a state-led effort that aims to restore passenger rail along the existing line from Denver toward northwest Colorado. The coalition’s broader vision extends beyond that first CDOT corridor, pitching a network that could eventually connect mountain valleys, airports, resort communities, and Western Slope cities with the Front Range—mostly by leveraging existing rail rights-of-way and focusing on phased rollouts.
A seven-unit helper set of Rio Grande power runs light through Red Cliff, Colorado on Tennessee Pass in March, 1981. American-Rails.com collection.The Western Rail Coalition describes itself as a Rocky Mountain region group formed to support the study and advancement of expanded passenger rail in the I-70 Mountain Corridor west of the Front Range, with technical support from advocates at Greater Denver Transit.
In practical terms, the coalition plays three roles:
That last point matters because the coalition’s biggest credibility boost is that Colorado has already taken a major step toward enabling more mountain passenger service: a long-term access agreement with Union Pacific for the Moffat Tunnel route (the core gateway through the Continental Divide on the Denver–Bond–northwest Colorado line).
The corridor
CDOT’s Mountain Rail program is focused on using the existing rail line from Denver to Craig, with station locations still under consideration in many communities. The Western Rail Coalition frames this alignment as the “Central Corridor” (Denver to Bond and then west toward Grand Junction via Glenwood Canyon) plus the branch north toward Steamboat Springs and Craig.
The key enabler: the Moffat Tunnel access deal
In May 2025, Colorado and Union Pacific signed a 25-year passenger-rail access arrangement tied to UP’s continued use of the Moffat Tunnel—an agreement the governor’s office described as establishing Colorado’s license for up to three daily roundtrips (or up to a set number of annual train miles) for Mountain Passenger Rail, with room to expand in later phases.
When service might begin
The governor’s office has similarly pointed to a daily year-round roundtrip to Granby by 2026, with flexibility to expand later toward Winter Park, Steamboat Springs, Hayden, and Craig.
Bottom line: If you’re asking “when do trains actually start running,” the clearest answer today is: Denver–Winter Park/Fraser–Granby service is targeted for late 2026 (with a November 1, 2026 goal).
What happens after Denver–Granby?
Beyond that starter segment, CDOT planning documents outline multiple service patterns—including options that eventually reach Craig and add local overlays in the Yampa Valley area—while emphasizing that later phases depend on infrastructure, equipment, operating agreements, and funding partnerships.
This “phased implementation” approach is where the Western Rail Coalition’s broader wish list intersects reality: a first train to Granby can demonstrate demand, build operating muscle, and create political momentum for extensions.
The idea
The Central Corridor is essentially Colorado’s most famous existing passenger route: the Union Pacific line used by Amtrak’s California Zephyr, the seasonal Winter Park Express, and the tourist-focused Canyon Spirit (formerly Rocky Mountaineer). The coalition argues that demand for shorter “intra-Colorado” trips (especially Denver–Glenwood Springs/Grand Junction) is strong and that additional service could complement the Zephyr rather than compete with it.
How it’s doing
The coalition’s own materials explicitly tie near-term progress in this corridor to CDOT’s Mountain Rail work—because Mountain Rail uses the same core gateway through the Moffat Tunnel and the line toward Bond.
But there is an important reality check: additional year-round intrastate trains between Denver and Grand Junction would require capacity, operating slots, station work, equipment, and negotiated host-railroad terms beyond the initial Denver–Granby phase. CDOT’s planning emphasizes that major projects will be phased and that equipment availability can be a near-term constraint (often pointing toward used equipment for initial service because new trainsets take years to procure).
When could it start?
No public document sets a firm start date for added Denver–Glenwood–Grand Junction frequencies as a state service. The best grounded answer today is:
The idea
The coalition highlights the Craig Branch north from Bond through communities such as Oak Creek, Steamboat Springs, and Hayden (Yampa Valley Regional Airport), noting that passenger service ended decades ago and that freight traffic is currently minimal compared with historical levels.
How it’s doing
This corridor is being folded into CDOT’s broader Mountain Rail concept—at least as an eventual endpoint. CDOT’s documents include service options that extend trains to Craig and add a local overlay in the Yampa Valley area, while noting that local participation may be required for certain local-pattern service costs.
When could it start?
The public-facing timeline still points to Denver–Granby first, then later extension phases. The coalition’s own Mountain Rail page mirrors that: late-2026 starter service first, with hopes to extend to Steamboat Springs and Craig later.
So, for the Yampa Valley: no firm “service begins” date yet, but it is at least attached to an active CDOT project pipeline.
The idea
If Mountain Rail is the corridor that already has state momentum, Tennessee Pass is the corridor that has romance and a complicated set of ownership/lease questions.
The Western Rail Coalition notes that the Tennessee Pass line runs roughly 222 miles from Pueblo up the Arkansas River Valley, over Tennessee Pass, then down the Eagle River to Dotsero—remaining largely intact but dormant for decades after Union Pacific deemed it surplus following the mid-1990s merger era.
The coalition’s “initial phase”: Eagle Valley passenger rail
WRC’s Tennessee Pass page describes an initial phase focused on passenger service in the Eagle Valley, and the coalition amplified that concept in a letter urging the state to explore an “Eagle River Valley Service.”
That letter is notable because it claims a time-sensitive window: it says Union Pacific’s out-of-service Tennessee Pass Line is leased to Rio Grande Pacific Corporation, which the coalition describes as interested in operating a local passenger service with modern, low-emission rail vehicles—but that continued interest depends on clear state/local support and may not survive if the lease is not renewed.
How it’s doing
Public reporting has shown local officials discussing task forces and participation steps to explore passenger rail feasibility on the line. The coalition also continues to press for CDOT to pursue a formal service development plan that would quantify costs and benefits.
When could it start?
Unlike Mountain Rail, Tennessee Pass service does not have a state-set launch date. Based on what’s public:
A realistic read: Tennessee Pass/Eagle Valley is in advocacy-and-feasibility territory, not “construction-to-service” territory—yet.
The idea
The coalition proposes passenger trains on the line between Grand Junction and Montrose, with intermediate stops (Delta, Olathe, Montrose Regional Airport), arguing that low freight volumes could allow frequent all-day passenger operations.
How it’s doing / when service begins
WRC’s own language is consistent: it supports “studying what would be required.” No public launch date is identified.
The idea
This is the coalition’s most unconventional proposal: a “rolling road” system that would load trucks/semitrailers onto low-floor rail wagons between Denver and Grand Junction, carrying drivers in passenger cars—an alpine model inspired by European services.
Status
This is best understood as an advocacy concept meant to broaden the I-70 conversation beyond “add lanes vs. do nothing.” There’s media coverage of similar ideas being floated locally, but it is not currently paired with a state implementation date in the way Mountain Rail is.
The Western Rail Coalition also points readers toward the separate Front Range Passenger Rail effort—an intercity service plan along the I-25 corridor from Fort Collins through Denver to Pueblo (with possible extensions north to Wyoming and south toward New Mexico).
While that’s not “Western Colorado,” it matters because a Front Range spine can feed mountain services (and vice versa). Colorado legislative materials for the Front Range project have indicated a planning path that included completion targets and a potential sales tax election timeframe.
In other words: Colorado’s passenger rail future is likely to be built as an ecosystem—Front Range ridership and governance can strengthen the case for mountain expansions, while mountain ridership and congestion relief can strengthen the argument for statewide rail investment.
Here’s the most grounded “corridor-by-corridor” outlook based on what is public today:
Passenger rail is often less constrained by “does the idea work?” than by “can the coalition hold long enough to fund, negotiate, and phase it?” The Western Rail Coalition is trying to solve that political problem for Western Colorado by:
If Colorado hits its late-2026 Denver–Granby target, the Western Rail Coalition’s next challenge will be turning “starter line success” into a credible roadmap for the harder corridors—where service development plans, governance, and operating funding will decide whether Western Rail becomes a network…or remains a map.
Apr 20, 26 11:03 PM
Apr 20, 26 10:46 PM
Apr 20, 26 02:30 PM
Apr 20, 26 09:43 AM
Apr 20, 26 09:40 AM
Apr 20, 26 09:38 AM
Apr 20, 26 09:34 AM
Apr 20, 26 09:32 AM
Apr 20, 26 09:31 AM
Apr 19, 26 09:21 PM
Apr 19, 26 04:21 PM
Apr 19, 26 12:10 PM
Apr 19, 26 10:38 AM
Apr 19, 26 10:36 AM
Apr 19, 26 10:34 AM
Apr 19, 26 10:32 AM
Apr 19, 26 10:30 AM
Apr 19, 26 10:03 AM
Apr 19, 26 12:11 AM
Apr 18, 26 11:57 PM
Apr 18, 26 11:01 AM
Apr 18, 26 10:54 AM
Apr 18, 26 10:51 AM
Apr 18, 26 10:47 AM
Apr 18, 26 10:45 AM
Apr 18, 26 10:39 AM
Apr 18, 26 10:34 AM
Apr 17, 26 11:30 PM
Apr 17, 26 11:08 PM
Apr 17, 26 09:47 PM
Apr 17, 26 09:27 PM
Apr 17, 26 02:48 PM
Apr 17, 26 02:28 PM
Apr 17, 26 01:46 PM
Apr 17, 26 01:42 PM
Apr 17, 26 01:38 PM
Apr 17, 26 01:34 PM
Apr 17, 26 01:31 PM
Apr 17, 26 01:27 PM
Apr 17, 26 01:23 PM
Apr 17, 26 01:19 PM
Apr 17, 26 09:46 AM
Apr 16, 26 10:52 PM
Apr 16, 26 04:34 PM
Apr 16, 26 12:55 PM
Apr 16, 26 12:33 PM
Apr 16, 26 12:29 PM
Apr 16, 26 12:24 PM
Apr 16, 26 12:13 PM
Apr 16, 26 11:59 AM