The Chainlink

A male cyclist was hit by a driver of a car at Halsted and Roosevelt during the Tuesday evening rush and suffered serious injuries.
A cyclist friend was in the vicinity of Halsted and Roosevelt around 5:30pm, 7-18-17 and viewed part of a car on bike collision. The driver was piloting the vehicle westbound traveling about the speed limit when they hit the southbound cyclist. The cyclist was unconscious and his leg was broken. The driver remained on the scene.The cyclist was alert when paramedics arrived and was taken to a hospital. Does anyone know this cyclist and how he is doing or any other info?

Additional discussion with DNAinfo article: http://www.thechainlink.org/forum/topics/bicyclist-hit-by-car-flipp...

Views: 8934

Attachments:

Replies are closed for this discussion.

Replies to This Discussion

Really astute observation, Bob.  I think a lot of us can relate to the "highest gear and can't accelerate" situation after a sudden stop too.

Choice three, if you think of it, might be to ditch the bike and run like hell.  I'm not joking.

It doesn't relate to the video, but this also reminds me of the situation where the front derailleur selector/lever accidentally gets out of position, you start to pedal, and the chain flies off the gears, leaving you standing still.  Yet another good reason to not leave yourself in an intersection during a red light.

I remembered something else while riding past this intersection yesterday. There is an unusually long lag between the "don't walk" sign and the red light on Roosevelt. For most intersections, when the blinking don't walk stops blinking, the light cycles to yellow and then to red pretty quickly. At this intersection, though, there's a lag of about 6 seconds where peds have a solid don't walk but cars on Roosevelt still have a green light.

Other lights along Halsted have wonky timing, but I take it for granted because I ride Halsted almost every day. Cyclists not familiar with the route, however, might make mistakes assuming that the lights act the same as most others in the city.

That's an interesting observation. Probably the "best" potential explanation I've seen.

Maurice,
Do you know if this intersection has the longer/delayed red signal during the pm rush so the intersection can clear? If it does, and if both the driver and the cyclist knew about it, both could have been trying to take advantage of it.

It's seems to me that some are attempting to "justify" this cyclist's reason for running a red light!

It's not that some are attempting to 'justify' any behavior, but an attempt to understand conditions (traffic or other), which are applicable to cyclist and driver, and to understand these facts and the motivation that led to their actions. What's wrong with trying to look at a situation through all angles? How else can you impartially analyze anything?

Any update on the condition of the cyclist?

I'm tempted to send a message to his mom, Cheryl, but I definitely want to respect their privacy. The last report was that he was alert and aware of everything and was in surgery to repair his legs. Hopefully, perhaps if they choose, to let us know how he's doing currently. The cycling community is hoping for his full recovery. Get well!
I timed it yesterday at about 4pm.

The "don't walk" signal stops blinking.
8 seconds later, the light turns yellow.
2 more seconds before it turns red.

That's a really long delay.
Thank you Maurice.

RSS

© 2008-2016   The Chainlink Community, L.L.C.   Powered by

Disclaimer  |  Report an Issue  |  Terms of Service