The first section was billed at the briefing as straightforward to get us out and away from Coldstream, and simple tulips saw us arriving at TC1.

Derek used his tried and tested method for providing the crews with at least half of the route instructions at the start. A lot of information given on A4 handouts, not all to be used, but all to be considered when plotting a route.

The first problem is that, until I got home, I had not seen that the TC locations were given at the end of the instructions for MTC0 to MTC9.  In intermediate class we were promised with being given half of the TC locations however when the event is underway it is easy to forget such basic things. James asked as we waited outside TC1 if there was anything we could be plotting, I should have scoured our instruction sheets or timecards to find the given TC locations, but my mind was already set on getting the decode for the next clue and the upcoming sections. From then on we therefore had to plot the whole event blind (without knowing where the TC that the next clue would lead to). Why make life easy for yourself?

The following five sections we managed between us to solve and plot correctly, some clues were time consuming and needed the full attention of both driver and navigator to plot, however we arrived at TC6 dropping no codes but dropping 6 minutes due to the extra time required plotting.

Section 7, however was to be one to forget for us. I had marked the preceeding TC location on the map as we arrived and the decode key referred to a clock face type of clue which we had both seen before. We eagerly read the various times, arriving at a junction on the hour and leaving on the minute however after an obvious string of missing slots the clue didn’t seem to work any more (due to not seeing a small white at 80703215). We appeared to have a choice of two routes so we made a decision to try both in the least time consuming way, both incidentally were completely wrong to the section. We set off on the first loop, didn’t see a code so decided to turn and travel up the second yellow, possibly against rally traffic (or so we assumed). After a short distance we saw a code, unexpectedly facing in our direction, we immediately knew that our assumption of the route was wrong. We recorded the code but were then passed by another competitor and so decided to follow them until the TC knowing that we possible had missed a code. What we hadn’t accounted for was that the next TC was TC8, we had missed out most of section 7 and half of section 8 but more importantly we had missed TC7. We were heavily penalised, 15 minutes for a dropped code and 30 minutes for not visiting the TC.

We arrived into the re-group still unable to solve the clock face, knowing we were out of contention for a respectable place in class, hoping for a miracle that the section would be scrubbed (it wasn’t the clue works perfectly well if you spotted the white!). We were still in the rally though and were more determined to have a good second half.
 
The second half saw again tricky clue solving which required both of our brains but no missed codes until section 16 saw us only dropping 3 minutes. We had relied on some very inspired guesswork, or was it skill, in some sections to keep us on route until this point?

Section 16 had a well-hidden code in a not so obviously white lay-by (73954560), but everyone in class missed it also so not an overly detrimental effect to our run in.

The last section, section 17 had been promised as a regularity section with timing to the minute. We were told another herringbone was required, the third of the event (Derek knows I don’t like herringbones!) which appeared to have 4 points, A to D inscribed along it’s length. In the comfort, warmth and tranquillity of my living room it plots quite straightforwardly, however in a rally car after nearly 3 hours of competing it didn’t appear to fit. We wrongly assumed that the points referred to spot heights (possibly led by earlier clues that did) and so we were defeated at the last, after many minutes of deliberation and idea swapping.

A desperation tactic was employed when a historic vehicle (David Thomson's Sunbeam) passed us and we decided to follow. Historic entries normally have novice type clues and often coupled with very able navigators normally follow a correct route, so are a great aid at times like these. However, I had a NAM triangle plotted, and as we slowed to follow the longest route, David went straight on. We picked up the code but had lost our tail but then a second guardian angel manifested itself as a motor vehicle from days gone by (Stuart Bankier in the Volvo Amazon), went round the triangle, and so we followed him until finish. David’s Sunbeam actually came back as we headed off, and we joked at the finish that they had returned to look for their lost buddy.
 
We were at the finish though, in one piece, still speaking to each other and so an altogether not bad event.

I know hindsight is a great thing but if we'd managed to solved the clock face clue, we would have ended the first half, third in class on 6 minutes and a much improved 2nd half with 24 minutes would have put us a respective 2nd in class (we actually ended 2nd last in class and 9th overall). In the end we were just happy we didn't come last.
 
I personally had a most enjoyable event and am looking forward to the Williamson 100 to gain more experience navigating. I obviously have still a lot to learn but am having fun in the classroom/passenger seat.
 
Cheers again James for the drive.
 

Back to Top

Updated 26 November 2005
Webmaster - Jim Paterson