BETA / LIVE
The Communication Handbook - UNITAF Force Manual (FM)




The Communication Handbook
Communicators are experts in radio telephony, communicating vital transmissions across the battlefield in quick succession can often save lives, and lead to a successful mission.



FM/G92 - Training Teams

FM/BP-458 - Staff Instructors
  • Member of J7 Staff responsible for overseeing a specific combat area, its training and training team
  • Minimum of 1 and maximum of 2 per skill card; each staff member can oversee up to 4 skill cards in total
  • Serves as the primary point of contact in the combat area for Training Command, Chief Instructors, Instructors, Observers, and the wider unit
  • Ensures adequate training and practices are conducted through the training team
  • Appoints and removes Training Instructors and Observers as needed, based on advice from Chief Instructors and in collaboration with Training Command
  • Collaborates with Policy staff to implement changes and distribute them upon publication by Unit Command
  • Holds the second highest weighted opinion among the roles involved
  • Actively participates in training, application, and observation of combat area skills
  • Accountable to Training Command and appointed at their discretion
FM/BP-457 - Chief Instructors
  • Designated member of the unit serving as a subject matter expert in a specific combat area
  • Minimum of 1 and maximum of 2 may be assigned to any combat area
  • Acts as a senior advisor to unit command, providing guidance on potential changes and advising on ongoing discussions
  • Active participant in training, application, and observation of combat area skills
  • Holds the highest weighted opinion among all other roles
  • Accountable to both the Staff Instructor and Training Command
  • Appointment made at the discretion of Training Command
FM/BG-456 - Introduction to Training Teams

The 'Training Team' is a specialised group within the unit responsible for overseeing and managing the evaluation and improvement of a specific combat area. Comprising appointed individuals including Chief Instructors, Staff Instructors, Training Instructors, and Observers, the team operates under the guidance of Training Command. Each member has distinct roles and responsibilities, ranging from providing subject matter expertise to facilitating training sessions and assessing skill levels. Together, they ensure that training standards are met, skills are effectively taught and practiced, and feedback is provided to enhance individual and unit proficiency in specific combat areas.

FM/BP-459 - Training Instructors
  • Unit member appointed as a Training Instructor in a specific combat area, having transitioned from the role of Observer
  • Recognized by the training team as a well-rounded individual capable of effectively teaching relevant combat area skills in group settings
  • Possesses a solid understanding of the combat area skills
  • Holds the third highest weighted opinion among the roles involved
  • Limited to a maximum of 6 Training Instructors per combat area
  • Actively engages in training, application, and observation of combat area skills
  • Accountable to both the Staff Instructor and Chief Instructors
FM/BP-460 - Observers
  • A member of the unit who is appointed as an Observer in a specific combat area, who in the eyes of the training team is trusted to assess others in a non-teaching capacity in the combat areas skills.
  • Typically a starting role on route to Training Instructor.
  • Holds the lowest weighted opinion.
  • Maximum of 8 per combat area
  • Active in the training, application and observation of combat area skills.
  • Accountable to the Training Instructors and Chief Instructors.

FM/G71 - Rules of engagement

FM/BG-348 - Understanding rules of engagement (ROE)

Rules of engagement (ROE) are directives that dictate how and when military forces can engage in combat. ROE outline conditions for using force, including target identification, self-defence, and proportionality. They are designed to ensure lawful and ethical conduct in military operations, and vary depending on the mission and environment. ROE always take precedence in operational decisions.

FM/BS-349 - Identify legitimate targets

Identify targets as legitimate targets before engagement. This is crucial to prevent harm to civilians and ensure adherence to the principles of distinction and proportionality in combat.

Combatants: Individuals who are actively engaged in hostilities or are members of armed forces.

  • Enemy soldiers in uniform not surrendering or wounded
  • Armed militants
  • Persons directly participating in hostilities
  • A person posing an immediate threat (e.g., aiming a weapon) can be considered a combatant
  • Parachuting active airborne infantry

Non-Combatants: Individuals who are not actively participating in hostilities. These are not legitimate targets.

  • Civilians not taking direct part in hostilities
  • Unarmed medical and religious personnel
  • Wounded/surrendering soldiers who are not participating combat in any way, and prisoners of war
  • Parachuting crew from a downed aircraft
FM/BS-350 - Minimize collateral damage against civilian infrastructure

Do not cause damage to civilian infrastructure, unless necessary to archieve a military purpose. In general, preserving life should be prioritised over the avoidance of damage, but the destruction must be proportional to the purpose.

Examples:

  • Acceptable situations:
    • Using explosives on a civilian house used as a military HQ
    • Dropping a bomb on an actively engaging enemy tank next to a house
  • Unacceptable situations:
    • Cluster-bombing an enemy-held town
    • Destroying a house to take out a single shooter

FM/G69 - Direct Communication

FM/BG-325 - Common phraseology
CalloutMeaning
Go firmInstruction to stop in place for a long amount of time and therefore to  take long-term defenses, such as establishing proper cover, building trenches etc.
ARDAll round defense. Instruction to establish security in a full 360° arc. Usually elements/individuals will be assigned to a sector of this defense.
Set security ([arc in degrees]) [cardinal direction] Instruction to take security centered around particular direction for the specified width. e.g. “Set security 180 north”, means hold position and establish security covering West through North, through to East. The direction specified is often the most likely direction of enemy attack and therefore usually held by the individual with the most firepower (e.g. the Automatic Rifleman/Machine Gunner). If no arc is specified it is 90°.
  
FM/BG-686 - Voice volume usage

During operations, always be mindful of your voice volume, as the enemy can hear you, and your choice could impact the success or failure of the mission. 

Generally, use a normal voice when you have radios and the situation is calm. Switch to yelling when urgent communication is needed, like when throwing a grenade, overcoming loud external noise, or if radios aren't available. Use whispering to keep your position concealed when infiltrating behind enemy lines, setting up and coordinating ambushes or simply when you don't want the guy on the other side of the wall hear you approach him as you coordinate with your team.

FM/BS-331 - Alert others when throwing a grenade

When throwing a grenade, shout:

[type of grenade] out

TypeGrenade category
FRAGFragmentation grenade
SMOKESmoke grenade
FLASHBANGFlashbang
FM/BS-333 - Alert others to a threatening grenade

When you see a grenade landing or being thrown in your direction, shout: 

grenade

FM/BS-334 - Alert others to incoming indirect fire

When hearing or observing incoming indirect fire, shout: 

IDF incoming

FM/G281 - Sending a Situation Report (SITREP)

FM/BG-1288 - What is a Situation Report?

A Situation Report (SITREP) is a concise method for a leader to quickly understand the status and activity of their troops. It enables efficient communication up and down the chain of command, ensuring leaders maintain situational awareness across all elements.

For our purposes, a SITREP answers two simple questions:“What is your location?” and “What is your activity?”

SITREPs can be requested at any level and are most commonly used during pauses in combat, at the conclusion of engagements, or when higher command requests an update.

FM/BS-1289 - Give a structured Situation Report

REQUEST: STREPs are called for using a simple, clear command.

“(Element), send SITREP.” 

ACKNOWLEDGE (if required): The responding element acknowledges the request. If unable to report immediately, they may reply:

“(Element) – WAIT OUT.”

RESPOND: When ready, the element provides their concise SITREP, following the format:

  1. Location: Current position or reference point.
  2. Activity: What the element is doing.

“(Element): SITREP – firm at Compound 6-6, awaiting orders.”

CONFIRMATION: The requesting leader acknowledges receipt of the report.

"(Element): ROGER OUT."

FM/G282 - Sending an ACE Report

