Training Log Archive: SnailtrailIn the 7 days ending Mar 26, 2016:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||||||||
| |||||||||||||
| Su | Mo | Tu | We | Th | Fr | Sa | |||||||
Sunday Mar 20, 2016 #
Event: Raccoongaine
10 AM
Rogaine race (Raccoongaine) 6:21:00 [4] *** 28.79 km (13:14 / km) +809m 11:36 / km
weight:155lbs shoes: Salomon Speed Cross Pro
28.79Km, 809m elevation gain. However, 21 minutes late. 580 points gross, 370 after penalty.
Hugest mistakes on CTRLs 103 and 147, resulting from getting sucked into other teams' errant ways.
On 103, after a strong run on the road from the start, I thought I'll just wing it by looking where others in front of me went, so why bother check the map, right? wrong! I completely bobbled that and Instead of nabbing it in ~6', took a whopping 24' of running around in circles.
On 147, I cut from the ride too early, and then saw a team heading down from the top. Assuming they would have passed the control on their way down, I wrongly followed them south, hit the trail, came back, then back again, ran east, picked the indistinct trail north almost to the park boundary, from which I actually saw the control ~75m on the west. That ctrl took 45 minutes from the previous one!!! Could have saved myself from that by just sticking to my own navigation.
Minor errors:
(i) Could not find the spur approaching 132 from the trail right away, wasted some time there;
(ii) after 132, I thought I'll go to 142, headed all the way down to the creek, saw the mess on the ground, looked at the watch and decided it was too out of the way for my time. That cost me climbing all that spur back up;
(iii) After 114, thought I'll run to 130 before crossing to the east of the road. The mistake was wasting time trying to see if the stream is crossable, only to have to head back and run around to pick the control;
(iv) 135 was tricky from the north. I took a direct bearing from the trail on the north, and on reaching the approximate pace count could not see the control and veered west, only to see the deep reentrant. I used the cliffs for direct bearing back to the control, but time was lost;
(v) 121 – tried from the other side of the creek only to see a deep stream with strongish current and no obvious crossing point. In hindsight, I should have heeded the course notes and attack from behind, not wasting my time looking at the promised land from across the river;
(vi) After CTRL 138, concluded that it's time to run to finish. On the way picked the easy 124, and then, on the south side of lake, with 55' left, while I should have gone to 127 and 118 and F to cut my losses, I got greedy and underestimated the leftover distance while overestimating my prowess, and chose 120 and 145, which eventually got me 21 minutes late, despite a mad dash (for my fitness level) at an average of 7.5 min/Km for most of the way back, except for the final steep hill just before the finish.
Hugest mistakes on CTRLs 103 and 147, resulting from getting sucked into other teams' errant ways.
On 103, after a strong run on the road from the start, I thought I'll just wing it by looking where others in front of me went, so why bother check the map, right? wrong! I completely bobbled that and Instead of nabbing it in ~6', took a whopping 24' of running around in circles.
On 147, I cut from the ride too early, and then saw a team heading down from the top. Assuming they would have passed the control on their way down, I wrongly followed them south, hit the trail, came back, then back again, ran east, picked the indistinct trail north almost to the park boundary, from which I actually saw the control ~75m on the west. That ctrl took 45 minutes from the previous one!!! Could have saved myself from that by just sticking to my own navigation.
Minor errors:
(i) Could not find the spur approaching 132 from the trail right away, wasted some time there;
(ii) after 132, I thought I'll go to 142, headed all the way down to the creek, saw the mess on the ground, looked at the watch and decided it was too out of the way for my time. That cost me climbing all that spur back up;
(iii) After 114, thought I'll run to 130 before crossing to the east of the road. The mistake was wasting time trying to see if the stream is crossable, only to have to head back and run around to pick the control;
(iv) 135 was tricky from the north. I took a direct bearing from the trail on the north, and on reaching the approximate pace count could not see the control and veered west, only to see the deep reentrant. I used the cliffs for direct bearing back to the control, but time was lost;
(v) 121 – tried from the other side of the creek only to see a deep stream with strongish current and no obvious crossing point. In hindsight, I should have heeded the course notes and attack from behind, not wasting my time looking at the promised land from across the river;
(vi) After CTRL 138, concluded that it's time to run to finish. On the way picked the easy 124, and then, on the south side of lake, with 55' left, while I should have gone to 127 and 118 and F to cut my losses, I got greedy and underestimated the leftover distance while overestimating my prowess, and chose 120 and 145, which eventually got me 21 minutes late, despite a mad dash (for my fitness level) at an average of 7.5 min/Km for most of the way back, except for the final steep hill just before the finish.