Virginia

[WillWeaverRVA]

VDOT's 2024 Traffic Data has been posted.

Something I just noticed but should've known: Loudoun County is actually the second county in Virginia with 5-digit secondary routes, by virtue of SR 10382 (Sinegar Place) crossing the county line from Fairfax County into Loudoun County. The county line is not posted, however.

[D-Dey65]

Every now and then I consider the possibility of a southbound flyover ramp from US 301 to I-95 at Exit 12. There seems to be an opening in the trees between the southbound lanes of US 301 and I-95 which indicated one used to exist. 

[Mapmikey]

Every now and then I consider the possibility of a southbound flyover ramp from US 301 to I-95 at Exit 12. There seems to be an opening in the trees between the southbound lanes of US 301 and I-95 which indicated one used to exist.

This is where I-95 transitioned to US 301 for 20 years. The opening was a southbound ramp with no bridge of any kind.

I'm a little surprised Exit 12 was retained with Exit 13 just a half mile ahead.

[D-Dey65]

Every now and then I consider the possibility of a southbound flyover ramp from US 301 to I-95 at Exit 12. There seems to be an opening in the trees between the southbound lanes of US 301 and I-95 which indicated one used to exist.

This is where I-95 transitioned to US 301 for 20 years. The opening was a southbound ramp with no bridge of any kind.

Yeah, that's what I thought.

I'm a little surprised Exit 12 was retained with Exit 13 just a half mile ahead.

Me too. But I think they just wanted to keep the direct connection between northbound I-95 and US 301. A couple of motels and other businesses up that way could benefit. Or maybe they just didn't want to tear out that flyunder interchange after spending all that money building it up.

[Mapmikey]

Every now and then I consider the possibility of a southbound flyover ramp from US 301 to I-95 at Exit 12. There seems to be an opening in the trees between the southbound lanes of US 301 and I-95 which indicated one used to exist.

This is where I-95 transitioned to US 301 for 20 years. The opening was a southbound ramp with no bridge of any kind.

Yeah, that's what I thought.

I'm a little surprised Exit 12 was retained with Exit 13 just a half mile ahead.

Me too. But I think they just wanted to keep the direct connection between northbound I-95 and US 301. A couple of motels and other businesses up that way could benefit. Or maybe they just didn't want to tear out that flyunder interchange after spending all that money building it up.

There haven't been any operating motorist services on 301 between Exit 12 and Exit 13 in 15+ years. My guess is when the 1950s bridge on 301 south over the Exit 12 off-ramp needs replacing they will close the exit then.

[Beltway]

I'm a little surprised Exit 12 was retained with Exit 13 just a half mile ahead.

Me too. But I think they just wanted to keep the direct connection between northbound I-95 and US 301. A couple of motels and other businesses up that way could benefit. Or maybe they just didn't want to tear out that flyunder interchange after spending all that money building it up.

Easier just to leave it there. NB and SB US-301 config. there left as it was.

[D-Dey65]

North of Exit 13, there are two motels and a KOA Kampground (formerly a Jellystone Park campground).

[WillWeaverRVA]

VDOT is now accepting public input for proposed improvements to the southern end of VA 150, including the horrifically dangerous interchange with US 1/301.

[MASTERNC]

VDOT is now accepting public input for proposed improvements to the southern end of VA 150, including the horrifically dangerous interchange with US 1/301.

Would think a folded diamond would be ideal to remove the short weaving area between I-95 and US 1/301.  I'm guessing space is short on that end, hence still having a direct ramp to 1/301 NB that appears to be separated for I-95 traffic (whereas everyone else exits in the NW quadrant and turns left at a light).

[Beltway]

VDOT is now accepting public input for proposed improvements to the southern end of VA 150, including the horrifically dangerous interchange with US 1/301.

Would think a folded diamond would be ideal to remove the short weaving area between I-95 and US 1/301.  I'm guessing space is short on that end, hence still having a direct ramp to 1/301 NB that appears to be separated for I-95 traffic (whereas everyone else exits in the NW quadrant and turns left at a light).

I go thru there frequently, I would not call it 'dangerous' just a hassle to drive thru.

