Radio Procedure

Zedic's Military Radio Procedure Adaptation.
Ladies and Gentleman,

My name is Zedic and I was just browsing these forums and discovered the debriefing thread. I read that someone requested that we need to improve our communication over TS, In-Game, and Mumble for those that use it. Therefore, I will post my own adaptation of real Military Radio Procedure that I have developed over years for use in games such as this. So far in my time this has been the most effective use of communication I have come across and have had many tournaments and armys therein I was in command of adopt, utilize, and most importantly win because of effective communication. So....lets get it started.


RADIO PROCEDURE


Table of Contents

1. The Basics of Communication
a. Introduction
b. ABCs of Communications
c. Information Filtering

2. Components of All Radio Transmissions
a. Callsigns
b. Initiating Traffic
c. Message
d. Ending Traffic

3. Types of Frequencies and Proper Utilization (TS/I-G/MBL)
a. In-Game Communications
b. Teamspeak
c. Mumble

4. Reports and Returns
a. MESSAGE
b. SITREP (Situation Report)
c. LOCSTAT (Location Status/Report)
d. CONTACT REPORT
e. REQUEST FOR SUPPLIES
f. REQUEST FOR TRANSPORT (APC/Helicopter)
g. REQUEST FOR REINFORCEMENT/SUPPORT
h. REQUEST FOR CLOSE AIR SUPPORT (Helicopter)
i. REQUEST FOR CLOSE AIR SUPPORT (Fixed Wing)
j. REQUEST FOR DIRECT FIRE (Tanks/APCs)

5. Common Callsigns To Be Used for PR (Subject to Change on COs Order)
a. Disclaimer
b. List of Callsigns

6. Prowords

7. In Closing


The Basics of Communication



a. Introduction

This Tutorial is designed to give you a basic understanding of Military Radio Procedure without getting too far into it. 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 Project Reality and I hope you learn the valuable information that is has to offer. 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 qucik reference....yes I've done that once....), 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 20 + times just to get a single message out. Always double check your grids. TAKE THE TIME TO THINK OF WHAT TO SAY, DON'T 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, 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 and forward. Do not send irrelevant information. If you notice a "FRIENDLY SQUAD" on the Objective, DO NOT call it in. Everyone should know its there. Of course tell your squad mates, however do not send that to the 'Commanding Officer'. Be very careful of what you send. The more YOU talk, the less people can hear, and then people get killed cause you wanted to mention how Daddy killed the cat for new Violin strings.

Turn on the filter in your brain. IF, you do not have one here is the solution....DON'T SQUAD LEAD OR COMMAND. Thank you.




Components of All Radio Transmissions
The following is the rough breakdown of a Transmission so you can understand what goes where and why.



a. Callsigns

Every type of unit, every type of squad, and every type of Command Element has a different Callsign. Just from the Callsign name itself you can usually tell what type of Unit that is, whether its a Mechanized Infantry Squad, or perhaps an Attack Helicopter Squad. Callsigns are very important to know so you have an idea of 'whose who in the zoo'. Specific Callsigns types are discussed later in this tutorial, just at this point understand that everyone on the Radio should have a Callsign.


b. Initiating Traffic

When sending Traffic the FIRST thing you should always say is the RECEIVING CALLSIGN. It allows everyone to know whom your trying to contact and thus allowing you to send Traffic effectively. The SECOND thing you should say is YOUR CALLSIGN.
(e.g. "SQUAD 1, THIS IS SQUAD 2.")

If the Receiver hears you, their own acknowledgment is very simple. All they have to say is one of two things. Either the RECEIVING CALLSIGN can say their own Callsign only (e.g. "SQUAD 1."), or they can say the proword "SEND" after they've already said their Callsign. (e.g. "SQUAD 1, SEND")

This is the most CRUCIAL instance in any Traffic. If the Receiver doesn't know your talking to them they could just quickly 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 Callsign you wish to speak to there are a few things you must remember otherwise your good to just speak. Keeping in mind the ABCs though. The FIRST thing to remember is that BEFORE EACH TRANSMISSION, ENSURE YOU SAY YOUR CALLSIGN!

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.

(e.g. "SQUAD 2, DID YOU GET THAT BACONATOR FROM BURGER KING YET, OVER."
"SQUAD 1, ROGER, OVER."
"SQUAD 2, OK.....WHERES MINE, OVER."
"SQUAD 1, THE DOG ATE IT."
"SQUAD 2, ROGER, YOUR DEAD.")