FM/BG-1293 - Conducting and compiling an ACE Check within an element

Before an ACE Report can be sent, the leader must gather the required information from their team. This is called an ACE Check.

AS A LEADER

  • Gather information from your buddy team directly, then from the other team’s leader.
  • Conduct the check off-radio when possible to reduce chatter.
  • If spread out, collect from each member individually.

AS A TEAM MEMBER

Individual members provide raw details only when needed, following A-C-E order, without using colours or headers.

Correct:

“Need 4× 5.56 STANAG, need a stitch, nearly out of bandages.”

Incorrect:

“Orange on 5.56, orange need a stitch, red on bandages.”“Ammo low on 5.56, Casualty need a stitch, Equipment low on bandages.”

Only report what is required:

“Low on 5.56 STANAG and nearly out of bandages.”

If there are no needs:

“All good.” or “All green.”

Compiling an ACE Report

Once all ACE Checks are received, the leader compiles them into a single report for the higher element.

SL: 1-1, this is Actual – ACE Report.FTL (Kevin): Actual, this is 1-1 – Roger, WAIT OUT.

[Kevin collects ACE Checks from team]

KEVIN: Actual, this is 1-1 – orange 5.56 STANAG, orange 9 mm,5 up 3 wounded, orange bandages.SL: Roger, out.

  • Leaders merge information logically: consolidate ammo shortages, casualty counts, and equipment losses before reporting.
  • Maintain brevity and standard colour codes.
FM/BS-1292 - Give a structured ACE Report

AMMO: Report your team’s ammunition status, covering all primary and secondary weapons including non-disposable launchers (e.g. MAAWS, SMAW, Javelin, Stinger). Specify the types and calibres where shortages exist.

Example: “Red 9 mm, orange STANAG, red AT-4.”

CASUALTIES: Summarise the team’s medical condition:

  • Number of personnel up (conscious/able to fight)
  • Number of wounded
  • Detailed triage information belongs in a CASREP, not an ACE.

Example: “5 up, 1 wounded.”

EQUIPMENT: Report any loss of key gear or mission-critical items such as radios, NVGs, disposable launchers, or specialist tools.

Example: “Red on AT-4, orange on bandages.”

  • Only report relevant shortages.
  • Use ORANGE for low and RED for out.
  • GREEN is never reported - it adds no value.
FM/BG-1290 - What is an ACE Report?

An ACE Report is a concise update given from one element leader to the next higher leader regarding their element’s operational status.It allows rapid assessment of ammunition, casualties, and equipment across multiple teams without unnecessary detail.

  • Only include what your element needs, not what it has. Within Ammo and Equipment, report issues from most to least severe.
  • Simplicity and brevity are key – report only what matters.

FM/G166 - Sending a Casualty Report (CASREP)

FM/BG-830 - What is a casualty report?

A casualty report (CASREP) is a concise, focused communication detailing the status of casualties within an element. This enables leaders and medical units to quickly assess the severity of the situation and allocate resources accordingly.

CASREPs are used in the following scenarios:

  • When a leader needs to know casualty status.
  • To convey the specific extent and severity of wounded personnel.
  • For medical units (ambulances, medevac teams) to understand casualty situations.
FM/BS-831 - Give a structured Casualty Report (CASREP)

When reporting casualties, use the following format:

[number of immediate casualties] immediate

[number of immediate casualties] delayed

[number of immediate casualties] minimal

[number of immediate casualties] KIA

(request medical assistance)

Note the order and wording corresponds with FM/BS-188 - Identify the triage category of a patient

FM/G392 - Close air support (CAS)

FM/BS-802 - Establish target reference points (TRP)

Plot target reference points, TRP, on prominent map and terrain features for the purposes of shared known points.

Label TRPs in the format "TRP [group identifier] [number 01–10]", where the distinct group identifier broadly summarises an area of operations, phase, or cardinal direction relative to friendly positions or movements. 

Examples: “TRP N01” or “TRP SE03”.

FM/BG-1824 - Ingress/Egress

A FAC may require a CAS attack to be conducted from a specific direction to ensure safe and effective employment of weapons. This may be required for reasons including:

  • Deconfliction with friendly forces.
  • Avoidance of restricted airspace, such as air defence threats or national boundaries.
  • Reducing the risk of friendly fire during Danger Close engagements.

Ingress and egress directions can be specified using one of two methods:

  • Cardinal Direction
    • Example: “Ingress from north-east to south-west.”
       
  • Pre-established Marker
    • Example: “Ingress from Marker Alpha.”
FM/BS-1807 - Check in as a CAS aircraft
  • When entering or re-entering an AO
    • Establish communications with the supported element
    • Provide aircraft capabilities and limitations

Format

[FAC Callsign], this is [Aircraft Callsign],

Include:

  • Aircraft team composition
  • Current location
  • Available ordnance
    • Rockets
    • Guns
    • Missiles
    • Bombs
      • Skip if not applicable
  • Night vision capability (if applicable)
  • Available station time in minutes (if required)

Example

  • SIERRA 1, this is HAMMER 1-1. 
  • We are a flight of two A-10s, currently orbiting GRID 042167. 
  • Ordnance available:
    • 38 HE Rockets
    • 2,400 rounds 30mm
    • 6 GBU12
  • Night vision capable.
  • 40 minutes station time remaining.
FM/BG-1806 - Follow on CAS actions

Aircraft should confirm target identification before engagement.
Examples:

Visual infantry in treeline

Visual red smoke

Following each attack:

  • Aircraft report observed effects
  • FAC assesses results
  • FAC may re-clear, adjust, redirect, or terminate the engagement
FM/BS-1805 - Control an ongoing CAS engagement
  • Monitor aircraft attacks and battlefield changes
  • Update target information when required
  • Adjust restrictions as necessary
  • Terminate the attack if conditions become unsafe

Abort Command 

STOP STOP STOP

Immediately terminates the current attack run

Evasive Action 

EVADE

Directs the aircraft to break off and prioritise aircraft safety

Reclearing

Recleared, same target

Directs the aircraft to reengage the same target 

Terminating the engagement

Terminate, target destroyed

Ends the engagement 

FM/BS-1804 - Clear an aircraft to engage
  • Confirm a correct readback has been received.
  • Select the appropriate clearance type.
  • Restate danger close if applicable
  • Monitor the engagement and adjust, restrict, reclear or terminate the attack as required.

Format

Readback correct, Cleared In Type II

Readback correct, Cleared In Type III

Alternative Format

Cleared Hot Type X

Cleared to Engage Type X

Danger Close Example

Readback correct, Cleared Hot Type II, Danger Close

FM/BS-1803 - Correct an incorrect readback
  • Receive the readback.
  • Confirm the receiver has correctly read back all required information.
  • If the readback is incorrect:
    • State "Negative Readback".
    • Identify the incorrect line.
    • State the correct information for that line.
    • Direct the aircraft to read back the corrected line.
    • Verify the corrected readback.
    • Repeat as required until all information is correct.
  • Proceed with request

Example

Sender:

Friendlies 200 metres north of target.

Receiver:

Negative Readback. Line 4. Friendlies 200 metres south of target. Read back Line 4.

Sender:

Line 4, friendlies 200 metres south of target.

 

FM/BG-1802 - CAS clearance types

Following a correct readback, the FAC may issue a clearance. The clearance type defines the level of engagement authority granted to the aircraft against the designated target or target area.

  • Type II
    • Authorises a single engagement against the designated target.
  • Type III
    • Authorises multiple engagements against the designated target or target area until:
      • The FAC terminates the engagement, or
      • The aircraft assesses the target has been neutralised

 

