Corridor H

[Beltway]

They cannot do that -- but they can offer 100% FHWA funding for an ADHS project, like they did with US-219 between Meyersdale and Bedford PA. That is an ADHS corridor and they got ~300 million dollars 100% funded back a few years ago for that segment.
My prediction detailed is upthread. This will be too important and too valuable for VA to pass up.

If the FHWA can withhold a certain percentage of federal highway funding to states that don't pass a primary seat belt law or a reduced blood-alcohol percentage for DUI charges, then why can't it withhold some or all of a state's federal funding unless it builds a segment of a federally-authorized highway?

Well they could, but even Interstate system segments a state didn't want to build were not forced to completion that way. Many segments were left unbuilt. Even the mainline route I-84 between Hartford and Providence.

[SP Cook]

I totally understand Virginia's reluctance to do anything about H until WV does its job.  You only have to go north a bit to see several roads that do the exact opposite.  Adequate 4 lanes in Virginia, back country 2 lanes start at the state line.  And then we have WV's history of building its 4 lanes in almost the exact opposite order of their importance.  The two interstates, leaving out the short I-81, that affect Virginia were thus  left unfinished by WV for many decades after Virginia spent millions in quite rural and unpopulated parts of the Commonwealth.  And, of course, first an incompetent governor actually GAVE THE MONEY BACK to build the western sections Of H 4 decades ago, and then extremists tied the road up for years, and seem to be trying to again. 

There is no reason for Virginia to think about H until the last two sections are at least under construction.  When they are, and certainly when completed, the public will demand a safe road to finish the project. 

I also understand that Virginia now has a government of NOVA, by NOVA, and for NOVA, and no one in power today cares about anyone on the other side of the Rappahannock, but politicians come and politicians go.   

My presumption is that Virginia will do what HB calls "Virginia twinning", like you see on Corridor Q in Giles or Tazewell counties.  That really doesn't cost that much compared to the way WV, KY, and NC have built most of the Corridors.

[Beltway]

I also understand that Virginia now has a government of NOVA, by NOVA, and for NOVA, and no one in power today cares about anyone on the other side of the Rappahannock, but politicians come and politicians go. 
My presumption is that Virginia will do what HB calls "Virginia twinning", like you see on Corridor Q in Giles or Tazewell counties.  That really doesn't cost that much compared to the way WV, KY, and NC have built most of the Corridors.

It's not quite that bad as there is a lot of pushback, but even in Richmond where I live a lot of people are sick and tired of the influence and attitudes of NOVA (specifically the core D.C. suburban counties and cities). Many stronger feelings as you go to western and southern parts of the state.

I would definitely predict that VDOT would go with a full 4-lane relocation on limited access R/W. US-48 is not adequate and goes thru some village areas that at minimum would need to be bypassed.

VA Corridor Q is a complete relocation on the new sections west of US-460 at Grundy.

US-58 Hillsville-Stuart is being built with some sections relocated and the others with total reconstruction of existing highway to high standards (like 60 mph design speed).

That is the model for VA Corridor H -- to my mind.

[Beltway]

Here is the message I sent yesterday to Six-YearProgram@VDOT.Virginia.gov which is their public-facing group mailbox for contacting the SYIP office. CC-ed two CTB members.

Awaiting a response.

SYIP New Project Request

Request for consideration of a new SYIP entry for Preliminary Engineering (PE). I would appreciate it if this request could be forwarded to the Staunton District Administrator and Staunton District Planning Manager for formal review as part of the upcoming FY2028–2034 SYIP development cycle.
 
The purpose of the request is to initiate PE for the Virginia segment of US‑48 (I‑81 to the West Virginia line) in order to evaluate long‑term needs associated with:
-- ADHS eligibility and remaining unfunded segments
-- WVDOH's advancement of Corridor H to the state line
-- Freight connectivity between I‑81 and West Virginia
-- The absence of any prior PE or corridor‑level engineering work on the Virginia segment
 
I am requesting that the corridor be entered into the SYIP as a PE line item so that VDOT can undertake the appropriate engineering and planning analysis.
 
Thank you for your assistance, and I appreciate the District's consideration of this request.
 
Sincerely,
Scott M. Kozel
Richmond, VA

[Beltway]

VDOT Preliminary Engineering (PE) includes the full early‑stage project development process:
– Location study / corridor study
– Alternatives development
– NEPA (CE / EA / EIS)
– Environmental constraints analysis
– Traffic, freight, and safety analysis
– Conceptual engineering
– Preliminary cost estimates
– Right‑of‑way impact analysis
– Public involvement

[ARMOURERERIC]

Just reading that the first Wardenville contract was awarded today.

[Beltway]

Yep.

[The Ghostbuster]

Google Maps has been updated to show the completed US 48 between Kerens and WV 72: https://www.google.com/maps/@39.059196,-79.7290242,17199m/data=!3m1!1e3?entry=ttu&g_ep=EgoyMDI2MDcwNS4wIKXMDSoASAFQAw%3D%3D.

[The_Ginger]