d. Ending Traffic

The SENDING CALLSIGN is responsible for ending the Transmission. There is only one exception and that is if the Receiver was a higher 'Rank/Position/Command' then that of the Sender. This is very simple, all you must do is at the end of your last message in which you expect no reply from once the Traffic is basically finished, insead of "OVER", just say "OUT". HOWEVER, DO NOT SAY OVER AND OUT! Its just not proper Radio Procedure and is...well.... Dumb.

(e.g."SQUAD 1, NEGATIVE, OVER."
"SQUAD 2, YOU WILL BE, OUT.")




Types of Frequencies and Proper Utilization (TS/I-G/MBL)


a. In-Game Communications

Squad Level Communication is just that. It is the lowest form of communication in game and does not require Callsigns for individuals, just use names of persons within the squad. Although the only point I am going to make with respect Squad Level chat is if the Squad Leader is talking, SHUT UP!

Squad Leader to Commander Communication should be the most commonly used type of any. This is considered the "Lower Means" for all intensive purposes. Speaking directly to the Commander is how 75% of all your communication as a Squad Leader should be. The remaining 25% is there for times when you must use TeamSpeak to coordinate with other Squads and Assets. The following is a list of Reports and Returns that should be sent through the "Lower Means" to the Commander.
i. MESSAGE (unless it is to another Squad Leader)
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 to Pilots via TEAMSPEAK))
vii. REQUEST FOR REINFORCEMENT/SUPPORT
viii. REQUEST FOR CLOSE AIR SUPPORT (Initial Request just to get things going, remaining coordination done directly to Pilots via TEAMSPEAK)


b. Teamspeak

Teamspeak is the primary Support and Asset Coordination means. This is refered to as "HIGHER MEANS" because on it you can get a hold of all the Squad Leaders and the Air Assets. Keeping in mind that everyone can hear your Traffic, the ABCs of Communication have never been more important, so keep your Communications approapriate.

The following "REPORTS AND RETURNS" are recommended for Teamspeak use, however a preliminary message to the Commander (unless you are under fire) is advised prior to sending it.
i. REQUEST FOR TRANSPORT (APC/Helicopter)
ii. REQUEST FOR REINFORCEMENT/SUPPORT
iii. REQUEST FOR CLOSE AIR SUPPORT (Helicopter)
iv. REQUEST FOR CLOSE AIR SUPPORT (Fixed Wing)
v. REQUEST FOR DIRECT FIRE (Tanks/APCs)


c. Mumble

This program has only been brought to my attention as of late. I have used it a few times quite well and my best recommendation is for all Squads to have atleast one member with it on. Mumble is a phenomenal program for communicating with friendly Squad Leaders, APCs, or Transport Helicopters WITHOUT sending loads of Traffic through Teamspeak.

Mumble is not a Callsign use as you must be close to the person you are trying to talk to. That being said, use it as though you walked up to someone and were talking to them. FYI, when doing that, in the Military we call that a "FACE-TO-FACE", used to discuss the plan quickly and coordinate on the ground rather than other Frequencies.




Reports and Returns
The Real Information


a. MESSAGE

USED FOR SENDING LONG MESSAGES. PROWORD "MESSAGE" IS SAID PRIOR TO BEING SENT.

"SQ 1, THIS IS SQ 2, MESSAGE, OVER?"
"SQ 2, SEND."
"SQ 1, KATANAMA NEEDS TO GO, HIS COOKIES ARE BURNING IN THE OVEN, OVER"
"SQ 2, ROGER, I KNEW HE WAS A BAKING NANCY, OVER."...."
"SQ 1, OUT."[/COLOR]


b. SITREP (Situation Report)

SITUATION REPORTS SHOULD BE SENT EVERY 10 MINUTES. THE FOLLOWING IS THE FORMAT

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND GRID OF SQUAD LOCATION AND DISPLACEMENT (e.g. spread out 50m east to west, or holding on building etc.)
PARA C: CURRENT SITUATION AT GRID (We are moving through, we are holding here, we are defending this position, we are staging for attack, we are receiving no enemy in area and are secure etc)
PARA D: OWN ACTIONS (What do you plan on doing)
PARA E: ADMINISTRATIVE POINTS (Do you need anything? Ammo? Medical? Supplies? Reinforcements? Etc?)

A SITREP WILL LOOK LIKE THIS:

