Training Log Archive: coadyIn the 1 days ending Jun 9, 2013:
| ||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||
| |||||||
| Su |
Sunday Jun 9, 2013 #
10 AM
Orienteering race (QBIII - long) 1:32:26 [5] 12.3 km (7:31 / km) +230m 6:52 / km
ahr:154 max:172 shoes: Inov-8 Mudclaw 333
splits indicate I lost time at
3 (ran past the second clearing - they seemed to join then over corrected and didn't see the control on the first pass. relocated to track when I realised I had gone too far)
5 (took the right side of the cliff, it looked yellow but I climbed an extra 2 contours, left would have been better, went past the control location but didn't see it, a case where it was more visible further from the control as it didn't occur to me to look 5m above)
7 (was searching for control but then it occurred to me that it was on the bare rock, and I was not searching the rock .. has some people near me from 6 which may have distracted me)
11 (took the track, no mistake, but perhaps could have hit the control in a more direct line in the last bit.)
15 (started to go N but saw a decent "track" to get me out of the fallen timber, so took the left track option which was slow, no nav error but i guess it would have been quicker going N from the control rather than W)
was happy with run apart from #3, a few people within 5 mins but way down on the standings
RouteGadget
3 (ran past the second clearing - they seemed to join then over corrected and didn't see the control on the first pass. relocated to track when I realised I had gone too far)
5 (took the right side of the cliff, it looked yellow but I climbed an extra 2 contours, left would have been better, went past the control location but didn't see it, a case where it was more visible further from the control as it didn't occur to me to look 5m above)
7 (was searching for control but then it occurred to me that it was on the bare rock, and I was not searching the rock .. has some people near me from 6 which may have distracted me)
11 (took the track, no mistake, but perhaps could have hit the control in a more direct line in the last bit.)
15 (started to go N but saw a decent "track" to get me out of the fallen timber, so took the left track option which was slow, no nav error but i guess it would have been quicker going N from the control rather than W)
was happy with run apart from #3, a few people within 5 mins but way down on the standings
RouteGadget