The FAC retains authority to adjust, restrict, or abort the attack at any time.

Aircraft may refuse a CAS request if they assess it creates unacceptable risk to the airframe or mission.

FM/BG-1801 - CAS request quick guide
  • Line 1: [Aircraft Callsign], this is [FAC Callsign], CAS request
    • Aircraft response: [Aircraft Callsign], send CAS request
  • Line 2: GRID [grid reference] OR TRP [name] OR SHIFT TRP [name], NORTH/SOUTH [Distance in metres], EAST/WEST [Distance in metres]
  • Line 3: [target type/size], [environment/cover], marked by [method], [laser code if applicable]
  • Line 4: Friendlies [distance] [direction] of target, (marked by [method])
  • Line 5: [attack direction], [restrictions], Request [ordnance], danger close (if applicable)
    • Aircraft response: Readback of lines 2-5
FM/BS-1800 - Request Close Air Support

Line 1: Handshake

  • Establish communications with the aircraft
  • Identify yourself and declare a CAS request

Format:

[Aircraft Callsign], this is [FAC Callsign], CAS request

Example:

HAMMER 1-1, this is SIERRA 1, CAS request

Aircraft response:

HAMMER 1-1, send CAS request

Line 2: Target Location

  • Provide the target location using the most appropriate reference method

Format (choose one):

  • GRID [grid reference]
  • SHIFT TRP [name], NORTH/SOUTH xx, EAST/WEST xx
  • TRP [name]

Examples:

GRID 118094

SHIFT TRP ALPHA, NORTH 150, EAST 75

TRP ALPHA

Line 3: Target Description and Marking

  • Briefly describe the target
  • Include target size, type, environment, and marking method

Format:

[target type/size], [environment/cover], (marked by [method], [laser code if applicable])

Examples:

Infantry in treeline

Squad in compound, marked by red smoke

Single vehicle in open, marked by sparkle

Infantry in treeline, marked by laser, code 1688

Line 4: Friendly Positions

  • Identify friendly positions relative to the target
  • Include friendly marking methods where applicable

Format:

Friendlies [distance] [direction] of target, (marked by [method])

Examples:

Friendlies 200 metres south of target

Friendlies 150 metres east of target, marked by blue smoke

Friendlies no factor

Line 5: Attack Guidance, Restrictions & Ordnance

  • Specify attack direction and restrictions
  • Request desired ordnance
  • State danger close where applicable

Format:

[attack direction], [restrictions], Request [ordnance], (danger close if applicable)

Examples:

Attack north to south, Request HE Rocket

Attack south to north, no fires west of target, Request Bomb

Attack east to west, remain north of friendlies, Request guns danger close

Attack north to south, light AA threat from compound west of target, Request Maverick

Aircraft response:

  • Readback of lines 2-5
FM/BG-1822 - Danger close

Danger Close refers to targets within 300 metres of friendly forces. Engagements at this distance present an increased risk of friendly casualties from weapon effects. As a result, both the FAC and aircrew should exercise additional caution, positively identify the target, and carefully consider the suitability of the selected weapon and attack profile before authorising and executing the strike.

FM/BG-1821 - Target marking

During a CAS mission, the pilot must visually identify the target before employing weapons. The FAC should use the most appropriate target marking method for the situation and clearly state the method during Line 3 of the CAS request.

Smoke

Smoke may be deployed by hand or fired from a 40 mm launcher, either directly on or adjacent to the target. The FAC should state the smoke colour and describe the target's position relative to the smoke. Consider that other smoke of the same colour may already be present in the area, potentially causing confusion.

Tracer

If friendly forces are actively engaging the target, tracer fire may be used as a reference. This method is only appropriate where friendly and hostile forces use different tracer colours, reducing the risk of misidentification and fratricide.

Sparkle

During low-light operations, an infrared (IR) laser visible through night vision devices may be used to mark the target. The FAC should move the laser in a circular motion around the target, allowing the pilot to distinguish the stationary origin of the laser from the moving point marking the target. If necessary, the pilot may request a more obvious indication, such as pointing the laser vertically to identify the FAC's position or increasing the size of the circling motion.

Laser Designator

Where aircraft are capable of detecting laser designators, the FAC may use a laser designator to mark the target. The same laser may also be used to guide laser-guided munitions where appropriate.

Landmarks

Large, distinctive landmarks may be used to talk a pilot onto the target. Chosen landmarks should be clearly visible from the air, easily distinguishable from surrounding terrain, and unique enough to avoid confusion.

Map Markers and Grids

Map markers and grid references should not be relied upon for visual target acquisition. While they provide an approximate location, they are generally insufficient for a pilot to accurately identify a specific target without an accompanying visual reference.

FM/BG-1823 - Laser codes

Laser codes allow compatible munitions to be assigned a specific guidance code, preventing multiple laser sources from interfering with weapon guidance. In ACE, laser codes can be adjusted using Ctrl + Alt + Q/E to increment or change the currently selected laser code.

The FAC must communicate the active laser code to the pilot, allowing the aircraft to configure its weapons to guide onto the correct laser source.

This functionality only applies to ACE-compatible laser-guided munitions and will not function with non-ACE munitions. For simplicity, effective laser discipline and ensuring only one active laser source is present can achieve the same practical outcome in most situations.

FM/BG-1825 - Example 1

Aircraft: F/A-18 — Raven 1
FAC: Mike 7

Line 1
FAC: “Raven One, this is Mike, CAS request.”
Aircraft: “Raven One, send CAS request.”

Line 2
FAC: “GRID 123,456.”

Line 3
FAC: “Hostile fortification, fortified position, marked by red smoke and laser, laser code 1234.”

Line 4
FAC: “Friendlies 700 metres east of target.”

Line 5
FAC: “Ingress from south, Request guided bomb.”

Aircraft Readback:
Aircraft: “Raven One, target GRID 123,456. Hostile fortification, fortified position, marked by red smoke and laser, laser code 1234. Friendlies 700 metres east of target. Ingress from south, requesting guided bomb.”

FAC:
“Raven One, readback correct, Cleared Hot Type II.”

Aircraft:
“Raven One, inbound.”

Aircraft (Target Identification):
“Raven One, visual red smoke, visual hostile fortification.”

(Aircraft conducts attack.)

Aircraft (Follow-on CAS Actions):
“Raven One, off target, observed impacts on target, fortification damaged.”

FAC:
“Raven One, assessing effects, stand by.”

FM/BG-1826 - Example 2

Aircraft: A-10C — Hog 4
FAC: Anvil 7

Line 1
FAC: “Hog 4, this is Anvil, CAS request.”
Aircraft: “Hog 4, send CAS request.”

Line 2
FAC: “GRID 069,420.”

Line 3
FAC: “Infantry platoon, open terrain, marked by red smoke and tracers 200 metres south of a large industrial complex.”

Line 4
FAC: “Friendlies 200 metres north of target.”

Line 5
FAC: “Ingress from east, caution MANPADS in the area, Request guns, Danger Close.”

Aircraft Readback:
Aircraft: “Hog 4, target GRID 169,420. Infantry platoon, open terrain, marked by red smoke and tracers 100 metres north of a large industrial complex. Friendlies 200 metres north of target. Ingress from east, caution MANPADS in the area, requesting guns, Danger Close.”

FAC (Incorrect Readback):
“Negative. Target GRID 069,420. Infantry platoon, open terrain, marked by red smoke and tracers 200 metres south of a large industrial complex. Friendlies 200 metres north of target. Ingress from east, caution MANPADS in the area, requesting guns, Danger Close.”