"COMMAND THIS IS SQ 3, SITREP, OVER."
"COMMAND SEND."
"SQ 3, GRID B6 K8, CENTERED ON GRID AND SPREAD NORTH-WEST TO SOUTH-EAST 40 METERS, BREAK."
"SQ 3, WE ARE OBSERVING A POSSIBLE ENEMY WEAPONS CACHE AND ENEMY INFANTRY IN AREA OF GRID C6 K9, BREAK."
"SQ 3, WILL ADVISE IF COME UNDER CONTACT BUT MY INTENT IS TO HOLD FIRM, BREAK."
"SQ 3, REQUEST HELICOPTER RECON OF POSSIBLE ENEMY CACHE ON FORE-MENTIONED GRID, HOW COPY?"
"COMMAND, SOLID COPY ON ALL, REFERENCE REQUEST, WAIT, OUT."



c. LOCSTAT (Location Status/Report)

THIS IS VERY BASIC AND SIMPLE, ALMOST UNREQUIRED BECAUSE OF THE MAP, HOWEVER HERE IT IS REGARDLESS.

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND GRID OF POSITION AND DISPLACEMENT
PARA C: SEND GRID OF INTENDED DESTINATION

A LOCSTAT WILL LOOK LIKE THIS:

"COMMAND, SQ 2, LOCTSTAT, OVER."
"COMMAND, SEND."
"SQ 2, MY LOC (Location), GRID G2K4, MOVING WEST TO GRID E2K7, OVER?"
"COMMAND, ROGER."
"SQ 2, ROGER, OUT."



d. CONTACT REPORT

**NOTE** WITH A CONTACT REPORT YOU NEED TO GATHER YOUR INFORMATION QUICKLY SO YOU CAN SEND IT ASAP. THE INITIAL MESSAGE SENT TO COMMANDER IS A "CONTACT, WAIT, OUT" WHILE YOU SORT YOURSELF OUT.

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
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 CONTACT REPORT WILL LOOK LIKE THIS:

"COMMAND, SQ 1, CONTACT, WAIT, OUT."
"COMMAND, SEND."
*Squad 1 gathers information and is ready to send*
"SQ 1, CONTACT, GRID A6K9, 1 TIMES ENEMY SQUAD ON POSITION, SECOND CONTACT, GRID A6K6, 1 TIMES ENEMY TANK AND APC, BREAK."
"SQ 1, TARGETS ARE STATIONARY AND FIRING ON OUR POSITION, BREAK."
"SQ 1, MY SQUAD IS HOLDING FIRM AND ENGAGING THE ENEMY INFANTRY WHILE MOVING OUT OF VIEW OF THE ARMOUR, BREAK."
"SQ 1, REQUEST CLOSE AIR SUPPORT ON ENEMY ARMOUR AT FORE-MENTIONED GRID, WILL LAZE ON CALL, OVER?"
"COMMAND, SOLID COPY ON ALL, ATTACK HELO IS ON STATION AND BEING DISPATCHED TO YOU NOW, ETA 45 SECONDS, LAZE NOW, OVER."

And subsequent messages will follow, but then this becomes a CAS request. The CONTACT REPORT is over.



e. REQUEST FOR SUPPLIES

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND GRID OF SUPPLY DROP REQUESTED AND COLOUR OF SMOKE TO MARK POSITION.
PARA C: LZ (Landing Zone) STATUS (See PROWORDS) AND APPROACH VECTOR (Bearing from which you want the helicopter to come in from)

A SUPPLY REQUEST WILL LOOK LIKE THIS:

"COMMAND, THIS IS SQ 4, REQUESTING SUPPLY DROP, OVER?
*Squad Leader marks rough position on Map with the Commo Rows*
"COMMAND, SEND."
"SQ 4, GRID C3K8, WILL MARK WITH PURPLE SMOKE, BREAK."
"SQ 4, LZ GREEN, APPROACH FROM SOUTH-EAST, HOW COPY?"
"COMMAND, SOLID COPY, SUPPLIES INBOUND, ETA 2 MINUTES."
"SQ 4, 2 MINUTES, ACK, OUT."



f. REQUEST FOR TRANSPORT (APC/Helicopter)

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND GRID OF PICK UP POSITION AND TYPE OF MARKING (On the Squad Leader, West side of Building, on smoke, etc. Just inform them where to land if necessary)
PARA C: LZ (Landing Zone) STATUS (See PROWORDS) AND APPROACH VECTOR (Bearing from which you want the helicopter to come in from)

