Updated: 2023-08-11 --- # Tactical Communication Fundamentals ## Talk Short One of the most important concepts is to exercise communications brevity. Consider every word and if it adds meaning to the transmission. - Avoid filler words, e.g. don't say “roger that” when “roger” will do - Utilize standard units in order to omit them to the maximum extent practical - Use Prowords to shorten transmission and improve clarity ## Talk Secure Utilize secure communications to the maximum extent practical (DCS permitting), avoid passing friendly positions over unsecured nets, utilize codewords to the extent required >[!note] >When conducting PVE operations with vCSG-3, all communications are assumed to be secure ## Push to Talk, Not Push to Think Have the transmission ready to go and all information available before you key the mic. If you key the microphone and can't remember what you want to say or misspeak, simply unkey the mic, take a breath, and key again. If you find yourself halfway through a transmission and you are making repeated mistakes or lose a piece of information you need, unkey the mic and prepare, then start again. # Tactical Communication Formats Many tactical communication formats follow a similar pattern, they have a particular order information is passed in, called lines, and line names or numbers are usually omitted in order to improve coms brevity. Using these formats requires both sides to know or have a format reference in order to understand the information being passed. However, if the formats are known, communication can be much faster. >[!example] Example: MNPOPCA Check in >Line 1 Mission Number: DCA1101 >Line 2 Number and type of aircraft: 2 Hornets >Line 3 Position and altitude: marking mom's 123/45 Angels 20 >Line 4 Ordnance: 6/0/2 >Line 5 Playtime: 2+00 >Line 6 Capabilities: No alibis >Line 7 Abort Code: no code > >Sample Transmission: >"Closeout, Camelot-1-1 Checking in DCA1101, 2 Hornets marking mom's 123/45 Angels 20, 6/0/2, 2+00, No alibies, standing by for tasking" # Tactical Callsigns In tactical communication, the calling station first states the callsign of the receiving station, then their own callsign. Callsigns are stated at the beginning of the transmission. >[!quote] Winder-1-1 >"Closeout, Winder 1-1, Radio Check" In certain situations, only the sending or receiving units callsign may be stated. Units may have an admin callsign and a tactical callsign. In CSG-3, the admin callsigns are the squadron callsign plus the modex and are used when communicating with CATCC. Admin Callsigns can be shortened to just the modex. >[!Example] Admin Callsign >“Bengal 401" The tactical callsigns are the squadron callsign plus the flight number and the number within the flight. Tactical callsigns are used on all tactical nets and with field based ATC. >[!example] Tactical Callsign >"Winder-1-3" When operating as a flight, the tactical call sign without the second number is a collective callsign for the whole flight >[!example] Collective Callsign >"Winder-1" # Prowords Prowords are words with pre-arranged meaning that are intended to facilitate understanding and brevity. See the Brevity Manual: [[APPENDIX A - ALSSA BREVITY LIST]] Prowords are not intended to conceal meaning. In order to use prowords effectively, both parties must be familiar with their meaning. Two commonly misused prowords are [[APPENDIX A - ALSSA BREVITY LIST#OVER |OVER]] and [[APPENDIX A - ALSSA BREVITY LIST#OUT direction|OUT]]. Over and Out have opposite meanings and are never used together. Over and Out are not commonly used on informal nets like tactical control nets. Two other commonly misused prowords are [[APPENDIX A - ALSSA BREVITY LIST#ROGER|ROGER]] and [[APPENDIX A - ALSSA BREVITY LIST#WILCO|WILCO]]. Since the meaning of roger is contained within wilco, they are never used together. # VAW-126 Specifics When operating as a tactical controller in vCSG-3, several standards are used to improve professionalism and standardization on the radio. When acknowledging a transmission that does not require a specific response from the controller, the controllers callsign should be used without any additional words. >[!quote] Aircraft >"Closeout, Winder-3-4 Engaging Target India November 01, Time on Top 05, will come back with BDA" >[!quote] Controller >"Closeout" When handling an informal/abbreviated check-in on a new frequency for a controlled asset, the controller should always respond with a "Hey you, this is me" followed by "Loud and Clear" (if the asset is in fact loud and clear), and either "Radar Contact" if the asset can be found in the scope, "Looking", if the controller is still looking for them on the Scope or "Negative Contact" if the controller cannot find them on the scope. Additionally if an [[APPENDIX A - ALSSA BREVITY LIST#ALPHA CHECK|ALPHA CHECK]] has not been conducted, and it makes sense to do so, conduct one. >[!quote] Aircraft >"Closeout, Bengal-2-1 on Jade" >[!quote] Controller >"Bengal-2-1, Loud and Clear, Radar Contact"