Aircraft Readback:
“Hog 4, target GRID 069,420. Infantry platoon, open terrain, marked by red smoke and tracers 200 metres south of a large industrial complex. Friendlies 200 metres north of target. Ingress from east, caution MANPADS in the area, requesting guns, Danger Close.”

FAC:
“Hog 4, readback correct, Cleared Hot Type II, Danger Close.”

Aircraft:
“Hog 4, inbound.”

Aircraft (Target Identification):
“Hog 4, visual red smoke, visual infantry platoon.”

(Aircraft conducts attack.)

Aircraft (Follow-on CAS Actions):
“Hog 4, off target, observed impacts on target, infantry dispersing, enemy still active.”

FAC:
“Hog 4, re-clear same target, engage remaining infantry.”

Aircraft:
“Hog 4, in hot.”

(Aircraft conducts second attack.)

Aircraft (Follow-on CAS Actions):
“Hog 4, off target, observed impacts on target, enemy casualties confirmed, remaining infantry withdrawing.”

FAC:
“Hog 4, terminate, target neutralised.”

FM/BG-1827 - Example 3

Aircraft: AH-6 — Egg 2
FAC: Reaper 7

Line 1
FAC: “Egg 2, this is Reaper, CAS request.”
Aircraft: “Egg 2, send CAS request.”

Line 2
FAC: “GRID 2234,4353.”

Line 3
FAC: “Six technicals with 50 cal, open terrain, marked by IR sparkle.”

Line 4
FAC: “Friendlies no factor.”

Line 5
FAC: “Ingress as required, Request guns.”

Aircraft Readback:
Aircraft: “Egg 2, target GRID 2234,4353. Six technicals with 50 cal, open terrain, marked by IR sparkle. Friendlies no factor. Requesting guns.”

FAC:
“Egg 2, readback correct, Cleared Hot Type III.”

Aircraft:
“Egg 2, inbound.”

Aircraft (Target Identification):
“Reaper, Egg 2, unable to determine target location from sparkle. Request increased laser movement.”

FAC:
“Egg 2, Reaper, Wilco. Sparkle now circling the target.”

(FAC increases the IR laser movement around the target to improve target identification.)

Aircraft:
“Egg 2, visual technicals, in hot.”

(Aircraft conducts first attack.)

Aircraft (Follow-on CAS Actions):
“Egg 2, off target, observed impacts on target, two technicals destroyed, four remaining.”

FAC:
“Egg 2, continue engagement.”

(Aircraft conducts additional attacks.)

Aircraft:
“Egg 2, off target, observed impacts on target, remaining technicals destroyed.”

FAC:
“Egg 2, terminate, target neutralised.”

FM/G398 - Fire Mission requests

FM/BG-625 - Vector 21: Ranging

Use your Vector 21 to measure the current distance and inclination angle to your target by holding Tab + R with center circle aligned on target.

  • If equipped with an AtragMX, these values will automatically be transferred from the Vector 21 as displayed below.
Vector 21 data automatically populating into the ATragMX

Above: Vector 21 data automatically populating into the ATragMX

FM/BG-807 - Link Vector 21 and MicroDAGR for location data
  • microDAGR settings
    • Click the top bar containing the current time
    • Click “Connect To”
  • Main screen:
    • Upper half: your position
    • Lower half: sighted position
  • Compass screen:
    • Bearing indicator of sighted target
  • Target sighting:
    • Vector 21: scope in
    • Press Tab + R
    • Left: azimuth, right: slant range

See https://ace3.acemod.org/wiki/feature/microdagr for all MicroDAGR functionality

FM/BG-806 - Vector 21 fall of shot function
  • Change settings from deg & SI to mrad & SI
    • 5x Tab for settings
    • R to cycle units: left: 6400, right: SI-U
    • 5x Tab to save
  • Fall of shot function:
    • Short-press then press and hold Tab on target
    • Keep holding Tab until the end
    • Hit R on spotted impact, 1-P appears
    • Release Tab
    • Hit R with adjustments visible to cycle range/deviation and vertical shift
  • A for Add, d for drop (note uppercase vs. lowercase)
  • L for Left, r for right (ditto)
  • Read from left to right for immediately transmittable one-round adjustment

See https://ace3.acemod.org/wiki/feature/vector for all Vector 21 functionality

Vector 21 fall-of-shot function usage

Above: Vector 21 fall-of-shot function usage

FM/BG-1845 - Describing a target shape

Target shape describes the physical size and orientation of a target. Selecting the correct target shape helps supporting fires accurately engage the target area.

Point Target

A point target is used when the target occupies a small area and can be effectively engaged using a single target location.

Examples include:

  • Individual vehicles
  • Single buildings
  • Bunkers
  • Small enemy positions

Format

POINT

Linear Target

A linear target is used when the target is distributed along a line.

Examples include:

  • Trenches
  • Tree lines
  • Convoys
  • Defensive walls

Format

LINEAR, AZIMUTH [azimuth in milliradians, 0-3199], DISTANCE [length in metres] METERS

The target location previously provided acts as the start point of the line.

 

Circular Target

A circular target is used when the target occupies an area around a central point.

Examples include:

  • Compounds
  • Enemy concentrations
  • Patrol bases
  • Assembly areas

Format

CIRCULAR,RADIUS [radius in metres] METERS

Selection

Select the target shape that most accurately represents the target's physical footprint. Accurate target shape selection improves the effectiveness of supporting fires and reduces the risk of engaging unintended areas.

FM/BS-1844 - Request a Fire Mission

Line 1: Handshake

  • Establish communications with the fire support element
  • Identify yourself and declare a Fire Mission request

Format:

[Fire Support Callsign], this is [Observer Callsign], Fire Mission

Example:

ANVIL, this is WATCHMAN, Fire Mission

Fire Support Element Response:

[ Fire Support Callsign], send Fire Mission

Line 2: Target Location

  • Provide the target location using the most appropriate reference method

Format (choose one):

  • GRID [grid reference]
  • SHIFT TRP [name], NORTH/SOUTH xx, EAST/WEST xx
  • TRP [name]

Examples:

GRID 118094

SHIFT TRP ALPHA, NORTH 150, EAST 75

TRP ALPHA

Line 3: Target Description and Marking

  • Describe target type, size, protection and shape
  • Include target size, type, environment, and marking method

Format:

[type], [quantity], [protection/location], [Point OR Circle OR Linear], [shape parameters if required]

Examples:

Infantry in treeline, point target

Tank troop in the open, linear azimuth 3600, 200metres

Infantry in trench line, circle, 100metres

 

Line 4: Volume/ Duration

  • Define how much fire is required.

Format:

[Number] Rounds [Ammunition type], Danger close (if applicable), Request time of flight (If required)

Or

Continuous [duration (if required)] [Ammunition type], Danger close (if applicable), Request time of flight (If required)

Examples:

6 Rounds HE, Danger Close, Request time of flight

Continuous Smoke, 2 minutes

 

Line 5: Clearance

  • Define when the fire mission is initiated

Format:

When Ready

Or

At my command

Or

Time [HHMM]hrs

Examples:

When ready

At my command

Time 1030hrs

Fire Support Element response:

  • Readback of lines 2-5
FM/BP-1851 - Target ID format
  • Target IDs must be assigned sequentially.
  • The next fire mission receives the next available Target ID.
  • Target IDs must not be reused during the same operation.
  • All subsequent references to the target should use the assigned Target ID.

Format

T001

T002

T003

...

T999

FM/BS-1803 - Correct an incorrect readback
  • Receive the readback.
  • Confirm the receiver has correctly read back all required information.
  • If the readback is incorrect:
    • State "Negative Readback".
    • Identify the incorrect line.
    • State the correct information for that line.
    • Direct the aircraft to read back the corrected line.
    • Verify the corrected readback.
    • Repeat as required until all information is correct.
  • Proceed with request

