Bicycle Austin 

Drivers are at-fault in 90% of cyclist and pedestrian fatalities. (report, p. 25)  •  In 40% of fatal car/bike crashes the driver was drunk. (source)

A volunteer project by Michael Bluejay.

Awarded "Best of Austin" by the Austin Chronicle.

Bicycle Austin forum

This forum’s roots date back to the very first bike email list in Austin, starting in 1994, and it played a part in the getting the segregated bike lanes you see all over town.  Be a part of history and make a post!

You are not logged in.

#1 2019-09-01 01:39:39

dougmc
Administrator
Registered: 2008-06-01
Posts: 640

2019-09-14 Sat night/Sun morning 2am 37th Annual Full Moon Cruze

It's that time of year again, and the ride you've been waiting for is coming ... the 37th Annual Full Moon Cruze bike ride!

This year, the ride will happen on Saturday night/Sunday morning, September 14/15th, 2019. Assemble at about 1:30 am at the James D. Pfluger Bicycle and Pedestrian Bridge and we'll ride out at about 2:15 am to 2:30 am.

DO NOT BE CONFUSED BY THE DATE!  This ride happens on Saturday night/Sunday morning, the night of the 14nd and/or the morning of the 15th!  Set an alarm so you don't forget, take a nap, charge those lights, etc.!

If you only make one bicycle ride a year -- this is the one to make!

The route can be found here: http://www.mapmyride.com/routes/view/134792405

The pace is ... whatever you want it to be.  Since we're all following the same route you can go as fast or as slow as you want, and there's enough people that whatever your speed, you won't be alone.

If you're into the Facebook thing, here's an event that you can click on: https://www.facebook.com/events/2128472557452935/

As always, ride at your own risk, and having lights, water and enough equipment to change a flat tire is a good idea.

The schedule for upcoming full moon rides, both monthly and annual, can be found at http://cycling.frenzied.us/full-moon-rides

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

[ Generated in 0.007 seconds, 8 queries executed - Memory usage: 547.24 KiB (Peak: 564.22 KiB) ]