Split Analysis
NOY6 - Balickera Quarry: Moderate Long
alsoCass
median leg score: 81.4
calculated time lost: 8:33 (+25.4%)
| split | cumulative total | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| # | dist | time | place | delta | score | lost* | pace | dist | time | place | delta | pace | comments | |||||||||||||||||||||
| 1. | 362m | 11:44 | 8 | +8:44 | 291% | 38.9 | 6:08 | 6:08 | 32:24 | 362m | 11:44 | 8 | +8:44 | 291% | 32:24 | Plan was to take a bearing. My bearing drifted a little high and I ended up in sight of a track. Decided to use the track to confirm my position and things went downhill from there - I misidentified the track that I was on, I left the track toward the control but grew concerned by the lack of a watercourse. The watercourse was missing because I was in the wrong spot, but this mistake caused issues for the rest of the course as I doubted the water features on the map. Eventually I noticed the large mounds that I was doing laps around and spotted them on my map - I was really confused about why I hadn't noticed them, and it wasn't until after I had finished that I pieced together my mistake. | ||||||||||||||||||
| 2. | 66m | 48 | 3 | +10 | 26% | 90.3 | 12:07 | 428m | 12:32 | 7 | +8:19 | 197% | 29:17 | Followed the watercourse to the control, (the creek was the catching feature, but didn't need it). | ||||||||||||||||||||
| 3. | 399m | 7:00 | 6 | +3:10 | 83% | 64.0 | 1:29 | 1:29 | 17:32 | 827m | 19:32 | 7 | +10:39 | 120% | 23:37 | This was a yucky leg. I didn't really pay any attention to the features of the map - except for the creek and the two crossings). My plan was okay - cross the creek and then follow it run until I hit the other creek, then look for the control. I didn't really run much as the trees made it difficult (lots of ducking and dodging). In hindsight I probably should have run a little further up the hill (30 paces) and then headed back to the second creek, then south to the control. A lot less exact, but probably faster running. Or avoiding the first creek entirely, running straight to the track and then up to the control. I really didn't enjoy this leg, but stepping back I think that was just because I made a poor route choice. | ||||||||||||||||||
| 4. | 174m | 1:55 | 5 | +33 | 40% | 81.4 | 11:00 | 1001m | 21:27 | 7 | +10:56 | 104% | 21:25 | Ran to the road, counted 60 paces and headed back to the creek, found the control straight away. | ||||||||||||||||||||
| 5. | 168m | 1:53 | 2 | +12 | 12% | 100.3 | 11:12 | 1169m | 23:20 | 5 | +11:08 | 91% | 19:57 | I had no picture of the route. Just planned to follow the watercourse. I was a few metres from the control when I head a pair (working together) say "there is the fence", and I felt a bit silly that I hadn't even noticed the fence on the map. I found the control easily, but never seem to see everything on the map. | ||||||||||||||||||||
| 6. | 301m | 3:21 | 5 | +38 | 23% | 84.6 | 11:07 | 1470m | 26:41 | 5 | +11:16 | 73% | 18:09 | Ran directly to the road, I could have gone on a more eastern bearing but I always end up spending a great deal of time running alongside a handrail when I do that - wasting time trying to figure out where I am. So straight to the track, along the track to the corner, cut the corner to the control. | ||||||||||||||||||||
| 7. | 127m | 1:36 | 3 | +35 | 57% | 79.2 | 12:35 | 1597m | 28:17 | 5 | +11:41 | 70% | 17:42 | This was a nice leg, but my bearing was off, thankfully the watercourse was easy to identify, I stopped at the watercourse, figured out where I was and it was quick up to the control. | ||||||||||||||||||||
| 8. | 458m | 3:54 | 2 | +36 | 18% | 96.9 | 8:30 | 2055m | 32:11 | 5 | +10:36 | 49% | 15:39 | Long legs on tracks aren't fun. There was no route choice at all... just get on the track and run for a while until the track splits, then run to the control. I still managed to go a bit off on the bearing... need to work on that. | ||||||||||||||||||||
| 9. | 100m | 59 | 3 | +13 | 28% | 87.6 | 9:50 | 2155m | 33:10 | 5 | +10:49 | 48% | 15:23 | Took a bearing, the watercourse ensured I wouldn't go to far. The control was obscured by a conveniently fallen branch. | ||||||||||||||||||||
| 10. | 116m | 1:41 | 5 | +26 | 35% | 77.6 | 14:30 | 2271m | 34:51 | 5 | +11:00 | 46% | 15:20 | Another control following the watercourse - a bit hard to get lost on this one. | ||||||||||||||||||||
| 11. | 113m | 2:22 | 8 | +1:29 | 168% | 48.8 | 56 | 56 | 20:56 | 2384m | 37:13 | 5 | +12:15 | 49% | 15:36 | Simple plan, poor execution. Get on the road until I come to the watercourse, I vageuly noticed a circle on the map but ignored it and ran. This is when my mistake at control 1 came back to bite me - I was convinced that a water feature on the map wasn't necessarily distinct on the ground - so I turned too early. Took me a bit to convince myself to head back to the road and to look for whatever that circle might be. Spotted the feature (a cement marker) and the water course, but wasted a minute. | ||||||||||||||||||
| 12. | 161m | 1:57 | 4 | +19 | 19% | 87.5 | 12:06 | 2545m | 39:10 | 5 | +12:32 | 47% | 15:23 | The watercourse was a convenient catching feature, ran to it and found the control. | ||||||||||||||||||||
| 13. | 242m | 2:26 | 4 | +15 | 11% | 91.8 | 10:03 | 2787m | 41:36 | 4 | +12:43 | 44% | 14:55 | Routegadget does me a disservice on this control, and doesn't reflect what actually happened at all. I ran to the road, arrived at the junction, ran along the road (counted pages) then turned off to the control. Found it easily. | ||||||||||||||||||||
| 14. | 97m | 35 | 6 | +12 | 52% | 67.6 | 6:00 | 2884m | 42:11 | 4 | +12:55 | 44% | 14:37 | I nearly took off running in the wrong direction because I assumed the road would take me to the finish - lucky I checked! | ||||||||||||||||||||
* red = reported, gray = calculated