A REQUEST FOR TRANSPORT [HELICOPTER/APC] LOOKS LIKE THIS:

"COMMAND, SHADOW 1, REQUEST FOR [HELO EXTRACTION/APC PICK-UP], OVER?"
"COMMAND, SEND."
"SHADOW 1, GRID E4K6, NORTH SIDE OF HILL IN THE VALLEY, BREAK."
"SHADOW 1, [LZ GREEN, APPROACH FROM WEST/PICK UP POINT SECURE], OVER."
"COMMAND, ROGER, [HELO INBOUND, DUST-OFF IN 20 SECONDS/APC EN ROUTE, ETA 3 MINUTES], OUT."

*From there on out, it is recommended you use Mumble or Teamspeak to coordinate directly to the pilot if possible, if not, then have the Commander relay.*



g. REQUEST FOR REINFORCEMENT/SUPPORT

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND YOUR GRID, AND WHERE YOU NEED SAID REINFORCEMENTS/RENDEVOUS GRID
PARA C: WHAT THE TASK OF THE REINFORCEMENTS IS
PARA D: FURTHER COORDINATING INSTRUCTIONS (e.g. Ensure they bring a specific kit, supplies, an extra medic, etc)

A REQUEST FOR REINFORCEMENTS/SUPPORT LOOKS LIKE THIS:

"COMMAND, THIS IS SQUAD 6, REQUEST FOR INFANTRY SUPPORT OVER?"
"COMMAND, SEND."
"SQ 6, MY LOC, GRID B5K6, SEND SUPPORT TO GRID B5K9, BREAK."
"SQ 6, HAVE THEM HOLD ON THAT GRID IN AMBUSH FOR ENEMY ARMOUR AND INFANTRY, BREAK."
"SQ 6, ENSURE THEY BRING A HAT KIT AND LMG, HOW COPY?"
"COMMAND, SOLD COPY, YOUR SUPPORT IS SQ 5, WILL INFORM THEM OF THEIR TASK. OUT."

*Alternatively, this can be done over TeamSpeak so that all the Squads can hear what you need. As well the Commander will be saved from having to repeat such a long message.*



h. REQUEST FOR CLOSE AIR SUPPORT (Helicopter)

*THIS SHOULD BE DONE ON TEAMSPEAK DIRECTLY TO THE HELICOPTER*

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND TARGET GRID, TYPE OF TARGET, AND REQUESTED MUNITIONS FOR TARGET
PARA C: IF DANGER CLOSE MISSION, SEND GRID OF YOUR LOCATION, MARK YOUR POSITION WITH COLOURED SMOKE
PARA D: SEND ATTACK VECTOR (Bearing from which you want the helicopter to approach the target) AND CONFIRM IF ENEMY ANTI-AIR VEHICLES ARE IN THE AREA
PARA E: LAZING THE TARGET ON THE PILOTS COMMAND AND SQUAD LEADER CLEARING HIM HOT.

A REQUEST FOR CLOSE AIR SUPPORT (Helicopter) LOOKS LIKE THIS:

"VADER FLIGHT, THIS IS SQ 2, REQUESTING CLOSE AIR SUPPORT, OVER?"
"SQ 2, GO FOR VADER FLIGHT."
"SQ 2, TARGET GRID F4K6, 1 TIMES ENEMY ARMOUR, REQUEST HELLFIRE ON TARGET, HOW COPY?"
"VADER, COPY ALL, TARGET, ENEMY ARMOUR, GRID F4K6, OVER."
"SQ 2, APPROACH VECTOR SOUTH-EAST TO TARGET, NO ENEMY AAV SITED, OVER?"
"VADER, ROGER, SOUTH-EAST, IN-BOUND NOW, ETA 1 MINUTE."
"SQ 2, ROGER." *1 Minute passes and they are in area*
"SQ 2, THIS IS VADER, CONFIRM TARGET IS LAZED."
"SQ 2, LAZING NOW *wait for the laze to stick the reply with...* SPOT ON, CLEARED HOT!"
"VADER, CLEARED HOT."

*After that confirm if target was destroyed etc etc.*



i. REQUEST FOR CLOSE AIR SUPPORT (Fixed Wing)

