View Full Version : I-35 NB to I-240 WB Ramp Crater



venture
07-23-2012, 12:26 AM
Have been watching it develop for the last couple of weeks. Growing more and more each day. It is probably about 4-5 feet in diameter now with a nice raised setup about 6-10 inches off the level pavement. Obviously the high heat and turning traffic is stressing that part of relatively new pavement out.

Anyone want to take a guess how long it will take for ODOT to actually address the problem? I figure they'll wait for the first few dozen cars to report damage before doing anything. Right now it is pretty smooth to roll through it without damaging a tire, but it is only a matter of time until it all starts breaking away.

At some point they really need to just get on the ball and get that intersection replaced. The design is horrible and the traffic just creates an all around dangerous intersection.

BoulderSooner
07-23-2012, 07:03 AM
2019

SoonerDave
07-23-2012, 08:34 AM
This interchange has to be one of the single most dangerous of its kind in the city. I've told my new-driver 16-year-old son that the area is OFF LIMITS in the afternoon, don't care where he's going. Heck, my wife isn't even that confident an expressway driver, and I tell her the same thing - just stay away. I drive by that area every day and the days without an accident are the exception. I've never kept a log, but I'd bet there's a wreck there during afternoon rush hour three weekdays out of every five.

I realize its a plea that will likely fall on deaf ears, but this interchange rebuild desperately needs to be kicked up the priority list. I realize its only perception on my part, but it seems like the Broadway Extension and surrounding areas up there have been rebuilt a dozen times while people keep getting hurt and wrecked at this comparatively untouched interchange.

One thing I think would help at least a little on this issue is the permanent closure of the Shields-avenue on-ramp to eastbound I-240. There's a ton of dangerous merging because the ramp is WAAAAAYYY too short all while eastbound I-240 traffic is trying to merge to the I-35 southbound ramps, and I expect contributes to at least a good portion of the wrecks there. Route that traffic to the Walker on-ramp, or even south to 89th and east to I-35, and loop on from there. Drastic, I realize, but this interchange is a horrendous mess.

Horrible, horrible mess.

Snowman
07-23-2012, 08:54 AM
Have been watching it develop for the last couple of weeks. Growing more and more each day. It is probably about 4-5 feet in diameter now with a nice raised setup about 6-10 inches off the level pavement. Obviously the high heat and turning traffic is stressing that part of relatively new pavement out.

Anyone want to take a guess how long it will take for ODOT to actually address the problem? I figure they'll wait for the first few dozen cars to report damage before doing anything. Right now it is pretty smooth to roll through it without damaging a tire, but it is only a matter of time until it all starts breaking away.

At some point they really need to just get on the ball and get that intersection replaced. The design is horrible and the traffic just creates an all around dangerous intersection.

it might help the process emailing ODOT

HangryHippo
07-23-2012, 09:44 AM
Boulder, I really enjoy most of your contributions here on OKCTalk, but I swear, you are the bearer of bad highway news every time you post in the Transportation forum. haha. 2019?! I'm just kidding you of course, I just can't believe it's going to take so long to repair some of the metro's horrible interchanges.

venture
07-23-2012, 09:56 AM
it might help the process emailing ODOT

Done a few days ago. :)

jn1780
07-23-2012, 10:39 AM
There usually good at patching things that should have been replaced 20 years ago. They should be experts at that by now. LOL

MrZ
07-23-2012, 12:15 PM
I can attest to how horrible that ramp from Shields onto 240 is. I was trying to merge onto 240 from Shields and had to yield to a line of traffic with no openings. The guy behind me came flying down the ramp and was looking back to see where the traffic was and didn't see me. Hit me from behind at 50MPH and knocked me into the line of traffic that just was starting to move and caused me to get hit from the front also. Luckily I was in a tank of a car and both cars that hit me were little imports. They got the damage a lot worse than I did but my car was still a total loss. This was 1988. That tells you how long this intersection has been a mess.

SoonerDave
07-23-2012, 12:26 PM
I can attest to how horrible that ramp from Shields onto 240 is. I was trying to merge onto 240 from Shields and had to yield to a line of traffic with no openings. The guy behind me came flying down the ramp and was looking back to see where the traffic was and didn't see me. Hit me from behind at 50MPH and knocked me into the line of traffic that just was starting to move and caused me to get hit from the front also. Luckily I was in a tank of a car and both cars that hit me were little imports. They got the damage a lot worse than I did but my car was still a total loss. This was 1988. That tells you how long this intersection has been a mess.

Absolutely perfect example of why I think that Shields on-ramp should be shuttered. If its going to be seven more years until they rebuild it, I think this an option they have to consider. Know its drastic, and will increase the hassle factor for some folks, but at some point something has to be done to mitigate the danger of this area.

Easy180
07-23-2012, 07:07 PM
Absolutely perfect example of why I think that Shields on-ramp should be shuttered. If its going to be seven more years until they rebuild it, I think this an option they have to consider. Know its drastic, and will increase the hassle factor for some folks, but at some point something has to be done to mitigate the danger of this area.

Would be a hassle for many but I agree that Shields on ramp is in a terrible spot

bombermwc
07-25-2012, 03:21 PM
I believe this is the one they are working on today, isn't it?

Wambo36
07-25-2012, 04:44 PM
One thing I think would help at least a little on this issue is the permanent closure of the Shields-avenue on-ramp to eastbound I-240. There's a ton of dangerous merging because the ramp is WAAAAAYYY too short all while eastbound I-240 traffic is trying to merge to the I-35 southbound ramps, and I expect contributes to at least a good portion of the wrecks there. Route that traffic to the Walker on-ramp, or even south to 89th and east to I-35, and loop on from there. Drastic, I realize, but this interchange is a horrendous mess.

Horrible, horrible mess.
Agreed. Anytime I find myself needing to use the Shields EB on ramp, I make it a point to go back to Walker and get on. Gives me a little more room to negotiate wit the road ragers.

Dubya61
07-25-2012, 04:48 PM
Agreed. Anytime I find myself needing to use the Shields EB on ramp, I make it a point to go back to Walker and get on. Gives me a little more room to negotiate wit the road ragers.

Or just continue on the "access" road around the intersection to 82nd. Or take Santa Fe or Shields south to 89th and approach the problem from a much saner on ramp. I doubt if either of those are faster, but I drive away from that intersection a lot less stressed than if I was on I-240 all along and still had to deal with the kamikaze drivers trying to use that entry ramp.

Spartan
07-25-2012, 09:46 PM
If only downtown had an earthen ramp to sell the southside...

venture
07-28-2012, 07:57 PM
I believe this is the one they are working on today, isn't it?

Yes it was. All fixed!

RadicalModerate
07-30-2012, 09:45 AM
How quickly we forget--or remember?--The Lessons of Kansas City . . .
(like, two years ago . . . when that entire ramp at an Interstate Exchange in the vicinity of I-435/another Interstate/the way to Highway 71 Southbound collapsed . . . and caused inconvenience . . . =)

Personally, I am more concerned about The Trench developing on southbound Penn up around 122nd.
But I'm just selfish.