Southeast High Speed Rail Corridor

The Southeast Corridor (SEC) is a proposed passenger rail transportation project in the Mid-Atlantic and Southeastern United States to extend high-speed passenger rail services from Washington, D.C. south through Richmond, Petersburg with a spur to Norfolk[1] (the Hampton Roads region) in Virginia through Raleigh, Durham, Greensboro and south to Charlotte in North Carolina and connect with the existing high-speed rail corridor from D.C. to Boston, Massachusetts known as the Northeast Corridor. Since first established in 1992, the U.S. Department of Transportation (USDOT) has extended the corridor to Atlanta, Georgia and Macon, Georgia; Greenville, South Carolina; Columbia, South Carolina; Jacksonville, Florida; and Birmingham, Alabama.

Corridor as designated by the Federal Railroad Administration

History

No funding has been allocated in recent years. Most funding for the SEHSR in the early 2000s was by the USDOT and the states of North Carolina and Virginia. Both states already fund some non-high-speed rail service operated for them by Amtrak, and own locomotives and passenger cars.[2]

On January 28, 2010, the White House announced that Southeast Corridor would receive $620 Million of its request.[3] This money is primarily for capacity upgrades along the Raleigh–Charlotte portion of the corridor (aka the Piedmont Improvement Program), along with some money for the Richmond–D.C. portion, as the Tier II Environmental Impact Statement for the important Raleigh–Richmond portion is not expected to be complete until 2015.

The first large section of the SEHSR, from Washington, D.C. through Virginia and North Carolina south to Charlotte, was projected in 2010 to begin service sometime between 2018 and 2022, based on funding availability.[2]

In 2019, the State of Virginia announced it would acquire the rights to use the abandoned portion of the CSX S Line between Petersburg, Virginia and Ridgeway, North Carolina.[4]

Later in 2020, the State of North Carolina received federal funding allowing for the purchase of the active segment of the CSX S line between Ridgeway and Raleigh.[5]

Route

D.C.–Richmond

Expanding the Long Bridge over the Potomac River from two to four tracks will allow a doubling of the amount of Amtrak service between Washington D.C. and Virginia, including services proposed under the SEHSR plan.

The D.C. to Richmond segment of the proposed Corridor travels along 123 miles of CSX track currently used by CSX freight trains, non-high-speed Amtrak trains, and the VRE commuter rail's Fredericksburg Line. $75 million in federal funding issued in September 2012 paid for construction of a third main track in Stafford and Prince William counties,[6] while Virginia's Atlantic Gateway infrastructure project funded additional main tracks in two segments in Fairfax County along with some of the design and engineering costs for providing relief for the capacity constrained Long Bridge over the Potomac River between DC and Alexandria.[7] In October of 2014, the Federal Railroad Administration filed a notice of intent to perform (in partnership with the Virginia Department of Rail and Public Transportation) a Tier II Environmental Impact Statement (EIS) for upgrading this segment, with an aim of increasing train frequency and cutting the current travel time by thirty minutes.[8] The draft version of the Tier II EIS was released in September of 2017, with the final version was released in May of 2019.[9] In 2019, Virginia agreed to acquire 350 miles of right of way from CSX, effectively giving the Commonwealth control over much of the Richmond-D.C. leg of the corridor.[10] As part of the deal, Virginia will build a new two-track rail bridge over the Potomac River for Amtrak and VRE trains parallel to the existing Long Bridge. The new bridge will take passenger traffic off the existing bridge, which will serve only freight traffic. The Long Bridge has historically been one of the worst bottlenecks in the national rail system.[11] The Commonwealth of Virginia will cover roughly one-third of the costs, federal funds (including Amtrak) will cover another third, and the remainder will be sought from a variety of regional partners, such as VRE, the Northern Virginia Transportation Authority, the District of Columbia, and Maryland, all of which have pledged support for bridge expansion.

Richmond–Norfolk (Hampton Roads spur)

In 1996, USDOT added a connection from Richmond east to Newport News to SEHSR. However, with the extension of Northeast Regional Amtrak service to Norfolk in December 2012,[12] the Virginia Department of Rail and Public Transportation (DRPT) re-evaluated rail access to the Hampton Roads metropolitan area and on September 1, 2012 announced that while rail service from Richmond to Newport News will be maintained, the preferred high-speed corridor has been shifted to a Richmond–Petersburg–Norfolk alignment.[1]

Richmond–Raleigh

CSX's main "A" (red) and "S" (blue) lines. Note the removed track between Centralia, Virginia and Norlina, North Carolina, indicated by the dashed line.

