Getting Started Guide

1.0 Mission Statement:

United Operations is hereby established to serve as a community for fostering teamwork, simulation and cooperation in gaming. We are a mature community bound by a set of common principles:

• 1.1 - We believe that the virtues of friendship, fun, professionalism, respect, cooperation, teamwork and courtesy are more important than power.
  
• 1.2 - No member of the community shall be granted privileges, powers, protections, exemptions or otherwise receive special treatments which exceed those held or available in common. No member shall willfully act or conspire to supplant the rule of the Charter.
  
• 1.3 - All Regulars will be respected enough to have a common influence on the direction and administration of the community.
  
• 1.4 - Gaming involving tactical play and simulation is most fulfilling - although we welcome diversity in moderation.
  
• 1.5 - We value merit over title and action over pretense. All of our Regulars are valuable assets in their own way, and will excel within their domain.
  
• 1.6 - We are a free community - monies will never be requested of our Regulars, and those who ever do donate will never benefit from it.
  
• 1.7 - Freedom of speech - no Regular will be penalized for expressing his opinions. This is a community of mature people.
  
• 1.8 - We value the input of Regulars, and we are eager to devote our time and effort to educating and welcoming new additions.

Click here to view the full text of the charter - It's highly recommended that you view the full charter before playing here.

What you need to know to play with us?
* We use our custom set of modifications, including ACE, ACRE and a multitude of custom mods and maps.
* You must be on TeamSpeak with ACRE working properly to play on our servers
* We prefer tactical gameplay and realism over shooter run-and-gun gameplay.
* Keep global chatter to a minimum when slotting and briefing. Do not use global text channels in game.
* Always listen to whoever has volunteered to be the commander for a mission

What will get you banned?
* Team Killing will never be tolerated
* Lack of effort to work as a team and follow orders
* Bad attitude and disrespect towards other players
* Attempting to derail or otherwise disrupt gameplay
* "Lone Wolfing" or otherwise ignoring the teamwork aspect of how UO plays

The latest teamspeak and server information can be obtained by clicking on the following link - http://forums.united...es&folder=&id=6

Confirm that all your drivers are up to date

This step we really can't provide you with a guide. However, we have seen multiple issues arise with performance, crashes or other problems with ArmA 2 and Teamspeak 3 due to outdated or broken drivers. Make sure your drivers are all updated to the latest stables. If your running beta drivers and having issues, then we really can't help you.

List of hardware vendors for reference:
ATI - www.ati.com
Nvidia - www.nvidia.com
Intel - www.intel.com
AMD - www.amd.com

Disk based installation (non-steam)

Installling Arma II (REQUIRED TO PLAY ON SERVER)
1. Enter the serial number
2. Accept the licence agreement
3. Choose a location for the ArmA II files (c:\program files\bohiemia interactive)
4. Wait for the installation to complete
5. Choose to place a shortcut on the desktop and read the 'readme.txt' file.

Install ArmA II OA (REQUIRED TO PLAY ON SERVER)
1. Enter the serial number
2. Accept the licence agreement
3. Confirm the location to install ArmA II OA files (c:\program files\bohiemia interative)
4. Wait for the installation to complete
5. Patch ArmA II
6. Choose to place a shortcut on the desktop and read the 'readme.txt' file.

Install British Armed Forces Pack (NOT REQUIRED TO PLAY ON SERVER)
1. Enter the serial number
2. Accept the licence agreement
3. Wait for the installation to complete
4. Patch ArmA II and ArmA II OA
5. Choose to place a shortcut on the desktop and read the 'readme.txt' file.

Install Private Military Company Pack (PMC) (NOT REQUIRED TO PLAY ON SERVER)
1. Enter the serial number
2. Accept the licence agreement
3. Wait for the installation to complete
4. Patch ArmA II and ArmA II OA
5. Choose to place a shortcut on the desktop and read the 'readme.txt' file.

Or buy the 'reinforcements pack' - which includes all the above items under one serial number.

---

