Police Car Strikes Cyclists in Alexandria
Our Community › Forums › Crashes, Close Calls and Incidents › Police Car Strikes Cyclists in Alexandria
- This topic has 55 replies, 20 voices, and was last updated 5 years, 11 months ago by
DismalScientist.
-
AuthorPosts
-
April 25, 2019 at 8:13 pm #1098001
bentbike33
Participant@ImaCynic 190064 wrote:
I don’t think speed is as big of a factor as some make it out to be, when it comes to car/bike incursions. Even a Smart car travelling at 25mph has plenty of energy to flatten a cyclist. On the other hand, necking down lanes might slow things down, but it also tend to cause drivers to bias to the right, and I think that poses a greater risk to cyclists.
I think speed has less to do with relative momentum between bikes and cars, and more to do with reaction time and attention paid by drivers to what is going on around them. More speed = longer braking distance = less time to react upon seeing something for which to apply the brakes. Even the reason the officer did not look right before turning right on red probably had a lot to do with the speed of the traffic with which he/she was looking to merge; the cars coming from the left were much more of a threat than anything that would be coming from the right.
On my weekend rides, I like to devise routes mainly on neighborhood streets, but of course in Northern Virginia you will eventually need to use a more major route if you want to get anywhere. Inevitably my comfort level drops precipitously when I have to use a road with yellow paint in the middle as drivers’ sense of entitlement to speed increases. As the speed limit rises, drivers naturally think the road is safer to travel at higher speed meaning the less likely it is they have to pay attention to what’s going on. Similarly, the more the road resembles the type of road where the speed limit is high, the more likely are drivers to go fast on it, regardless of the actual posted speed limit (lordofthemark’s point).
April 25, 2019 at 8:42 pm #1098003ImaCynic
Participant@huskerdont 190067 wrote:
The research does not bear this out. There are plenty of sources for this, but I’ll just point to one.
http://humantransport.org/sidewalks/SpeedKills.htm
Summary:
20 mph: 5% chance of pedestrian death
30 mph: 45% chance of pedestrian death
40 mph: 85% chance of pedestrian death
The numbers may vary a bit for cyclists, but you get the idea.
Getting people to obey posted speed limits could save a lot of lives, as could reducing speeds in areas with heavy pedestrian and cycling traffic.
I believe the stats you cited is based on a driver actually slowing down to prevent a pedestrian impact, rather than impacting at the speed shown, so these are actually conservative numbers.
The point I am trying to make is that on typical roads around here, cars are already travelling fast enough to kill, even with a small car observing the lowest posted speed limit. A quick Google search on car bike crash causes will show that with most car/bike incidents, speed is not a major factor.
April 25, 2019 at 8:53 pm #1098004lordofthemark
Participant@ImaCynic 190071 wrote:
I believe the stats you cited is based on a driver actually slowing down to prevent a pedestrian impact, rather than impacting at the speed shown, so these are actually conservative numbers.
The point I am trying to make is that on typical roads around here, cars are already travelling fast enough to kill, even with a small car observing the lowest posted speed limit. A quick Google search on car bike crash causes will show that with most car/bike incidents, speed is not a major factor.
1. Lots of people get hit by cars around here and do not die, so the percentages really do matter.
2. The earlier points were about the seriousness of the crash, not the cause. In the scenarios bentbike mentions, speed might not have been mentioned as a factor by police but would still have been a factor – either because speed had a causal impact even though the driver was not speeding, because (like the person rushing to make a right on red because other cars are speeding) its cars other than the driver in the crash who are speeding, or simply because the police are not sure of the speed.
April 26, 2019 at 1:58 am #1098012dbb
ParticipantFrom the Post today “Fairfax Police Chief Edwin C. Roessler Jr. said that Crawley was in the roadway, bound to obey the laws which apply to vehicles, and that he was going the wrong way on the highway — north in the southbound lanes — and didn’t exercise caution before entering the intersection.” What Chief Roessler seems to omit from his statement is that the police car was blocking the crosswalk so the cyclists had to leave the crosswalk to get across the street.
Just say’n
April 26, 2019 at 3:00 am #1098013Rootchopper
ParticipantIf the cyclist had been a cop and the driver a private citizen, would Roessler have drawn the same conclusion?
April 26, 2019 at 9:38 am #1098015n18
Participant@dbb 190081 wrote:
From the Post today “Fairfax Police Chief Edwin C. Roessler Jr. said that Crawley was in the roadway, bound to obey the laws which apply to vehicles, and that he was going the wrong way on the highway — north in the southbound lanes — and didn’t exercise caution before entering the intersection.” What Chief Roessler seems to omit from his statement is that the police car was blocking the crosswalk so the cyclists had to leave the crosswalk to get across the street.
Just say’n
Link to article in the Washington Post. This is typical of crashes involving peds/cyclists. The driver side of the story is heard first, and taken as the truth while the other party is either unconscious, in shock, confusion, or laying in a hospital. The police department had to hear the driver story first, and seemed to make conclusions; even before hearing the cyclist side of it. In this FCPD blog, they say “the officer was stopped at a red light”. Not so. He crossed the white line, so he is the box so to speak, running a red light. The cyclist didn’t leave the crosswalk until the cruiser moved, to avoid a collusion. So it seems that both at fault, the officer for running a red light, and the cyclist for not waiting for the walk signal. Only one is ticketed, but more importantly, it gives the wrong driver-education; that they don’t need to stop at the white line, that’s what it’s there for.
April 26, 2019 at 12:53 pm #1098017huskerdont
Participant“A quick Google search on car bike crash causes will show that with most car/bike incidents, speed is not a major factor. “
I wonder about this statement. Perhaps you mean “speeding”? It is entirely possible that an officer could fail to list speeding as a factor in an accident report when more obvious causes exist (e.g., failure to stop or yield). The officer would be unlikely to list speed at all if there was no evidence that the speed limit was broken; in this case, speed could definitely still be a factor in the severity of the crash even if it were not an official cause of the crash.
There is a quadrupling of potential impact energy for every doubling of speed. There is no doubt that smaller cars can kill even at slower speeds, but your odds are inversely proportional to the energy you encounter, and this energy goes up with speed. The faster speeds increase stopping distance as well, as bentbike mentions, so a collision could be more likely.
April 26, 2019 at 5:26 pm #1098023scoot
Participant@n18 190084 wrote:
In this FCPD blog, they say “the officer was stopped at a red light”. Not so. He crossed the white line, so he is the box so to speak, running a red light.
To be fair, the citizen dashcam shows that the police driver did initially stop for the red light as required. It’s hard to tell if he was completely behind the stop line, but it is clear that he wasn’t blocking the crosswalk at all while stopped. His error was his subsequent attempt to make a right-on-red when it was not safe to do so. Because he didn’t check to see if anyone was about to use that crosswalk. If the bicyclist hadn’t been there, that would have been a legal turn.
April 26, 2019 at 6:00 pm #1098026bentbike33
ParticipantAs I suspected, Mr. Crawley appears to have been using what the Fairfax County Bike Map considers a “Secondary Trail (Shared Use Path)”.
Note that the link does not go to the specific location. Look for “Mount Vernon Plaza Shopping Center”.
April 26, 2019 at 6:46 pm #1098028dasgeh
Participant@scoot 190095 wrote:
To be fair, the citizen dashcam shows that the police driver did initially stop for the red light as required. It’s hard to tell if he was completely behind the stop line, but it is clear that he wasn’t blocking the crosswalk at all while stopped. His error was his subsequent attempt to make a right-on-red when it was not safe to do so. Because he didn’t check to see if anyone was about to use that crosswalk. If the bicyclist hadn’t been there, that would have been a legal turn.
I thought the police car was slightly over the stop line, but that there was room in the crosswalk. Also it looked like the cyclist was in the crosswalk, making the chief’s statement that he was on the highway incorrect. It really seems like a case of “they were both wrong” and the fact that PD is trying to cover it up is shameful.
April 26, 2019 at 6:56 pm #1098030mstone
ParticipantIt certainly doesn’t give me any hope that FCPD will start cracking down on drivers rolling through crosswalks looking only to their left while turning on red. But I didn’t really believe that would happen so I guess not much has changed.
April 26, 2019 at 7:10 pm #1098031dbb
ParticipantI’d hazard a guess that if you were to look in the dictionary for distracted driver, there would be a picture of a police officer. Radio, computer, cell phone, etc. What could possibly go wrong?
April 26, 2019 at 7:14 pm #1098032n18
Participant@scoot 190095 wrote:
To be fair, the citizen dashcam shows that the police driver did initially stop for the red light as required. It’s hard to tell if he was completely behind the stop line, but it is clear that he wasn’t blocking the crosswalk at all while stopped. His error was his subsequent attempt to make a right-on-red when it was not safe to do so. Because he didn’t check to see if anyone was about to use that crosswalk. If the bicyclist hadn’t been there, that would have been a legal turn.
To me, the citizen dashcam does show the cruiser with it’s rear wheels over the white line, so unless he stopped first before crossing the white line, then proceeded and stopped again, then he didn’t break any laws, but I doubt he stopped twice.
April 26, 2019 at 7:36 pm #1098039bentbike33
Participant@dbb 190104 wrote:
I’d hazard a guess that if you were to look in the dictionary for distracted driver, there would be a picture of a police officer. Radio, computer, cell phone, donut, coffee, etc. What could possibly go wrong?
ftfy
April 26, 2019 at 7:40 pm #1098040scoot
Participant@n18 190105 wrote:
To me, the citizen dashcam does show the cruiser with it’s rear wheels over the white line, so unless he stopped first before crossing the white line, then proceeded and stopped again, then he didn’t break any laws, but I doubt he stopped twice.
In the first three seconds of the video, the police car is stopped behind the crosswalk. His front end might be over the white stop line, but his rear wheels certainly are not. The movement of the dashcam driver from SB US-1 into the turn lane opens up a small gap in the right lane behind the bus. The police officer decides he can fit into this gap. As the bus passes (0:04), he begins his turn. The only reason he stops for a second time (at 0:06) is because he has hit the bicyclist.
Note also that the Fordson stop line is farther forward in the right lane than the others. A common design that facilitates better sightlines for right-on-red drivers.
-
AuthorPosts
- You must be logged in to reply to this topic.