*THIS SHOULD BE DONE ON TEAMSPEAK DIRECTLY TO THE AIRCRAFT*

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
PARA B: SEND TARGET GRID, TYPE OF TARGET, AND REQUESTED MUNITIONS FOR TARGET
PARA C: IF DANGER CLOSE MISSION SEND GRID OF YOUR LOCATION, MARK YOUR POSITION WITH COLOURED SMOKE
PARA D: SEND ATTACK VECTOR (Bearing from which you want the helicopter 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:

"DARK STAR (Bomber), THIS IS SHADOW, REQUESTING CLOSE AIR SUPPORT, OVER?"
"SHADOW, GO FOR DARK STAR."
"SHADOW, ROGER, TARGET GRID D3K8, 1 TIMES ENEMY AAV, REQUEST BOMB, OVER?"
"DARK STAR, I CONFIRM, GRID D3K8, ENEMY AAV, BOMB ARMED, OVER."
"SHADOW, ROGER, ATTACK VECTOR NORTH-WEST, RECOMMEND DIVE ON TARGET."
"DARK STAR, WILCO, ETA 20 SECONDS, LAZE NOW."
"SHADOW, LAZING NOW, *wait for the laze to stick and reply with* SPOT ON, CLEARED HOT!"
"DARK STAR, CLEARED HOT, BOMBS AWAY."
"SHADOW, GOOD HIT, TARGET DESTROYED."
"DARK STAR, TARGET DESTROYED, OUT."




j. REQUEST FOR DIRECT FIRE (Tanks/APCs)

*THIS SHOULD BE DONE ON TEAMSPEAK DIRECTLY WITH TANKS, OR ON MUMBLE!*

PARA A: INITIATE TRAFFIC WITH RECEIVING CALLSIGN
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, etc)
PARA D: CONFIRM SHOTS ON TARGET, IF NOT ADJUST FIRE

A REQUEST FOR DIRECT FIRE LOOKS LIKE THIS:

"TANGO 1'2, THIS IS SQ 4, REQUEST DIRECT FIRE, OVER."
"TANGO 1'2, SEND."
"SQ 4, GRID E3K6, ENEMY INFANTRY, REQUEST [HEAT/HEI-T], OVER?"
"TANGO 1'2, GRID E3K4, ENEMY INFANTRY, ROGER."
"SQ 4, ROGER, LEFT-HAND EDGE, OF TREE LINE, SUPPRESS AREA, OVER?"
"TANGO 1'2, ROGER FIRING NOW."
"SQ 4, ADJUST FIRE SLIGHTLY LEFT."
"TANGO 1'2, SLIGHTLY LEFT, ROGER."
"SQ 4, ON TARGET."
"TANGO 1'2, ROGER."
"SQ 4, CHECK FIRE, GOOD SHOOTING, OUT."



Common Callsigns To Be Used for PR (Subject to Change on COs Order)

a. Disclaimer

The following Callsigns are mostly gathered from movies or other media and are in no way definite Military Callsigns as that would be a breach of Operational Security.


b. List of Callsigns

The following Callsigns can have numbers after the name to denote different Squads, e.g. the actual Squad number at the end, but the name just tells the type of Squad. However with vehicles, such as tanks, it is advised to give them two numbers. e.g. Three tanks are in the SAME Squad, lets say Squad 1, their Callsigns should be something like "WARPIG 1'1; WARPIG 1'2; WARPIG 1'3, alternatively you can use Letters too; WARPIG 1'ALPHA; WARPIG 1'BRAVO; WARPIG 1'CHARLIE. If you contact "WARIPIG 1" then that is refering to ALL TANKS within that Squad.

INFANTRY - WARRIOR; FOXHOUND; INDIA
HEAVY WEAPONS SQUAD - HUNTER; TAKEDOWN; LIMA
MAIN BATTLE TANKS - WARPIG; IRON KNIGHT; TANGO
ANTI-AIR VEHICLES - VULCAN; STARGAZER; X-RAY
ARMOURED PERSONNEL CARRIERS - WARHORSE; STRYKER; ZULU
LIGHT VEHICLES (HMMWV/FAST ATTACK VEHICLES) - RACER; BLITZ; VICTOR
SUPPLY TRUCKS - RHINO; TRUCK; UNIFORM
TRANSPORT HELICOPTERS - DUST-OFF; SHAKEDOWN; HOTEL
ATTACK HELICOPTERS - VADER; SHOWTIME; WHISKEY
RECON HELICOPTERS (AH-6, MEC SCOUT, ETC) - HAWKEYE; AZREAL; OSCAR
FIXED WING FIGHTER - MAVERICK(Anything from Top Gun); JOKER; YANKEE
FIXED WING BOMBER - DARK STAR; SMOKEY; NOVEMBER
SNIPERS/RECON - SHADOW; VIPER; SIERRA; ROMEO
SPECIAL FORCES - EAGLE; RENEGADE; KILO; JULIET
LOGISTICS - CHECKMATE; BLUEBELL; OSCAR
COMMANDER - COMMAND; ZERO; CHAOS; BOSSMAN; CHIEF; GODFATHER