Example

Sender:

Friendlies 200 metres north of target.

Receiver:

Negative Readback. Line 4. Friendlies 200 metres south of target. Read back Line 4.

Sender:

Line 4, friendlies 200 metres south of target.

 

FM/BS-1846 - Transmit and respond to a Message to Observer (MTO)
  • Review the fire mission request.
  • Determine whether the request is ACCEPTED, CHANGES, or DENIED.
  • Assign a Target ID if the request is ACCEPTED or CHANGES.
  • Ensure Target IDs are assigned sequentially.
  • Transmit any changes to the requested mission.
  • Transmit the Target ID.
  • Transmit the Time of Flight.
  • Receive acknowledgement from the observer.
  • Confirm a shared understanding of the mission before firing.

Fire Support Element Format

[Observer Callsign], this is [Fire Support Callsign], [Request Response], [Changes (if required)], Target ID [TXXX], Time of Flight [x] seconds

Observer Format

[Fire Support Callsign], changes acknowledged (if required), [Readback of Line 5]

Possible Request Responses

  • ACCEPTED
  • CHANGES, [changes to request]
  • DENIED, [reason]

Examples

ACCEPTED

Fire Support Element

WATCHMAN, this is ANVIL, ACCEPTED, Target ID T001, Time of Flight 24 seconds

Observer

ANVIL, AT MY COMMAND

CHANGES

Requested: 6 Rounds HE, Danger Close, At My Command but only 3 rounds are available.

Fire Support Element

WATCHMAN, this is ANVIL, CHANGES, 3 ROUNDS HE, DANGER CLOSE, Target ID T002, Time of Flight 22 seconds

Observer

ANVIL, changes acknowledged, AT MY COMMAND

DENIED

Fire Support Element

WATCHMAN, this is ANVIL, DENIED, OUT OF RANGE

Observer

ROGER, OUT

FM/BS-1847 - Communicate Fire Mission updates
  • Inform the observer of key stages of the fire mission.
  • Include the assigned Target ID in all mission updates.
  • Transmit the appropriate update as the mission progresses.
  • Receive any required acknowledgements or readbacks.
  • Continue updates until the mission is complete.

Format

[Observer Callsign], this is [Fire Support Callsign], [Target ID (if required)], [Mission Update]

Mission Updates

READY TO FIRE

  • Guns are ready to engage the mission.
  • Observer responds with:
    • ACKNOWLEDGED (if WHEN READY or TIME [HHMM]HRS)
    • FIRE (if AT MY COMMAND)

SHOT [Time of Flight if requested]

  • The first round has been fired and is in flight.
  • Observer reads back.

ROUNDS COMPLETE

  • All requested rounds have been fired.
  • Observer reads back and may issue further instructions.

SPLASH

  • Round will impact in approximately 5 seconds.
  • No response required.
  • Target ID not required

Examples

WATCHMAN, this is ANVIL, T001, READY TO FIRE

WATCHMAN, this is ANVIL, T001, SHOT, 32

WATCHMAN, this is ANVIL, T001, ROUNDS COMPLETE

WATCHMAN, this is ANVIL, SPLASH

FM/BG-1859 - Bracketing

Bracketing is a method of adjusting fire onto a target when the initial impact misses. By continuously halving corrections and alternating between ADD and DROP, the observer is guaranteed to converge onto the target without requiring any calculations.

Bracketing is particularly useful when:

  • Environmental conditions affect the fall of shot.
  • Target location accuracy is uncertain.
  • Precision targeting tools are unavailable.
  • The initial fire mission does not achieve the desired effect.

The observer may wish to issue a CHECK FIRE command and ask for individual rounds to be fired and adjusted.

Initial Brackets

Use the following initial bracket based on Observer-Target distance:

Observer-Target DistanceInitial Bracket
0-1000 metres100 metres
1000-2000 metres200 metres
Greater than 2000 metres400 metres

Adjustment Principles

  • If the impact is short of the target, use ADD.
  • If the impact is beyond the target, use DROP.
  • Always halve the previous correction.
  • Always reverse the correction direction after each adjustment.
  • Continue until the 100-metre bracket has been broken.

Breaking the 100-Metre Bracket

Once the adjustment sequence reaches 100 metres:

  • Issue ADD 50, FIRE FOR EFFECT if the impact was short.
  • Issue DROP 50, FIRE FOR EFFECT if the impact was over.

Lateral Adjustment

Lateral error may be corrected using:

  • LEFT [distance]
  • RIGHT [distance]

Major lateral deviations may be corrected during range adjustment. Fine corrections are normally made once range corrections are close to the target.

FM/BS-1848 - Control an ongoing Fire Mission
  • Monitor the fire mission and battlefield conditions.
  • Issue fire control commands to the firing element as required.
  • Adjust the fire mission as necessary to achieve the desired effect.
  • Confirm commands are understood where necessary.
  • Continue controlling the mission until it is completed or terminated.

Format

[Fire Support Callsign], this is [Observer Callsign], [Control Command]

Control Commands

FIRE

  • Execute an AT MY COMMAND mission.

CHECK FIRE

  • Immediately stop firing during a fire mission.

CANCEL CHECK FIRE

  • Resume firing following a CHECK FIRE.

CEASE LOADING

  • Stop loading additional rounds.
  • Fire any rounds already loaded.

REPEAT

  • Repeat the fire mission using the current firing data.

ADJUST FIRE

  • Adjust the point of impact onto the target.
  • Corrections may be issued using:
    • ADD [distance]
    • DROP [distance]
    • LEFT [distance]
    • RIGHT [distance]
  • Bracketing may be used to progressively adjust impacts onto the target.

FIRE FOR EFFECT

  • Following adjustments, the fire mission will be on target and the fire support element should continue with the remaining rounds.

Examples

THUNDER 1, this is SIERRA 1, FIRE

THUNDER 1, this is SIERRA 1, CHECK FIRE

THUNDER 1, this is SIERRA 1, CANCEL CHECK FIRE

THUNDER 1, this is SIERRA 1, CEASE LOADING

THUNDER 1, this is SIERRA 1, REPEAT

THUNDER 1, this is SIERRA 1, ADD 400

THUNDER 1, this is SIERRA 1, DROP 200

THUNDER 1, this is SIERRA 1, LEFT 100

THUNDER 1, this is SIERRA 1, RIGHT 50

THUNDER 1, this is SIERRA 1, ADD 50, FIRE FOR EFFECT

FM/BG-1850 - Battle Damage Assessment (BDA) Categories

Battle Damage Assessments (BDAs) are used to communicate the observed effectiveness of a fire mission against a target. Use the following categories to describe the resulting effect.

Destroyed

A target is destroyed when it can no longer function and cannot be restored to combat effectiveness.

Examples include:

  • An infantry unit is completely killed.
  • A vehicle is destroyed and reduced to wreckage.

For infantry, the number of casualties may be reported if known. Estimates are acceptable.

Neutralised

A target is neutralised when it can no longer effectively perform its combat role.

Examples include:

  • A large portion of an infantry unit is killed and the survivors are unable to continue effective combat.
  • A vehicle loses mobility, weapons, or another critical capability.

For vehicles, neutralisation may be temporary if repairs or recovery are possible.

Suppressed

A target is suppressed when its ability to observe, manoeuvre, or engage friendly forces is significantly reduced.

Examples include:

  • HE rounds forcing enemy personnel to seek cover.
  • Smoke obscuring enemy observation and lines of sight.
  • Continuous fire disrupting enemy movement and coordination.

