Amtrak Cascades

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Amtrak Cascades
AmtrakCascadesLogo.svg
Amtrak Cascades 2006.jpg
The Cascades at Carkeek Park in 2006.
Overview
Service type Inter-city rail
Status Active
Locale Pacific Northwest
First service May 1, 1971
Current operator(s) Amtrak
Ridership 2,335 daily
852,269 total (FY11)[1]
Website http://www.amtrakcascades.com
Route
Start Vancouver
End Eugene
Distance travelled 467 miles (752 km)
Train number(s) 501, 513, 507, 509, 513, 517 (odd) southbound
510, 500, 504, 506, 508, 516 (even) northbound
Technical
Rolling stock EMD F59PHI diesel locomotive
EMD F40PH locomotive used as non-powered control units
Talgo articulated tilting train sets
Track gauge 4 ft 8 12 in (1,435 mm)
Track owner(s) Union Pacific and BNSF
Departure board at Seattle's King Street Station in 1981, listing the Mount Rainier, the Pacific International, and other since-discontinued trains

The Amtrak Cascades is a passenger train route in the Pacific Northwest, operated by Amtrak in partnership with the U.S. states of Washington and Oregon and the Canadian province of British Columbia. It is named after the Cascade mountain range that the route parallels.

The corridor runs 156 miles (251 km) from Vancouver, British Columbia south to Seattle, Washington, continuing 310 miles (500 km) south via Portland, Oregon to Eugene, Oregon. Two daily trains travel to and from Vancouver, with Seattle or Portland as its starting or ending point; supplemental Thruway Motorcoach service connects travelers from Vancouver to trains heading south from Seattle, as well as providing additional service between Portland and Eugene, and connections to other Amtrak Thruway destinations in Washington and Oregon. The second daily service between Seattle and Vancouver, BC started on August 19, 2009.[2] As of December 2011 four trains run daily between Seattle and Portland, with two of those providing service to Eugene.[3]

Cascades is Amtrak's eighth-busiest route, and it carries the most passengers of any of the railroad's services outside of the Northeastern U.S. or California.[1] Total ridership for 2011 was over 850,000. During FY2011, the service had a total revenue of $30,025,126, an 8.9% increase over FY2010.[1] Farebox recovery ratio for the train has also increased from 48% in 2008 to 72% in 2010.[4]

History

The Mount Rainier in 1974. Note the dome car and coaches still bearing pre-Burlington Northern liveries.

The Amtrak Cascades route was originally operated as a joint partnership by the Northern Pacific, Great Northern, and Union Pacific prior to the creation of Amtrak in 1971.[5] In 2013 travel times between Seattle and Portland remained the same as they had been in 1966, with the fastest trains making the journey in 3 hours 30 minutes.[6][7]

When Amtrak began operations in 1971 there were three Seattle-Portland running and the connection to Vancouver was discontinued. These trains were initially unnamed, but with the advent of Amtrak's first "official" timetable in November 1971, one became the Coast Starlight (which continues south to Los Angeles), while the other two became the Mount Rainier and Puget Sound.[8]

1972 brought the return of the Vancouver service, with the inauguration of the Pacific International, operating with a dome car (unusual for short runs).[9]

Amtrak introduced the Seattle–Salt Lake City, Utah Pioneer in 1977. The Pioneer took over one round-trip between Seattle and Portland, arriving in Seattle in the late evening and Portland just before noon. Amtrak eliminated the Puget Sound altogether, and shifted the Mount Rainier's northbound trip to replace it.[10]:59

The corridor grew in 1980 with the State of Oregon financially subsidizing two daily round trips between Portland and Eugene. Named the Willamette Valley, these trains were discontinued in April 1982. This was on the heels of the Pacific International's discontinuance in September 1981.[8] This left three trains on the Portland-Seattle corridor: the Coast Starlight, the Pioneer and the Mount Rainier. This situation remained unchanged for the next 12 years.

Expansion in the 1990s and 2000s

Amtrak Cascades consist in Portland, Oregon with NPCU at the head of the train.

