Wednesday, September 15, 2021

New traffic signals activated on River Road at Braeburn Parkway, crosswalk


Signals are turning red with no
pedestrians or turning vehicles present

Without advance public notice, four new traffic signals have been activated on River Road between Whittier Boulevard and Braeburn Parkway in Bethesda. The signals are part of a project the Maryland State Highway Administration began last summer to improve safety for pedestrians crossing River Road, and vehicles turning against traffic onto Pyle Road. While some in the Bannockburn area had advocated for safety improvements at that location for many years, SHA agreed to the project after a horrific auto accident at the intersection resulted in the deaths of three people in February 2016.

Last night, however, the traffic signals were operating in a much different manner than SHA had described. The signals at the crosswalk between Whittier and Braeburn were supposed to turn red when a pedestrian was crossing River Road, and the signals at Braeburn were to turn red when a vehicle attempted to turn across traffic there, with new limitations on what turns could be made. 

New traffic signal west of Whittier Boulevard
turns red Tuesday night with no pedestrian present
at or near the crosswalk

But on Tuesday evening, the signals were changing on their own, with no pedestrians or turning vehicles present. As such, they are functioning as one or two additional red lights to slow traffic and extend travel times for drivers between the District and the Capital Beltway. They were turning red with great frequency.

The misuse of the new signals by SHA aligns with the agency's politicization in recent years. While SHA made decisions based on sound engineering policies for decades, since Gov. Larry Hogan - a real estate developer - took office, the agency bends to the vast majority of the whims of Montgomery County's elected officials. Similar to the abuse of the new signals, SHA recently slashed the speed limit on River Road between Ridgefield Road and the Beltway from 45 MPH to 35 MPH, with no formal public process. The change was requested by the Montgomery County Council.

That stretch of River Road is designed for a 50 MPH speed limit, as the relentless braking needed to comply with the new 35 MPH limit amply demonstrates. Such braking is usually a clear sign to a traffic engineer that he or she has set the speed limit too low for safety. 

Taming speeds along a major state highway used by commuters, and increasing their travel times, is in line with developers' plans to urbanize the River Road corridor. In the coming decades, some developers are hopeful that various church sites, the American Plant location near the Beltway, country clubs, and valuable SHA right-of-way will become available for dense redevelopment. Getting drivers used to urban speeds is paving the way for that, and it's not surprising that developer Hogan was in office when SHA suddenly began making political decisions.

Likewise, under Hogan, the SHA has tossed its protocols and procedures out the window when politically necessary. While there was an extensive public process regarding the Braeburn Parkway-area safety solutions, there was no public process at all in the speed limit decision, nor the apparent decision to use the new safety signals as speed control.

Basic safety procedures were ignored in both cases, as well. It is standard for a transportation agency to deploy digital signs announcing a new traffic pattern weeks in advance. Signs were only deployed regarding the 35 MPH speed limit after I publicized the failure to do so. And once again, no digital signs warned of the new traffic pattern and signals in the Braeburn Parkway area.

I have not even found any bulletins online from SHA announcing the activation of the signals. The project website is out-of-date.

6 comments:

  1. Anonymous1:59 PM

    I agree this is a mess. River Road is a dual-lane divided highway, and no driveways connect directly to it (by design). It's designed for more than 35mph.

    My kids and I have a game in the car where we seek out roads with a higher limit than River Road, but are less safe. For example look at Democracy Blvd near Seven Lock (by the ice rink). Pedestrians, driveways, and still a higher limit.

    Or look at Bradley Blvd -- same limit but with only one lane each way, and driveways every few feet to the point that MCPS will not allow kids to walk to a bus stop on there -- if you live on Bradley, the bus comes directly to your house. Yet it's 35mph too.

    MD SHA did a 200+ page engineering study. This should have remained at 45mph, but politics got in the way. We even had our US congressional representatives intervening.. over a state road that the Feds have nothing to do with! Nonsense.

    ReplyDelete
  2. Anonymous4:12 AM

    What is this "relentless braking" that you have observed?

    I can understand being unhappy with the decrease in the speed limit, but if you can't keep your car at a steady speed without constantly hitting the brakes (or the accelerator), then maybe you shouldn't be driving.

    ReplyDelete
  3. Anonymous4:46 AM

    If the limit was 45 people would average 60. At 35 people go more like 50.

    ReplyDelete
  4. 4:12: You're obviously trolling - if you don't need to brake often on that stretch of River Road to stay under 50 MPH, or on MacArthur Boulevard in the Palisades (to cite another infamously-wrong speed limit road) to stay at 25 MPH, you must have many speeding tickets by now. There is something called "physics." Study it.

    4:46: The problem is, when you have a road designed for 50, and change the speed limit drastically without changing the engineering of the road, it creates its own safety issues (but I suspect they are banking on making a lot of money from the speed cameras they plan to put there).

    ReplyDelete
  5. Anonymous8:00 AM

    Robert Dyer @ 6:27 AM -

    There are two pedals - the brake and the accelerator. If you ease up on the accelerator you won't need to keep hitting the brake. Driving 101.

    MacArthur Boulevard NW isn't the best example of an "infamously-wrong speed limit road". The lanes are very narrow, it has sharp curves, houses are close to the road, and there are many pedestrians crossing. If you can't keep your speed under 37 MPH (the threshold for a radar ticket) when you drive there, then maybe you shouldn't be driving.

    ReplyDelete
  6. 8:00: Perhaps the laws of physics function differently in your dimension. Keep us posted. I don't know what kind of car you are driving that you wouldn't have to apply brakes to stay under the speed limit frequently on both roads. I drive the speed limit on many other state roads like MD 355 north of downtown Bethesda, and don't have this problem. Why? Because they have a speed limit that matches the design of the road and terrain. If the problem was me, I'd be going 60 on 355, and that never happens.

    I have a perfect driving record with no tickets, so I definitely should be driving, and have the qualifications to make these judgements about speed limits.

    why do you take it so personally when Montgomery County and SHA are wrong that you have to attack me about it?

    ReplyDelete