Google Maps has been updated to show the completed US 48 between Kerens and WV 72: https://www.google.com/maps/@39.059196,-79.7290242,17199m/data=!3m1!1e3?entry=ttu&g_ep=EgoyMDI2MDcwNS4wIKXMDSoASAFQAw%3D%3D.

Good good! Apple Maps has also updated, but they show US 48 and US 219 on the old road and US 219 on the new alignment. Hopefully that gets fixed soon.

[Beltway]

Google Maps has been updated to show the completed US 48 between Kerens and WV 72: https://www.google.com/maps/@39.059196,-79.7290242,17199m/data=!3m1!1e3?entry=ttu&g_ep=EgoyMDI2MDcwNS4wIKXMDSoASAFQAw%3D%3D.

I drove thru there last July. I saw the construction with the high level bridge where it crosses US-219.

This will be a huge improvement over that long winding road. I figure cutting 14 miles down to 10.

Wonder if the original road will remain US-219 and with only US-48 on the new road?

[The_Ginger]

Wonder if the original road will remain US-219 and with only US-48 on the new road?

See posts 1550 to 1560 for an early answer to that, or my photos for actual evidence of what you are implying.

[hbelkins]

Wonder if the original road will remain US-219 and with only US-48 on the new road?

See posts 1550 to 1560 for an early answer to that, or my photos for actual evidence of what you are implying.

The current signage in no way is an indication of what the permanent signage will look like once the route is completed from WV 72 to existing US 219 north of Parsons, much less between Parsons and Thomas/Davis.

[Beltway]

Wonder if the original road will remain US-219 and with only US-48 on the new road?

See posts 1550 to 1560 for an early answer to that, or my photos for actual evidence of what you are implying.

The current signage in no way is an indication of what the permanent signage will look like once the route is completed from WV 72 to existing US 219 north of Parsons, much less between Parsons and Thomas/Davis.

The Elkins-Kerens segment carries both US-48 and US-219 along most of its length.

[mvak36]

I don't believe this has been posted, but it looks like WV got a BUILD grant for Corridor H.

Awarded amount: $23,359,302, Requested: $25 million. Project name and Cost: Corridor H – Waites Run to Virginia State Line - $144 million. Project Description: The project will construct a new limited-access, four-lane divided highway, connecting the existing Corridor H to US 48 at the state line.

https://www.transportation.gov/policy-initiatives/build/awarded-projects-tigerraisebuild-2009-2026

[hbelkins]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.



Source: Someone on Twitter/X who had responded to someone else wanting to know why Kentucky's governor had not paid a visit to DC to check on the health of Mitch McConnell.

(I'm not sure what those other two routes are. No one is going to go to Knoxville and then east on I-40 to access I-81, no one is going to take a non-freeway route to Beckley to hit I-64 east, and what's the deal with taking US 29 out of Charlottesville over to connect with I-95 somehow?)

[1995hoo]

That doesn't look like US-29. It's too far east and too much of a diagonal. It looks more like some version of the route I use. When I come home from Charlottesville, I usually use the following: US-250 east to Shadwell. Left onto VA-22. Near Cismont, the straight-thru movement on VA-22 becomes VA-231 when Route 22 branches off to the right towards Louisa. I continue up 231 to Gordonsville. Second exit from the roundabout onto US-15. Nine miles north to Orange, then a right at the light onto VA-20. Follow that to its end at VA-3 and make another right. Follow Route 3 to either I-95 or US-1, depending on traffic and time of day, and then either one of those up to Fairfax County.

That route can be faster than it looks. For me it works well because US-29 is out of the way (too far northwest) and has too many annoying traffic lights. There are a lot more lights than there were in the early 1990s when I made that drive all the time.

[Rothman]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.



Source: Someone on Twitter/X who had responded to someone else wanting to know why Kentucky's governor had not paid a visit to DC to check on the health of Mitch McConnell.

(I'm not sure what those other two routes are. No one is going to go to Knoxville and then east on I-40 to access I-81, no one is going to take a non-freeway route to Beckley to hit I-64 east, and what's the deal with taking US 29 out of Charlottesville over to connect with I-95 somehow?)

Hmmmmmm...



https://maps.app.goo.gl/eXMttjcMTewXCEX47

[Beltway]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.

Alexandria VA - Huntington WV
10 minutes and 28 miles shorter.

I-68 route involves crossing the Potomac River on I-495. Something to avoid if possible.

I-64 route is 34 miles and 10 minutes longer than Corridor H. Dealing with I-81 and I-77 traffic.

Surprised that with the missing links that Corridor H provides that service.

[hbelkins]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.



Source: Someone on Twitter/X who had responded to someone else wanting to know why Kentucky's governor had not paid a visit to DC to check on the health of Mitch McConnell.

(I'm not sure what those other two routes are. No one is going to go to Knoxville and then east on I-40 to access I-81, no one is going to take a non-freeway route to Beckley to hit I-64 east, and what's the deal with taking US 29 out of Charlottesville over to connect with I-95 somehow?)

Hmmmmmm...



https://maps.app.goo.gl/eXMttjcMTewXCEX47