Suppression is usually temporary and normally lasts only while the effects of the fire mission are being maintained.

Insufficient

A target is insufficiently affected when the observed results do not meet the required or desired effect, but no further engagement is requested.

This category indicates that the target remains capable of operating beyond the intended level despite the fire mission having concluded.

FM/BS-1849 - Conclude a Fire Mission
  • Determine when the fire mission is complete or no longer required.
  • Issue a CEASE LOADING command if rounds are not complete
  • Declare the end of the fire mission.
  • Provide a Battle Damage Assessment (BDA).
  • Include the target identifier and target description (optional).

Format

CEASE LOADING (if required), END OF MISSION, [Target ID], BDA [Effect], [Target Description (optional)]

 

Examples

END OF MISSION, T001, Target DESTROYED

CEASE LOADING, END OF MISSION, T025, BDA 1 TANK DESTROYED, 1 TANK DAMAGED

END OF MISSION, TARGET BRAVO, INFANTRY IN TRENCH LINE NEUTRALISED

FM/BG-1852 - Fire Mission Request quick guide
  • Line 1: Handshake 
    • [Fire Support Callsign], this is [Observer Callsign], Fire Mission
      • Fire Support Response: [Fire support Callsign], send Fire Mission
  • Line 2: Target Location
    • GRID [grid reference]
    •  TRP [name]
    • SHIFT TRP [name], NORTH/SOUTH [distance in metres], EAST/WEST [distance in metres]
  • Line 3: Target Description and Marking
    •  [type], [quantity], [protection/location], [POINT/CIRCULAR/LINEAR], [shape parameters if required]
  • Line 4: Volume/ Duration
    • [Number] ROUNDS [ammunition type], Danger Close (if applicable), Request Time of Flight (if required)
    • CONTINUOUS [duration (if required)] [ammunition type], Danger Close (if applicable), Request Time of Flight (if required)
  • Line 5: Clearance
    • FIRE WHEN READY
    • FIRE AT MY COMMAND
    • FIRE at TIME [HHMM]HRS
  • Fire Support Response: Readback of Lines 2-5
FM/BG-1856 - MTO quick guide

Fire Support Element

[Observer Callsign], this is [Fire Support Callsign], [Request Response], [Changes (if required)], Target ID [TXXX], Time of Flight [x] seconds

Observer

[Fire Support Callsign], changes acknowledged (if required), [Readback of Line 5]

Possible Request Responses

  • ACCEPTED
  • CHANGES, [changes to request]
  • DENIED, [reason]
FM/BG-1857 - Control an ongoing CFF quick guide

Format

[Fire Support Callsign], this is [Observer Callsign], [Control Command]

Possible Control Commands

  • FIRE
  • CHECK FIRE
  • CANCEL CHECK FIRE
  • CEASE LOADING
  • REPEAT


 

FM/BG-1858 - Conclude a Fire Mission quick quide

Format

CEASE LOADING (if required), END OF MISSION, [Target ID], BDA [Effect], [Target Description (optional)]

FM/BG-1853 - Example 1

HE Mission Against Infantry in a Treeline (At My Command)

Observer

ANVIL, this is WATCHMAN, Fire Mission

Fire Support

ANVIL, send Fire Mission

Observer

GRID 118094

Infantry Section, 10 Personnel, Treeline, POINT

6 ROUNDS HE, Request Time of Flight

AT MY COMMAND

Fire Support Readback

ANVIL, GRID 118094, Infantry Section, 10 Personnel, Treeline, POINT, 6 ROUNDS HE, AT MY COMMAND

Observer
WATCHMAN Readback Correct

Fire Support MTO

WATCHMAN, this is ANVIL, ACCEPTED, Target ID T001, Time of Flight 24 seconds

Observer

WATCHMAN, AT MY COMMAND

Fire Support

WATCHMAN, this is ANVIL, T001, READY TO FIRE

Observer

WATCHMAN, FIRE

Fire Support

WATCHMAN, this is ANVIL, T001, SHOT, 24

Observer

WATCHMAN, T001, SHOT, 24

Fire Support

WATCHMAN, this is ANVIL, SPLASH

Fire Support

WATCHMAN, this is ANVIL, T001, ROUNDS COMPLETE

Observer

END OF MISSION, T001, BDA DESTROYED, INFANTRY IN TREELINE

FM/BG-1854 - Example 2

Smoke Mission to Screen Friendly Movement (When Ready)

Observer

ANVIL, this is WATCHMAN, Fire Mission

Fire Support

ANVIL, send Fire Mission

Observer

SHIFT TRP ALPHA, NORTH 150, EAST 75

Enemy Observation Post, 4 Personnel, Hilltop, CIRCULAR, RADIUS 50 METERS

CONTINUOUS 2 MINUTES SMOKE

FIRE WHEN READY

Fire Support Readback

WATCHMAN, SHIFT TRP ALPHA, NORTH 150, EAST 75, Enemy Observation Post, 4 Personnel, Hilltop, CIRCULAR RADIUS 50 METERS, CONTINUOUS 1 MINUTE SMOKE, FIRE WHEN READY

Observer

Negative Readback. Line 4. CONTINUOUS 2 MINUTES SMOKE. Read back Line 4.

Fire Support

Line 4, CONTINUOUS 2 MINUTES SMOKE.

Observer

WATCHMAN, Readback Correct.

Fire Support MTO

WATCHMAN, this is ANVIL, ACCEPTED, Target ID T002, Time of Flight 18 seconds

Observer

WATCHMAN, FIRE WHEN READY

Fire Support

WATCHMAN, this is ANVIL, T002, SHOT, 18

Observer

WATCHMAN, T002, SHOT, 18

Fire Support

WATCHMAN, this is ANVIL, SPLASH

Fire Support

WATCHMAN, this is ANVIL, T002, ROUNDS COMPLETE

Observer

WATCHMAN, T002, ROUNDS COMPLETE

Observer

END OF MISSION, T002, BDA SUPPRESSED, ENEMY OBSERVATION POST

FM/BG-1855 - Example 3

Danger Close Mission Against Trench System (Mission Changed)

Observer

ANVIL, this is WATCHMAN, Fire Mission

Fire Support

ANVIL, send Fire Mission

Observer

TRP BRAVO

Infantry Platoon, 30 Personnel, Trench Line, LINEAR, AZIMUTH 1600, DISTANCE 300 METERS

6 ROUNDS HE, DANGER CLOSE, Request Time of Flight

AT MY COMMAND

Fire Support Readback

WATCHMAN, TRP BRAVO, Infantry Platoon, 30 Personnel, Trench Line, LINEAR AZIMUTH 1600, DISTANCE 300 METERS, 6 ROUNDS HE DANGER CLOSE, AT MY COMMAND

Observer
WATCHMAN Readback Correct

Fire Support MTO

WATCHMAN, this is ANVIL, CHANGES, 3 ROUNDS HE, DANGER CLOSE, Target ID T003, Time of Flight 22 seconds

Observer

WATCHMAN, changes acknowledged, AT MY COMMAND

Fire Support

WATCHMAN, this is ANVIL, T003, READY TO FIRE

Observer

WATCHMAN, FIRE

Fire Support

WATCHMAN, this is ANVIL, T003, SHOT, 22

Observer

WATCHMAN, T003, SHOT, 22

Fire Support

WATCHMAN, this is ANVIL, SPLASH

Fire Support

WATCHMAN, this is ANVIL, T003, ROUNDS COMPLETE

Observer

WATCHMAN CEASE LOADING, END OF MISSION, T003, BDA NEUTRALISED, INFANTRY IN TRENCH LINE

