Communicating shot adjustments - Guide - UNITAF Force Manual (FM)




Communicating shot adjustments
The FM outlines our core skills, policies and guides to ensure every member stands ready for the mission ahead.



Current Version (258 days ago)

FM/BG-623.V2.02 - Communicating shot adjustments

Good communication between the spotter and sniper can really help achieve mission success. This starts prior to the mission brief and stepping off, during which time the pair should establish an understanding of what each would like and what the other is comfortable to give in terms of communicating shot adjustments. Agree on the method to be used ahead of time to avoid distraction and confusion once the mission starts.

There are numerous ways to communicate shot adjustments. This guide will cover three of the most common, but sniper teams are encouraged to modify or use what works best for them to achieve positive results in their operations. Regardless of the method used, the principle is the same in that you are giving corrections that will move the point of impact, or ‘splash’, onto center mass of the target or aiming point.

 

Adjusting in MRADs 

This is potentially the smoothest and most accurate method of communicating shot adjustments in many of our operations. Most sniper loadouts consist of rifles with MilDot reticles which are matched by the spotting scope that also uses MilDots. This allows for a seamless translation between what the spotter observes and what adjustments the sniper needs to make. 

MRAD adjustments can be given in mils themselves, or as ‘clicks’ of adjustment on the scope. Use whichever method is most comfortable between the spotter and sniper. When announcing corrections in mils, always try to give the actual decimal measurement versus saying a fractional value. For example, to correct a round landing 4/10ths of a mil to the right you would say “.4 mils left.” This makes it easier for the sniper to automatically know to make an adjustment of 5 clicks left on the scope. Otherwise, you can do the math for them and give them the correction in clicks. An example in this case for a shot observed landing 1.1 mils low would be “11 clicks up.” See Figure 1 below for an illustration of these examples.

 

Adjusting via Clock Sectors

Although not as accurate as using MRADs, communicating shot adjustments via clock sectors can be a quick and expedient means of moving the bullet impact on target. It is also useful when the spotter or sniper does not have access to a MRAD reticle. 

To adjust a shot in this manner, think of the target as having a rifle competition target superimposed on it and divided into sections numbered like a clock. The spotter then communicates the adjustment based on where the bullet impacted in relation to the bullseye. A shot that impacted slightly low would be communicated as a “9 or 8 at 6 o’clock.” A high-left impact would be called an “8 or 7 at 10 o’clock.” See Figure 2 below for an illustration of these examples.

 

Adjusting Points of Aim

Another expedient method of communicating shot adjustments is altering points of aim. This involves a two-way communication between the sniper and spotter. The sniper calls out where he was aiming at the moment when he took the shot. This may or may not be center mass due to rifle sway or other factors, or may be something like “right at the head between the eyes”. The spotter then observes the impact of the round and then tells the sniper where to aim instead in order to move the impact onto the desired hit location. In the example above, if the round went high and to the right of the target’s head the spotter might say something like “Try aiming lower at the left shoulder.” Again, this is not the most accurate way of communicating shot adjustments, but can readily be used when the sniper does not have a mildot reticle and speed is of the essence for follow-on shots. 

MRAD adjustments and Clock adjustments.

Above: MRAD adjustments and Clock adjustments.

Published by Maj James on 05/07/2024 at 19:57

Previous Versions

This page generated 0.99MB in 0.0508 seconds.