In 1994, Amtrak instituted a six-month trial run of modern Talgo equipment over the Portland-Seattle corridor. Amtrak named this service Northwest Talgo, and announced that it would institute a second, conventional train on the corridor (supplementing the Mount Rainier) once the trial concluded. Regular service began on April 1, 1994. Looking toward the future, Amtrak did an exhibition trip from Vancouver through to Eugene. Amtrak introduced the replacement Mount Adams on October 30.[11][12] At the same time, the state of Oregon and Amtrak agreed to extend the Mount Rainier to Eugene through June 1995, with Oregon paying two-thirds of the $1.5 million subsidy.[13]

Vancouver service returned on May 26, 1995, when the Mount Baker International began running between Vancouver and Seattle. The state of Washington leased Talgo equipment similar to the demonstrator from 1994.[14][15] Amtrak renamed the Mount Rainier the Cascadia in October 1995; the new name reflected the joint Oregon-Washington operations of the train.[16]

A third Seattle-Portland corridor train began in 1998, replacing the discontinued long-distance Pioneer. By spring 1998, all three Seattle–Portland/Eugene trains were using leased Talgo equipment, while the Vancouver train used conventional equipment. Amtrak introduced a temporary Pacific Northwest brand for all four trains, dropping individual names, in preparation for the introduction of new Talgo equipment built in the United States and owned by the state of Washington. Amtrak announced the new Amtrak Cascades brand in the Fall 1998 timetable; the new equipment began operation in December.[17][18] Amtrak extended a second train to Eugene in late 2000.

In 2004, the Rail Plus program began,[citation needed] allowing cross-ticketing between Sound Transit's Sounder commuter rail and Amtrak north from Seattle to Everett.

The corridor has continued to grow in recent years, with another Portland-Seattle train arriving in 2006, and the long-awaited through service between Vancouver and Portland, eliminating the need to transfer in Seattle, beginning in August 2009[19] as a pilot project to determine whether a train permanently operating on the route would be feasible. With the Canadian federal government requesting Amtrak to pay for border control costs for the second daily train, the train was scheduled to be discontinued on October 31, 2010. However, Washington State and Canadian officials held discussions in an attempt to continue the service,[20] which resulted in the Canadian government's permanently waiving the fee.[21]

Total ridership for 2008 was 774,421, the highest annual ridership since inception of the service in 1993.[22] Ridership declined in 2009 to 740,154[23] but rose 13% in fiscal year 2010 to 836,499 riders.[23]

Rolling stock

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

<templatestyles src="Stack/styles.css"/>

The baggage car from the Mount Adams set separate from the rest of the cars. Note the shared-wheel arrangement.
Inside the bistro car with the route on the ceiling.

Service on the Cascades route is provided by five articulated trainsets manufactured by Talgo, a Spanish company. These cars are designed to passively tilt into curves, allowing the train to pass through them at higher speeds. Despite a maximum design speed of 124 miles per hour (200 km/h), current track and safety requirements limit the train's speed to 79 miles per hour (127 km/h), although $781 million work is currently underway for the Cascades route which will allow them to operate at speeds up to 110 miles per hour (180 km/h).[24]

The Cascades is painted in a special scheme consisting of cream, brown and dark green. The train is normally operated in a push-pull configuration with an EMD F59PHI or GE P42DC at one end, a 12- or 13-car Talgo-built trainset, and an unpowered EMD F40PH locomotive called a Non-Powered Control Unit (NPCU) on the other end used as a cab car.[25]:140 The NPCU contains a concrete weight to meet FRA weight requirements for collision safety as well as regulations for crash safety for the Talgo cars, which are not FRA crash-rated.

Four of the five trainsets are named after mountains in the Cascade Range: Mount Rainier, Mount Baker, Mount Adams, and Mount Hood. The last set is named after Mount Olympus, in the Olympic Range. A typical train consists of a baggage car; two business-class coaches; one lounge/dining car; one cafe car (also known as the Bistro car); six standard coaches; and one service car.[26] From the mid 1990s to the May 12th, 2008, Amtrak System timestable, full service dining was available on trains going north out of Seattle's King Street Station to Vancouver, BC. The southern trains to Portland Oregon briefly had full dining services until the May 16th, 1999 Systems Timestable. As noted, the cars still run but, are now only used for lounge services and are open to all passengers. One of the five sets currently in service, the Mount Adams set was originally built as a demonstrator for potential service between Los Angeles, California and Las Vegas, Nevada. It was built with two additional standard coaches, for a total of 14 cars. It operated on the Seattle-Vancouver, B.C. run for several years in its original configuration. It was also originally painted in a different color scheme, using the blue, black and silver of Amtrak's Pacific Surfliner instead of the green, brown and cream found on the other sets.[25]:139

