How to pass your land nav course: a system, not talent

Land navigation fails more candidates than any other field event, and it fails them for the same reason every time: they treat it as a sense of direction, when it's actually a checklist executed under fatigue. Nobody is born knowing where north is. The people who find every point are running a system — plot carefully, plan the route, count paces, trust the compass, cross-check with terrain. All of it is learnable, and most of it is learnable before you ever set foot on the course.

Before the course: three things to own cold

1. Your pace count

Measure a 100-meter line and walk it, counting every time your left foot strikes the ground. Do it five times and average. Most people land between 60 and 70 paces per 100 m. Now do it again with a ruck, again uphill, again through brush, again at night — your count grows with difficulty, sometimes by ten paces or more, and knowing your numbers for your conditions is the difference between arriving at the point and arriving 80 m short of it. In the field, track hundreds with pace beads, pebbles moved between pockets, or knots on a cord — never memory.

2. The map, as a language

Contour lines are the whole game. Learn the five major terrain features — hill, ridge, valley, saddle, depression — and the minors (draw, spur, cliff) until you can look at the brown lines and see the shape without thinking. Check the contour interval on every new map sheet. Practice folding the map to your area of operations and orienting it to the ground: map north to compass north, terrain features aligned with what you see. A map you have to rotate mentally is a map that will lie to you when you're tired.

3. Grid coordinates without hesitation

You should be able to plot an 8-digit grid with a protractor in under a minute, twice, getting the same answer both times. If MGRS itself is still shaky — which part is the easting, why you truncate instead of round — fix that first: our 5-minute MGRS guide covers the system from scratch. Read right, then up. Every land nav horror story that starts "I was 2 km from where I should have been" is a plotting error that took ten seconds to make.

At the map table: the ten minutes that decide everything

When you get your points, resist the urge to move. The map table is where courses are passed.

1. Plot every point twice. Plot, lift the protractor, plot again. If the two marks disagree, find out why now — not 3 km from now.
2. Plan legs, not lines. For each leg write azimuth and distance in a route card. The straight line is rarely the fast line: a 200 m detour along a trail beats 150 m through a draw full of wait-a-minute vines.
3. Pick an attack point for every target. Navigate confidently to something big and unmissable near the point — a trail junction, a stream bend, a saddle — then run a short, careful compass leg from there. Precision over the last 300 m beats precision over 3 km.
4. Choose catching features. For each leg, know the feature beyond your target that tells you you've gone too far: a road, a creek, a ridgeline. When you hit the catching feature, you stop and turn around — no debate.
5. Aim off on purpose. Navigating to a point on a linear feature? Deliberately aim 50–100 m to one known side. When you hit the trail or stream, you know which way to turn — instead of guessing wrong half the time.

On the course: the discipline part

• The compass doesn't have opinions. When your gut says left and the needle says right, the needle wins. Every experienced navigator has a story about the time they "corrected" a working azimuth. Hold the compass level, follow the direction of travel arrow, and pick successive steering marks — a distinctive tree on your azimuth, walk to it, repeat.
• Detours cost paces. Boxing around an obstacle? 90° turn, count paces, parallel your azimuth, 90° back, and subtract nothing from your leg count until you're back on line. Sloppy detour accounting is silent death — you arrive "on distance" while being 200 m short.
• Cross-check with terrain. Pace count says 700 m and you should be crossing a stream — is there a stream? Terrain association and dead reckoning check each other; when they disagree, stop and resolve it.
• The lost protocol. The moment you suspect you're off: stop. Don't wander "just a bit further." Orient the map, find the last feature you positively identified, and if needed walk back to it. Losing ten minutes backtracking beats losing an hour spiraling.
• Navigate alone, even in a crowd. On group courses, the herd drifts toward whoever walks most confidently — who is often wrong. Run your own plot, your own azimuth, your own count. "Following the guy who looked sure" has failed more candidates than bad plotting.

Night land nav: same system, tighter tolerances

Everything above still applies — you just can't see. Compensate deliberately: shorter legs between bigger, more unmissable attack points; more reliance on pace count and less on terrain you can't see; red light only, and sparingly, because every white flash costs you half an hour of night vision. Distances feel longer and slopes feel steeper in the dark — trust the count, not the feeling. If your course allows a buddy, one navigates, one counts.

The five classic failures

1. Plotting error at the table — wrong by 100 m before taking a step.
2. Swapped easting and northing — wrong by kilometers. Read right, then up.
3. Pace count abandoned mid-leg — "it felt like 600 meters." It wasn't.
4. Refusing to backtrack — turning a 200 m error into a 2 km one.
5. Following the crowd — outsourcing your navigation to a stranger's confidence.

A two-week practice plan

You don't need a training area to build most of this skill:

• Days 1–3: pace count on a measured 100 m, all conditions you can manage. Learn your numbers.
• Days 4–7: map work, 20 minutes a day. Plot grids, read terrain features along imagined routes, quiz yourself: "what would I see walking this leg?"
• Week 2: put it together outdoors — a park or forest works. Plot three or four points, plan legs with attack points and catching features, walk them by compass and pace count, and only then check how close you landed.