Prowords


General Terms

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
BREAK - Used to divide up points, use when changing topics, or when your running out of time using the "In-Game" chat.
SEND - Send your transmission
MORE TO FOLLOW - More information coming
I CONTINUE - I am continuing last message
CONTACT - I am engaged by effective enemy fire
WAIT - Wait.....
OVER - My message is complete
OUT - This transmission is complete
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.
SAY AGAIN - Send your last traffic
REPEAT - Repeat last Firemission or Direct Fire Attack
FIGURES - Numbers to Follow

Aircraft Terms

RTB - Returning to Base
BINGO - Mission fuel spent (In this instance, we will use it for needing repairs)
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

Will edit as I think of things, but right now I am unable to...




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 are in that.

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/resolve the issue.

Zedic

More shit

RADIO CHATTER
"Roger" - I understand your last
"Wilco" - I understand your last and will comply with your orders
"Over" - I am finished with my transmission and am awaiting a reply
'Out" I am finished with my transmission and do not want a reply
"Say Again" - Please repeat your last transmission (DO NOT USE “REPEAT” FOR THIS TASK)
"I Say Again - " – I am repeating my last transmission (DO NOT USE “REPEAT” FOR THIS TASK)
“Correction - “ - There was an error in my last transmission, the following is correct
“Wait One” - I am pausing for a few seconds
“Wait Out” - I am pausing for more than a few seconds
“Break; Break” - I am done with one conversation but I am initiating another.


Other Radio Terms / Uses

Radio Check:
Radio check is used to check your comms with another callsign, who will rate the clarity and strength of your transmission

“[Other Callsign] This is [Your Callsign]. Radio check. Over” - [Other Callsign] what is my volume and clarity?

Other callsign will reply:

[Signal Strength] ----And--- [Signal Clarity]

Loud......................................Clear
Good......................................Readable
Weak......................................Unreadab le
Very Weak..............................Distorted
Fading With Interference........Intermittent

(Alternate Code 5 system)
5 being loudest, clearest.
1 being quietest, most distorted.

EXAMPLE:
Bravo one, this is Hotel three. Radio check, over.
Hotel three, this is bravo one, I read you loud and clear, over
Bravo one, this is hotel three, Roger, out.


SALUTE REPORT:
The SALUTE report is used to notify a commander/other element of another force (Usually enemy) under your surveillance. Report goes as follows:

“[Other Callsign] this is [Your Callsign]. Stand by for SALUTE report, over.”
Other callsign should roger that and stand by for report.

The report:
You should name what line you're transmitting so that both you and the receiver do not get lost

Line Sierra – [Size of Force]
Line Alpha – [Activities of force]
Line Lima – [Location of force (Using PR's A#KP# coordinates)]
Line Uniform – [Unit identification (Markings, symbols, uniforms, etc.)]
Line Tango - [Time and date (Specify what time zone (I would use UTC or “Zulu” time) for PR)]
Line Echo – [Equipment used by force (Weapons, body armor, vehicles, assets, etc.)]




EXAMPLE (Taken from Generation Kill):
“Brown horse this is White horse. Stand by for SALUTE report 2-1, over.”
“White horse, this is brown horse. Stand by to copy. Over.”

[WHITE] Line Sierra – 2-0 personnel
Line Alpha – Patrolling what appears to be a headquarters.
Line Lima – 38 Sierra Papa Victor 344329
Line Uniform – Republican Guard
Line Tango - 2-3 March 2-0-0-3, 1-7-3-0 Zulu
Line Echo – AK-47s, and RPKs
I'll copy so far, over.

[BROWN] Yeah, say again line Lima, over.

[WHITE] Roger, I say again. Line Lima, – 8 Sierra Papa Victor 344329

[BROWN] Solid copy, do you have any remarks, over?

[WHITE] Roger. All personnel appear to be on guard, very weak posture. Over.

[BROWN] Roger, solid copy on all. Out.