BETA / LIVE
FMDG Communications - Radio Comms (Staging) - UNITAF Force Manual (FM)




FM/C57 - FMDG Communications - Radio Comms (Staging)
The FM outlines our core skills, policies and guides to ensure every member stands ready for the mission ahead.



FM/G180 - Radio networks (WIP)

FM/BP-1139 - Squad radio network

A squad network is the lowest network in use. All squad members that have a radio are a part of it and can transmit on it. 

A squad radio network is not transactional, but using correct prowords is encouraged. 

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/G251 - Squad radio communications

FM/BG-1171 - Usage of a squad radio network

The squad network is the primary network most people will find themselves listening to and transmitting on. It's primary function is to facilitate the smooth operation of the squad.

Because all squad members (if they have a radio atleast) are part of the squad network, it allows for good situational awereness for all squad members. This also means that all squad members are aware of the tasking of their team and that of the other teams, enabling an easy succession of command when needed.

 

The squad leader should be the primary transmitter on the squad radio network. Most communication between fireteams should flow over the squad network. This keeps everyone's situational awereness up to date, and reduces misunderstandings, as verbal communication in hectic situations can become increasingly hard to understand.

Other than the squad leader, the fireteam leaders in turn use the squad radio network to communicate with the squad leaderm. They also occasionally communicate with their buddy teams over the radio in situations like bounding maneuvers, where shouting might not reach far enough in loud environments.

FM/BS-1170 - Transmit on a squad network as a squad leader

As a squad leader, make liberal use of the squad network to communicate:

  • Orders to fireteams or buddy teams
  • Intent and information about the current mission
  • Contact reports from other elements when relevant
  • Any other information that is relevant to the entire squad
FM/BS-1172 - Transmit on a squad network as a fireteam leader

As a fireteam leader, make use of the squad network to communicate:

  • With the squad leader
  • Orders to team members when shouting would be ineffective
  • Contact reports verbally given by members of the fireteam
FM/BS-1169 - Transmit on a squad network as a squad member

As a squad member, do not transmit on the radio network unless:

  • The information is urgent
  • Shouting would not reach the intended recipient
  • As a reply to a question over the radio
Back to
No Previous Chapter
Forward to
No Next Chapter
This page generated 1.55MB in 0.1633 seconds.