FM/G397 - Ground-attack weapons

FM/BG-1843 - Radar guided munitions
Definition

Radar guided munitions are precision-guided weapons that use radar systems to detect, track, and engage targets.

Primary Use
  • Suppression of Enemy Air Defence (SEAD).
  • Engagement of radar-emitting targets.
Guidance Method
  • Active Radar.
  • Passive Radar.
Common Variants
  • AGM-88 HARM
  • AGM-88E AARGM
  • AGM-84 Harpoon
FM/BG-1842 - GPS guided munitions

Definition

GPS guided munitions are precision-guided weapons that use satellite navigation and onboard guidance systems to strike pre-programmed coordinates.

Primary Use
  • All-weather precision attacks against fixed targets.
  • Engagement of targets requiring accurate coordinate-based strikes.
Guidance Method
  • Global Positioning System / Internal Navigation System (GPS/INS).
Common Variants
  • GBU-31 JDAM
  • GBU-38 JDAM
FM/BG-1841 - TV guided munitions
Definition

TV guided munitions are precision-guided weapons that use electro-optical imagery to track and engage visually identifiable targets.

Primary Use
  • Precision attacks against stationary or slow-moving targets.
  • Engagement of targets in high visibility conditions.
Guidance Method
  • Electro-Optical (EO) / Television guidance.
Common Variants
  • AGM-65A Maverick
  • AGM-62 Walleye
  • KAB-500Kr
FM/BG-1840 - Infrared guided munitions
Definition

Infrared guided munitions are precision-guided weapons that track thermal signatures emitted by targets.

Primary Use
  • Precision attacks against vehicles.
  • Engagement of targets with sufficient thermal signatures.
Guidance Method
  • Passive Infrared seeker.
Common Variants
  • AGM-65D Maverick
  • Brimstone
  • Spike-ER
FM/BG-1839 - Laser-guided munitions
Definition

Laser-guided munitions are precision-guided weapons that track reflected laser energy from a designated target.

Primary Use
  • Precision engagement of point targets.
  • Minimise collateral damage.
Guidance Method
  • Semi-Active Laser (SAL).
  • Laser Beam Riding (LBR).
Common Variants
  • GBU-12 Paveway
  • AGM-114 Hellfire
  • Advanced Precision Kill Weapon System (APKWS)
FM/BG-1838 - Unguided rockets
Definition

Unguided rockets are self-propelled explosive projectiles launched from aircraft rocket pods or pylons.

Primary Use
  • Light vehicles.
  • Infantry.
  • Structures.
Guidance Method
  • Unguided.
  • Accuracy depends on pilot aim, aircraft positioning, and firing parameters.
Common Variants
  • Hydra 70
  • FFAR
  • S-5
FM/BG-1837 - Unguided bombs
Definition

Unguided bombs are free-fall munitions that follow a ballistic trajectory after release.

Primary Use
  • Area suppression.
  • Destruction of structures.
  • Destruction of fortifications.
  • Destruction of vehicles.
Guidance Method
  • Unguided.
  • Accuracy depends on pilot aim, aircraft positioning, and release parameters.
Common Variants
  • Mk 81
  • Mk 84
  • FAB-500
FM/BG-1836 - Guns and cannons
Definition

Guns and cannons are internally or externally mounted direct-fire weapons that rely on pilot aim and aircraft positioning to engage targets.

Primary Use
  • Personnel.
  • Light vehicles.
  • Soft targets.
Guidance Method
  • Unguided.
  • Accuracy depends on pilot aim and aircraft positioning.
Common Variants
  • M61 Vulcan - 20 mm rotary cannon.
  • GAU-8/A Avenger - 30 mm rotary cannon.
  • M2 Browning - .50 calibre machine gun.

FM/G160 - Fire support planning

FM/BG-1167 - Structure of fire support elements

Fire support elements follow a three-tier hierarchy to enable scalable and organized delivery of indirect fire.

  • Battery: Coordinates up to three Sections; highest level of fire support control.
  • Section: Controls two to three Gun Teams; operates semi-independently within the Battery.
  • Gun Team: Operates a single mortar or artillery piece; composed of a Gunner and Assistant.

This structure supports scaling from squad-level support to full Batteries. The highest level of commander present takes command, Battery -> Section -> Gunner.

FM/BG-1861 - Target reference points

Target Reference Points (TRPs) are pre-planned, easily identifiable locations used by pilots, Forward Air Controllers (FACs) and Forward Observers to coordinate positions for Close Air Support and Fire Support Missions. They provide a shared reference system, allowing rapid and accurate communication without relying on grids.

TRPs are placed on prominent, recognisable terrain features (such as road junctions, buildings, hilltops, or bridges) that are visible from both air and ground. Each is given a standardised label in accordance with FM / BS-802 to ensure clarity.

FM/BG-1168 - Fire mission pre-planning

Pre-planning fire missions during the mission design or briefing phase helps ensure that indirect fire support can be delivered rapidly and accurately once operations are underway. It also enhances coordination with manoeuvre elements by reducing the time needed to identify, communicate, and engage targets.

Common components of fire mission pre-planning include:

  • Pre-Planned Targets (PPT): Plotting likely enemy positions, chokepoints, or objectives ahead of time allows for quicker engagement during execution. These targets should be labelled using standard MTO formats (see FM/BS-726) to streamline communication and avoid confusion.
  • Target Reference Points (TRPs): TRPs serve as shared map references that observers and gun crews can use to orient fire missions. They are typically placed on prominent terrain features and labelled in accordance with FM/BS-802. This practice simplifies communication and improves accuracy, particularly for on-call missions.
  • Fire Support Standards: Establishing default parameters for suppression, smoke, and general-purpose fire missions ensures consistency and saves time under pressure. These may include:
  • Fire Mission Types:
    • Pre-Planned: Coordinated before the operation and often linked to a PPT or TRP. Enables faster delivery due to known parameters.
    • On-Call: Requested dynamically during the mission. Often relies on TRPs or observer data to establish target locations quickly.

Pre-planning these elements helps ensure fire support is available when and where it’s needed, without delaying the momentum of the operation.

FM/BS-802 - Establish target reference points (TRP)

Plot target reference points, TRP, on prominent map and terrain features for the purposes of shared known points.

Label TRPs in the format "TRP [group identifier] [number 01–10]", where the distinct group identifier broadly summarises an area of operations, phase, or cardinal direction relative to friendly positions or movements. 

Examples: “TRP N01” or “TRP SE03”.

FM/BS-803 - Establish pre-planned targets (PPT)

Plot pre-planned targets, PPT, on likely targets to facilitate fast Block Not Found.

Label the PPTs with the same format as specified in Block Not Found.

FM/BS-804 - Set standard fire-support parameters

Set the following parameters prior to mission start:

  • Rounds used, volume and rate of fire for a IMMEDIATE SUPPRESSION mission
  • Rounds used, volume and rate of fire for a IMMEDIATE SMOKE mission
  • Rounds used, volume and rate of fire for a SUPPRESSION mission
  • Preferred method used for target location

FM/G113 - Callsigns (WIP)

FM/BG-1136 - Callsigns

A callsign is the identifier that is used to address another unit over radio. Every unit down to the fireteam level has a unique callsign to identify it.

Some individuals also have their own callsigns. These are generally for people with leadership or specialised roles, like the platoon commander, platoon seargeant or forward air controller.

FM/BP-586 - Callsign structure

A callsign consists of a word with a series of numerals appended. 

 

Infantry elements

For infantry elements, the following structure is used.

[company identifier] [platoon identifier] [squad identifier] [fireteam identifier]

