Night Lane, Two East-West Roads
You are the compass man for a four-soldier dismounted team on a night land-navigation lane in mixed woods and pasture. You carry a 1:50,000 topographic map, a lensatic compass, and a red-lens headlamp. Your pace count is 62 paces per 100 meters on flat ground. The map margin shows a grid-magnetic angle of 12 degrees east. Your first leg is 1,700 meters on a grid azimuth you converted to 58 degrees magnetic. The checkpoint is a trail junction roughly 400 meters south of Phase Line Bravo, a straight east-west paved road. At 0230 fog drops visibility to about 30 meters. After roughly 35 minutes you cross a hard-surface east-west road, but your pace count says you have covered only 1,100 meters. The assistant team leader wants to keep walking. The pickup window closes at 0500, and the team has no working GPS.
1. You cross an east-west hard-surface road after only 1,100 meters of a 1,700-meter leg. What are the two most probable explanations, and what do you do in the next five minutes?
Read the worked answer
Two candidate explanations, pointing in opposite directions.
- Your pace count is short. Sixty-two paces per 100 meters is a flat-ground, daylight, light-load figure. Under a rucksack, in fog, on slopes and in brush, stride shortens. Eleven hundred counted paces could be 1,400-1,600 true meters, which means the road you just hit may be Bravo after all.
- You are on a different east-west road. A small azimuth-holding error compounds with distance: 10 degrees of error over 1,500 meters puts you roughly 260 meters off line, and most maps in this terrain show more than one east-west road, field boundary, or improved track.
Actions in the next five minutes:
- Halt the team, take a knee, pull 360-degree security, no white light.
- Re-check the compass and the conversion. With east declination, magnetic = grid minus the G-M angle, so a 58-degree magnetic heading should have come from a 70-degree grid azimuth. Recompute rather than trust memory.
- Terrain-associate the road you are standing on: width, surface, culvert spacing, fence lines, crown, visible curve. Compare against the map signature of Bravo and of any parallel road.
- If any second linear feature is near (stream, treeline, fence), run a resection to fix your position.
- Reset the pace count from this point and log the time.
Decision rule: if the road matches Bravo, you are short of the leg's end, so continue on azimuth and re-check at 500 meters. If it does not match, treat it as a parallel road and re-attack. Do not keep walking on an unverified assumption - that is how a 30-minute error becomes a missed pickup.
2. The fog holds. The team must still find the trail junction. Compare re-plotting a straight line from your uncertain position with using the road as a handrail or with a deliberate offset, and state which you choose and why.
Read the worked answer
Straight re-plot from an uncertain position is the weakest option. Your position is uncertain by several hundred meters. A new azimuth converts that positional uncertainty into angular error with distance: a 100-meter lateral error at 500 meters of leg is roughly 11 degrees of aim error. Fog removes the mid-leg terrain cues you would use to correct, so the error compounds instead of self-correcting.
Handrail. The road is a continuous, unmistakable linear feature. Move along it, slightly offset for noise and silhouette discipline, until you reach a mapped junction, culvert, or sharp curve. That gives you a known point to use as an attack point toward the trail junction. Cost: extra distance, extra time, and exposure along a feature that other people also use.
Deliberate offset. Aim not at the junction but at a point a known distance to one side of it, for example 150 meters north. When you hit the handrail you know which way to turn. This converts a hard question (did I hit the exact point in fog?) into an easy one (which way do I turn?).
Boxing - move 90 degrees off, travel parallel, then 90 degrees back - works when the objective has handrails on multiple sides and you can hold distance accurately.
Choice: handrail to a mapped junction, then a short deliberate offset to the trail junction. It uses the most reliable feature on the ground, keeps position error bounded, and is easy to explain to the team in the dark. Before moving I would set a hard turn-back time against the 0500 pickup and tell the team the plan and the fallback.
3. The pickup is at 0500 and the team is behind schedule. How do you manage the clock and risk, and what do you tell higher?
Read the worked answer
Build a time budget backwards from 0500. Work out the route time to the pickup point, add a navigation-error allowance of roughly 25-30 percent, and subtract darkness and fatigue. That produces a decision point, not a hope. A reasonable rule: if the team is not at the trail junction by the decision time, break off and move directly to the pickup via the handrail, because arriving late and scattered is worse than arriving without the checkpoint.
Risk factors to weigh: no GPS, fog, one navigator, falling body temperature, and the psychological pull to keep pushing because the objective is close. Fatigue makes people accept bad assumptions, which is exactly when the pace count and azimuth should be re-verified rather than trusted.
Options to brief: continue to the objective; abandon the objective and go to the pickup; or, if the team becomes genuinely uncertain of position, occupy a defensible position, go silent and stationary, and signal at first light. That last option must be pre-authorized or it becomes an unplanned incident.
What to tell higher: a short SITREP - current location by grid if you have confidence in it, otherwise a terrain description and a bounding box, status of personnel and equipment, what happened (unexpected road crossing, pace discrepancy, fog), your decision, your new estimated time of arrival, and what support you need (a light or signal at the pickup point, a radio check at a set time). State confidence honestly. A report that says "approximately" is far more useful to a commander than a false grid.