Between Richmond and Raleigh, the corridor uses the CSX S line (the former Seaboard Air Line main line),[13] which generally parallels US 1. The tracks on the segment of this line between Centralia, Virginia and Norlina, North Carolina were removed in the late 1980s and through traffic shifted to the CSX A line (the former Atlantic Coast Line main line). The relative absence of freight trains along the remaining portions of the S line will mean that significant curve straightening and other work can be accomplished without disrupting current service.

The S line also provides a more direct route for trains between Raleigh and the Northeast via Richmond. Since the abandonment of the S line, Amtrak trains traveling north of Raleigh use the A line and the North Carolina Railroad between Raleigh and Selma. (The A line does not pass through Raleigh, instead running roughly parallel to I-95 through Rocky Mount, Wilson, and Fayetteville.)

The proposed project does not include electrification of the railway, unlike in the Northeast Corridor. However, top speeds would be raised from 79 to 110 miles per hour (127 to 177 km/h), resulting in an average speed of 85–87 mph (137–140 km/h). Travel time currently between Richmond and Raleigh on the Carolinian and Silver Star is close to four hours, but full implementation as proposed would reduce this to nearly two hours. The proposed two hours in time savings is nearly evenly split between the shorter distance provided by the more direct S line routing and speed increases.

The overall project cost for fully restoring and improving the S line, including the curve straightening and new bridges necessary to raise top speeds to 110 mph (180 km/h), has been estimated at roughly $4 billion. In response, the North Carolina-Virginia Interstate High-Speed Rail Compact Commission has proposed investigating a staged effort that would first restore the S line to its 79 mph (127 km/h) max speed state from the 1980s, and pursue other improvements only after service was restored.[14] This would have the benefit of reducing the travel time between Richmond and Raleigh by nearly one hour for a much lower startup cost, though it may somewhat increase the cost of performing the later improvements. The Silver Star would also travel over a restored S line, as it did before 1986, and would also see the improvement in travel time.[15]

As part of Atlantic Gateway, Virginia sought to take control of the abandoned S Line right-of-way between Petersburg and the North Carolina border.[16] In late 2019, negotiations were concluded and CSX, Virginia, and North Carolina reached separate deals that called for the two states to acquire the portions of the S-Line within their respective boundaries. Virginia will acquire 65 miles (105 km) of the S-Line between the North Carolina-Virginia line and Petersburg, while North Carolina will acquire 10 miles (16 km) of the line between Ridgeway and the North Carolina-Virginia line. North Carolina officials said that the Virginia deal will boost their efforts to acquire the remainder of the S-Line to Raleigh, which remains in light service as the Norlina Subdivision of CSX carrying some freight traffic.[10] The North Carolina Department of Transportation was awarded a $47.5 million federal grant in 2020 to purchase the line.[13]

Raleigh–Charlotte

The segment of the corridor between Raleigh and Charlotte travels along currently operational lines of the North Carolina Railroad, roughly parallel to I-85. The portion of the route between Raleigh and Greensboro is over the H-line, while the Greensboro–Charlotte section travels along Norfolk Southern's main line. (While the lines are owned by the North Carolina Railroad, Norfolk Southern has an operational contract for trackage rights.) Both see current freight and passenger traffic (Amtrak's Carolinian and Piedmont), with freight traffic along the main line particularly heavy. However, double-tracking was removed from several sections of the Greensboro to Charlotte main line since its heyday, and significant signal upgrades, curve straightening, super-elevation, and restoration will be required to support high-speed passenger service along the corridor without interfering with freight operations.

NCDOT has worked with NS, CSX, and the NCRR to restore the double-tracking and make other incremental upgrades, a process that reduced the travel time between Raleigh and Charlotte by 35 minutes from 2001 to 2010. Additional work began in 2010 under the Piedmont Improvement Project, funded by a $520 million grant under the 2009 ARRA stimulus.[17] The PIP projects included restoring complete double-track between Greensboro and Charlotte, adding passing sidings between Raleigh and Greensboro, straightening several curves, closing crossings, and building bridges to separate train and highway movements, all of which were completed by January 2018.[18] The ARRA funds, along with funds from the City of Raleigh and NC DOT, also constructed Raleigh Union Station, a replacement train station located at the Boylan Wye intersection of the H and S lines. The station opened in July 2018 with a concourse and platform along the H line only, but space is reserved for future construction of a northern concourse and platform along the S-line for future SEHSR trains.

Charlotte–Atlanta

Added to the SEHSR Corridor in 1998, a feasibility study was completed in August 2008 on the further extension from Charlotte through Spartanburg and Greenville, South Carolina to Atlanta and then Macon, Georgia.[19] Further extensions to Savannah, Georgia, along with an extension from Raleigh through Columbia, South Carolina to Savannah and on to Jacksonville, Florida are also part of the federally designated SEHSR corridor, but those extensions have not yet been studied. All feasibility studies have suggested that synergy between parts of SEHSR and the neighboring Northeast Corridor is important. The Charlotte to Raleigh portion is predicted to be much more profitable with the corridor connected to D.C. and the Northeast Corridor. Similarly, the feasibility study found it much easier to justify the Charlotte to Atlanta and Macon route if the Charlotte to D.C. portion was completed. Atlanta is also the connecting point between SEHSR and federally designated Gulf Coast Corridor.[20]

