mr_bill

Well, the bike is a first gen Scott Foil Premium.

As far as damage on the bike, I'm sure someone will offer their opinion on the condition of the bicycle. Inspection by internut always ends well.

-mr. bill

CB HI

See video at 1:00 Just a crack in the carbon makes the frame totaled.

wphamilton

I'll note that for future reference. I just call it stop line because that's how it is in the statutes of Georgia, where I live. https://law.justia.com/codes/georgia...icle-4/40-6-72

mr_bill

In the UVC and MUTCD, it is called a "stop line." As far as I can tell, in 49 of 50 states driving laws it's called a "stop line." California calls it a "limit line."

However, for whatever reason many State DOTs use the term "stop bar" and many manufacturers use the term "stop bar."

-mr. bill

Paul Barnard

You just think traffic is slow to get moving on a green light as things are now!

Paul Barnard

I think you make a legitimate point. I suspect the reason the line is so far back at that intersection is because of just how narrow that road is. If the cyclist was going to take a right it looks like he could have easily visually cleared to the left from the white line. If he were going to take a left, with the height of the vegetation to the right and the dip in the road, I think he would have had to move past the line to make sure it was clear. It's hard to say for sure. I think our (cyclists) safety lesson in this mishap is that if you are going to move past the stop line you have to be on high guard and maybe favor the right so as to give turning motorist more room.

The cop was dead damn wrong for having his umbilical cord to society stuffed in his face. It's inexcusable. If he wasn't giving a turn signal, more shame on him.

genec

Cop was also damn wrong for making that cutoff left turn...

BTW thanks for noticing that indeed, there are high weeds and reduced visibility to the right. Some here just denied the heck out of that... and for that, I wish them all the best in safely negotiating similar roadways.

mr_bill

jon c. 

Talking on a cell phone is always a distraction. And the cop in this case is clearly in error.

FBOATSB

In the video, looks to me the cop instinctively punched it in order to cut in front of the oncoming vehicle, cutting the corner even more severely than just tootling along talking on his phone.

Paul Barnard

If you are bored and wondering how threads like this go in other kinds of forums, here you go!

https://www.thehulltruth.com/index.php

https://www.24hourcampfire.com/ubbth...p-hits-bicycle

Milton Keynes

Had he stopped back there I bet he'd still have gotten run into.

Milton Keynes

And of course so many stupid "bicycles shouldn't be on the road" comments on that article.

wphamilton

Sorry, I still don't see any weeds high enough to reduce visibility.

genec

I'm shorter than you. And actually, that is NOT the view from the stop line... but the view one sees when they pull up, to gain a better view.

Paul Barnard

That was not taken from the stop line either. It was taken from well beyond the stop line. The elevation appears to be several feet higher there. I am not arguing that his line of sight WAS impeded at the stop line, only that it could have been.

wphamilton

The cyclist didn't even look to the right when he was near the stop line.

Seriously just looking at the weeds they're not what you'd call high weeds, nor thick, and if they did obstruct the view of that 50 feet or so stretch, there's no way it would obstruct enough to not see a vehicle there. I didn't think it necessary to even comment, when I posted those photos.

Paul Barnard

Is it not possible that the cyclist had been there before and knew that he needed to move further forward to get an optimal view? Never mind. You have made up you mind.

wphamilton

If by that you mean that I have looked for and presented factual information, and based a conclusion on that, then yes You could go so far as to say that I am the only person contributing to this thread that has done so, while getting a lot of static from people presenting unlikely and unfounded "maybe's"

To answer your specific question, yes that might have been running through his mind. It was a dumb move on his part.

mr_bill

Bmach

mr_bill

But wait, we should *all* take this time to *learn* from this cyclist's *MANY* blunders. We could save our lives!

• The driver heading south in the Buick Verano passes at 0:23 seconds. Joe checks the time at 0:27. The police officer in the SUV has *still* not reached the intersection at 0:34. ELEVEN seconds is PLENTLY of time for Joe to make a left turn at that intersection. Had he not needlessly waited at the stop sign, the accident (not crash) would not have happened.
• From 0:34 to 0:37 Joe checks to the left. Poor situational awareness. The closest hazard is to the right! Focus on the accident (not crash) coming from the right!
• A HUGE disadvantage of diamond frame horizontal top bar bikes is the time it takes to panic dismount when stopped. This accident (not crash) could have been COMPLETELY avoided if Joe was riding a bike with a step-thru frame. Plenty of time to dismount and simply run away from the accident (not crash).
• Shouting "Woah, woah!" when not riding a horse is generally ineffective.

Anything else? I mean, lives are at stake here.

-mr. bill

Paul Barnard

Based on your exhaustive research, how much does the road rise from the stop line to where the cyclist was stopped?

Without knowledge of that, we are pissing in the wind.

mr_bill

About one and a quarter meters.
Did I mention that Google Street view is at 2.5 meters above the ground?
The average male adult's eye height in 1.63 meters above the ground.

-mr. bill

wphamilton

No need to be sarcastic - I did check that before posting anything. Pretty flat on the approach, and something around 5-8 feet to the cross road https://www.strava.com/segments/2557775. The segment ends before the intersection and is flat on the approach, but you can investigate rides from the leaderboard to see the approximate elevation changes beyond the segment. Google Maps has it at only about 3 feet but I think that may be underestimated, from looking at the video. So you have a range of estimates, from a minimum of 3 feet to say, 10 feet to be generous. The weeds that people are so concerned about aren't any higher than the safety rail.


When I was looking at the rider's video, there doesn't seem to be any issue at all with visibility at the intersection, although as I mentioned he never looks right. He just rolls right up to the crossroad looking left and ahead. That's all a red herring. The concern I'd have had is the dip in the road about a quarter mile away which would partially obscure approaching vehicles. But vehicles are easily visible beyond that because of the rise.


If a biker DOES pull up at the intersection, you wouldn't want to be in the path of someone cutting a sharp turn, that should be basic, common sense. If you've looked through the various comments from locals to the area, that intersection is known to be risky, which is another flag about the cyclist's lack of caution.


The cyclist's video is deceptive compared to the longer one - it just shows him stopped there and the cop not paying attention and hitting him. It doesn't look like abnormal positioning there, as if he was just sitting in his allotted lane. But when you see the whole story, that's not the case. No one is defending the cop here, but the cyclist himself doesn't have much ground to stand on either.