The maps given out for the race. |
On the other hand I didn't have a lot of expectations of my finish result, I was looking at this as a learning experience, and it lived up to its bill... I had no qualms about my 4th place finish, and will certainly analzye my performance for shortcomings and mistakes. With the bike I had, I have my doubts that I would been able to finish the course, but I think I could have collected around 30 punches. Being effective finding the punches is where I lost my most time, and this is the area I will focus my analysis on.
1. Not minding the clues. The 13th checkpoint was not a punch, but a 'tag' and that was literal, as it was a piece of graffiti in one of the river tunnels underneath the railroad tracks. This was mentioned in the pre-race briefing, and explicit in the clue, but I was in the mind set of finding the marker/punch, and by the time I remembered to look at the clues I felt I had spent enough time, and after a brief search, moved on to the next station. Checking the map and clue before searching for each checkpoint makes a difference.
2. Not using map cues. Two more points I had trouble with were 25 and 26. 25 ended up being an easy one, but I didn't think to look along the power lines (clearly marked in the map), and spent quite a bit of time looking fruitlessly before moving on (found 25 on the way back to Plymouth). I spent some time looking for 26, and at my initial vantage point knew it was a river crossing, but not liking that idea. After moving on to 27, realized that 26 could be accessed on the trail leading west from point 27.
3. Not using the maps to regulate flow. Related to the 25 & 26 error was where I went from CP 24. If I had stayed on the south side of the river from 24, would have easly gone to 26 and then 27, and picked up 25 on the way back, which is what I did anyway. I ended up missing CP 28, but if I had stayed on the south side/gravel road, I would gotten the punch, with less time spent.
4. My GPS device got dislodged from the wrist strap. I noticed it at CP 17, so went back to CP 16 to look for it. I did find it, but that also cost me some time.
My Kenda SB8 kept me rolling. |
Beyond these mistakes, I did have the advantage of being pretty familiar with Hines, and after studying the map and checkpoints, I decided to head south initially, and hope I had enough time to get some of the checkpoints north of the start. Considering the trouble I had finding the checkpoints, seems like developing a strategy to find them is one of the most important aspects to plan (that is, have some sort of formal process to expand the search area. I would often go over areas I had been through before).
Overall I really enjoyed myself, and (most of the time) liked the exploration aspect of the race. Definitely saw some areas of Hines I have never explored, and got in a mile or two of actual trail riding. The other racers that I encountered were generally pretty cool, and the race was conducted with a clear set of rules and in a timely fashion. I had been hoping to ride to the start, but the weather and deciding to swap out my rear tire had me driving over.
Definitely a bit muddy in some of the areas. |
This was the second annual race, so I hope to attend the third annual next year and find some improvements, and get a few extra miles riding to the start. If you live in the SE MI area and want to try out something a bit different from the usual 'hammer out the trail' race, consider this one.
No comments:
Post a Comment