Well, yeah, from Wheelwright, going to Abingdon to hit I-81 makes sense. 40-plus years ago, Malcolm Kilduff used to travel that way to get to the DC-Annapolis area until I clued him in to the former US 48 before it became I-68. He would travel I-81 on the way because he was usually leaving from Hazard (and this was before Alt. US 58 was completed between Norton and Coeburn) and then travel I-68 on the way back, unless he was leaving from Beattyville, in which case he would take I-68 going east. He used to always refer to I-79 as "the spine of West Virginia."

[74/171FAN]

Corridor H photos (from Parsons to Elkins) and related photos from 7-3-2026.

[Dirt Roads]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.

Apple Maps has been suggesting this as the preferred route from Charleston -to- Washington DC since before the completion of the Parsons extension.

Given that Corridor H and Corridor D somewhat parallels the The Shenandoah route of the old B&O between Washington D.C. and Cincinnati, I've been watching over the years to see how the development of Corridor H affects portions of Southeast Ohio.  Apple Maps is now starting to show Corridor H as an option from certain locales in Southeast Ohio:

Jackson OH -to- Washington D.C.   396 miles   6 h 39 m   via Clarksburg/Morgantown (Apple Maps)
Jackson OH -to- Washington D.C.   421 miles   6 h 50 m   via Charleston/Strasburg (Apple Maps)
Jackson OH -to- Washington D.C.   408 miles   6 h 58 m   via Clarksburg/Weston/Strasburg (calculated)

This opens up the concept that folks in Chillicothe and Cincinnati and some sections of Northern Kentucky now have similar comparative trip options:

Cincinnati -to- Washington D.C.   507 miles   7 h 55 m   via Brownsville/Uniontown (Apple Maps)
Cincinnati -to- Washington D.C.   518 miles   7 h 56 m   via Breezewood (Apple Maps)
Cincinnati -to- Washington D.C.   524 miles   7 h 57 m   via Clarksburg/Morgantown (Apple Maps)
Cincinnati -to- Washington D.C.   525 miles   8 h 50 m   via Clarksburg/Weston/Strasburg (calculated)

That's not quite enough of an improvement, but might turn Manassas/Centreville (or perhaps Leesburg/Ashburn) into an equivalent destination as to Rockville/Silver Spring.

[Life in Paradise]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.



Source: Someone on Twitter/X who had responded to someone else wanting to know why Kentucky's governor had not paid a visit to DC to check on the health of Mitch McConnell.

(I'm not sure what those other two routes are. No one is going to go to Knoxville and then east on I-40 to access I-81, no one is going to take a non-freeway route to Beckley to hit I-64 east, and what's the deal with taking US 29 out of Charlottesville over to connect with I-95 somehow?)

I just ran the same Google Maps search for starting and endpoints and still had the Corridor H preference shown, but my other two options were I-68 and I-64 with I-68 being 3 minutes slower than Corridor H.  I'm sure that when the two remaining gaps (in West Virginia and then the Wardenville/I-81 finish) are done that time will stretch out to more like 30 minute savings.

[Dirt Roads]

I just ran the same Google Maps search for starting and endpoints and still had the Corridor H preference shown, but my other two options were I-68 and I-64 with I-68 being 3 minutes slower than Corridor H.  I'm sure that when the two remaining gaps (in West Virginia and then the Wardenville/I-81 finish) are done that time will stretch out to more like 30 minute savings.

Forget the time savings.  You'll want to spend most of your trip across the Alleghenies exploring the Potomac Highlands.  I hardly ever have stayed there (except to visit a preacher friend who once lived in Davis), but every time I've been through the area I made at least three (3) stops along the way averaging over an hour each.  Once the entirety of Corridor H opens up, many folks that use it as a quicker route are going to find that it is too Wild and Wonderful not to stop and spend lots of time hiking down to the waterfalls and such.

(I'd better clarify that back in my railroading days I was "on the clock" when travelling through those areas and couldn't stop to sightsee.  Probably gave me a bad case of the Wanderlust.)

[Beltway]

Google Maps now shows Corridor H as the preferred route from Kentucky to DC over I-68.

Alexandria VA - Huntington WV
10 minutes and 28 miles shorter.
I-68 route involves crossing the Potomac River on I-495. Something to avoid if possible.
I-64 route is 34 miles and 10 minutes longer than Corridor H. Dealing with I-81 and I-77 traffic.
Surprised that with the missing links that Corridor H provides that service.

To/from the other side of Washington -- Bowie, MD -- Corridor H still better --

Bowie MD -- Huntington WV
3 minutes and 15 miles shorter via Corridor H

Granted that is 409 miles vs 425 miles and 6:58 vs 7:02.

[Beltway]

Forget the time savings.  You'll want to spend most of your trip across the Alleghenies exploring the Potomac Highlands.  I hardly ever have stayed there (except to visit a preacher friend who once lived in Davis), but every time I've been through the area I made at least three (3) stops along the way averaging over an hour each.  Once the entirety of Corridor H opens up, many folks that use it as a quicker route are going to find that it is too Wild and Wonderful not to stop and spend lots of time hiking down to the waterfalls and such.

Sure -- it will do both -- sightseeing and interstate travel.

I-64 and I-68 thru the mountains have their own scenic wonders.