Rally Pace Notes are useful codes for a navigator to describe map directions for a driver. Undoubtedly you may have seen some of this watching a video on UTube and either the scrambling of microphone or noise from the drive itself made it hard to understand what is going on. This is the basic scoop, but please- research further -there are two people inside the car, and with a camera secured between both. Both are wearing helmets and you see in front of you wild road winding between hillsides and turning like crazy as see both people severely rattled by the automobiles motion. The is dust, curves, rocks and shifting light from dark shadow to bright glare. If it happens to be raining or even night, the visibility is more compromised. Trying to navigate any rally at any speed other than like 10 mph, can be tricky. If the driver is blindfolded, successfully running a course, that would be the nirvana of rally. In order to pull this off, with eyes wide open of course, is that navigators have devise a “how to steer” code. On cannot assume turns, turn-offs, directional changes, hills, slopes, blind turns, road situations or conditions. This code would then be written into a jargon and a set of directions on a notepad with a time clock, all spelled out by the navigator.
So you might be able to see that over a period of time you might be able to correlate your expected location to your clock and your notes. Since all notes are pretty much individual to the navigator, the essence of the notes should be universal in description for any rally person to understand. Both the clock and and notes should be visible to the navigator. The clock might be fastened in front of the glove box while a notepad might be cable fastened near the navigator. It might be unfortunate should the notepad fly out of the hands of the navigator. One might also think to have lighting to the notepad, and not glare to the driver. Pages to the notepad might be durable enough to allow for tearing or moisture. It could be also last minute changes need to be noted.
The real key is then being able to describe to the driver, either by shouting or since you are probably wearing helmets, though a piped speaker / headset the directions. The driver will likely be concentrating on acceleration, braking and turnings. His job balanced by smoothly negociating the car on the road. It is not always going to be obvious on unfamiliar roadway or dirt route up ahead. At times, the navigators quick thinking will heads up what will be the next move.
There are standard ways to describe the angles… as in (1) is straight and (4) might mean 40 degrees, while (9) would be 90 degrees. If you said (hairpin) it means you are cutting beyond 90 degrees and the driver might have enough time to cut beyond the 90 degrees; which any of these informations should tell the driver to set himself up on the road to take that degree of turn. All you then need to make sure is if you and your driver have LEFT and RIGHT down perfectly. Lastly a distance expection would be described, such as “500-9-right” would mean 500 feet with a right turn.
The other great standard way in describing turns is the number system based on severity. The lower the number… the more severe. If you said (1), then, without any doubt you will mean hairpin. (2) might be a hairpin..but not as severe as one. Most turns will be (3) while slight turns will be a (4), (5) or (6). Some more advanced levels of describing map to driver would be the following.
FLAT L – Flat turns to either direction – FLAT R
Then distance would be describe fully visualize vocal distances. If a hill up or down be expected the navigator could in essence verbal it with a standard code.