In May 2013, the Federal Railroad Administration (FRA), in cooperation with the Georgia Department of Transportation (GDOT), initiated a Tier I Environmental Impact Statement (EIS) for passenger rail service between Charlotte and Atlanta. During the scoping phase, the six possible routes from the feasibility study were reduced to the following three:

  • Alternative 1: Southern Crescent
Using the existing Norfolk Southern right-of-way, coextensive with the middle leg of Amtrak's Crescent. The estimated 237-mile (381 km) route would have an estimated travel time of 4:35~5:34 hours, train speed between 79 mph (127 km/h) to 110 mph (177 km/h), with four round trips per day. The route has the lowest capital expenditure cost at $2 billion to $2.3 billion, but is also the least competitive compared to auto and air travel.
Potential stations would be at: Charlotte GatewayCharlotte AirportGastoniaSpartanburgGreenvilleClemsonToccoaGainesvilleSuwaneeDoravilleAtlanta MMPTAtlanta Airport.[21][22]
  • Alternative 2: Interstate 85
Using the existing Interstate 85 right-of-way. The estimated 244-mile (393 km) route would have an estimated travel time of 2:42~2:50 hours, train speed between 125 mph (201 km/h) to 180 mph (290 km/h), with 14 round trips per day. The route has the highest capital expenditure cost at $13.3 billion to $15.4 billion, but would be competitive against auto travel.
Potential stations would at: Charlotte GatewayCharlotte AirportGastoniaSpartanburgGreenvilleAndersonCommerceSuwaneeDoravilleAtlanta MMPTAtlanta Airport.[21][22]
  • Alternative 3: Greenfield
The Greenfield alternative is a dedicated-use alternative primarily on new right-of-way. The estimated 267-mile (430 km) route would have an estimated travel time of 2:06~2:44 hours, train speed between 125 mph (201 km/h) to 220 mph (354 km/h), with 16-22 round trips per day. The route would have a capital expenditure cost at $6.2 billion to $8.4 billion, but would be competitive against both auto and air travel, when access and security clearance times are included.
Potential stations would at: Charlotte GatewayCharlotte AirportSouth GastoniaGreenville–Spartanburg AirportAndersonAthensSuwaneeDoravilleAtlanta MMPTAtlanta Airport.[21][22]

All three options would be able to substitute the Suwanee and Doraville stations with ones in Lawrenceville and Tucker in Georgia, should CSX right of way be used for the final approach into Atlanta rather than the Norfolk Southern right of way that the former two cities are located on.[23]

In September 2019, the Tier I EIS was completed. Final selection of a preferred route and approach into Atlanta will be deferred to the Tier II EIS, currently unfunded.[24]

On September 30th, 2020, the FRA and GDOT chose the Greenfield Corridor as the preferred alternative. However, it did not specify a final approach into Atlanta.[25]

Atlanta and further south

There are three routes out of Atlanta being considered for high/higher speed rail. In 2012, during the study for the Tier 1 Environmental Impact Statement, two main alternatives for higher speed rail have been considered. The first alternative is called Shared Use with top speeds of 90 mph (145 km/h) to 110 mph (177 km/h). The second alternative is called Hybrid High Performance with top speeds of 130 mph (209 km/h). There are also high-speed rail alternatives in the same study with top speeds of 180 mph (290 km/h) to 220 mph (354 km/h) or higher.[26]

The three routes are:

For the Louisville route, a feasibility study indicated that the high-speed trains for this link would be economically feasible. The stations along the route could include Cartersville and Dalton in Georgia; Chattanooga, Murfreesboro and Nashville in Tennessee; and Bowling Green and Elizabethtown in Kentucky.[27] Although the Atlanta-Louisville high-speed rail link is not federally designated, the link will connect two federally designated corridors, SEHSR and Chicago Hub Network. The same route has been included in the US High Speed Rail Network of the US High Speed Rail Association, a non-profit advocacy group.[28]

In June 2012, a feasibility study report presented to the State Transportation Board of Georgia indicated that a high-speed rail between Atlanta and Jacksonville would be economically feasible. Fares between Atlanta and Jacksonville would range between $119.41 and $152.24. The construction for that route would cost from $5 billion to $16 billion.[29]

Western Virginia