A six-car spare set, including a baggage car, service car, lounge-dining car, café car and two standard coaches, was also built. The two additional coaches from the fifth trainset and the two coaches from the spare set were placed in service on four of the other sets, resulting in four 13-car trains and one 12-car train. Fins on the baggage and service cars serve only as an aesthetic transition from the high top of the American-built locomotives to the roof of the low-slung European-designed passenger cars.

During 2013, two new Talgo 8 trainsets, owned by the Oregon Department of Transportation, entered traffic to enable further expansion of services.[27] These trainsets differ from the original five by having cab cars integrated into the set, therefore not requiring the use of ex-F40PH NPCUs. Additionally, these sets also maintain other minor interior differences such as cafe car layout and onboard electrical systems. The two new sets are named Mount Bachelor and Mount Jefferson, after the respective peaks located in Oregon.

Funding

Funding for the route is provided separately by the states of Oregon and Washington, with Union Station in Portland serving as the dividing point between the two. As of July 1, 2006, Washington state has funded four daily round trips between Seattle and Portland. Washington also funds two daily round trips between Seattle and Vancouver, BC. Oregon funds two daily round trips between Eugene and Portland. The seven trainsets are organized into semi-regular operating cycles, but no particular train always has one route.

Local partnerships

As a result of Cascades service being jointly funded by the Washington and Oregon departments of transportation, public transit agencies and local municipalities can offer a variety of discounts, including companion ticket coupons.

  • FlexPass and University of Washington UPass holders receive a 15% discount (discount code varies) on all regular Cascades travel. Employers participating in these programs may also receive a limited number of free companion ticket coupons for distribution to employees.[28]
  • The Sound Transit RailPlus program allows riders to use weekday Cascades trains between Everett and Seattle with the Sounder commuter rail fare structure.[29]

The Cascades service also benefits from Sound Transit's track upgrades for Sounder service, notably the upcoming Point Defiance Bypass project.

Proposed changes

According to its long-range plan, the WSDOT Rail Office plans eventual service of 13 daily round trips between Seattle and Portland and 4–6 round trips between Seattle and Bellingham, with four of those extending to Vancouver, BC.[30] Amtrak Cascades travels along the entirety of the proposed Pacific Northwest High Speed Rail Corridor; the incremental improvements are designed to result in eventual higher-speed service. According to WSDOT, the "hundreds of curves" in the current route and the cost of acquiring land and constructing a brand new route" make upgrades so cost-prohibitive that at most speeds of 110 mph (177 km/h) can be achieved.[31]

The eventual high-speed rail service according to the long-range plan should result in the following travel times:

  • Seattle to Portland – 3:30 (2006); 3:20 (2017, assuming completion of Point Defiance bypass);[31] 2:30 (planned)
  • Seattle to Vancouver BC – 3:55 (2006); 2:45 (planned)
  • Vancouver BC to Portland – 7:55 (2009); 5:25 (planned)

In order to increase train speeds and frequency to meet these goals, a number of incremental track improvement projects must be completed. Gates and signals must be improved, some grade crossings must be separated, track must be replaced or upgraded and station capacities must be increased.

In order to extend the second daily Seattle to Bellingham round trip to Vancouver, BNSF was required to make track improvements in Canada, to which the government of British Columbia was asked to contribute financially. On March 1, 2007, an agreement between the province, Amtrak, and BNSF was reached, allowing a second daily train to and from Vancouver.[32] The project involved building an 11,000-foot (3.35 km) siding in Delta, BC at a cost of US$7 million; construction started in 2007 and has been completed.

In December 2008, WSDOT published a mid-range plan detailing projects needed to achieve the midpoint level of service proposed in the long-range plan.[33]