LevelIdentifier
CompanyIdentified by a word (like “HITMAN”)
PlatoonIdentified by numbers 1 through 4
SquadIdentified by numbers 1 through 4
FireteamIdentified by ALFA, BRAVO and CHARLIE

 

Vehicle elements

For vehicle elements, a slightly different structure is used. This is only for when a vehicle element is not integrated into another element. A vehicle company is never the same as a infantry company.

[company identifier] [platoon identifier] [vehicle identifier]

LevelIdentifier
CompanyIdentified by a word (like “BUFALLO”)
PlatoonIdentified by numbers 1 through 4
VehicleIdentified by numbers 1 through 4

 

Air elements

Air elements follow a simple structure.

[flight identifier] [mission number] [vehicle identifier]

LevelIdentifier
FlightIdentified by a word (like “JESTER”)
MissionIdentified by numbers 1 through 9 (for our purposes, the mission number can be chosen arbitrarily)
VehicleIdentified by numbers 1 through 4
FM/BP-1137 - Personal callsigns

Personal callsigns are appended to the callsign of the element the individual is part of.

CallsignUser
6Company commander / platoon leader. Also or vehicle elements, but not for air elements.
7Platoon sergeant
MedicPlatoon medic (if attached)
FOForward observer (if attached)
FACForward air controller (if attached)
EODEOD (if attached)

 

FM/BS-582 - Use ACTUAL to refer to the leader of an element specifically

When needing to speak to the leader of an element specifically, and not anyone else on net who may take transmissions for the callsign (platoon sergeant/radio operators etc.), append ACTUAL after the element's callsign.

ACTUAL is never combined with a personal callsign as defined in FM/BP-1137 - Personal callsigns

FM/BS-583 - Shorten callsigns when possible

To keep radio communications brief, shorten callsigns whenever possible, according to the following rules:

  • Drop the common section of the callsign of all stations on the net (ALPHA 1-1 ←→ ALPHA 1-2 becomes (1 ←→ 2)
  • Drop the numerals when only a single station of that callsign is on the net (ALPHA 1 ←→ BRAVO 1 becomes ALPHA ←→ BRAVO)
FM/BS-584 - Use personal callsigns for the HQ element

When addressing a specific person in the HQ element, use their personal callsign. The assignment of HQ personal callsigns works in reverse from the number 9, where 9 is the commander of that callsign. Typically, the second-in-command will be 8, forward air controllers, observers or medics can be 7, 6 and so on.

  • The personal callsign will be displayed on the ORBAT.
  • Personal callsigns are never transferred to another person, even when said person is incapacitated.
FM/BS-821 - Use ALL STATIONS to address all callsigns on the network

When adressing all callsigns on a network, use ALL STATIONS instead of listing all callsigns separately.

FM/G164 - Conducting an ACE report (ACEREP) - WIP

FM/BG-590 - What is an ACE report?

An ACE Report is a quick and standardised way for a subordinate element to communicate its logistical needs to a superior element. It helps leaders maintain a clear picture of what their units require to stay combat-ready.

  • Ammo (A) – For primary and secondary weapons.
  • Consumables (C) – Short-use or expendable items (e.g. grenades, flares, medical supplies).
  • Equipment (E) – Larger or non-expendable items (e.g. vehicle track replacement, launchers, demo charges).

Note: All casualty reporting is now handled separately and does not appear in the ACE Report.

By collecting ACE Reports, leaders can consolidate requests and coordinate resupply more effectively. If many items are needed, a “full resupply” or logistics package (LOGPAK) can be requested in lieu of listing every item.

FM/BS-820 - Conduct a team level ACE report

When subordinates and their leader are co-located and can speak face-to-face, they do an ACE Report vocally at the team level.

Requesting an ACE Report (Team-Level, Vocal)Team Leader says, for example:

Team Leader: “All right, I need an ACE Report. What do you need?”

Responding to an ACE Report (Team-Level, Vocal)

  • Each person quickly checks ammo (A), consumables (C), and equipment (E).
  • If they need something, they say exactly what that is. 
  • If they don’t need anything, they can say “[NAME] ALL GREEN.”
  • The leader combines these inputs for vocal or radio transmission to superior.

NAME 1: [NAME 1] ALL GREEN

NAME 2: [NAME 2] Low on STANAG

NAME 3: [NAME 3] ALL GREEN

NAME 4: [NAME 4] BLACK on AT

FM/G117 - Sending an ACE report (ACEREP) - WIP

FM/BG-590 - What is an ACE report?

An ACE Report is a quick and standardised way for a subordinate element to communicate its logistical needs to a superior element. It helps leaders maintain a clear picture of what their units require to stay combat-ready.

  • Ammo (A) – For primary and secondary weapons.
  • Consumables (C) – Short-use or expendable items (e.g. grenades, flares, medical supplies).
  • Equipment (E) – Larger or non-expendable items (e.g. vehicle track replacement, launchers, demo charges).

Note: All casualty reporting is now handled separately and does not appear in the ACE Report.

By collecting ACE Reports, leaders can consolidate requests and coordinate resupply more effectively. If many items are needed, a “full resupply” or logistics package (LOGPAK) can be requested in lieu of listing every item.

FM/BS-589 - Give a structured ACE report

Giving an ACE report is simple - say what you need and omit anything unnecessary.

  • If nothing is needed: Say “All Green.”
  • If you have shortfalls: Say “Low on [item],”
  • If you are completely out: Say “Black on [item].”
  • If you have extensive requirements: Say “Request full resupply/LOGPAK”

Examples

  • “Low on 5.56, need grenades.”
  • “Black on AT, low on MG ammo”
  • “All Green.”
  • “Request full resupply.”

FM/G118 - Situation report (SITREP) - WIP

FM/BG-591 - What is a situation report (SITREP)?

A situation report (SITREP) is a quick and standardised way for a unit to communicate its current status to another element. It gives the information needed to make informed decisions and adjust plans if necessary.

A SITREP informs higher command of:

  • Position: Where you are
  • Activity: What your unit is doing
  • Threat: What the enemy is doing (level of contact or significant observations)
  • Status: Whether you need any assistance and your effectiveness
FM/BS-592 - Give a situation report
  1. POSITION - Where are you?
    • Block Not Found
  2. ACTIVITY - What are you doing?
    • Direction and speed of movement, if any
    • Any other relevant action your element is performing (rearming, providing overwatch,…)
  3. THREAT - What is the enemy doing?
    • Size of the enemy
    • Pressure the enemy is excerting on your element
    • Any special threats (vehicles, heavy MG, sniper,…)
  4. STATUS - What is your status?
    • Estimate of how long your element can sustain the current pressure excerted by the enemy
    • If your element is no longer able to sustain the pressure, declare “Combat ineffective”
    • If you need support (AT, medical, repair, rearm,…) state it clearly
FM/BG-818 - SITREP example

DELTA 9: DELTA 3, THIS IS DELTA 9, SITREP.

DELTA 3: 9, this is 3, WAIT OUT.

(Delay while gathering info)

DELTA 3: 9, this is 3.

DELTA 9: 3, go for 9.

DELTA 3: SITREP:

  • GRID 234-567
  • Advancing toward Objective Bravo
  • Taking intermittent sniper fire from the north
  • Requesting mortar support to suppress sniper

Alternative Response under different conditions:

DELTA 3: SITREP: 

  • Approximately 500 meters south of HILL 302
  • Going firm around crashed friendly vehicle
  • Enemy armour sighted east, possible flank
  • Combat Ineffective; vehicle disabled. Urgent AT support required
This page generated 3.39MB in 0.2573 seconds.