Practical Land Navigation

The Five Ds

Successful land navigation requires mastering:

D	Description
Distance	How far to travel (pace count, odometer, timing)
Direction	Compass bearing or azimuth
Designation	Target point identification (grid, landmark)
Description	Terrain features along route
Danger	Obstacles, hazards, no-go areas

Description

Distance

How far to travel (pace count, odometer, timing)

Direction

Compass bearing or azimuth

Designation

Target point identification (grid, landmark)

Description

Terrain features along route

Danger

Obstacles, hazards, no-go areas

Map Reading Fundamentals

Map Colors

Color	Represents
Black	Man-made features (buildings, roads, boundaries)
Blue	Water (streams, lakes, swamps)
Brown	Contour lines (elevation), some roads
Green	Vegetation (forests, orchards)
Red/Pink	Major roads, built-up areas
White	Open/cleared areas

Color

Represents

Black

Man-made features (buildings, roads, boundaries)

Blue

Water (streams, lakes, swamps)

Brown

Contour lines (elevation), some roads

Green

Vegetation (forests, orchards)

Red/Pink

Major roads, built-up areas

White

Open/cleared areas

Contour Lines

Contour interval: Elevation change between lines (check map legend)
Index contours: Every 5th line, thicker, labeled with elevation
Closely spaced: Steep terrain
Widely spaced: Gentle slope

Contour Features

  Ridge:       V points DOWNHILL         Valley:      V points UPHILL
               (away from peak)                       (toward peak)

    ╱──╲                                   ╲──╱
   ╱ ╱──╲ ╲                              ╱ ╲──╱ ╲
  ╱ ╱ ╱──╲ ╲ ╲                          ╱ ╱ ╲──╱ ╲ ╲
  high     V → downhill                  low    V → uphill


  Saddle:     Hourglass between           Depression:  Closed contours
              two peaks                                with tick marks
                                                       pointing INWARD
   ╱──╲     ╱──╲
  ╱    ╲   ╱    ╲                           ╱──────╲
  ╲    ╱   ╲    ╱                          │  ┤──├  │
   ╲──╱     ╲──╱                            ╲──────╱
     Pass between peaks                     tick marks → lower center


  Cliff:     Contours merge              Steep slope vs Gentle slope
             (nearly touching)
                                          ║║║║║║  vs  ─  ─  ─  ─  ─
  ─────════════─────                      steep         gentle
     ↑ cliff face ↑                       (close)       (far apart)

Slope Estimation from Contour Spacing

\[\text{Slope angle} = \arctan\left(\frac{\text{Contour Interval} \times n_{\text{lines}}}{\text{Horizontal distance}}\right)\]

Example: 5 contour lines in 2cm on a 1:24,000 map (40ft interval)

\[\text{Elevation change} = 5 \times 40 = 200\text{ ft} = 61\text{ m} \\ \text{Horizontal distance} = 2\text{ cm} \times 240\text{ m/cm} = 480\text{ m} \\ \alpha = \arctan\left(\frac{61}{480}\right) = \arctan(0.127) \approx 7.2°\]

A 7° slope is moderate hiking terrain. Above 30° is scrambling. Above 45° is climbing.

Terrain Association

Match map features to ground features:

Orienting the map: Align map to terrain using compass
Identify major features: Hills, valleys, water
Confirm position: Using multiple features

Reading Map Marginalia

Every USGS topographic map prints critical reference data in its margins. Before navigating, read the margins — they tell you everything you need to interpret the map correctly.

The Two Coordinate Systems

USGS topo maps print two different coordinate systems simultaneously:

System What It Looks Like Purpose

System	What It Looks Like	Purpose
UTM/MGRS Grid	Blue grid lines labeled `3 83 000`, `3 84 000` (meters)	Field navigation with protractor — flat Cartesian math
DMS Lat/Lon	Margin tick marks labeled `118°15'0"`, `34°20'0"` (degrees/minutes/seconds)	GPS interoperability, plotting across map sheets

UTM/MGRS Grid

Blue grid lines labeled 3 83 000, 3 84 000 (meters)

Field navigation with protractor — flat Cartesian math

DMS Lat/Lon

Margin tick marks labeled 118°15'0", 34°20'0" (degrees/minutes/seconds)

GPS interoperability, plotting across map sheets

The grid numbers (e.g., 3 83 000) are UTM Easting in meters — 383,000m from the zone’s false origin. Each grid square on a 1:50,000 map represents 1,000m × 1,000m (1km).