Steam based installation
1. Purchase ArmA II Combined Operations (ArmA II+OA) from steam (if you haven't already done so)
2. Go to your games library, click on ArmA II OA in your game list and install.
3. Enter a serial number if required.
4. Make sure you run ArmA II, ArmA II OA and any DLC packs (at least once) before starting the next steps - This will create registry links for six updater and other programs.

---

Install Current ArmA II OA / Reinforcement Patch (REQUIRED TO PLAY ON SERVER)
1. Visit www.arma2.com and grab the latest ArmA II Patch

1.60 Patch Link - http://www.kellys-he..._Update_160.zip

Install Teamspeak 3 (REQUIRED TO PLAY ON SERVER)
1. Install teamspeak 3
2. If your using a 64 bit operating system (control panel -> system to find out) then download the 64 bit client of teamspeak.
3. If you're using a 32 bit operating system (control panel -> system to find out) then download the 32 bit client of teamspeak.

Install Six Updater (REQUIRED TO PLAY ON SERVER)
1. Install Six Updater 2.9.x (http://cdn.withsix.com/software/su/su-setup.exe)
2. Click on the following link to install the Unite Operations Primary Server repository - sixupdater://six.unitedoperations.net/srv1.yml
3. Select the 'Server UnitedOperations.net Primary Server' from the list on the left
4. Click just below the green hexigon button at the top and select 'install and update' from the drop down list.

When this gets done you should be ready to join the server.

Common Locations

We need to confirm exactly where your ArmA2, ArmA2 OA and TeamSpeak 3 files are installed. If you know where these are, just confirm it. Otherwise, follow the steps below and save these locations in notepad.

Non Steam Installation
C:\Program Files\Bohemia Interactive\ArmA 2
C:\Program Files (x86)\Bohemia Interactive\ArmA 2

Steam Installation
C:\Program Files\steam\steamapps\common\ArmA 2
C:\Program Files (x86)\steam\steamapps\common\ArmA 2
C:\Program Files\steam\steamapps\common\ArmA 2 Operation Arrowhead
C:\Program Files (x86)\steam\steamapps\common\ArmA 2 Operation Arrowhead

TeamSpeak 3
C:\Program Files\TeamSpeak 3 Client
C:\Program Files (x86)\TeamSpeak 3 Client

Manual Location Discovery
If you do not know where the folders are located you can follow these instructions to also find the folders (Vista & Windows 7 only):

1. Start the program you cant find (ArmA2, ArmA2OA, TS3)
2. Right click your task bar, and click task manager
3. Click the "Processes" Tab
4. Find the process you are trying to locate

ArmA2.exe
ArmA2OA.exe
ts3client_win32.exe
ts3client_win64.exe

5. Right click the appropriate process, and click "Open File Location"

Once you have clicked "open file location", a folder browser window will open showing you the location of the file that is running. Repeat the steps above for any folder locations that you need to find.

---

Confirm that your installations are correct for ArmA II, ArmA II Operation Arrowhead, and TeamSpeak 3

Six Updater requires certain registry keys to be correct (as they should be anyways) to auto-detect the locations and files to install, update and launch the game. These should already setup and correct for you. However, there are two main scenarios that these will not be correct:

1. You have moved some of the folders after installing them
2. You have Steam versions of the games, and have never launched them from steam

In these circumstances, its best to follow the instructions below.

Steam Installation
In order to ensure that your configuration is good in steam - you must launch each game from Steam at least once. Additionally, to be on the safe side, you should launch steam as Administrator to do this. So, the steps are as follows:

1. Launch Steam as Administrator
2. Launch ArmA 2 from the Library (if applicable)
3. Close ArmA 2
4. Launch ArmA 2 Operation Arrowhead from the Library (if applicable)
5. Close ArmA 2 Operation Arrowhead

This should ensure that your system is setup correctly for Six Updater with steam installs of the game.

Non Steam Installation

Verify that the following registry path's point to the correct folders for their appropriate game folders (A2 & A2OA)

32-bit Windows
HKEY_LOCAL_MACHINE\SOFTWARE\Bohemia Interactive Studio\ArmA 2
HKEY_LOCAL_MACHINE\SOFTWARE\Bohemia Interactive Studio\ArmA 2 OA

64-bit Windows
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bohemia Interactive Studio\ArmA 2
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bohemia Interactive Studio\ArmA 2 OA

TeamSpeak 3

Click your start menu, and type "regedit". Launch regedit. Browse to one of the following locations: [indent]Registry Locations
(2 Possible Locations)

HKEY_LOCAL_MACHINE\SOFTWARE\TeamSpeak 3 Client
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TeamSpeak 3 Client

Double click "(Default)", change the string to the location of your teamspeak 3 folder (ex C:\Program Files\TeamSpeak 3 Client)

---

Confirm that TeamSpeak 3 and ArmA2 Operation Arrowhead are set to launch as Administrator

Now that we have confirmed our registry settings are okay, and we have already found the locations of our files, lets take the easy route to make sure that these will always run as administrator. This helps prevents issues with ACRE. Browse to the folder locations of ArmA2 OA and TeamSpeak 3, and right click each of their respective executable files and select "Properties".

arma2oa.exe
ts3client_winXX.exe

Download Six Updater

In order to play on the server you will need to download and install Six Updater. Six Updater is management program for mods and maps. You can download Six Updater by visiting http://cdn.withsix.com/software/su/su-setup.exe

---

Installing Six Updater
Once you have downloaded the Six installer from the link above you will see an icon which looks similar to the one below:

Double click on this icon to begin the installation process. The next screen you should encounter is the one below:

Click on the 'Next >' button to proceed. The next screen is detailed below:

The installer is asking you where you want to place the six updater files. Next you'll see two screens which are filling in your name / organisation and a screen of legal information, click 'Next >' for both:

The final screen you should see before installing is a summary of information - Just double check before you install that the 'Destination Folder' is correct:

Installation of Six Updater should now begin, usually this process is very quick and you may not see any installation bar. When it's over you'll get a screen similar to this to let you know everything was successful.

United Operations Six Updater Repository

Once you have Six Updater installed and working then you need to import the United Operations Primary Server Repository. This 'repo' will download all the maps, mods and teamspeak alterations you will need to play on the server (for other UO servers just duplicate the preset).

UO Primary Server Repo : sixupdater://six.unitedoperations.net/srv1.yml - Just click on this link once Six Updater is installed to import the repo.

---

Installing the UO Repository

Once you click on the link to the repository you should see something similar to the image below:

Notice that the blue areas on the screen, this signifies that items are ready to install. Other colours that you may see are 'green' - good to go and 'yellow' - something needs updating. Now we need to check how six is configured.

---

Checking Six Updater

In order to check where Six Updater is storing your files you need to go to the blue button in the top left of the window and click on it, a drop down box should appear and you need to select the menu item 'options'. Once you have done that a screen similar to this will pop up (except without the funky arrows):

---

Understanding Six Updater - A tab guide - Home Tab

---

Understanding Six Updater - A tab guide - Preset Tab

---

Understanding Six Updater - A tab guide - Game Profile Tab

---

Understanding Six Updater - A tab guide - Server Tab

Installing / Updating the UO Repository

If you haven't done so see 3.1 Checking Six Updater. This details the UO repository you need to use, once you click on this link you will see something similar to the image below:

Below you will see an image of what you need to select in order to start the installation process of the mods from the UO repository for the primary server.

After you have finished downloading then all section should be marked in green like the image below, if they aren't then re-run the install / update procedure again. If they refuse to go green then your best course of action is to jump onto Teamspeak and ask for help from any regular.

The repository changes a fair amount but the process to update it does not, just make sure the drop down is set to 'install / update mods' and click on the green button (above it) to update to the latest version.

Before jumping on the primary server - check the following

1. Make sure you're running ArmAII OA and teamspeak 3 in administrator mode.
2. Make sure that your ArmA II profile is set to the same one you use in Six Updater
3. Make a duplicate preset and connect to the testing server to make sure teamspeak, ACRE and ACE are all working correctly.

If you have a problem with any of the items located in this guide then jump on teamspeak and ask any regular for help. They have all been where you are now and will help if they have the time (DO NOT JUMP INTO THE GAMING CHANNELS AND ASK FOR HELP - this will get you banned quickly).

Q: When I am in game, I get an "ACRE not connected to TeamSpeak Error".
A: One of the following steps may be your problem:

1. Make sure you are running both A2 and TS3 as Administrator
2. Confirm that jayarma2lib installed properly in your ArmA2OA folder
3. If you have somehow manually installed ACRE or JayArmA2Lib, make sure to "Convert to Six" these mods in SixUpdater.

Q: When I connect to the server, I receive "Session Lost", "Missing downloadable content" or a "Signature Verification Error".
A: This means that one or more of your mods have not properly installed, or files are corrupt. Run the "Verify and Repair" action inside of Six Updater after making sure the UnitedOperations server is selected (bold).

Q: Why does Six Updater re-install itself all the time?
A: This is because Six Updater is constantly under development by Sickboy, and is constantly in contact with the Officer staff at UO for improvements which can be made to help stream line peoples installation & updating processes.


Q: I don't think my mods are properly updated, what do I do?
A: If you are ever in doubt that the files are somehow invalid, or that things did not update correct (even if the Mods are "GREEN"), then the best course of action is to select the "Verify and Repair" action. This will re-verify all files in your current installation against our servers.


Q: How do I pick one of the alternate sound mods available on the UO repository?
A: Make sure that the "Server UnitedOperations.Net - Primary Server" preset option is selected first. Then, select the "Custom Repos" tab in the middle of the Six Updater program. Then right click the optional modification you want to use, and click the "Add to Preset" button. This will then add that optional mod to your preset and you can now properly install and update this mod.


Q: How do I give Six Updater the password to the server to auto-connect to it? Q: Do I always have to use Six Updater to Launch the Game?
A: Make sure that the "Server UnitedOperations.Net - Primary Server" preset option is selected first. Click the "Server Browser" tab. The UO primary server should be the only one listed here. Scroll this window all the way to the right hand side, and you should see a field titled "Saved Password". Enter the current game server password here, and Six is now able to auto-join the game!


Q: Why doesn't UO use the official Six Network?
A: Many times United Operations utilizes either custom builds of mods, older stable versions, or beta/development versions depending on circumstances and stability; we put our mod pack through much more extreme testing prior to allowing them to reach the UO community and servers. It is much easier for us to run a completely separate, non-standard modset rather than having to patch or otherwise fiddle with current mainline installations.

Radio Handling


ACE Interact Key


Weapons


More Weapons


Formations


Formations Continued ...


Medical & Casualties

United Operations Radio Procedures Guide

By Zedic

Table of Contents
1. The Basics of Communication
a. Introduction
b. ABCs of communications
c. Information filtering

2. Components of All Radio Transmissions
a. Call signs
b. Initiating traffic
c. Message
d. Ending traffic

3. Types of Nets, Frequencies, and Proper Utilization (TS3, ArmA2 & VON)
a. Frequencies
b. Nets
c. Teamspeak 3 and ArmA2 plugin
d. Squad level communication (whisper / normal / yell / shortwave)
e. Platoon level communication / lower means
f. Task force operations net / higher means
g. Fire support control net

4. Reports and Returns
a. Radio check
b. Message
c. Sitrep (situation report)
d. Locstat (location status / report)
e. Contact report
f. Request for supplies
g. Request for transport (APC / Helicopter)
h. Request for reinforcements / support
i. Request for close air support (CAS / Helicopter)
j. Request for close air support (CAS / Fixed Wing)
k. Request for direct fire (Tanks / APCs)
l. Request for indirect fire / fire mission (Squad leader to follow forward observer or artillery)

5. Common Call Signs
a. List of call signs

6. Prowords

7. In closing


1. The Basics of Communication

a. Introduction

This tutorial is designed to give you a basic understanding of military radio procedure without getting too in-depth. It is meant as a tool to be used and enhance your playing experience, as well optimize the communication amongst your team or group.

I have customized this particular version so that it is more useful in ArmA2 and I hope you learn the valuable information therein. Take notes on specific 'reports and returns' (perhaps even write it on a 'post it' and stick it on the side of your monitor for quick reference), and the only way to get better at anything within this guide is, of course, to "PRACTICE!" Thanks for reading.

b. ABCs of Communications

Now were actually into the real information. The following are the ABC's of communication.

ACCURACY: It pays to be sure of what your saying. Don't be the fool stuck correcting himself twenty plus times just to get a single message out. Always double check your grids. TAKE THE TIME TO THINK OF WHAT TO SAY, DO NOT JUST SAY IT! DON'T BE THAT GUY!

BREVITY: No one likes a chatty cathy, keep your traffic brief and to the point. Avoid long winded answers or requests. Again, as stated before, TAKE THE TIME TO THINK OF WHAT TO SAY! CUT THE CRAP OUT, AND GET THE BARE MINIMUM NEEDED FOR THE RECEIVING CALLSIGN TO GET THE MESSAGE!

CLARITY: Now this one is difficult because of Teamspeak, VON (Voice Over Net), computers, people from all over the world etc. However, as best as you can, be clear on what your trying to say. Put the coffee down, take the smoke out, if your dipping spit before you talk, and if English is not your first language then slow down what your saying and speak up.

c. Information Filtering

This point should be straight forward. Do not send irrelevant information. If you notice a "friendly squad" on the objective, DO NOT CALL IT IN. Everyone should know it's there. Of course tell your squad mates, however do not send that to the 'Commanding Officer (CO)'. Be very careful of what you send. The more you talk, the less people with something important to say can.

Turn on the filter in your brain. If, you do not have one here is the solution, Don't squad lead or command.



2. Components of All Radio Transmissions

The following is the rough breakdown of a transmission so you can understand what goes where and why.

a. Call Signs

Every type of unit, every type of squad, and every type of command element has a different call sign. Just from the call sign name itself you can usually tell what type of unit that is, whether it's a mechanized infantry squad or perhaps an attack helicopter squadron. It is very important to know so that you have an idea of 'whose who in the zoo'. Specific call sign types are discussed later in this tutorial, just at this point understand that everyone on the radio should have a call sign.

b. Initiating Traffic

When sending traffic, the first thing you should always say is the 'recieving call sign'. It allows everyone to know whom your trying to contact and thus allowing you two to send traffic. The second thing you should say is your call sign.

"Apache 1, this is Apache 2."

If the receiver hears you, their own acknowledgment is very simple. All they have to say is one of two things. The receiving call sign can say their own call sign

"Apache 1."

or they can say the proword "SEND" after they've already said their Callsign.

"Apache 1, Send"

This is the most cruical instance in any traffic. If the receiver doesn't know your talking to them they could be killed by that enemy you attempted to warn them of.

c. Message

The meat and potatoes of any transmission. Once you establish contact with the call sign you wish to speak to, there are a few things you must remember while keeping in mind the ABCs throughout.

The first thing to remember is that BEFORE EACH TRANSMISSION, ENSURE YOU SAY YOUR CALL SIGN! The second thing to remember is to ensure you say "OVER" at the end of each transmission. In some cases if the end of your sentence is understood then it may not be required, however, saying it is better than not.

"Apache 2, did you get that Baconator from Burger King yet, OVER"
"Apache 1, roger, OVER."
"Apache 2, OK.... Where's Mine, OVER."
"Apache 1, the dog ate it, OVER."
"Apache 2, roger, you're dead, OUT."

d. Ending Traffic

The sending call sign is responsible for ending the Transmission. There is only one exception and that is if the receiver has a higher 'rank / position / command' then that of the sender. All you have to do is at the end of your last message in which you expect no reply once the traffic is basically finished, instead of "OVER", just say "OUT". However, DO NOT SAY OVER AND OUT! It's just not proper radio procedure and is... well ... dumb.

"Apache 1, negative OVER."
"Apache 2, you will be, OUT."


3. Types of Nets, Frequencies, and Proper Utilization (TS3 & ArmA2 & VON)

a. Frequencies

A frequency is the group of numbers that you will be using to transmit on using the Teamspeak 3 plugin for ArmA2. Depending on the type of radio you are using (long range (LR) or short range (SR)) will decide which frequency range you can dial in. A frequency is one of the most important factors when it comes to communications. It is the difference between being able to talk with your fellow team mates and coordinate properly or not.

When communicating a frequency, the standard format will be saying the first number before the decimal points as a whole, then the word “AND”, followed by the last part as a whole.

"FREQ: 3.314" would be spoken as “THREE AND THREE ONE FOUR”

Having the decimal as an "AND"

"FREQ: 29.225" would be spoken as “TWO NINE AND TWO TWO FIVE”.

The following is the frequency bands that each of the two types of radios run on:

Long Range Radios (LR) - 3.000 - 30.000 (Max effective range: 10Km)
Short Range Radios (SR) - 30.000 - 300.000 (Max effective range: 700m)

b. Nets

A net is a frequency that has been deemed for a specific group, whether it be for a squad, platoon, headquarters, or a call for fire net. It is just the term used for which ever frequency you are speaking on as opposed to calling it by numbers. During missions the commander will designate which frequencies will be for what nets.

“Squad ones net will be three and three one four. Close air supports net will be three and three one six and headquarters net will be three and two zero zero”.

c. Teamspeak 3 and the ArmA2 Plugin

Teamspeak 3 is what all of these new communications levels are based on. Through the newly adopted 'plug-in' system incorporated through ArmA2 we are able to hone our communications skills to an entirely new level. However, with this new system comes new hurdles as well. Currently the system does not allow more than one person to broadcast at one time intentionally. This is realistic so ensure that once your transmission is complete that you end your broadcasting as soon as possible so as to not be “hot mic-ing or perma-sending” on the net. With this new system all personel will be required to exercise discipline on the radio.

d. Squad Level Communication (whisper / normal / yell / shortwave)

Squad Level Communication is just that. It is the lowest form of communication in game and does not require call signs for individuals. If you are speaking using the “whisper / normal / yell” settings, just use names of persons within the squad or fire team. The short range radio is used for the squad leader to his fire team leaders, or (depending on the mission) platoon leaders to their squad leaders (depending on range). Call signs will be used on the short range radio.

e. Platoon Level Communication / Lower Means

Platoon level communication is platoon leader to squad leaders, or mission commander to his squad leaders (mission dependent). This type of communication is done via the long range radio and is to be used for official purposes only. This net is considered a command net and is not for unnecessary chatter. Since the new radio system only allows for one person to speak at a time, radio discipline will be most important when on this net as it is the direct orders net for your lower level leadership. The following is a list of reports and returns that should be sent through the lower means to the platoon commander for him to communicate on higher means.

i. Message
ii. Sitrep
iii. Locstat
iv. Contact report
v. Request for supplies
vi. Request for transport (APC / Helicopter - Initial request just to get things going, remaining coordination done directly with pilots via own squad / platoon frequency)
vii. Request for reinforcements / support
viii. Request for close air support (Initial request just to get things going, remaining coordination done directly to pilots via your own squad / platoon frequency)

f. Task Force Operations Net / Higher Means

Task force operations / command net is the means with which the task force / mission commander communicates to all the element leaders for their orders and for asset coordination. The task force net is referred to as "HIGHER MEANS" because on it you can get a hold of all the element commanders and the air / artillery assets. Keeping in mind that everyone can hear your traffic, the ABCs of communication have never been more important, so keep your communications appropriate. The following "reports and returns" are recommended for higher means use.

i. Request for transport (APC / Helicopter)
ii. Request for reinforcements / support
iii. Request for close air support (Helicopter)
iv. Request for close air support (Fixed wing)
v. Request for direct fire (Tanks / APCs)
vi. Request for indirect fire (Artillery)

g. Fire Support Control Net

Fire support control net is used by forward air controllers and forward observation officers. There could be two different nets for each depending on the amount of assets currently in use. This net is specifically for the forward observation officer (FOO) and forward air controller (FAC) to be able to have direct control over his guns or aircraft without interruptions. With respect to artillery guns, they will always remain on this net and receive all fire missions via the FOO. Rotary aircraft will often have to change their frequencies once receiving their inital orders via the FAC to the calling station (person requesting air support). Fixed wing aircraft will remain under the control of the FAC throughout, however situation will dictate.

h. ArmA2 Voice Over Network (VON)

The Voice Over Network (VON) is not at all affected by the new ArmA2 Teamspeak3 plugin. It can still be used as a backup system or as a primary depending on the situation. All the same rules for communication still apply.


4. Reports and Returns

a. Radio Check

This is used for confirming radio status. It can be used for individual call signs or as a collective.

Individual:
“Warrior 1, this is warrior 1'1, radio check, OVER?"
"Warrior 1, loud and clear, OVER."
"Warrior 1'1, loud and clear, OUT."

Collectively:
"All callsigns warrior, this is warrior 1, radio check, OVER?"

Please note on an all call signs you can just say your call sign. However, you report in the alphabetical order, based on the order of march or based on how the commander sets it. SO WAIT YOUR TURN!

Reply from all call signs:
"Warrior 1'1."
"Warrior 1'2."
"Warrior 1'3."
"Warrior 1'4."
"Warrior 1, loud and clear, OUT."

b. Message

This is used for sending long messages, the proword "MESSAGE" is used prior to being sent.

"Warrior 1, this is warrior 2, message, OVER?"
"Warrior 1, send, OVER"
"Warrior 2, Dredge needs to go, his cookies are burning in the oven, OVER"
"Warrior 1, roger, loser.... OVER"
"Warrior 2, OUT."

c. Sitrep (Situation Report)

Situation reports should be sent every ten to twenty minutes. The following is the preferred format:

Para A: Initiate traffic with receiving call sign.
Para B: Send grid of your call signs location and displacement (spread out 50m east to west or holding a building)
Para C: Current situation at grid (We are moving through, we are holding here, we are defending this position, we are staging for attack)
Para D: Own Actions (What do you plan on doing)
Para E: Administrative points (Do you need anything? Ammo? Medical? Supplies? Reinforcements?)

A typical sitrep will look like this:

"Warrior 1, this is Warrior 1'3, sitrep, OVER."
"Warrior 1, send, OVER."
"Warrior 1'3, Grid 079 987, centered on grid and spread north west to south east, 40 meters, more to follow, OVER."
....
"Warrior 1, OVER."
"Warrior 1'3, we are observing a possible enemy weapons cache and enemy infantry in area of grid 079 979, more to follow, OVER."
....
"Warrior 1, OVER."
"Warrior 1'3, will advise if come under contact but my intent is to hold firm, more to follow, OVER."
....
"Warrior 1, OVER."
"Warrior 1'3, Request helicopter recon of possible enemy cache on forementioned, how copy?"
"Warrior 1, solid copy on all, reference request, wait, OUT."

d. Locstat (Location Status / Report)

The preferred method of a locstat (location status report):

Para A: Initiate traffic with receiving call sign.
Para B: Send grid of position and displacement.
Para C: Send grid of intended destination.

A typical locstat will look like this:

"Tango 1, Tango 1'2, locstat, OVER."
"Tango 1, Send, OVER."
"Tango 1'2, My loc, grid 0898 1155, moving west to gid 0884 1161, OVER."
"Tango 1, roger, OVER."
"Tango 1'2, roger, OUT."

e. Contact Report

With a contact report you need to gather your information quickly, so you can send it as soon as possible. The initial message sent to command is a 'contact, wait, out' while you sort yourself out.

The preferred way of giving a contact report:

Para A: Initiate traffic with receiving call sign.
Para B: Send grid of enemy position and target description, send subsequent grids and descriptions as required.
Para C: Your actions / intent.
Para D: Required support.

A typical contact report will look like this:

"Apache 6, this is Apache 1, contact, wait, OUT."
....
*Apache 1 collects all the necessary information and is ready to send.*
....
"Apache 1, contact report, OVER.”
“Apache 6, send, OVER.”
"Apache 1, grid 0983 1143, 1 times enemy tank and squad of infantry, BREAK."
"Apache 1, targets are stationary and firing on our position, BREAK."
"Apache 1, my squad is holding firm and engaging the enemy infantry while moving out of view of the armour, BREAK."
"Apache 1, request close air support on enemy armour at forementioned grid, will laze on call, OVER."
"Apache 6, solid copy on all, lightning 2'1 will be on your station and is being dispatched to you now, ETA 45 seconds, laze now, OVER."

Subsequent messages will follow, but then this becomes a CAS request (see below).

f. Request for Supplies

The preferred way of requesting supplies:

Para A: Initiate traffic with receiving call sign.
Para B: Send requesting call sign and lower frequency.
Para C: Grid of supply drop requested and color of smoke to mark position.
Para D: LZ (Landing Zone) Status (See PROWORDS) and approach vector (Bearing from which you want the helicopter to come in from)

A typical supply request will look like this:

"Slayer 6, This is sandman 1, requesting supply drop, OVER."
....
*Squad leader marks rough position on map with the icons if able*
....
"Slayer 6, roger, send, OVER."
“Sandman 1, call sign sandman 1 on freq three and three zero zero zero, OVER.”
“Slayer 6, three and three zero zero sero, roger, OVER.”
"Sandman 1, grid 1178 9654, will mark with purple smoke, BREAK."
"Sandman 1, LZ green, approach from south east, how copy? OVER."
"Slayer 6, solid copy on all, supplies inbound, call sign dust off 1'1 will be on your station, ETA 2 minutes, OVER."
"Sandman 1, 2 minutes, OUT."

g. Request for Transport (APC / Helicopter)

The preferred way of requesting transport:

Para A: Initiate traffic with receiving call sign.
Para B: Send requesting call sign and lower frequency.
Para C: Send grid of pick up position and type of marking (on the squad leader, west side of building, on smoke - Just inform them where to land if necessary)
Para D: LZ (Landing Zone) Status (See PROWORDS) and approach vector (Bearing from which you want the helicopter to come in from)
Para E: Helo on approach and marking LZ with smoke or flares.

A request for transport (Helicopter / APC) might look like this:

"Apache 6, Apache 3, request helo extraction / APC pick up, OVER?"
"Apache 6, roger, Send, OVER."
“Apache 3, call sign apache 3'A on freq three zero and one one one, OVER.”
“Apache 6, freq three zero and one one one, OVER.”
"Apache 3, grid 125 656, north side of hill in the valley, BREAK."
"Apache 3, LZ green, approach from west / pick up point secure, OVER."
"Apache 6, roger, helo inbound, call sign dust off 1'1, 50 seconds / APC en route, ETA 3 minutes, OVER."
"Apache 3, roger, OUT."
....
"Apache 3, this is dust off 1'1, inbound, 1km, pop smoke, OVER."
"Apache 3, roger, purple smoke, OVER."
"Dust off 1'1, eyes on purple smoke, OUT."

h. Request for Reinforcements / Support

This is the preferred format for requesting reinforcements or support:

Para A: Initiate traffic with receiving call sign.
Para B: Send your grid and where you need said reinforcements / rendevous grid.
Para C: What the tast of the reinforcements is.
Para D: Further coordinating instructions (Ensure they bring a specific kit, supplies, an extra medic)

A request for reinforcements or support might look like this:

"Warrior 1, this is Warrior 2, request for infantry support, OVER."
"Warrior 1, send, OVER."
"Warrior 2, my loc grid 5456 3415, send support to my loc, BREAK."
"Warrior 2, have them hold on that grid in ambush for enemy armour and infantry, BREAK."
"Warrior 2, ensure they bring javelin and gpmg, how copy?"
"Warrior 1, solid copy, reinforcements to grid 5456 3415, acquiring kit and will be en route, eta 6 minutes, OUT."

i. Request for Close Air Support (Helicopter)

This is the preferred way of requesting CAS:

Para A: Initiate traffic with receiving call signs.
Para B: Send requesting call sign and lower frequency.
Para C: Send target grid, type of target and request munitions for target.
Para D: If danger close mission, send grid of your location, mark your position with colored smoke.
Para E: Send attack vector (Bearing / cardinal point from which you want the helicopter to approach the target) and confirm if enemy anti-air vehicles are in the area.
Para F: Marking the target (Lazing or smoke) and squad leader clearing him hot.

A request for CAS (Helicopter) might look like this:

"Slayer 6, this is Warrior 1, requesting close air support, OVER."
"Warrior 1, go for Slayer 6, OVER."
“Warrior 1, call sign Warrior 1'1 on freq three and three three three zero, OVER.”
“Slayer 6, call sign Warrior 1'1, freq three and three three three zero, OVER.”
"Warrior 1, target grid 0204 1385, 1 time enemy armour, request hellfire on target, how copy? OVER."
"Slayer 6, copy all, target, enemy armour, grid 0204 1385, OVER."
"Warrior 1, roger, attack vector south east, no enemy AAV sited, OVER."
"Slayer 6, roger, south east, outlaw 1'1 will be inbound and on your station, eta 2 minutes OVER."
"Warrior 1, roger, OVER."
....
*2 Minutes pass and they are in area*
....
"Warrior 1, this is outloaw 1'1, on your station, 1200m from target, OVER."
"Warrior 1, roger, marking target, red smoke.OVER"
"Outlaw 1'1, red smoke, OVER."
"Warrior 1, cleared hot, OVER."
"Outlaw 1'1, cleared hot, OUT."

After that confirm if target was destroyed and conduct a Battle Damage Assessment (BDA).

j. Request for Close Air Support (Fixed Wing)

This is the preferred way to request close air support (fixed wing):

Para A: Initiate traffic with recieving call sign.
Para B: Send target grid, type of target and requested munitions for target.
Para C: If danager close mission send grid of your location, mark your position with colored smoke.
Para D: Send attack vector (Bearing / cardinal point from which you want the aircraft to approach the target) and confirm if enemy anti-air vehicles are in the area.
Para E: Lazing target on the pilots command and squad leader clearing him hot.

A request for close air support (fixed wing) looks like this:

"Slayer 6, this is Headhunter 5, requesting close air support, OVERR."
"Headhunter 5, go for Slayer 6.”
“Headhunter 5, roger, target grid 0308 5464, 1 times enemy AAV, requesting bomb, OVER."
"Slayer 6, I confirm grid 0308 5464, enemy AAV, bomb, OVER."
"Headhunter 5, roger, attack vector north west, recommend dive on target, egress north east, OVER."
"Slayer 6, wilco, eta 1 minute, laze now."
"Headhunter 5, lazing now *wait for the laze to stick and reply with* spot on, cleared hot!"
"Slayer 6, cleared hot, OUT."
"bombs away"
"Headhunter 5, good hit, target destroyed."
"Slayer 6, target destroyed, OUT."

Slayer 6 was a forward air controller relaying to the fixed wing aircraft all the information. When he said 'cleared hot, OUT' he switched frequencies to send all data to the plane to commence it's attack run. He can send this info via VON if necessary. Slayer 6 transmitted bombs away to let headhunter 5 know the munitions were en route.

k. Request for Direct Fire (Tanks / APCs)

The preferred way to request direct fire from a tank or APC:

Para A: Initiate traffic with receiving call sign.
Para B: Send grid of target, type of target and requested munitions for target.
Para C: Send reference point for fire (bearing, building, prominent feature)
Para D: Confirm shots on target, if not adjust fire.

A request for direct fire from a tank or APC might look like this:

"Saber 1'2, this is Apache 4, request direct fire, OVER."
"Saber 1'2, send, OVER."
"Apache 4, grid 1454 6332, enemy infantry, request HEAT / HEI-T, OVER"
"Saber 1'2, grid 1454 6332, enemy infantry, ROGER."
"Apache 4, roger, left hand edge of tree line, suppress area, OVER."
"Saber 1'2, roger, firing NOW."
"Apache 4, adjust fire slightly left."
"Saber 1'2, slightly left, ROGER."
"Apache 4, on target."
"Saber 1'2, ROGER."
"Apache 4, check fire, good shooting, OUT."

l. Request for Indirect Fire / Fire Mission (Squad Leader to Forward Observer or Artillery

The preferred way to request for indirect fire / fire mission:

Para A: Initiate traffic with receiving call sign.
Para B: Send grid of target and bearing to target.
Para C: Type of target and type of mission, (screen, suppression or saturation)
Para D: Confirm shot.
Para E: Confirm splash, followed by corrections as required.

A request for indirect fire / fire mission might look like this:

"Steel Rain, this is Apache 1, fire mission, OVER."
"Steel Rain, Fire Mission, Send, OVER."
"Apache 1, Ten figure grid 15478 85284, bearing 010, OVER?"
"Steel Rain, grid 15478 85284, bearing 010, OUT."
"Apache 1, roger, enemy infantry on position, request saturation, OVER."
"Steel Rain, enemy infantry, saturation, OUT."
"Apache 1, roger, OVER."
"Steel Rain, roger, OUT."
"SHOT."
"Apache 1, shot, OUT"
"SPLASH."
"Apache 1, splash, OUT."

If adjustment is required, send new grid or adjustment and proword 'REPEAT'.

"Steel Rain, this is Apache 1, OVER."
"Steel Rain, SEND."
"Apache 1, adjust fire to ten figure grid 15378 85284 / adjust fire 100 west, repeat, OVER?"
"Steel Rain, grid 15378 85284 / 100 west, OUT."
"Steel Rain, SHOT."
"Apache 1, shot, OUT."
"Steel Rain, SPLASH."
"Apache 1, splash, OUT."


5. Common Call Signs To Be Used (Subject to Change on COs Order)

INFANTRY – Warrior; Cowboy; India
HMMWV/LIGHT VEHICLES – Bronco; Rabbit; Victor
MEDICAL – Starlight; Serpent; November
APC/IFV – Warhorse; Aegis; Zulu
ARMOUR – Warpig; Crusher; Tango
ROTARY ATTACK – Azreal; Gunfighter; Tumbler
ROTARY TRANSPORT – Dust Off; Shackdown; Oscar
FIXED WING ATTACK – Vader; Showtime; Maverick
FOO/FAC – Twisted; Slayer; Chaos
COMMAND – Duke; Apollo; Zero

6. Prowords

General Terms

SAY AGAIN - Say your last transmission as I did not understand it
ROGER - I understand
WILCO - Will Comply
HOW COPY - Did you receive last traffic
SOLID COPY - I got it, I understand
GOOD COPY - Same as above
ACK - Acknowledged
SEND - Send your transmission
MORE TO FOLLOW - More information coming
I CONTINUE - I am continuing last message
BREAK - Used to divide up points and allow a break in your transmission for other to interrupt if necessary
CONTACT - I am engaged by effective enemy fire
WAIT - Wait.....
OVER - My message is complete
OUT - This transmission is complete
REPEAT - Repeat last Fire Mission or Close Air Support Mission
LOC (Said like the word "LOCK") - Location
CHECK FIRE - Cease firing
RV - Rendezvous Location
ORV - Objective Rendezvous Location, the position to move to the Objective from.
FIGURES - Numbers to Follow
OSCAR MIKE - On the Move
LUP - Lying Up Point
LOWER MEANS - Refers to a Sub-Call Sign Net
HIGH MEANS – Refers to a Parent Call Sign Net

Aircraft Terms

RTB - Returning to Base
BINGO - Mission fuel spent
WINCHESTER - Mission ammo spent
SPOT ON - Target is Lazed
CLEARED HOT - Aircraft cleared to engage target
LZ - Landing Zone
LZ GREEN - Landing Zone Clear and Secure
LZ YELLOW - Landing Zone is receiving sporadic enemy, move in with caution
LZ RED - Landing Zone area is in Contact and engaged
LZ HOT - Helo will not touch down, Enemy in immediate area of Landing Zone
RAS – Restricted Air Space

7. In Closing

Thanks for reading, I hope you learned something but this stuff only works if you practice. If you do not know the "phonetic alphabet", search for it in Google. I'd also like to recommend that if you want to hear this type of radio procedure watch the mini-series "Generation Kill", some great examples to follow.

Lastly, if you have any questions, or think I need to make some corrections, please inform me and I will do my best to answer/solve the issue.

Zedic