03.03.2015 Views

California State Rail Plan 2005-06 to 2015-16

California State Rail Plan 2005-06 to 2015-16

California State Rail Plan 2005-06 to 2015-16

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter X – Potential New Services<br />

• There is strong ridership on the one daily Coast Starlight round-trip and on<br />

the three daily Amtrak Thruway buses.<br />

• An existing local organization –the CRCC, is actively planning the service,<br />

and implementation plans have been completed.<br />

SACRAMENTO TO RENO<br />

The extension of intercity rail service from Sacramen<strong>to</strong> <strong>to</strong> Reno would bring <strong>State</strong>supported<br />

rail service <strong>to</strong> the Truckee/Tahoe and Reno/Sparks <strong>to</strong>urist areas as well<br />

as provide relief <strong>to</strong> the highly congested I-80 –Bay Area <strong>to</strong> Reno corridor.<br />

Background<br />

Amtrak’s <strong>California</strong> Zephyr and connecting buses <strong>to</strong> the Capi<strong>to</strong>l Corridor and<br />

San Joaquins serve Reno and intermediate I-80 Corridor points.<br />

The <strong>California</strong> Zephyr makes s<strong>to</strong>ps at Reno, Truckee, Colfax, Roseville, and<br />

Sacramen<strong>to</strong> once daily in each direction on its route <strong>to</strong> Chicago. Also, Amtrak<br />

buses connect <strong>to</strong> three San Joaquins and four Capi<strong>to</strong>l Corridor trains and serve<br />

Reno/Sparks, Truckee, Soda Springs, Colfax, Auburn, Rocklin, Roseville, and<br />

Sacramen<strong>to</strong>. Ridership on this bus route was 37,000 in 2004-05.<br />

In 1995, the Department and the Nevada Department of Transportation published<br />

the Sacramen<strong>to</strong>-Tahoe-Reno Intercity <strong>Rail</strong> Study that examined the feasibility of<br />

expanding passenger rail service along the I-80/Tahoe corridor from Sacramen<strong>to</strong><br />

<strong>to</strong> Truckee and Reno/Sparks on the UP line on which the <strong>California</strong> Zephyr<br />

currently operates. A number of scenarios were studied involving extending<br />

varying numbers of Capi<strong>to</strong>l Corridor trains from Sacramen<strong>to</strong> <strong>to</strong> Reno/Sparks, and<br />

all scenarios were determined <strong>to</strong> be feasible. In 2002, the CCJPA and the<br />

Placer County Transportation <strong>Plan</strong>ning Agency initiated a study <strong>to</strong> extend the<br />

Capi<strong>to</strong>l Corridor <strong>to</strong> Reno. The study was intended <strong>to</strong> provide current ridership,<br />

revenue, and train operating cost estimates for the train extension, and the capital<br />

costs for necessary station and track improvements. However, the study was<br />

suspended in March <strong>2005</strong> as a result of the UP’s decision <strong>to</strong> not conduct additional<br />

network modeling or consider operation of new passenger train service <strong>to</strong> Reno at<br />

this time. The UP has experienced a significant increase in freight traffic and has<br />

made a business decision <strong>to</strong> focus its efforts at this time on addressing additional<br />

freight demand.<br />

Operating <strong>Plan</strong><br />

The Department’s ten-year operating plan includes the extension of one<br />

Capi<strong>to</strong>l Corridor round-trip from Auburn <strong>to</strong> Reno/Sparks in 2008-09, and<br />

a second round-trip in 2010-11. This rail service would be supplemented by<br />

continued operation of existing bus service that runs over the same route as the<br />

train, but at other times of the day. This service would require an appropriate level<br />

of financial participation from the <strong>State</strong> of Nevada (and potentially Nevada<br />

business interests).<br />

135

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!