Near miss on Eads Street

[S. Arlington Observer]

A crash did not happen but it was a near miss at a dangerous intersection.

Every morning at the corner of S. Eads Street and 23rd Street South in Crystal City cars routinely “block the box” by piling into the intersection and blocking northbound Eads Street traffic. Usually it is 23rd Street motorists who pile into the intersection. But Eads Street drivers also get fully into the intersection to turn right even though they know they’ll be stuck there with no real chance to complete the turn because of the backup from the Jefferson Davis intersection light.

It is a very short block between Eads Street and Jeff Davis Highway (US 1) heading east on 23rd. Apparently the light on 23rd at Jeff Davis does not synchronize with the one at 23rd and Eads. This creates a huge incentive to pile into the intersection on 23rd Street to avoid waiting for two light changes to get to Jeff Davis (and to catch the Jeff Davis intersection change to green even when when the Eads light is still red.)

Many times I have weaved through stopped traffic blocking both bike and motor lanes. There is always a fear that the light at Jefferson Davis Highway will turn green at that point releasing the stalled drivers who may, or may not, be paying attention to cyclists trying to get between them.

This morning among the offending vehicles completely blocking the box was a Metrobus. When the light turned green for Eads Street traffic nobody could go anywhere and it wasn’t possible to weave past such a large obstacle with either a car or bicycle. So, although we had a green light, Eads Street, traffic could not proceed until the Metro bus finally moved. At that point Eads still had the green light and the 23rd Street light had long been red, so I and the vehicle to my left (on Eads) proceeded into the intersection only to be nearly hit by a motorist who decided to follow the Metrobus (red light notwithstanding.) The Eads Street vehicle to my left laid on the horn and I yelled, but frankly only our own reflexes prevented a crash since the 23rd Street driver seemed oblivious and did not stop.

Even though no crash happened, I want to document that this is a very perilous intersection. The daily need to move between stopped cars blocking the Eads Street travel lanes is dangerous. The almost institutionalized violation of the law is disheartening. I have reported the situation to the Arlington police. They did monitor the intersection for a few days. But they can’t (or won’t) be there every day.

It seems that the best solution is to adjust the signals on 23rd Street so that there is never any real advantage to blocking the Eads intersection in hopes of being released by the Jefferson Davis light. If the light at Jefferson Davis Drive did not turn green first people would not feel the need to try and jam into the intersection to “make it”. The two lights would handle a seamless flow of traffic whereby the people on either side of the Eads Street intersection would be in the same position.

This is an example of how a community commitment to cycling needs to be holistic, while responsibility is fractured. I’m not sure who controls those traffic lights or if the safety of cyclists (which, after all, are in a marked cycling lane on Eads Street at that point) even matter in their equations. Can somebody advise who to notify about traffic light timing?

No crash this morning. But with the situation it is likely to happen to somebody. Maybe not me, but surely somebody.

Topic

[KLizotte]

I never go through there at rush hour so have never seen the backup you describe; most of the time I take the S Fern Street which is a parallel street and much quieter than S. Eads. Have you tried S Fern instead?

I agree the lights should be synced however.

[83b]

Not that any of this is relevant, but I used to live right there and LOATHED that intersection. And the general pattern of traffic design problems and poor drivers was part of the attraction to move into the city. I also couldn’t believe some of the shenanigans with trying to use the gas station on that corner. Even though its one of the only ones in the neighborhood I started actively avoiding it.

[Sunyata]

@S. Arlington Observer 138036 wrote:

I’m not sure who controls those traffic lights or if the safety of cyclists (which, after all, are in a marked cycling lane on Eads Street at that point) even matter in their equations. Can somebody advise who to notify about traffic light timing?

Yikes… That sounds like a very badly controlled intersection.

In Arlington County, the Transportation Engineering and Operations Bureau handle light timing. Here is their website with contact info:
https://transportation.arlingtonva.us/streets/traffic-signals/

[dasgeh]

I agree this is one of the worst blocks in Arlington. It’s not just a cycling issue – it’s bad for everyone.

You can also reach Arlington’s DES on twitter (@arlingtonDES) and des@arlingtonva.us

[S. Arlington Observer]

@dasgeh 138093 wrote:

I agree this is one of the worst blocks in Arlington. It’s not just a cycling issue – it’s bad for everyone.

You can also reach Arlington’s DES on twitter (@arlingtonDES) and des@arlingtonva.us

Thanks to both you and Sunyata for the info on DES. I will follow up, though I don’t have a twitter account. I’ve resisted forever but may have to give in. My kids have Instagram, Twitter and 8 million other things. I feel lucky to not to be strangled for time with just Facebook.

But thanks. I will follow up with the County.

[consularrider]

@S. Arlington Observer 138098 wrote:

Thanks to both you and Sunyata for the info on DES. I will follow up, though I don’t have a twitter account. I’ve resisted forever but may have to give in. My kids have Instagram, Twitter and 8 million other things. I feel lucky to not to be strangled for time with just Facebook.

But thanks. I will follow up with the County.

Well, if the kids have Twitter they can do the tweet on your behalf and you can stay pure. I’m like you, between this forum and facebook, my retirement time is all used up and is cutting into my time on the bike.

[Subby]

I feel like the next intersection (heading to DC on Eads – 20th St, I believe) is worse bc you are back in the protected bike lane and you have cars turning right across your path. 23rd St is congested, but if you filter to the front it puts you in pretty good position to proceed. Not perfect but not really that bad, either. Just a general observation though – not trying to marginalize your having to deal with knuckleheads in that spot.

[lordofthemark]

When the MVT was mulchy I went that way a few times. Just tried to be real careful at 23rd and at 20th.

[vern]

@Subby 138146 wrote:

I feel like the next intersection (heading to DC on Eads – 20th St, I believe) is worse bc you are back in the protected bike lane and you have cars turning right across your path. 23rd St is congested, but if you filter to the front it puts you in pretty good position to proceed. Not perfect but not really that bad, either. Just a general observation though – not trying to marginalize your having to deal with knuckleheads in that spot.

That’s my experience as one who goes through this intersection daily. I always slow up at 20th or adjust my speed so that I know (or think I know) the cars see me that might turn right. At 23rd, I just wait until it’s safe to proceed, and if it’s all jammed up it’s usually pretty easy to slide through the mess and be on my way. But, because of the congestion driver’s do get antsy so cyclists must be very cognizant of driver’s who make sudden, erratic moves.

[Author]

Replies