You are reading a single comment by @Oliver Schick and its replies.
Click here to read the full conversation.
-
Oh, I have no doubt that it's the cyclist's transgression in this case, not only based on your description, but also because it's a very familiar crash pattern and expected with this sort of design. @Grand-Wizard-Goma-Sauce will know more, but I think the traffic light phasing may also change slightly depending on the time of day. I don't know how they've done those, though.
As i was stuck there for over three hours yesterday, so I did a few basic calculations (obviously not scientifically but still..).
Cyclist light (southbound):
Amber for 5.5-6 seconds before turning red
Red for 2.5-3 seconds before amber shows on my traffic light
Distance cyclist traveled from red to collision ~7m (1.5 seconds @ 12mph)
Northbound lights (mine):
Amber for 1 second before turning green (I pulled away whilst both amber and green was showing)
Distance i traveled from white line ~12m (~2 seconds though hard to calculate as i was accelerating up to 20mph)
This means that at the very minimum, i hit him 4.5 seconds after the light went red and so he went through it roughly 3 seconds after it went red and 8.5 seconds after it first went amber.
That's a massive amount of time given the cycle lane is arrow straight and there are both standard traffic lights (dedicated to the cyclist) and little lights (at eye level) which show bikes on.
Regardless of the road design, it's hard to argue he didn't make a very conscious decision to skip the light well after it turned red.