All those alternatives and none for the best way to address having a local interchange (a busy one at that with US-1/US-301 being a 6-lane arterial) too close to a freeway-to-freeway interchange -- build VA-150 C-D roadways to intercept the cloverleaf movements and carry traffic to and from I-95.

[WillWeaverRVA]

VDOT is now accepting public input for proposed improvements to the southern end of VA 150, including the horrifically dangerous interchange with US 1/301.

Would think a folded diamond would be ideal to remove the short weaving area between I-95 and US 1/301.  I'm guessing space is short on that end, hence still having a direct ramp to 1/301 NB that appears to be separated for I-95 traffic (whereas everyone else exits in the NW quadrant and turns left at a light).

I go thru there frequently, I would not call it 'dangerous' just a hassle to drive thru.

All those alternatives and none for the best way to address having a local interchange (a busy one at that with US-1/US-301 being a 6-lane arterial) too close to a freeway-to-freeway interchange -- build VA-150 C-D roadways to intercept the cloverleaf movements and carry traffic to and from I-95.

I wouldn't be opposed to that, but it doesn't solve the biggest issue with the interchange. There is very little distance between the two sets of very tight loop ramps. A lot of weaving happens there (and yes, I understand that my last name makes the fact I'm discussing weaving rather hilarious) and there have been accidents.

[Beltway]

All those alternatives and none for the best way to address having a local interchange (a busy one at that with US-1/US-301 being a 6-lane arterial) too close to a freeway-to-freeway interchange -- build VA-150 C-D roadways to intercept the cloverleaf movements and carry traffic to and from I-95.

I wouldn't be opposed to that, but it doesn't solve the biggest issue with the interchange. There is very little distance between the two sets of very tight loop ramps. A lot of weaving happens there (and yes, I understand that my last name makes the fact I'm discussing weaving rather hilarious) and there have been accidents.

A C-D roadway would separate the interchanging traffic from the thru traffic, and it would be going a lot slower, and that would alleviate the issue with the weaving section on the loop ramps.

I am opposed to the breaking up of cloverleaf interchanges, creating signalized intersections, especially if a C-D road system can address the issue.

[Thing 342]

I don't know how you'd do CI-CD lanes on that intersection and maintain access to both I-95 and VA-895 in both directions. You could maybe add dividers such that only traffic to/from I-95 gets access to this interchange, which would reduce weaving somewhat.

[D-Dey65]

A C-D roadway would separate the interchanging traffic from the thru traffic, and it would be going a lot slower, and that would alleviate the issue with the weaving section on the loop ramps.

I am opposed to the breaking up of cloverleaf interchanges, creating signalized intersections, especially if a C-D road system can address the issue.

Usually, I am too. But even with the C-D roadway there's still the risk of weaving between the two interchanges. I'm almost sorry there's no place to create a double-trumpet interchange with an adequately sized connecting road like you see on tollways. Then you could eliminate the existing interchange with US 1 and 301, add the C-D roads, and can facilitate less risky access issues between the main road and the I-95/VA 895 interchange.

[Beltway]

Usually, I am too. But even with the C-D roadway there's still the risk of weaving between the two interchanges. I'm almost sorry there's no place to create a double-trumpet interchange with an adequately sized connecting road like you see on tollways. Then you could eliminate the existing interchange with US 1 and 301, add the C-D roads, and can facilitate less risky access issues between the main road and the I-95/VA 895 interchange.

That interchange was built in the 1970s along with the upgraded semi-directional interchange between VA-150 and I-95. That worked well.

It was in 2002 when VA-895 was opened that we have the 4-way freeway-to-freeway interchange.

[D-Dey65]

But where would the access points be on VA-150? I just measured the distance between the north-to-west ramp from I-95 and the west-to-north ramp to US 1 and 301. They're 0.2 mile away from one another. I tried to measure the distance between the eastbound ramps between US 1 and 301 and I-95, but Google Maps kept forcing me to go too far away from where I wanted to go.

[froggie]

Beltway's idea of C/D roads would work the best operationally, but I don't see being feasible in this case for two reasons.  First, it would require additional ROW, of which the eastbound direction would impact the wastewater plant holding tanks.  Second, it would require relocation of the high-tension power line towers immediately adjacent to the rail line.

Of the options presented, my preference is Option 7B.  It gives the most distance for the weave on SB 150.

Worth noting that both of the Par-clo options narrowed traffic from 895 to a single lane before the merge with the 95 ramps and introduces an EXTREMELY short weave between that merge and the off-ramp to NB 1/301.  IMO traffic from 895 may need to be restricted from using the off-ramps to 1/301 in that scenario.

[Beltway]

The recommended build alternative for the Powhite Parkway Western Extension Project is Alternative 1A, a new four‑lane freeway between Woolridge Road and Hull Street Road in Chesterfield County.

That would extend the existing Powhite Parkway 8 miles west to US-360 near Winterpock.  Cost estimate $730 million in 2032 dollars. Planned to be toll-free. Like with HRTAC central Virginia now has a major local funding source in CVTPA.

https://www.vdot.virginia.gov/projects/richmond-district/chesterfield---powhite-parkway-study/

I live on the Powhite corridor so this would be a welcome improvement.

Supported by CVTPA (Central Virginia Transportation Planning Authority)  -- a new regional funding source, similar to how HRTAC (Hampton Roads Transportation Accountability Commission) finances projects in Tidewater.

[WillWeaverRVA]

The recommended build alternative for the Powhite Parkway Western Extension Project is Alternative 1A, a new four‑lane freeway between Woolridge Road and Hull Street Road in Chesterfield County.

That would extend the existing Powhite Parkway 8 miles west to US-360 near Winterpock.  Cost estimate $730 million in 2032 dollars. Planned to be toll-free. Like with HRTAC central Virginia now has a major local funding source in CVTPA.

https://www.vdot.virginia.gov/projects/richmond-district/chesterfield---powhite-parkway-study/

I live on the Powhite corridor so this would be a welcome improvement.

Supported by CVTPA (Central Virginia Transportation Planning Authority)  -- a new regional funding source, similar to how HRTAC (Hampton Roads Transportation Accountability Commission) finances projects in Tidewater.

Good to see. I was worried one of the non-full freeway options would have been chosen.

[Beltway]

The recommended build alternative for the Powhite Parkway Western Extension Project is Alternative 1A, a new four‑lane freeway between Woolridge Road and Hull Street Road in Chesterfield County.

Good to see. I was worried one of the non-full freeway options would have been chosen.

I was a bit worried myself, as traffic certainly justifies it being a new four‑lane freeway.

The environmental impacts are relatively light. Only 3 relocations of residences.

[74/171FAN]

The SR 636 (Nash Rd) extension from SR 655 to VA 10 in Chesterfield County opened last week.

[Beltway]

The SR 636 (Nash Rd) extension from SR 655 to VA 10 in Chesterfield County opened last week.

Thanks ... I need to go check that out.

https://www.chesterfield.gov/m/newsflash/home/detail/4576

[WillWeaverRVA]

The SR 636 (Nash Rd) extension from SR 655 to VA 10 in Chesterfield County opened last week.

Thanks ... I need to go check that out.

https://www.chesterfield.gov/m/newsflash/home/detail/4576

I drove it yesterday. It's a short segment but it makes a huge difference in getting to the Matoaca area from Chesterfield CH without having to go through Chester or take really curvy back roads.

The whole Nash Road corridor could honestly be primary (an extended VA 36?) if not for the weird staggered intersection with Woodpecker Road and the lack of shoulders between River Road and Woodpecker Road.

[Takumi]

I drove it today as well. It's uneventful. No intersections or even stubs like the Otterdale Road extension. But it's great for through traffic.

[Beltway]

I drove it yesterday. It's a short segment but it makes a huge difference in getting to the Matoaca area from Chesterfield CH without having to go through Chester or take really curvy back roads.

I drove it today. About 0.8 mile long, a roundabout with Beach Road, and a fairly substantial bridge over Swift Creek, about 700 feet long and up to 50 feet high.

Wondered how it could be $35 million but that helps explain it.

Decent improvement.