FM/C231 - Fire Support Communications

---

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

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.”

• 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.

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

• 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 

• 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

• 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.

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

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”.

• 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

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.

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.

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.

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.

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.”

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.”

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.”

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.

Above: Vector 21 data automatically populating into the ATragMX

• 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

• 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

Above: Vector 21 fall-of-shot function usage

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.

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

• 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

• 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.

• 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

• 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

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:

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.

• 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

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.

• 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

• 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

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]

Format

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

Possible Control Commands

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

Format

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

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

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

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

Use standard responses to confirm or clarify fire mission instructions then confirm readiness to fire or request further clarification if unsure.:

Release methods determine the timing and coordination of fire across multiple guns. Each method balances speed, control, and desired effects on the target:

Read back and comply with the release method given by the controller.

Give clear fire control commands during release phases, repeat commands as needed for safety or synchronization.

Clear status updates from gun crews allow fire controllers to track progress, synchronize timing, and manage ammunition effectively. 

Consistent use of brevity enables:

• Timely follow-up orders
• Safe fire stoppage if needed
• Effective BDA (Battle Damage Assessment) sequencing

See FM/BS-1149 - Communicate within a fire support element using the correct brevity for required prowords.

Use the correct brevity within a crew/section/battery to communicate effectively:

Fire support elements must remain flexible and safe to accommodate changing conditions or emerging hazards. Using safety controls ensures responsive and safe fire support delivery under pressure.

Understand safety control orders to stop or repeat a fire mission in a timely manner: