Flutterby™! : Rolling Stop

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Rolling Stop

2024-09-11 18:30:24.77026+02 by Dan Lyke 0 comments

Electrek: It turns out cyclists actually should roll through stop signs. Here’s why.

Alvin explained, “The main takeaway from the study is that a rolling stop law allowed people biking to do an action they preferred in treating a stop sign as a yield. And once drivers were educated, intersection interactions between people biking and driving were no more dangerous than before introducing the law.”

The quote says "the study", the article actually links to several studies, though the articles that the link farms are ripping off, like Velo: Of Course a Rolling ‘Idaho Stop’ Is Safer for Cyclists. Here’s Why. and Oregon Public Broadcasting: Allowing rolling stops on bicycles doesn't cause risky road behavior, study finds are referencing Transportation Research Part C: Emerging Technologies Volume 166, September 2024, 104754: Safety relevant driver and bicyclist behaviors resulting from bicycling rolling stops observed in a networked driving and bicycling simulator.

Delaware Yield Crash Data shows a -23% change in bicycle/automobile collisions in the 30 months before and after implementing the rules.

The Idaho Stop Law and the Severity of Bicycle Crashes: A Comparative Study Brandon Whyte, Masters Project 2013 (PDF) didn't find a difference in the number of collisions, but did find a "...significant difference in crash severity".

NHTSA Bicyclist Yield As Stop Fact Sheet (PDF)

I'm trying to find the Tampa Bay study mentioned in the original article, but that led to League of American Bicyclists: Laws To Promote Biking & Walking which mentions a study out of that region that addressed racial disparities in enforcement. Go figure.

Note that the key here seems to be in educating the causes of cyclist injury: Automobile drivers and law enforcment.

[ related topics: Sociology Television California Culture Sports Automobiles Pedal Power Bicycling Model Building Government ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.