WSDOT received more than $800 million in high-speed rail stimulus funds for projects discussed in the mid-range plan, since the corridor is one of the approved high-speed corridors eligible for money from ARRA.[34] The deadline for spending the stimulus funds is September 2017.

In 2009, Oregon applied for a $2.1 billion Federal grant to redevelop the unused Oregon Electric Railway tracks, parallel to the Cascades' route between Eugene and Portland.[35] But it did not receive the grant. Instead, analysis of alternative routes to enable more passenger trains and higher speeds proceeded. In 2015, the current route, with numerous upgrades, was chosen by the Project Team as the Recommended Preferred Alternative.[36] The schedule is for the Leadership Council to vote on this in December 2015, then a Draft Tier 1 Environmental Impact Statement should be released in 2016 and hearings held on it, for the Leadership Council to finalize the Recommended Selected Alternative in 2017, then publish the Final Tier 1 EIS and receive the Record of Decision in 2018. [37] Then if funds can be found, design and engineering must be done before any construction can begin.


Point Defiance Bypass

Map of Point Defiance Bypass.
  • Partnership with Sound Transit to bypass BNSF Railway Puget Sound shore track for an alignment between Tacoma at the north end and the Nisqually River at the south.
  • Increases train speeds in this corridor with a straighter, shorter track alignment.
  • Eliminates the need for Cascades trains to use the single-track Nelson Bennett Tunnel
  • First phase decreases travel time through the corridor by 6 minutes; second phase decreases travel time by at least another 5 minutes.
  • Sound Transit construction of the line between Tacoma and Lakewood was completed in 2012 after feasibility studies, design work and acquisition of land had begun in 2005.[38] The first phase of construction began in June 2009; by that time the completion date had been pushed back to 2019.[39] In 2010, the American Recovery and Reinvestment Act provided additional funding for the project, enough to bring the completion date forward to 2017.[39]
  • Construction between Lakewood and Dupont began in December, 2014 and should be completed by the summer of 2017.[40][41]

Ridership statistics

Data from the Washington State Department of Transportation.[42][43][44][45]

Year 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006
Ridership 94,061 180,209 286,656 304,566 349,761 425,138 452,334 530,218 560,381 584,346 589,743 603,059 636,092 629,996
YoY Diff. N/A 86,148 106,447 17,910 45,195 75,377 27,196 77,884 30,163 23,965 5,397 13,316 33,033 -6,096
YoY Diff. % N/A 91.6% 59.1% 6.2% 14.8% 21.6% 6.4% 17.2% 5.7% 4.3% 0.1% 2.3% 5.5% -1.0%
Year 2007 2008 2009 2010 2011 2012 2013
Ridership 676,765 774,531 761,610 838,251 847,709 845,099 811,692
YoY Diff. 46,769 97,766 -12,921 76,641 9,458 -2,610 -33,407
YoY Diff. % 7.4% 14.4% -1.7% 10.1% 1.1% -0.3% -4.0%

See also

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. The Official guide of the Railways and Steam Navigation Lines of the U.S., Rand McNally & Company, May 1966, The guide shows that the service was operated jointly, some trains using Seattle's King Street Station and the rest Seattle's Union Station
  6. The Official guide of the Railways and Steam Navigation Lines of the U.S., Rand McNally & Company, May 1966
  7. Amtrak Winter-Spring Timetable 2013
  8. 8.0 8.1 Schafer, Mike, Bob Johnston and Kevin McKinney.All Aboard Amtrak. Piscataway, NJ: Railpace Co., 1991
  9. Zimmerman, Karl. Amtrak at Milepost 10. Park Forest IL: PTJ Publishing, 1981.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Template:Solomon-Amtrak
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Oregon DOT
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. WSDOT - Second Amtrak Cascades Train to Canada
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. http://oregonpassengerrail.org/files/library/newsletter/opr-newsletter-fall-2015-final-20151013.pdf
  37. http://oregonpassengerrail.org/page/schedule
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 WSDOT - Project - Rail - Tacoma - Bypass of Point Defiance
  40. http://www.wsdot.wa.gov/projects/rail/pnwrc_ptdefiance/
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.

External links

<templatestyles src="Stack/styles.css"/>

Script error: No such module "Attached KML".