The DMS ticks (e.g., 118°15'0") are longitude in degrees, minutes, seconds — an angular measurement where ° = degrees, ' = arcminutes (1/60th of a degree), " = arcseconds (1/60th of a minute).

DMS to Decimal Conversion

\[\text{Decimal Degrees} = d + \frac{m}{60} + \frac{s}{3600}\]

Example: \(118°15'0''\text{W}\)

\[118 + \frac{15}{60} + \frac{0}{3600} = 118.25°\text{W} = -118.25°\]

Linear Distance per Angular Unit (at latitude \(\phi = 34°\text{N}\))

\[1° \text{ latitude} \approx 111{,}132 \text{ m} \quad \text{(constant)} \\ 1° \text{ longitude} \approx 111{,}132 \times \cos(\phi) = 111{,}132 \times \cos(34°) \approx 92{,}117 \text{ m} \\ 1' \text{ latitude} \approx 1{,}852 \text{ m} \quad | \quad 1'' \text{ latitude} \approx 30.9 \text{ m}\]

Declination Diagram

The bottom margin shows three norths and their angular relationships:

              TN   GN
               |  ╱
               | ╱ γ (grid convergence ≈ 1°)
               |╱
              ╱|
            ╱  |
      δ   ╱   |   δ = magnetic declination = 12°E
        ╱     |   γ = grid convergence ≈ 1°E
      ╱       |   G-M = δ - γ ≈ 11°
   MN         |

   TN = True North     — geographic pole (rotation axis)
   GN = Grid North     — UTM grid vertical (≠ TN except on central meridian)
   MN = Magnetic North — where compass needle points

Declination Conversion Formulas

\[\theta_{\text{true}} = \theta_{\text{magnetic}} + \delta \\ \theta_{\text{magnetic}} = \theta_{\text{grid}} - \text{G-M Angle}\]

Where \(\delta\) = magnetic declination (positive East, negative West) and G-M Angle = \(\delta - \gamma\).

Example: Sunland/Condor Peak, CA (December 2024)

\[\delta = +12° \quad \text{(East declination)} \\ \gamma \approx +1° \quad \text{(grid convergence, East of TN)} \\ \text{G-M Angle} = 12° - 1° = 11°\]

Practical Impact: Lateral Error from Uncorrected Declination

\[\text{Lateral Error} = d \times \tan(\delta)\]

At 1,000m with 12° uncorrected declination:

\[\text{Error} = 1{,}000 \times \tan(12°) = 1{,}000 \times 0.2126 \approx 213 \text{ m}\]

That’s over two football fields off target per kilometer. At night in mountains, 213m is the difference between the trail and a cliff.

See Magnetics for declination correction formulas and compass adjustment procedures.

Scale Bar and Representative Fraction

          1:50,000 Scale Bar

miles: |----|----|----|----|----| 1.0
       0   0.2  0.4  0.6  0.8

   km: |----|----|----|----|----| 1.0
       0   0.2  0.4  0.6  0.8

The representative fraction (RF) defines the ratio of map distance to ground distance:

\[\text{RF} = \frac{1}{S} \implies d_{\text{ground}} = d_{\text{map}} \times S\]

Where \(S\) = scale denominator.

Table 1. Scale Conversion Table
Scale	1 cm =	1 inch =	1km grid square =
1:24,000	240m	667 yd (0.38 mi)	4.17cm × 4.17cm
1:25,000	250m	694 yd (0.39 mi)	4.0cm × 4.0cm
1:50,000	500m	1,389 yd (0.79 mi)	2.0cm × 2.0cm
1:100,000	1,000m	2,778 yd (1.58 mi)	1.0cm × 1.0cm

Protractor Scale Mismatch Error

\[\text{Error \%} = \left|\frac{S_{\text{protractor}} - S_{\text{map}}}{S_{\text{map}}}\right| \times 100\]

Using 1:25,000 protractor on a 1:24,000 map:

\[\text{Error} = \left|\frac{25{,}000 - 24{,}000}{24{,}000}\right| \times 100 = 4.17\%\]

At an 8-digit grid reading (10m precision): \(10 \times 1.0417 \approx 10.4\text{m}\) — negligible. But at 1,000m traverse: \(1{,}000 \times 0.0417 = 41.7\text{m}\) — enough to miss a trail junction.

UTM Grid Information Block

Printed in the bottom margin:

Universal Transverse Mercator (UTM) Projection
Zone 11
North American Datum of 1983 (NAD83)
1000 Meter UTM / USNG / MGRS Grid
Grid Zone Designation: 11S
100,000-m Squares: LT LU MT MU

This tells you:

Field	Meaning
Zone 11	UTM zone — central meridian at 117°W, covers 120°W to 114°W
NAD83	Horizontal datum — defines the ellipsoid model. NAD83 and WGS84 are practically identical (sub-meter difference). NAD27 maps have 100m+ shift — never mix datums.
1000 Meter Grid	Grid lines are spaced 1,000m apart (the blue lines on the map)
GZD: 11S	Grid Zone Designation — Zone 11, latitude band S (32°N to 40°N)
100,000-m Squares: LT LU MT MU	The 100km square identifiers that appear on this map sheet. These are the two-letter codes in an MGRS coordinate (e.g., 11S MT 8345 5712).

Field

Meaning

Zone 11

UTM zone — central meridian at 117°W, covers 120°W to 114°W

NAD83

Horizontal datum — defines the ellipsoid model. NAD83 and WGS84 are practically identical (sub-meter difference). NAD27 maps have 100m+ shift — never mix datums.

1000 Meter Grid

Grid lines are spaced 1,000m apart (the blue lines on the map)

GZD: 11S

Grid Zone Designation — Zone 11, latitude band S (32°N to 40°N)

100,000-m Squares: LT LU MT MU

The 100km square identifiers that appear on this map sheet. These are the two-letter codes in an MGRS coordinate (e.g., 11S MT 8345 5712).

Index to Adjoining Sheets

The small 16-square grid (4×4) in the margin shows which USGS 7.5-minute quadrangle sheets are combined into this map:

 1  2  3  4
 5  6  7  8
 9 10 11 12
13 14 15 16

Squares with a transparent red outline and dots (bold opaque outer edge) indicate the quad sheets included in your map. On the Sunland/Condor Peak sheet, squares 2, 3, 6, 7, 10, and 11 are highlighted — meaning this map combines 6 adjacent USGS quads.

Each square in the index maps to a date and sheet name in the adjacent table (e.g., Sunland 40ft, Condor Peak 40ft — where "40 ft" is the contour interval of the original source quad).

Contour Interval

Contour Interval: 40 Feet

Every brown contour line represents a 40-foot elevation change. Index contours (every 5th line = every 200 feet) are thicker and labeled with elevation. The contour interval varies by source quad — always check before estimating terrain steepness.

Comparing Map Scales: 1:50,000 vs 1:24,000

The same terrain area may be available at different scales. Know what changes:

Feature	1:50,000	1:24,000
Ground per cm	500m	240m
Grid square on paper	2cm × 2cm	~4.2cm × 4.2cm
Quad sheets combined	6 (index shows 16-square grid)	2 (index shows 6-square grid)
Detail level	Regional overview, route planning	Trail-level detail, terrain association
100km squares shown	More (LT LU MT MU)	Fewer (LT MT)
Protractor match	1:50,000 scale on protractor — exact	1:25,000 scale on protractor — ~4% error (close, not exact)
Best for	Long-distance planning, vehicle nav	Foot movement, night nav, precision work

Feature

1:50,000

1:24,000

Ground per cm

500m

240m

Grid square on paper

2cm × 2cm

~4.2cm × 4.2cm

Quad sheets combined

6 (index shows 16-square grid)

2 (index shows 6-square grid)

Detail level

Regional overview, route planning

Trail-level detail, terrain association

100km squares shown

More (LT LU MT MU)

Fewer (LT MT)

Protractor match

1:50,000 scale on protractor — exact

1:25,000 scale on protractor — ~4% error (close, not exact)

Best for

Long-distance planning, vehicle nav

Foot movement, night nav, precision work

Protractor scale mismatch at 1:24,000. Most military protractors (GTA 5-2-12, Lethalife) have 1:50,000 and 1:25,000 scales but NOT 1:24,000. Using the 1:25,000 scale on a 1:24,000 map introduces ~4% error — at 8-digit precision that’s ~40m. Acceptable for learning, but for precision work use the map’s printed grid tick marks to interpolate manually, or get a 1:24,000-specific protractor.

For tonight’s mountain nav: Use the 1:24,000 map. It has more terrain detail, and at night you need every contour line and trail junction you can get. Accept the 4% protractor error — 40m at 10m precision is still close enough to find your catching features.

Drawing Magnetic North Lines

Drawing MN reference lines on your map eliminates mental declination math during navigation. This is a standard technique taught in FM 3-25.26 and used by competitive orienteers on every map.

When to Draw MN Lines

You’re navigating in the field (not just studying at home)
Your compass does NOT have a declination adjustment screw
You want instant map orientation without mental math
Night navigation — cognitive load is already high, eliminate math

Procedure

Equipment needed:
- Your map (1:24,000 or 1:50,000)
- Protractor or compass with degree markings
- Pencil (light marks — you may erase later)
- Straight edge (ruler, protractor edge, or the compass itself)

Steps:
1. Lay map flat on a hard surface
2. Locate the declination diagram in the margin (12°E for your area)
3. Place protractor at the BOTTOM of the map on any vertical grid line
4. From the grid line, measure 12° EAST (clockwise) and mark a point
5. Using the straight edge, draw a light pencil line from
   the bottom of the map through that point to the top
6. Repeat every 8-10cm (3-4 inches) across the entire map
   — all lines must be PARALLEL
7. Label one line "MN" so you remember what they are

Result:
   GN (grid lines)     MN (pencil lines)
    |                  /
    |                 /
    |    12°         /
    |               /
    |              /
    |             /

Using MN Lines in the Field

To orient the map:
1. Lay map flat (or hold level)
2. Place compass on map with edge along any MN line
3. Rotate map + compass together until needle aligns with MN line
4. Map is now oriented to the terrain — features on map match ground

To take a bearing FROM the map:
1. Orient map using MN lines (above)
2. Place compass edge from your position to your target on the map
3. Rotate bezel until needle aligns with MN lines
4. Read bearing at index line — this IS your magnetic bearing
   (no conversion needed — MN lines already account for declination)

MN lines bypass the declination conversion for MAP-TO-COMPASS work only. If someone gives you a GRID bearing (from a GPS or another map user), you still need to subtract the G-M angle to get the magnetic bearing for your compass.

The Reverse Bearing Trap: Field-to-Map vs Map-to-Field

Declination correction works in two directions, and they are opposite. This is the single most common declination mistake — getting the direction backwards.

The Two Directions

  MAP → FIELD (planning):
    You read a grid bearing from the map.
    You need a magnetic bearing for your compass.

  FIELD → MAP (plotting):
    You shoot a magnetic bearing with your compass.
    You need a grid bearing to plot on the map.

  THE CORRECTIONS ARE OPPOSITE.

Map-to-Field (Planning a Route)

\[\theta_{\text{magnetic}} = \theta_{\text{grid}} - \text{G-M Angle}\]

Example: East declination (your map, 12°E, G-M ≈ 11°)

\[\text{Grid bearing from map} = 090° \implies \theta_{\text{magnetic}} = 090° - 11° = 079°\]

Set 079° on your compass to walk the 090° grid line.

Field-to-Map (Plotting a Bearing You Shot)

\[\theta_{\text{grid}} = \theta_{\text{magnetic}} + \text{G-M Angle}\]

Example: You shoot 079° magnetic to a peak in the field

\[\theta_{\text{grid}} = 079° + 11° = 090°\]

Plot 090° from your position on the map to locate the peak.

The Trap

  If you apply the SAME correction both ways,
  you double the error:

  Map says 090° grid
  You subtract 11° → walk 079° magnetic     ✓ CORRECT

  You shoot 079° magnetic to a peak
  You subtract 11° again → plot 068° grid   ✗ WRONG (22° total error!)
  You should ADD 11° → plot 090° grid       ✓ CORRECT

Memory Aid: "LARS"

  For declination LESS than grid (East declination):

  L - Left on the compass dial (subtract for map→field)
  A - Add for field→map
  R - Right on the compass dial (add for map→field if West decl.)
  S - Subtract for field→map (if West declination)

  Or simply: if you subtracted going OUT, add coming BACK.

John McCann’s approach (recommended): Draw MN lines on the map and skip all this math. When MN lines are drawn, the map IS magnetic. Bearings transfer directly between map and compass in both directions — no correction needed, no reverse trap possible. This is why adjusting the map is superior to adjusting the compass.

Setting Up the Suunto Compass

The Suunto baseplate compass can be pre-set for declination, eliminating the need for MN lines or mental math.

Setting Declination on a Suunto

1. Locate the declination adjustment screw
   — small brass screw on the back of the compass housing
   — some models use a small key or flathead screwdriver

2. Turn the bezel so the orienting arrow points to N (360°/0°)

3. Using the adjustment screw, rotate the orienting arrow:
   — For EAST declination (your case, 12°E):
     Turn screw so orienting arrow moves EAST (clockwise)
     until it sits at 12° east of the N mark
   — For WEST declination:
     Turn screw so orienting arrow moves WEST (counter-clockwise)

4. Verify: with bezel set to 0°, the orienting arrow should now
   point to 348° (360° - 12°) on the internal degree ring

5. Done. Your compass now reads TRUE/GRID bearings directly.
   The needle still points to magnetic north, but the bezel
   compensates automatically.

Check the declination date. Your map says 12°E as of December 3, 2024. Declination changes ~0.1°/year in Southern California. For 2026, it’s still effectively 12°E. But maps from the 1990s or earlier may be several degrees off — always verify at www.ngdc.noaa.gov/geomag/calculators/magcalc.shtml or use the WMM model.

Suunto Field Quick-Check

After setting declination, verify before heading out:

1. Face a known landmark whose bearing you can verify
   (cell tower, peak, road intersection visible on map)
2. Shoot a bearing with the compass
3. Check against the map — should match the grid bearing
4. If off by ~12°, your declination adjustment didn't take

Do this at the trailhead BEFORE entering the mountains.

Compass Techniques

Taking a Field Bearing

1. Hold compass level at waist height
2. Point direction-of-travel arrow at target
3. Rotate bezel until needle aligns with orienting arrow
4. Read bearing at index line
5. Apply declination correction if compass not pre-set

Following a Bearing

1. Set bearing on compass (adjust for declination)
2. Hold compass level, rotate body until needle aligns
3. Identify distant object on bearing line
4. Walk to object, repeat
5. Don't look at compass while walking - look at target

Shooting a Back Azimuth

The back azimuth is exactly opposite your forward bearing:

\[\theta_{\text{back}} = (\theta_{\text{forward}} + 180°) \mod 360°\]

Or equivalently:

\[\theta_{\text{back}} = \begin{cases} \theta + 180° & \text{if } \theta < 180° \\ \theta - 180° & \text{if } \theta \geq 180° \end{cases}\]

Examples

\[\theta = 045° \implies \theta_{\text{back}} = 045° + 180° = 225° \\ \theta = 270° \implies \theta_{\text{back}} = 270° - 180° = 090° \\ \theta = 180° \implies \theta_{\text{back}} = 180° - 180° = 000° = 360°\]

Back Azimuth Verification Diagram

         N (000°)
         │
    315° │  045°
      ╲  │  ╱
       ╲ │ ╱
        ╲│╱
  270° ──┼── 090°     θ = 045°  ──→  θ_back = 225°
        ╱│╲             (NE)           (SW)
       ╱ │ ╲
      ╱  │  ╲
    225° │  135°      The back azimuth always points
         │            directly away from your target.
       S (180°)       Use it to verify: look BEHIND you.

Distance Estimation

Pace Count

A pace is two steps (count when same foot hits ground).

Establishing Your Pace

Measure a known distance (100m recommended)
Walk normally, counting paces
Repeat 3 times, take average
This is your pace count per 100m

Pace Count Formula

\[\text{Paces needed} = \frac{d_{\text{ground}}}{100} \times P_{100}\]

Where \(P_{100}\) = your pace count per 100m, \(d_{\text{ground}}\) = distance in meters.

Example: 750m leg, 66 paces/100m

\[\text{Paces} = \frac{750}{100} \times 66 = 7.5 \times 66 = 495 \text{ paces}\]

Slope Correction (for map distance → ground distance)

\[d_{\text{ground}} = \frac{d_{\text{map}}}{\cos(\alpha)}\]

Where \(\alpha\) = slope angle. On a 30° slope:

\[d_{\text{ground}} = \frac{500}{\cos(30°)} = \frac{500}{0.866} = 577 \text{ m}\]

The map shows horizontal distance. The ground distance is longer on slopes. A 500m map leg going uphill at 30° is actually 577m on your feet — that’s 15% more paces.

Table 2. Typical Values
Terrain	Paces per 100m
Flat road	62-68
Rough flat	68-76
Uphill	72-84
Downhill	60-68
Brush/heavy pack	76-88

Pace Beads (Ranger Beads)

   ╭───╮
   │ ○ │ ← Upper section: 4 beads (1000m each)
   │ ○ │
   │ ○ │
   │ ○ │
   ├───┤
   │ ○ │ ← Lower section: 9 beads (100m each)
   │ ○ │
   │ ○ │
   │ ○ │
   │ ○ │
   │ ○ │
   │ ○ │
   │ ○ │
   │ ○ │
   ╰───╯

Move one lower bead for each 100m walked.
After 9 lower beads, move one upper bead and reset lower.

Navigation Methods

Dead Reckoning

Navigate by compass bearing and distance alone.

1. Determine bearing from current position to objective
2. Estimate distance
3. Calculate pace count needed
4. Travel on bearing, counting paces
5. When count reached, you should be at objective

Errors accumulate. Dead reckoning alone over long distances is unreliable.

Terrain Association

Use terrain features for navigation:

1. Orient map to terrain
2. Identify current position
3. Plan route using distinct terrain features as checkpoints
4. Navigate feature to feature
5. Confirm position at each checkpoint

Attack Points

An attack point is a prominent feature near your objective from which you navigate precisely to the final target.

Route: Start → Checkpoint 1 → Checkpoint 2 → Attack Point → Objective

Using attack points reduces the "search area" for your objective.

Handrailing

Follow linear features (streams, ridges, trails) that run parallel to your direction of travel.

                    N
                    │
   Start ●          │ Objective ◎
          │         │      │
          │ move to │      │
          ▼ stream  │      │
   ═══════●════════════════●═══════ Stream (handrail)
          │         │  follow  │
          │         │  stream  │
          └─────────┘──────────┘
                    │
          Dead reckoning would cross
          open terrain (risky at night).
          Handrailing follows the stream
          to a point near the objective,
          then a short bearing to target.

Night advantage: You can hear and feel a stream even when you can’t see it. Handrails are your best friend in the dark.

Aiming Off

Deliberately aim to one side of the objective so that when you hit a linear feature, you know which direction to turn.

          N
          │
     Objective ◎ on road
          │
    ══════╪══════════════════ Road (linear feature)
         ╱│
        ╱ │
       ╱  │  ← If you aim STRAIGHT, you hit the road
      ╱   │     but don't know: turn left or right?
     ╱    │
    ╱     │
   ●      │
   Start  │
          │
    ══════╪══════════════════ Road
       ╱  │
      ╱   │  ← If you aim 5° LEFT, you hit the road
     ╱    │     and KNOW to turn RIGHT to find objective.
    ╱     │
   ●      │
   Start

Aiming Off Angle

\[\text{Deliberate offset} = 5°\text{-}10° \quad \text{(day)} \quad | \quad 10°\text{-}15° \quad \text{(night)}\]

The offset must be large enough that compass error cannot reverse it. At night, use the higher end — your bearing accuracy degrades.

Resection and Intersection

Resection (Finding Your Position)

Determine your unknown position using bearings to 2-3 known map features.

Procedure

Identify 2-3 distinct features visible on both map and ground
Shoot magnetic bearing to each feature
Convert each to back azimuth: \(\theta_{\text{back}} = (\theta + 180°) \mod 360°\)
Draw lines on map from each feature along its back azimuth
Intersection of lines = your position

Resection Diagram (3-Point Fix)

            Peak A (known)
             ╱  θ_A = 320°  →  back = 140°
            ╱
           ╱
          ╱
    ─────X─── ← YOUR POSITION (unknown)
        ╱ ╲
       ╱   ╲
      ╱     ╲
  Tower B    Saddle C
  (known)    (known)
  θ_B = 065°   θ_C = 185°
  back = 245°  back = 005°

  Lines from A (at 140°), B (at 245°), C (at 005°)
  converge at X = your location.

Why 3 bearings, not 2? Two lines always intersect somewhere — but that point might be wrong if one bearing is off. Three lines form a small triangle of error (cocked hat). Your position is inside that triangle. If the triangle is large, your bearings are bad — reshoot.

Triangle of Error

\[\text{If triangle side} > 100\text{m at map scale} \implies \text{reshoot all bearings}\]

Intersection (Finding Unknown Point)

Determine position of a distant feature from two known positions.

Intersection Diagram

  You (Position A)          You (Position B)
  known: 11S MT 8320 5700   known: 11S MT 8480 5720
         │                          │
         │ θ_A = 042°               │ θ_B = 318°
         │  ╱                        ╲  │
         │╱                            ╲│
          ╲                           ╱
            ╲                       ╱
              ╲                   ╱
                ╲               ╱
                  ╲           ╱
                    ╲       ╱
                      ╲   ╱
                       ╲ ╱
                        X ← Unknown point
                        (fire, signal, landmark)

Procedure

From known position A, shoot bearing \(\theta_A\) to unknown point
Move to known position B (ideally 60°-120° angle between A and B)
Shoot bearing \(\theta_B\) to same unknown point
Draw lines from A and B on their forward bearings
Intersection = unknown point location

Optimal Intersection Geometry

\[\text{Best accuracy when angle of intersection} \approx 90° \quad (60°\text{-}120° \text{ acceptable})\]

Angles near 0° or 180° produce long, thin error zones — the intersection point becomes ambiguous.

Field Techniques

Deliberate Offset

When navigating to a linear feature, aim for a recognizable point offset from your true objective.

Your objective: Trail junction at coordinate X
Your route: May have 100m error

Solution:
1. Aim for distinct bend in trail 200m west of junction
2. Upon reaching bend, turn east and follow trail to junction

Catching Features

Features beyond your objective that indicate you’ve gone too far.

Objective: Small clearing
Catching feature: River 300m beyond clearing

If you reach the river, you've overshot. Turn back.

Steering Marks

In open terrain, pick intermediate objects to maintain bearing:

1. Shoot bearing to objective
2. Note bearing
3. Identify rock/tree/feature in line with bearing, halfway
4. Walk to intermediate feature
5. Shoot new bearing, pick new steering mark
6. Repeat until objective reached

Night Navigation

Night land navigation is an order of magnitude harder than daytime. Terrain features disappear, pace count drifts, and your brain fills in details that aren’t there. This section covers what changes at night and how to compensate.

Before You Leave: Pre-Movement Checklist

Solo mountain night nav is inherently dangerous. Mitigate risk before stepping off:

Pre-Movement Checklist (Complete at Trailhead)

□ Route planned on map in DAYLIGHT with bearings and distances written down
□ All legs have catching features (what tells you you've gone too far)
□ Back azimuth for every leg pre-calculated and written on map margin
□ Declination set on compass (verify with known landmark)
□ Pace count established for terrain type
□ Phone charged, location shared with someone who expects check-ins
□ Headlamp with red lens mode (and backup light source)
□ Water, warm layer, emergency whistle, space blanket
□ Turnaround time set — "I will be at the truck by ____"
□ Map and compass accessible without removing pack

Route Planning for Night

1. Study the map in daylight. Memorize terrain shape, not just bearings.
2. Choose legs that follow HANDRAILS (ridgelines, streams, trails)
   — avoid open terrain where steering marks are invisible
3. Keep legs SHORT: 300-500m maximum between checkpoints
   — error accumulates fast at night
4. Choose checkpoints you can FEEL, not see:
   — slope changes (ridge to saddle)
   — ground type changes (trail to dirt, dirt to rock)
   — water crossings
   — trail junctions (count them)
5. Write bearings and pace counts on your map margin or a card
   — you will not want to read the map in the dark

Night Movement Techniques

Reduced pace: Move slower, steps shorter — your stride shrinks 10-20% on uneven ground in the dark
Adjust pace count: Add 15-25% to your daylight pace count for the same distance
Use handrails obsessively: Linear features (ridgelines, streams, trails, fence lines) are your primary nav tool at night — terrain association replaces visual bearing shots
Deliberate offset: Aim 5-10° to one side of your target, not 2-3° — night drift is larger than you expect
Check terrain with your feet: Slope angle changes, ground surface changes, and water sounds are your "visual" cues
Stop and listen frequently: Wind direction, water, traffic noise, and animal sounds all orient you
Count EVERYTHING: Trail junctions, stream crossings, saddles — if your map shows 3 stream crossings before the turn, count them

Night Pace Count Adjustments

Terrain	Day Pace / 100m	Night Pace / 100m
Flat trail	62-68	68-76
Rough flat	68-76	78-88
Uphill (moderate)	72-84	84-96
Downhill	60-68	70-80
Brush / off-trail	76-88	90-105

Establish your night pace count BEFORE going into mountains. Walk a known 100m distance in the dark on flat ground, count paces, repeat 3 times, average it.

Illumination Discipline

Red light preserves night vision — it takes 30 minutes for full dark adaptation, and one flash of white light resets the clock
Map reading: Use red lens mode on headlamp. Pre-fold map to show only the current leg — minimizes light exposure time
Compass: Suunto luminescent markings glow after light exposure. Charge them with a quick white light flash, then switch back to red
Avoid white light unless you’re in an emergency — once you break dark adaptation, you’re effectively blind for 20-30 minutes
Moon phases matter: A full or gibbous moon dramatically improves night nav. A new moon in mountains under tree canopy is the hardest condition

Mountain-Specific Night Hazards

Hazard	Mitigation
Cliffs / steep drops	Never walk downhill on an uncertain bearing. If the slope suddenly steepens, STOP. Check map. Contour lines merging = cliff. Back up and reassess.
Loose rock / scree	Night footing on talus is ankle-breaking terrain. Avoid scree fields — route around even if it adds distance.
Temperature drop	Environmental lapse rate: \(\approx 3.5°\text{F} / 1{,}000\text{ft}\) (\(6.5°\text{C} / 1{,}000\text{m}\)). Summit at 6,000ft above a 2,000ft trailhead = \(4 \times 3.5 = 14°\text{F}\) colder. Add wind chill. Bring a warm layer even if the car park is warm.
Dehydration	You still sweat at night. Drink on schedule, not on thirst.
Disorientation panic	If you don’t know where you are: STOP. Sit down. Drink water. Breathe. Orient the map. Shoot bearings to any visible features. You are not lost until you keep walking without a plan.
Wildlife	Mountain lions hunt at night. Make noise on the trail. Bears are less active at night but still present. Carry a whistle.

Hazard

Mitigation

Cliffs / steep drops

Never walk downhill on an uncertain bearing. If the slope suddenly steepens, STOP. Check map. Contour lines merging = cliff. Back up and reassess.

Loose rock / scree

Night footing on talus is ankle-breaking terrain. Avoid scree fields — route around even if it adds distance.

Temperature drop

Environmental lapse rate: \(\approx 3.5°\text{F} / 1{,}000\text{ft}\) (\(6.5°\text{C} / 1{,}000\text{m}\)). Summit at 6,000ft above a 2,000ft trailhead = \(4 \times 3.5 = 14°\text{F}\) colder. Add wind chill. Bring a warm layer even if the car park is warm.

Dehydration

You still sweat at night. Drink on schedule, not on thirst.

Disorientation panic

If you don’t know where you are: STOP. Sit down. Drink water. Breathe. Orient the map. Shoot bearings to any visible features. You are not lost until you keep walking without a plan.

Wildlife

Mountain lions hunt at night. Make noise on the trail. Bears are less active at night but still present. Carry a whistle.

The STOP Protocol (When Lost)

S - SIT DOWN. Stop moving immediately. Further movement without
    a plan makes everything worse.

T - THINK. When did you last know where you were? What terrain
    have you crossed since? What direction have you been traveling?

O - OBSERVE. Orient your map. Shoot bearings to any visible feature
    (lights, ridgelines, peaks). Listen for water, traffic, wind
    direction. Feel the slope — which way is downhill?

P - PLAN. Three options:
    1. Retrace your steps on a back azimuth to last known point
    2. Navigate to a catching feature (road, river, ridge)
    3. Stay put until daylight (if safe and you've told someone
       your location)

Solo night nav rule: when in doubt, go back. A back azimuth to your last known position is always safer than pushing forward into terrain you can’t see. Pride doesn’t navigate.

Celestial Orientation (Backup)

If your compass fails or you need a quick bearing check, the sky is your backup.

Polaris (North Star) — True North ±1°

                           Polaris ★
                          ╱        (Altitude ≈ your latitude)
                        ╱
               5× d   ╱
                     ╱
                   ╱
      ★─────────★  Pointer stars (Dubhe & Merak)
      │ Big     │
      │ Dipper  │
      ★         ★
       ╲       ╱
        ╲     ╱
         ★───★
          Handle

  Polaris altitude at 34°N = 34° above northern horizon.
  Extend your fist at arm's length: ≈ 10° per fist width.
  Polaris is ~3.5 fists above the horizon.

Polaris Altitude = Your Latitude (field estimation)

\[h_{\text{Polaris}} \approx \phi \quad \text{(within } \pm 1° \text{)}\]

Where \(h\) = altitude above horizon, \(\phi\) = observer’s latitude. This works because Polaris is ~0.7° from the celestial pole.

Orion (Seasonal — visible Oct through Mar)

          Betelgeuse ★  (red, NE shoulder)
                    │
        ★───────────★───────────★  ← Belt rises due EAST
                    │              sets due WEST
                    │
          Rigel ★    (blue-white, SW foot)

  When belt is rising (tilted, left side up):  EAST
  When belt is setting (tilted, right side up): WEST
  When belt is vertical (transit):              due SOUTH

Moon Phase Direction Finding

  Phase            Rises    Transits   Sets     At transit
  ─────────────────────────────────────────────────────────
  First Quarter    ~Noon    ~Sunset    ~Midnight   SOUTH
  (right half)
  Full Moon        Sunset   Midnight   Sunrise     SOUTH
  Last Quarter     ~Midnight ~Sunrise  ~Noon       SOUTH
  (left half)

  Quick rule: illuminated side points toward the sun.
  Draw imaginary line through horns of crescent → points
  roughly south in the Northern Hemisphere.

Shadow Method (if moonlight is strong enough)

  1. Push a straight stick vertically into flat ground
  2. Mark the tip of the shadow with a stone (Point 1)
  3. Wait 15-20 minutes
  4. Mark the new shadow tip (Point 2)
  5. Draw a line from Point 1 → Point 2

  Point 1 → Point 2 = roughly EAST
  (shadows move opposite to celestial body movement)

  Accuracy: ±15° — enough to orient a map, not to hold a bearing

Navigation Errors

Common Mistakes

Error	Prevention
Not orienting map	Always orient before navigating
Pace count loss	Use beads, mark on hand, partner counts
Following wrong bearing	Verify with back azimuth
Not accounting for declination	Pre-set compass or religiously correct
Terrain association failure	Study map before departure
Drift	Use steering marks, check frequently

Error

Prevention

Not orienting map

Always orient before navigating

Pace count loss

Use beads, mark on hand, partner counts

Following wrong bearing

Verify with back azimuth

Not accounting for declination

Pre-set compass or religiously correct

Terrain association failure

Study map before departure

Drift

Use steering marks, check frequently

Error Estimation

Position Error Components

\[\epsilon_{\text{along}} = d \times \epsilon_{\text{pace}} \quad \text{(along-track error from pace count)} \\ \epsilon_{\text{cross}} = d \times \tan(\epsilon_{\theta}) \quad \text{(cross-track error from compass)}\]

Where \(d\) = distance traveled, \(\epsilon_{\text{pace}}\) = pace count error (±3-5%), \(\epsilon_{\theta}\) = compass error (±3-5°).

Combined Position Error (root sum of squares)

\[\epsilon_{\text{total}} = \sqrt{\epsilon_{\text{along}}^2 + \epsilon_{\text{cross}}^2}\]

Example: 1,000m leg with ±4% pace error and ±4° compass error

\[\epsilon_{\text{along}} = 1{,}000 \times 0.04 = 40\text{ m} \\ \epsilon_{\text{cross}} = 1{,}000 \times \tan(4°) = 1{,}000 \times 0.0699 = 70\text{ m} \\ \epsilon_{\text{total}} = \sqrt{40^2 + 70^2} = \sqrt{1{,}600 + 4{,}900} = \sqrt{6{,}500} \approx 81\text{ m}\]

Error Growth Over Multiple Legs

  Error "cone" widens with distance from last known position:

         Known                                        ?
  Start ──●─────────────╲                            ╱──── After 3 legs
          │               ╲  ε₁ ≈ 81m              ╱      ε grows with √n
          │                ╲                      ╱
          │                 ●                   ╱
          │              CP₁  ╲    ε₂         ╱
          │                     ╲           ╱
          │                      ●        ╱
          │                   CP₂  ╲    ╱
          │                         ╲ ╱
          │                          ● Objective
          │                    (now ≈ 140m uncertainty)

This is why attack points matter. Each checkpoint where you confirm position resets the error cone to zero. Without checkpoints, errors compound across legs:

\[\epsilon_{n \text{ legs}} \approx \epsilon_{\text{single}} \times \sqrt{n}\]

Three 1,000m legs without a position fix: \(81 \times \sqrt{3} \approx 140\text{m}\) uncertainty radius.

Practice Drill

Route Planning Exercise

Choose start and end points on a map
Identify 3-4 checkpoints along route
Calculate bearing and distance for each leg
Identify attack point near objective
Identify catching features
Note escape routes / backstops

Field Exercise

Navigate a 4-point course
At each point, record grid coordinate (MGRS 8-digit)
Compare recorded coordinates to actual
Analyze errors

Quick Reference Card

Navigation Checklist

□ Map oriented to terrain
□ Current position confirmed (2+ features)
□ Route planned with checkpoints
□ Bearings and distances recorded
□ Declination accounted for
□ Attack point identified
□ Catching features identified
□ Pace count known for terrain type

Bearing Memory Aid

N = 0°/360°
E = 90°
S = 180°
W = 270°

NE = 45°
SE = 135°
SW = 225°
NW = 315°

Continue to Tools & Software for CLI tools and GIS software.