If you look at a map of Ohio, you see that three four lane routes eventually funnel into Point Pleasant,You're right:
That two-lane section between Buffalo and Henderson that hasn't been replaced/bypassed yet.Well the article misled me, then. Now it makes sense.
If you look at a map of Ohio, you see that three four lane routes eventually funnel into Point Pleasant,You're right:
(http://i.imgur.com/ljaE7fC.png)
Oopsie, I made a strawman. US 33 feeds into I-77 and Corridor D feeds into Corridor D. And it's not like Corridor D empties a bunch of traffic onto US 35 at Jackson; on the contrary, there's more traffic on US 35 northwest of Jackson than on the part leading up to the bridge in either state. (The bridge itself has more, but that's expected because bridges are choke points.)
Perhaps the relatives of those killed will see the humor in your posts, I really don't.
Of course people that don't just want to argue understand that 23 to 35 is the link from ColumbusEver hear of US 33?
32 to 35 from Cincinnati.Sup AA Highway.
Perhaps the relatives of those killed will see the humor in your posts, I really don't.Perhaps those killed are in heaven right now laughing because there's nothing better to do in that hellhole.
Of course people that don't just want to argue understand that 23 to 35 is the link from ColumbusEver hear of US 33?
32 to 35 from Cincinnati.Sup AA Highway.
Anyway, you should probably be complaining about Porkidor H in reference to funding for US 35.
Two lanes for most of its length, a lot hillier, traffic lights around Maysville and a speed trap that's signed only for a 55 mph maximum.
It's 80 percent federally funded vs. mostly state funding for US 35, hence the former toll proposal that got shot down.
32 to 35 from Cincinnati.Sup AA Highway.
Two lanes for most of its length, a lot hillier, traffic lights around Maysville and a speed trap that's signed only for a 55 mph maximum.
[/quote]QuoteTwo lanes for most of its length, a lot hillier, traffic lights around Maysville and a speed trap that's signed only for a 55 mph maximum.
Perhaps, but well-engineered for a 2-lane highway. Plus as I recall it has a few hill-climbing lanes.
32 to 35 from Cincinnati.Sup AA Highway.
Two lanes for most of its length, a lot hillier, traffic lights around Maysville and a speed trap that's signed only for a 55 mph maximum.
Yes. You are exactly correct. I do the Cincinnati (living in the eastern Suburbs) to Charleston, WV drive a handful of times per year. The AA has its own issues .... much as I despise the section of 35 in WV, it's still a case where 32 to 35 is preferable to the AA.
US-35 in WV from Point Pleasant to Buffalo simply needs to be upgraded to 4 lanes. It is what it is. High traffic corridor and it's particularly dangerous as it is now.
To be frank, I'm not sure why WVDOH doesn't just dualize on the existing alignment north of the WV 869 bridge. It seems like it would be a lot cheaper than building in the hills further in from the river like the other new 4-lane parts.
There's some stuff along the road, but most of it is farmland. A lot of the rest is small houses or trailers you could buy out fairly cheaply.To be frank, I'm not sure why WVDOH doesn't just dualize on the existing alignment north of the WV 869 bridge. It seems like it would be a lot cheaper than building in the hills further in from the river like the other new 4-lane parts.It's been awhile since I have been on that stretch, but how much would ROW acquisition and relocation costs, plus utility relocation costs, impact a financial decision vs. buying mostly wooded, unoccupied tracts and building there? Plus, there would either have to be a series of frontage roads built, or the road would not be "partially-controlled access" like most of the other modern four-lanes in West Virginia since there would be private access drives for homes and businesses. And I'd guess the speed limit would be 55, not 65, on such a road.
It appears a Public Private Partnership will be used to finish US 35: http://www.wvgazette.com/News/201311260023 (h/t Bitmapped).
http://donsurber.blogspot.com/2013/10/bonus-us-35-is-emblematic-of-our.html
http://donsurber.blogspot.com/2013/10/bonus-us-35-is-emblematic-of-our.html
Why are the paragraphs in this piece all very short?
Ha. That's probably payback for Kanawha Stone coming in here and taking away a project in Bizzack's territory a few years ago -- the second, stimulus-funded portion of the KY 15 four-laning in Breathitt County. Bizzack had done the first section but Kanawha Stone came in and underbid them on the second section.
Not surprising that they didn't include paving. In Kentucky, Bizzack no longer paves and I don't think Mountain Enterprises is a Bizzack subsidiary anymore. They subcontract paving to whichever company has the blacktop plant monopoly in that particular county.
DOH wasn't even accepting bids for paving at this letting. It's generally standard practice for them to split grade/drain from paving.
So will this complete the work within West Virginia?
However, the state still has to find a contractor to pave the road once construction is complete. A project with an estimated $70M dollar price tag.
The Department of Transportation looks to have a contractor picked sometime before the project is finished.
If that happens, the paving project could be completed sometime in spring 2019.
They still have to let the contract to pave it.
I'm surprised no one else posted this. The end of two lane hell is in sight!
Hi, all. Does anyone know if/when the US 35 construction in WV is/will be completed? We're heading to Hilton Head this summer and thought about going that way from Central Ohio instead of taking 33 to 77. I've heard horror stories about the two-lane stretch of US 35 in WV, and don't need to get stuck in traffic. US 33 isn't too bad, but a good portion southeast of Athens is two lanes, and invariably we get stuck behind someone driving way under the speed limit. If US 35 is complete then we can go that way.
http://wvmetronews.com/2019/04/19/paving-contract-awarded-for-route-35-gap-project/
Final paving contract awarded, to WV Paving. Completion in October 2020 (just before Election Day).
IMHO, long past due. The existing road is simply dangerous.
<edit> WV Paving, sorry.
If I get to go to the Portsmouth meet, I intend to go take a look at the construction on this project. I figure most of the county roads that turn westward off existing US 35 will run through the work zone.
If I get to go to the Portsmouth meet, I intend to go take a look at the construction on this project. I figure most of the county roads that turn westward off existing US 35 will run through the work zone.
I will be using the US-35 corridor on my July trip to NW Indiana, and be able to view the project.
Certainly. A turn away from the river (left if NB, right if SB) on any CR will within a half mile or so bring you to either a bridge which will carry the new 35 high above you, or a future at grade intersection with the new route.
A view of the US Route 35 expressway at the Interstate 64 interchange. US Route 35 ends just south at Teays Valley Road.
The pavement on US 35 looks awful. It didn't hold up well at all.
In that last photo, the two-lane road to the right ... does it go under a big concrete box culvert or does it end there? Hard to tell from the photo.
And in the first ones ... There's an overhead for the left turn onto westbound 64 over the opposing lanes of traffic on the connector from US 35 to Teays Valley Road? That's ... unusual.
<snipped>
And in the first ones ... There's an overhead for the left turn onto westbound 64 over the opposing lanes of traffic on the connector from US 35 to Teays Valley Road? That's ... unusual.
<snipped>
As for the first photo - the overhead gantry is for Teays Valley Road and is the end of US 35 technically. I always wondered if the highway will be extended south to US 119 in the future.
We drove on West Virginia's US-35 on October 1 en route to Dayton and we were surprised at how many "Bump" or "Dip" or similar signs there were on the northern four-lane portion. It didn't seem like all that old of a road (I see seicer's comments about when it was built) that it should have been in that sort of condition.
They now have WV 817 concurrently signed with US 35. Last time I was there, it wasn't signed concurrently; WV 817 ended at the intersection near the Buffalo Bridge and apparently picked back up again as a separate segment near Pt. Pleasant. All they'll have to do now is remove the US 35 signs and reposition the WV 817 signs on the posts when the new route opens.
They now have WV 817 concurrently signed with US 35. Last time I was there, it wasn't signed concurrently; WV 817 ended at the intersection near the Buffalo Bridge and apparently picked back up again as a separate segment near Pt. Pleasant. All they'll have to do now is remove the US 35 signs and reposition the WV 817 signs on the posts when the new route opens.
Ouch. Unclinched again!
They now have WV 817 concurrently signed with US 35. Last time I was there, it wasn't signed concurrently; WV 817 ended at the intersection near the Buffalo Bridge and apparently picked back up again as a separate segment near Pt. Pleasant. All they'll have to do now is remove the US 35 signs and reposition the WV 817 signs on the posts when the new route opens.
Ouch. Unclinched again!
817 was co-signed with US-35 when I went to the New River Gorge back in July 2018, so it's been signed there for a while (and of course will stay as 817 after the alignment change of 35).
WV DOT has changed the opening date to “sometime in October”.
Part of the issue has been, IMHO, the odd method in which the previous segments were done. In every other case I can think of, they built the new road a couple of hundred yards past what will be an exit, with traffic forced down what will someday just be an exit. Then when the next segment is finished, you just pull up the Jersey barriers and there you go.
Did not do that here. Both ends have long segments to tie into the old road, as if it was to be the permanent end, which was never the plan. The tie in at the Buffalo/Toyota bridge is done, which added time, but the one at the other end has not even started, at least a quarter mile of construction not even started.
Also, the state has decided to improve the Buffalo/Toyota Bridge exit. Was just going to be an at grade intersection, but will be reworked into an actual interstate type exit. Which is needed.
AFAIK, there is about 6 miles of final paving in one direction left, plus some signs, which is NBD.
The issue is the also odd junction at the north end. You can see it on the topographic overlay on Google Maps. I assume they are going to force traffic onto 817 further up the road (there is a junction about a mile away) and rework the lanes as quickly as possible. I really don’t see any other way.
And, finally.
https://www.wsaz.com/2021/11/05/ribbon-cutting-celebration-scheduled-final-section-us-35/
Veteran’s Day.
And, finally.
https://www.wsaz.com/2021/11/05/ribbon-cutting-celebration-scheduled-final-section-us-35/
Veteran’s Day.
Can't wait to see if WV-869 now gets signed along the segment US-35 vacates between the current southern end of the 4-lane and the Lower Buffalo Bridge (the bridge is currently WV-869, but unsigned).
And, finally.
https://www.wsaz.com/2021/11/05/ribbon-cutting-celebration-scheduled-final-section-us-35/
Veteran’s Day.
Can't wait to see if WV-869 now gets signed along the segment US-35 vacates between the current southern end of the 4-lane and the Lower Buffalo Bridge (the bridge is currently WV-869, but unsigned).
Hadn't thought about that, but wouldn't be surprised if it's just signed "To WV 62/To WV 812," given West Virginia's penchant for not signing numbered bridges.
Seems to me that it would be logical to straighten out the existing intersection near the bridge to make WV 817 a through route, and do a jughandle-type connection between WV 817 and the bridge approach route. It's oddly aligned now.
The comments on Facebook are great. They allowed GIFs on one of the threads and it was a bunch of people posting roller coaster graphics - because that's pretty much what the pavement is like throughout the entire highway from I-64 to Point Pleasant.
To answer the signage question, northbound the exit is signed "WV 817 - WV 62 -Buffalo - Eleanor" southbound is simply WV 62 - Buffalo - Eleanor" No use of the word "TO" and no mention of the bridge's route number. Also no signage for the Toyota plant, which you can get a view of southbound about a mile north of the exit. If you take exit signage points you to "WV 62". There is some reworking of the interchange between the old US 35 (now WV 817), the access road to the ramps, and the bridge, but that will probably be done next spring.
I note the speed limit on US-35 once you cross the river into Ohio is 70 mph and in West Virginia it's been 65 on previously-existing the four-lane portions. Is there any possibility West Virginia might raise it to 70, or is the combination of it being a non-Interstate and having a few at-grade intersections enough for West Virginia to keep it at 65? I don't know what West Virginia law is nor whether their DOT has a specific policy on that sort of thing.
I’m pretty sure it’s a full freeway after you cross into Ohio, hence the 70 limit. But at some point NW of Rio Grande it starts having at-grade intersections so I’m thinking it slows down.
I drove from Jackson to Teays Valley on US 35 back in the spring. The non-freeway portions in Ohio had speed limits lower than 70, but I can't remember if they were signed 65, 60, or 55.I believe the arterial segments are posted at 60 mph, with 70 mph on the full freeway sections.
I note the speed limit on US-35 once you cross the river into Ohio is 70 mph and in West Virginia it's been 65 on previously-existing the four-lane portions. Is there any possibility West Virginia might raise it to 70, or is the combination of it being a non-Interstate and having a few at-grade intersections enough for West Virginia to keep it at 65? I don't know what West Virginia law is nor whether their DOT has a specific policy on that sort of thing.The four lane highways are capped at 65 mph in West Virginia. There was originally a provision to permit 70 mph on them when the interstate speed limit was bumped to 75 mph, though it was removed from the final version of the bill due to safety concerns.
It will be interesting to see how West Virginia's updated county maps for the county in question -- Putnam or Mason, I can't remember for sure -- mark the connector route from the new four-lane to the Buffalo bridge.It’s 60 mph, at least on the expressway section I drove on last summer between OH 32 and the WV border.
I drove from Jackson to Teays Valley on US 35 back in the spring. The non-freeway portions in Ohio had speed limits lower than 70, but I can't remember if they were signed 65, 60, or 55.
I note the speed limit on US-35 once you cross the river into Ohio is 70 mph and in West Virginia it's been 65 on previously-existing the four-lane portions. Is there any possibility West Virginia might raise it to 70, or is the combination of it being a non-Interstate and having a few at-grade intersections enough for West Virginia to keep it at 65? I don't know what West Virginia law is nor whether their DOT has a specific policy on that sort of thing.
I’m pretty sure it’s a full freeway after you cross into Ohio, hence the 70 limit. But at some point NW of Rio Grande it starts having at-grade intersections so I’m thinking it slows down.
For what it's worth, though, in Ohio at-grade intersections don't automatically disqualify a road from being posted at 70 mph. US-30 is an excellent example, although to be fair that road is a lot flatter and more wide-open than West Virginia's portion of US-35.IIRC, ODOT has said they wouldn’t post higher than 60 mph on four lane divided highways that don’t have limited access.
Not just that. Most of OH 32 is 60 mph too, when it realistically could be at least 65.For what it's worth, though, in Ohio at-grade intersections don't automatically disqualify a road from being posted at 70 mph. US-30 is an excellent example, although to be fair that road is a lot flatter and more wide-open than West Virginia's portion of US-35.IIRC, ODOT has said they wouldn’t post higher than 60 mph on four lane divided highways that don’t have limited access.
US-30 has at-grade intersections, though it’s limited access throughout. However, there is the counter example being the western part of US-30 towards Indiana that has private driveways and holds 70 mph, so who knows.
That stretch of US-35 should realistically at least be 65 mph.
OH 32 being entirely 60 MPH except for its westernmost segment despite it having a low AADT and widely spaced intersections and interchanges - especially in comparison to US 35 which is signed for 70 MPH in stretches although it has driveway connections.I could be wrong, but I don’t believe any stretch of US-35 with at grade connections is posted above 60 mph.
OH 32 being entirely 60 MPH except for its westernmost segment despite it having a low AADT and widely spaced intersections and interchangesRegarding the westernmost segment, you'll be lucky to go above 55 mph (posted speed limit) in some places, at least until ODOT removes all traffic lights between I-275 and Batavia.
The four lane highways are capped at 65 mph in West Virginia. There was originally a provision to permit 70 mph on them when the interstate speed limit was bumped to 75 mph, though it was removed from the final version of the bill due to safety concerns.
Not just that. Most of OH 32 is 60 mph too, when it realistically could be at least 65.I can't speak to the whole thing, but I know that at least portions of the OH 32 where I've seen plans showed a 100 km/h design speed which is about 62mph. I'd love to see a 65mph speed limit, but I don't know that ODOT's going to do that given the design speed.
I was simply asking whether there's any possibility of West Virginia posting 70 mph on that road. Based on the various replies, it sounds like it's either unlikely or not permitted.There is no possibility. Nothing legally forbids it but WVDOH does not sign any road with at-grade intersections higher than 65mph.
The design speed could be some arbitrary number set by engineers when designing the road, but if the ground reality is that the roadway can safely handle 65 mph or 70 mph, that should be the speed limit.Not just that. Most of OH 32 is 60 mph too, when it realistically could be at least 65.I can't speak to the whole thing, but I know that at least portions of the OH 32 where I've seen plans showed a 100 km/h design speed which is about 62mph. I'd love to see a 65mph speed limit, but I don't know that ODOT's going to do that given the design speed.
Apple Maps shows the new road (though they also retained the US-35 shield on the old road as well). Google Maps doesn’t as of this writing.
Apple Maps shows the new road (though they also retained the US-35 shield on the old road as well). Google Maps doesn’t as of this writing.
Google has screwed up royally. It now shows the old US 35 as being “closed” and the new road not at all. Current “scoreboard” signs on I-64 and US 35 now read “GPS NAV ERROR US 35 and WV 817 ARE OEPN”. Using it to create a route will detour motorists, depending on their settings, to things like the AA, or Corridor B - Portsmouth Bypass.
Google has screwed up royally. It now shows the old US 35 as being “closed” and the new road not at all. Current “scoreboard” signs on I-64 and US 35 now read “GPS NAV ERROR US 35 and WV 817 ARE OEPN”. Using it to create a route will detour motorists, depending on their settings, to things like the AA, or Corridor B - Portsmouth Bypass.
Google has screwed up royally. It now shows the old US 35 as being “closed” and the new road not at all. Current “scoreboard” signs on I-64 and US 35 now read “GPS NAV ERROR US 35 and WV 817 ARE OEPN”. Using it to create a route will detour motorists, depending on their settings, to things like the AA, or Corridor B - Portsmouth Bypass.
I asked Waze for directions from my location near Atlanta to Henderson, WV, and it said," Can't find a route. It looks like there's no way to drive there. Try a nearby location." So I did, and same for Point Pleasant. :clap:
And the road is open in both directions, and most GPS companies seem to have fixed their issues, although the "scoreboards" still inform motorists that GPS is wrong. There are also reports of traffic, including truck traffic, still using WV 817 northbound (it is pretty much impossible to reach in southbound right now) which is obviously the result of cell phone addiction. Sad.
Anyway, the work at the (previous) north end continues, with about a third of a mile of northbound 35 still just not there, traffic is shifted to share the southbound lanes with a Jersey barrier, which is NBD. This does block what will be an at grade intersection with 817, which is also NBD. While the paving equipment is sitting there, apparently ready to go, the asphalt plants close soon, so I don't know. It is just dirt now.
And the road is open in both directions, and most GPS companies seem to have fixed their issues, although the "scoreboards" still inform motorists that GPS is wrong. There are also reports of traffic, including truck traffic, still using WV 817 northbound (it is pretty much impossible to reach in southbound right now) which is obviously the result of cell phone addiction. Sad.
Anyway, the work at the (previous) north end continues, with about a third of a mile of northbound 35 still just not there, traffic is shifted to share the southbound lanes with a Jersey barrier, which is NBD. This does block what will be an at grade intersection with 817, which is also NBD. While the paving equipment is sitting there, apparently ready to go, the asphalt plants close soon, so I don't know. It is just dirt now.
Google Maps has it up and labeled correctly as US 35, old 35 is labeled as WV 817
And the road is open in both directions, and most GPS companies seem to have fixed their issues, although the "scoreboards" still inform motorists that GPS is wrong. There are also reports of traffic, including truck traffic, still using WV 817 northbound (it is pretty much impossible to reach in southbound right now) which is obviously the result of cell phone addiction. Sad.
Anyway, the work at the (previous) north end continues, with about a third of a mile of northbound 35 still just not there, traffic is shifted to share the southbound lanes with a Jersey barrier, which is NBD. This does block what will be an at grade intersection with 817, which is also NBD. While the paving equipment is sitting there, apparently ready to go, the asphalt plants close soon, so I don't know. It is just dirt now.
Google Maps has it up and labeled correctly as US 35, old 35 is labeled as WV 817
Any yet they still don't have the 'brand new' segment of WV-817 that has been open here since at least May '18........
https://www.google.com/maps/@38.8162744,-82.1125834,16.75z
https://goo.gl/maps/Sjg3kB7coVEJ1Q6A8
Interesting that WV still uses lighting under the BGS, based on supports for them in the pictures, when most states were done with them starting with sometime in the past decade.
(https://i.imgur.com/LqMLV70.png)