Another year has passed since my last ride in the El Tour de Tucson. This year is the 34th anniversary of this annual fund-raising event, and once again I signed up to ride the full distance - which was 106 miles this year. This year was thankfully warmer than previous years, but holy cow - the wind was terrible. But I'll get to that in a minute.
The night before the ride I packed up my bicycle gear, and I made sure that I wouldn't repeat last year's mistake and forget my helmet. As I was putting my things together, I discovered that my bicycle had a flat tire. It was no fun changing it, of course, but it was so much better to have fortuitously discovered that problem the night before rather than the morning of. After that issue was resolved I set my alarm for 4:30am climbed into bed around 10:30pm. However, for some reason I could not fall asleep, so I probably did not drift off until sometime around 2:30am, which meant that I was hauling my exhausted self out of bed after only two hours of sleep. (Would someone please remind me why I do this every year?)
Anyway, I was on the road by 5:00am, and after a brief stop at a McDonald's for some carb loading via an Egg McMuffin, I headed off to Armory Park in downtown Tucson where the ride was scheduled to begin. I had studied the map before the ride, and I noticed that the route had changed for this year. First of all, the long, uphill ride on La Cañada Drive was gone, but it appeared to be replaced by an even longer uphill ride on Oracle Road. In addition to that change, the end of the ride had been changed from the 20+ miles riding Tangerine Road and the Frontage Road along I-10 to Avra Valley Road and Silverbell Road. This was all new territory for me, so needless to say - I did not know what the the day would have in store for me when I would arrive at those sections of the route.
Sometime shortly after 5:30am I arrived at the Tucson Convention Center (TCC), which is where I always park my car for the day, and after a few minutes putting the last of my things together, I hopped on my bicycle and rode over to Armory Park to get in line for the ride. I arrived around 10 or 15 minutes before 6:00am, and there were perhaps a couple hundred riders in line before me. (That number includes the "Platinum Riders," who must have had a ride time of less than five hours during a previous year.)
|Arriving near the start line. |
|The group of cyclists in front of me. |
(The banner in the distance is the actual starting line.)
As I waited for the ride to begin, I talked with the cyclists around me, and I met a guy whose wife had inadvertently cheated on one of the shorter distances during the previous year's ride. It seems that she didn't want to deal with the large crowd at the start line, so she began her ride 1 hour earlier than the rest of the riders. This meant that she wouldn't have an official time for the ride, but she didn't care. However, she was the first woman to cross the finish line for her distance, so they erroneously listed her as the winner. This isn't an actual race, so it's not that big of a deal, but nevertheless she registered for this year's ride under a different name. ;-)
|A quick panorama of the crowd of cyclists around 6:30am. |
As I mentioned earlier, the temperature was a little warmer than in past years; it was somewhere in the low 50s while I was waiting. But I had learned from some more-experienced El Tour participants during my 2014 and 2015 rides to wear something disposable like pajama pants while waiting in line, and any clothes which are abandoned near the start line are donated to charity once the riders have left. With that in mind, I had bought a large set of black pajama pants to wear over my legs as I waited, and I had made sure to leave the tags on to show that they were new. As the start time drew near, I removed those, folded them nicely with the tags showing, and placed them on the side of the road. (Other cyclists simply threw jackets and pants over the barriers which lined the street.)
As has happened in previous years, in the last few minutes before the ride begins, all of the cyclists don the last of their equipment, and then all the riders bunch up toward the start line, thereby filling up all the gaps in the crowd.
|Cyclists pushing toward the start line in the last few minutes. |
Shortly before 7:00am we all sang the National Anthem, and after a few perfunctory words from local politicians, they sounded the horn which announced the start, and we were off. I will admit, it always fills me with a small amount of nervousness before arriving at the starting line when I think about heading out as a lone cyclist within a sea of thousands; I am always afraid that I will fall over and get hit, or someone else will fall over and I'll crash into them, but every year it is an orderly affair as the cyclists cautiously start out in unison. (It seems that everyone else is also concerned about avoiding an accident.)
|106-mile riders starting out for the day. |
30 minutes after the ride had started I found myself at the Santa Cruz River crossing, where all of the cyclists are required to dismount and hand-carry their bicycles across the dry river bed. Once again, a Mariachi Band was playing music for everyone as we arrived on the other side of the river.
Once across the river, I climbed back on my bicycle and headed off. However, this is where I need to mention the wind which I had alluded to in my opening paragraph; the first 35 miles of this ride is predominantly uphill as we rode south, and we had a great deal of wind blowing to the north, which meant that the first several hours were uphill into the wind. There were brief downhills and a few respites from the wind here and there, but for the most part the beginning of my day was spent tucking my head down and riding into the wind. One of the biggest sources of relief for everyone was around the 25-mile point when we turned north onto Kolb Road and had the wind behind us for a change. It was only for 2½ miles, but still - I heard dozens of other cyclists verbally reacting to the difference, and throughout the rest of the day I heard cyclists complaining about how awful that wind had been.
Of course, one of my personal demoralizers is when I hit the 30-mile mark; that is when the route passes Pima Community College, which is the start of the 75-mile route. I always think to myself, "If I had done that ride, I would be starting from here, rather than having just ridden 30 miles."
As we turned off Kolb Road onto Irvington Road, we entered my section of town, where I train all the time. In fact, I had ridden the northbound climb on Houghton Road and Escalante Road a couple of times that week, so I was quite used to that terrain and the climbs did not bother me. Shortly after reaching the end of Escalante Road, the route turned north onto Freeman Road, where we were all treated to several miles of fast-paced, downhill riding. (With no winds!)
At the bottom of Freeman Road the course followed the familiar route of Speedway to Houghton to Snyder, which took about 30 minutes to negotiate, and then it was time for the second river crossing. By this time I had been riding for over 3½ hours with no breaks, and I was running low on water, so I stopped to refill my water bottles, eat a few snacks, and remove the last of my cold weather gear.
After a brief 20-minute rest stop, I was back on the road. My next obstacle was the steep climb up East Snyder Road near North Rockcliff Road. I have mentioned this hill in my other blogs about riding in the El Tour de Tucson, so I won't go into detail here, except to reiterate what I have said in the past - thankfully this climb is only a few hundred meters in length.
Once I had put the Snyder Road climb behind me, I had a short ride to Cowbell Crossing, where my wife, Kathleen, was cheering on passing cyclists around the 52-mile mark with a group of her coworkers and our dog, Boudicca. Kathleen had been watching my progress via my Garmin Live Track, although what she was seeing was a few seconds behind my actual location, so she barely had time to run to the side of the road with Boudicca and wave as I rode by. (I had thought about stopping, but their group was set up on the opposite side of the road so I chose not to stop. In hindsight, I probably should have at least stopped to say "Hi" to everyone.)
The route meandered west along Sunrise and Skyline Drives, then we climbed north on Oracle Road, which was a departure from previous years of climbing north on La Cañada Drive. This extended the length of the climb by a couple of miles, so I'm still not quite sure if I approve of the changed route.
Around the 60-mile point I ran into an interesting predicament; my Garmin Cycling GPS announced that it's battery was almost depleted and it was going to shut down. I had fully charged it the night before, and I had used my Garmin GPS on several 100-mile rides with no problems in the past, but this year I had more devices connected than in previous years. For example, my GPS was linked to my cell phone for Live Tracking (which was constantly updating my location for family members to watch), and my GPS was paired with a Garmin Varia Radar which helps me know when vehicles are approaching from behind. Fortunately I had planned ahead; my cell phone was already attached to a spare battery and was still fully charged, and I had brought a spare USB battery pack in case of emergency. With that in mind, I quickly pulled off to the side of the road, and then I attached a USB cable from the battery pack to my GPS. Once I had all of that connected, my GPS showed that it was charging and I hopped back on the road. (Note: By the end of my ride, the GPS was fully-charged once again and the battery pack was still half-charged.)
I was running low on water as I reached the 75-mile mark, so I pulled off the road with dozens of other cyclists. I quickly refilled my water bottles, and I also availed myself of the Girl Scout cookies which the volunteers had provided. (No Thin Mints, of course, because those would have melted in the heat.)
After a 15-minute break I was back on the road and heading west on Moore Road. Thankfully the worst of the climbs were behind me, and the next 10 to 15 miles were predominantly downhill, which was a welcome change after the miles of climbing earlier in the day.
As I rode by a family which was cheering on the riders, their boys were all holding out their hands for high fives; most riders passed them by without obliging, but I held out my hand and swatted them all - thankfully without losing my balance in the process.
As I have seen on other long rides, I encountered a variety of interesting bicycles throughout the day's ride; most cyclists were on road bikes, of course, but there were a lot of mountain bikes, several single-speeds, a bunch of tandems, a smattering of recumbent bikes, and a couple of complete novelties - someone was riding a an ElliptiGO for the full 106 miles, and another guy was riding a unicycle. (I have no idea what distance the unicyclist was riding, but it was before we had merged with the cyclists riding for 28 miles, so the unicyclist was riding at least 37 miles.)
The route headed down Avra Valley Road and then onto Silverbell Road, which I mentioned earlier was different than riding down the Frontage Road in previous years. There were a few things about this new route which were a welcome change; namely that the ride was nowhere near as boring as 20 miles of riding along a frontage road next to an Interstate. The biggest drawback was, however, that riding south meant facing into the wind - again.
Nevertheless, after an hour's ride south on Silverbell Road, the route turned east on Speedway, then shortly after that the route briefly turned onto Mission Road and then 22nd Street, thereby retracing the final miles of the route from previous years. After that we turned onto 6th Avenue for the final stretch to the finish.
|Turning onto 6th Avenue for the final mile. |
|Approaching the finish line. |
I crossed the finish line around 8½ hours after I had started, although my actual riding time was just shy of 8 hours. (The remaining half-hour was spent on my two stops and the several intersections where I had to wait for the street lights to change.) It should go without mentioning that I was exceedingly happy to be done with the ride, and after picking up my silver medal for my time category, I found a quiet place to stash my bicycle for a few minutes and I bought a slice of pizza with a bottle of Gatorade to celebrate my successful completion of another "Century Ride."
Looking over the miles that I rode, my ride began with 25 miles of riding uphill into the wind, and it ended with 20 miles of riding uphill into the wind; so just shy of 50% of the ride was spent riding uphill while enduring a steady wind in my face. That was subpar, to say the least, but there wasn't anything that could be done about it. I would estimate that the wind added at least an hour to my ride time, although it would probably be more accurate to say that it added 1½ hours to my ride time.
- Primary Statistics:
- Start Time: 6:58am
- Distance: 106 miles (105.6 miles on my GPS)
- Duration: 8 hours, 36 minutes (7 hours, 52 minutes on my GPS)
- Calories Burned: 3,074 kcal
- Altitude Gain: 4,259 feet
- Average Speed: 13.4 mph
- Peak Speed: 32.7 mph
- Average Cadence: 73.0 rpm
- Average: 72.1 F
- Minimum: 48.2 F
- Maximum: 86.0 F
- Heart Rate:
- Average: 147 bpm
- Maximum: 183 bpm
You know you've been cycling in 100+ temperatures too long when you head out for a ride in 80-degree weather and you think to yourself, "Wow, it's kinda chilly; I wonder if I need leg warmers?"
So, I went out for a late-night ride on my mountain bike last night... I left the house around midnight, and my route took me through some of the desert on the northeast side of Tucson.
FYI - It's a little unnerving when a whole pack of coyotes starts sounding off near you when you're by yourself with nothing but a single headlight to keep your bike on the narrow path. Just sayin'...
Perhaps a midnight ride wasn't my best idea.
PS - The coyote image is from Michael Frye, who has even more amazing artwork on his website.
As you may have seen from several of my earlier posts, I'm a big fan of recreational road cycling. Over the past few years I have ridden thousands of miles, and I have blogged about several of the "Century Rides" in which I have participated. During the average month I love climbing on my bicycle and riding through the surrounding desert three or four times per week.
Earlier this year I had shoulder surgery, and cycling became an important part of my recovery program. When my doctor and physical therapist both said that it was okay for me to start riding again, I spent several painful weeks working through the shoulder pain and slowly increasing my mileage, but it was ultimately worth the effort.
That being said, I also like to track my rides on the MapMyFitness website, and over time a playful competition developed between myself and a few of the other riders on some of my favorite desert courses. I am too old to be a serious competitor, so I was always a few minutes behind the fastest riders. But I usually rode more often than a few of the other riders, and therefore I was able to earn enough points to maintain my standing.
However, earlier this year someone moved to town who - for some inexplicable reason - decided that he needed to cheat.
On the one hand, this makes no sense to me: the MapMyFitness website is supposed to be about tracking your health, so why anyone would want to cheat seems beyond my comprehension.
On the other hand, some people like to compete with each other, as I mentioned earlier about myself and a few others on the MapMyFitness website. And where there's competition, some people like to win - regardless of what it takes to do so.
All of this leads me back to the cheater. What this guy likes to do is ride several of the courses with several cycling GPS devices and upload the results from all of his devices to the MapMyFitness website. I wasn't aware of this before, but the MapMyFitness website is poorly-designed in such a way that it allows people to do this, so it doesn't bother to check if a person is uploading multiple rides for the same course at the same time. This seems like a pretty trivial thing to check, so it was amazing to me just how easy the MapMyFitness website made cheating possible.
Needless to say, once this guy started uploading his fraudulent ride data, it became impossible to compete with him. I usually rode one of my favorite courses twice each time that I rode, and this guy would ride the same course two or three times. But since he was uploading the data from three GPS devices, the MapMyFitness website was giving him credit for six or nine rides. At that point it didn't matter how many times that I rode each course - there was no way that my honesty would be able to keep up with his dishonesty.
Now you would think that the folks at MapMyFitness would care about this, so a few months ago I decided to bring this to their attention. Here's what I sent them:
I have been a member of MapMyFitness for several years now, and an MVP member for some time. To be honest, from a workout tracking perspective, MapMyFitness has a lot of stiff competition from Strava, Ride With GPS, Garmin, etc. There is one reason why I chose MapMyFitness over its competitors - and that is for the friendly competition with other members. Over the past couple years, a few members have competed with me for Guru and Sprint King on a few of the MapMyFitness courses, and the opportunity to challenge or be challenged by someone else has created fun and attainable goals for me to strive for. This has been especially beneficial for me recently because I spent the latter part of last year and the early part of this year recuperating from surgery due to a series of cycling accidents last year, and the challenge of competition got me back on my bicycle again. As I mentioned earlier, this spirit of competition is specifically the reason why I chose MapMyFitness over its competition, and why I became an MVP member.
However, over the past few weeks I have realized just how easy it is for someone else to cheat, and as a result it has become apparent that honest behavior on my part will never achieve the numbers that someone who is being deliberately deceitful can attain. While I realize that MapMyFitness cannot actively police all of the activities that its users post, I think some things are easy enough to detect. Consider the following workouts from one person in question:
It is readily apparent that this user is uploading the same workout from three different Garmin devices, so each time that he completes a course his numbers are multiplied by three. With that in mind, on days when he has completed some of the courses in our area more than once, his numbers are simply unattainable by anyone who doesn't resort to his methods of dishonesty. Following my surgery I can barely make it 20-25 miles before I have to quit for the day, so there is no way that I could ride the 90-100 miles that I would need to ride in order to overcome this person's deceit.
As I mentioned earlier, I realize that MapMyFitness is more or less on an 'Honor System' and it cannot actively police all of the activities which are uploaded, but it would be easy to detect this specific user's behavior by simply checking if any user is in a course more than once at the same time; when that happens, do not count one of the courses.
Unfortunately, I also realize that my complaint will likely fall on deaf ears, and as a result I will probably cease using MapMyFitness in the near future. Since the one feature for which I chose your service is apparently suffering from unchecked fraudulent behavior, I feel that am left with little alternative. Thankfully, as I mentioned earlier, there are other choices available to me.
To be honest, I did not expect a response, so I was surprised to hear back from them. However, the banal substance of their response was ultimately worse than hearing nothing:
Kyle (Help & Support)
Thank you for writing in about this.
We have a system in place for identifying users that circumvent the rules on both challenges and courses. Sometimes, these are missed and certain users are able to manipulate the system, but we actively monitor and check leaderboards and challenges for cheating. We appreciate you reporting this to us and I have passed this along to the appropriate team.
Cheating participants will not be awarded prizes.
Let me know if you have any additional questions or concerns
It may sound like I'm being overly harsh to what seems like a polite response, but the truth is - the scammer rocketed to the top of the leaderboard on several courses, and MapMyFitness didn't do anything about it. The year is barely half over, and this fraudster has already amassed scores which cannot possibly be attained by anyone who refuses to stoop to his level of deception.
So I used to look forward to the friendly competition on the MapMyFitness website, but now that's something of an impossibility. No matter what any honest person does, they simply cannot compete with this schmuck. It's amazing how all it takes as one jerk to ruin something.
So, today's ride through Saguaro National Park was a little warm...
Of course, the highest temperatures were when I was climbing Riparian Ridge... That was no fun at all, believe me.
I saw a four-foot rattlesnake in the bicycle lane during one of my cycling laps around Saguaro National Park today, and I'm not quite sure how I feel about that.
On the one hand, he's not riding a bicycle; but on the other hand, he's not in a motorized vehicle.
I think he gets by on a technicality.
I was watching a video about last year's 104-mile El Tour de Tucson cycling event, when they interviewed the guy in this photo...
This cyclist is 86 years old, and he was riding the full 104 miles as he has done every year for the past 33 years.
I have officially lost every opportunity for whining about how hard that ride was for me...
PS - Bonus points for this guy's cycling jersey from the 160-mile Ride Around Mount Rainier in One Day.
I posted the following to Facebook, but I thought that it would be good to repost here...
How I spent my Saturday - riding 104 miles around the city of Tucson with 9,000 other people from around the world. This year I abandoned my usual habit of riding for time and I tried to simply have fun with it. Sure, it took me a lot longer than last year, but this year I didn't want to sell my bike when I was done...
2015 El Tour de Tucson
A year has passed since my last adventure riding in the El Tour de Tucson, so it was time for this year's ride. 2015 marked the 33rd anniversary of this annual event, and once again I signed up to ride the full 104 miles. If I was going to subtitle this years ride, I would call it "The Ride Which Almost Wasn't," but I'll explain what I mean by that a little later.
This year there were a couple of big differences from my ride last year, the biggest of which was that I rode with my friend Kevin, with whom I had recently ridden the 100-mile Cool Breeze Century. Kevin and I had been discussing the ride over the past few weeks, and I have been riding with a different philosophy - ride to have fun.
This may sound strange, but for the longest time I had been hating my rides. Seriously - I hated all of them. Of course, that is an untenable situation for someone who wants to be a recreational cyclist, so I had to figure out what was wrong with the way that I was riding. After some self-examination, I determined that my problem was simply that I was always racing the clock on each ride, and I was always trying to outdo my previous time. So a couple of months ago I decided to stop racing the clock, and I discovered that I was enjoying [sic] my rides a little more.
With that in mind, Kevin and I agreed to ride at a comfortable pace, and to stop for more of the Support and Gear (SAG) stops along the way. That being said, the El Tour de Tucson is an extremely well-supported ride with SAG stops every 5 or 6 miles, so we had plenty of opportunities to rest and refuel.
One of the bright spots about this year's weather was that it promised to be warmer than last year, which was literally freezing before the race started.
The 104-mile race starts at 7:00am, but seeing as how neither Kevin nor I wanted to race the clock, we agreed to meet at the starting point at 6:15am. (That was a whole lot better than last year when I got in line around 5:00am.) I woke up early, double-checked my pre-race cycling checklist, packed the last of my gear into the car, and headed across town to meet Kevin. As I drove across town I could see that the weather seemed to be pretty close to predictions, which meant that I wasn't going to freeze this year. (That was great news.)
I made it across town in short order, and I pulled into the parking lot at the Tucson Convention Center (TCC) shortly after 6:00am. TCC is near the starting line and has ample parking for lots of participants, so several cyclists were getting their gear ready as I parked and started to prep my gear for the day. I had loaded all of my equipment onto my bicycle, and as I was putting on the last of my cycling clothing I made a horrific discovery: I was missing my cycling helmet. (This is why I referred to this day's race as "The Ride Which Almost Wasn't.")
Wearing a helmet is always a good idea, but in this specific instance it was imperative; the race mandates that all riders wear a helmet in order to participate. I mulled over my options, and I did a quick estimate to determine how long it would take me to drive home, pick up my helmet, and drive back. I might have been able to get home and back by the 7:00am start time, but as I was deliberating what to do, Kevin called me. I explained the situation, and after he had a good laugh at my expense, Kevin said that he could wait for me to get back before starting. I mentioned that the timing chips on our race placards do not start until we physically cross the start line, so starting a few minutes late might not be that big of a deal.
However, as the two of us talked, I saw that Kathleen was trying to call me, so I put Kevin on hold and answered Kathleen's incoming call. She found my helmet lying on the counter, and she was asking if she should bring it to me. Thankfully Kathleen already needed to be on that side of Tucson around 7:00am, so the two of us set up a place to meet somewhere near the start line. Once Kathleen and I hung up, I switched back to my call with Kevin, and I explained the arrangements to him. Kevin said that he would wait for me near the start line for me, then I locked up my car and pedaled over to Kevin's location.
After Kevin and I met, the two of us rode over to the place where Kathleen and I had agreed to meet, and she arrived around 6:40am. She quickly handed off my helmet, (see the following photo), then Kathleen headed off to her appointment while Kevin and I got in line for the race. (Note: I'm wearing a lot of cold weather gear in the following photo, but as the day grew warmer I slowly removed all of my cold weather gear.)
It was already 6:45am by the time that Kevin and I got in line, so we were understandably pretty far in the back. But still, neither Kevin nor I wanted to race, so our place in line meant little to either of us.
An unintended bonus from my earlier debacle meant that Kevin and I didn't have long to wait when we got back in line. (Which was a good thing since the temperature had dropped to 39 degrees.) After everyone had sung the National Anthem and a few kind words were spoken by the event dignitaries, the ride officially began at 7:00am. It took several minutes for the back of the line to start moving, but once we began to roll everything progressed in an orderly fashion, and we were on our way.
Here's a time-lapse video from the Arizona Daily Star of the race start; Kevin and I are in there somewhere... (We're on the far side of the street at 1:13, but good luck finding us!)
A little over a half-hour into the ride we hit our first adventure of the day - crossing the Santa Cruz River, which was thankfully dry this year. Nevertheless, it's always amusing to see hundreds of cyclists hand-carrying their bicycles across the dry riverbed. Although one of the best parts of this experience it is always the Mariachi band on the far side of the river.
Kevin and I rode through southeast Tucson along with the thousands of other cyclists who were participating in the 104-mile course, and yet we were able to ride close enough together to carry on a conversation as pedaled our way through the first several miles of the race. We met a lot of interesting people along the way, too. One of my favorites was a nice guy from the FBI who was riding his first century ride; we met up with him on the Houghton Road climb and East Escalante Road, (which are the last parts of a difficult climb to the highest point of elevation and we dropped him).
Thankfully I train on the east side of town all the time, so I ride Houghton Road and East Escalante Road several times a year. Another great part about hitting the highest point of the ride is that we get to ride downhill for several miles on Freeman Road.
About 3½ hours into our trek we reached the half-way point of the ride, which is also the second river crossing. We also took this as an opportunity for a short break, so we rested up, refilled our water bottles, and ate a few snacks. After that, we were back on our bicycles.
The next obstacle on our ride was the steepest climb of the day - East Snyder Road near North Rockcliff Road. Although it's the steepest part of the course, it is also thankfully one of the shortest climbs - perhaps only 200 meters or so. (But still, every year dozens of riders have to walk their bicycles up the hill. Neither Kevin nor me, though. Hehe.)
There's not much to say about the next couple hours of riding; we took advantage of a few rest stops, one of which was serving Eegee's frozen drinks. (Those were totally worth stopping for.) Once again - I hated the ride up La Cañada Drive, though.
When we were around 10 miles or so from the end, Kevin asked me how close we were to my time from last year, to which I replied, "Last year I had already finished the ride an hour and a half ago." (That seemed somewhat demoralizing for Kevin.) Nevertheless after 8¼ hours we rode across the finish line, and my second El Tour de Tucson was over.
| || |
|Kevin and I riding towards the finish line. |
- Primary Statistics:
- Start Time: 7:02am
- Distance: 104 miles (103.5 miles on my GPS)
- Duration: 8 hours, 17 minutes (6 hours, 58 minutes on my GPS)
- Calories Burned: 3,502 kcal
- Altitude Gain: 3,209 feet
- Average Speed: 14.8 mph
- Peak Speed: 31.8 mph
- Average Cadence: 78.0 rpm
- Average: 65.6 F
- Minimum: 35.6 F
- Maximum: 95.0 F
- Heart Rate:
- Average: 143 bpm
- Maximum: 175 bpm
When I arrived home, I posted the following synopsis to Facebook: "How I spent my Saturday - riding 104 miles around the city of Tucson with 9,000 other people from around the world. This year I abandoned my usual habit of riding for time and I tried to simply have fun with it. Sure, it took me a lot longer than last year, but this year I didn't want to sell my bike when I was done... "
UPDATE: A few months after the ride, one of our local television stations put together the following video. There's a bit too much advertising from several of the corporate sponsors, but apart from that it gives a good overview of the event.
My friend and fellow cycling enthusiast Keith shared the following security camera footage from the good folks at Woodinville Bicycle which captures the hilarious antics of a would-be thief attempting to steal a bicycle... I think we have a future Darwin Award recipient in the making.