Another proposed rail project, known as the Transdominion Express, would connect to SEHSR and extend from Richmond west to Lynchburg and from Washington, D.C. (Alexandria) south via an existing Virginia Railway Express route to Manassas, extending on south to Charlottesville, Lynchburg, Roanoke and Bristol on the Tennessee border.[30]

See also

References

  1. "High-speed rail to Hampton Roads one step closer". The Virginian-Pilot. 1 September 2012.
  2. "Project History". Southeast High Speed Rail Corridor. April 2010.
  3. "Fact Sheet: High Speed Intercity Passenger Rail Program: Charlotte - Raleigh - Richmond - Washington, D.C." Whitehouse.gov. 2010-01-27. Retrieved 2016-05-05.
  4. Lazo, Luz (2020-01-11). "Virginia's $3.7 billion rail plan called a 'game changer.' Here's what we know about it". The Washington Post. Retrieved 2020-08-07.
  5. Straddling, Richard (2020-09-18). "NC gets federal grant to buy corridor for Raleigh-Richmond high-speed rail". Raleigh News & Observer. Retrieved 2020-09-19.
  6. "FRA funds third track for northern Virginia". Railway Age. September 18, 2012. Retrieved February 9, 2017.
  7. "Virginia seeks project manager for Atlantic Gateway". Railway Age. February 7, 2017. Retrieved February 9, 2017.
  8. "D.C. to Richmond Southeast High Speed Rail :: Home". Dc2rvarail.com. Retrieved 2016-05-05.
  9. "Southeast High-Speed Rail DC to Richmond". U.S. Department of Transportation Federal Railroad Administration. 28 August 2020.
  10. Richard Stradling (December 23, 2019). "High-speed rail from Raleigh to Richmond just got a little closer to reality". The News & Observer.
  11. Lazo, Luz (19 December 2019). "Virginia to build Long Bridge and acquire CSX right of way to expand passenger train service". Washington Post. Retrieved 19 December 2019.
  12. "Amtrak rolls out ticket prices for Norfolk". Norfolk Virginian-Pilot. 30 August 2012. Retrieved 30 August 2012.
  13. Duncan, Charles (21 September 2020). "High-Speed Rail Between Raleigh and Richmond Takes "Critical Step" with $47 Million Funding". Spectrum News North Carolina. Retrieved 23 September 2020.
  14. "Two states see slow start for fast trains between Raleigh and Richmond | News & Observer". Newsobserver.com. 2014-10-23. Retrieved 2016-05-05.
  15. "Archived copy" (PDF). Archived from the original (PDF) on April 2, 2015. Retrieved March 11, 2015.CS1 maint: archived copy as title (link)
  16. "What to expect from Virginia's Atlantic Gateway projects". The Washington Post. July 8, 2016. Retrieved February 9, 2017.
  17. "NCDOT: Piedmont Improvement Program". NCDOT.gov. Retrieved 2018-07-24.
  18. "NCDOT: Largest Program of Improvements to State's Rail Infrastructure Complete". NCDOT.gov. 2018-01-10. Retrieved 2018-07-24.
  19. "Atlanta to Charlotte". Georgia Department of Transportation. Retrieved October 19, 2019.
  20. "Evaluation of High-Speed Rail Options in the Macon-Atlanta-Greenville-Charlotte Rail Corridor" (PDF). Cambridge, Massachusetts: Volpe National Transportation Systems Center. August 2008. Retrieved October 19, 2019.
  21. "Atlanta to Charlotte Passenger Rail Corridor Investment Plan - Alternatives Development Report" (PDF). Atlanta, Georgia: Georgia Department of Transportation. October 2015. Retrieved October 19, 2019.
  22. Henderson, Bruce (October 18, 2019). "High-speed rail could link Charlotte to Atlanta in 2 hours. Have your say next week". The Charlotte Observer. Retrieved October 19, 2019.
  23. "Alternatives Considered" (PDF). March 2019. Retrieved October 11, 2020.
  24. "Southeast High-Speed Rail: Atlanta to Charlotte Passenger Rail Corridor - Federal Railroad Administration". Retrieved October 19, 2019.
  25. "The Federal Rail Administration (FRA) and the Georgia DOT have reviewed comments received during the Tier 1 DEIS public comment period". September 30, 2020. Retrieved October 11, 2020.
  26. "Executive Summary: Atlanta Birmingham Corridor" (PDF). Tier 1 EIS. Georgia Department of Transportation. Retrieved 8 November 2012.
  27. "Study: High-speed trains across South are feasible". The Miami Herald. June 21, 2012.
  28. "US High Speed Rail Network Map". US High Speed Rail Association. Retrieved June 22, 2012.
  29. "High-speed rail from Atlanta to Jacksonville feasible, study says". The Florida Times Union. June 20, 2012.
  30. Virginia Department of Rail and Public Transportation (2011). "Amtrak Virginia". Virginia.gov.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.