After event 320 we discussed communication brevity over package comms. Sometimes tactical calls can drag on and interrupt more important messages. Threat bullseye's and Fox calls can clutter up communications and step-on important information such as SAM launches/Defensive/Offensive calls. In low intensity situations it's a good idea to call threat bullseye's and Fox-3 shots, but in the high intensity situations we encounter most events these can clutter up communications.
What to say on Package Communications
1. Engaged Offensive (their)Bullseye Strength. "Falcon1 Engaged Offensive 133-54 two-ship"
2. Engaged Defensive Type (your)Bullseye. "Hornet2 Engaged Defensive Adder 033-55"
3. SAM Launch(Visual) Direction/Position. "SAM Launch Tivat Airbase"
4. Singer(RWR Launch) Type Direction/Position. "Singer 17 West of Bullseye"
5. Mud(RWR/Visual) Type Direction/Position. "Mud 2 Target"
6. RTB Reason. "Lobo1 RTB Dakota"
7. Package Directives: "Package retrograde south" "Package continue As-Fragged" "Lobo1 orbit South, Falcon engage Mud 2"
8. Immediate Danger Directives: "Panther1 bandit your-six 5-miles 10-thousand" "Hornet1 Fox-2 Inbound Break Break Break"
What not to say on Package Communications
1. Giving Information not needed. "Falcon1 we have found a column of T-80s on a road heading west, there are SA-15s mixed in so we are targeting them first how coupy?"
Stick to tactical calls only. Information that has already been pre-briefed is not required. If engaging use a quick Engaged Offensive, if a SAM is found use Mud calls.
2. Giving threat calls about potential bandits(Not Immediate Danger) "Strobes bullseye 322-87" "Bandit 022-102 4-ship Mig-29"
This information given on tactical comms causes clutter and diminishes more important flight communication. Typically AWACS calls and flight communication is enough to find bandits. Only give threat calls on package if they are an immediate danger.
3. Fox Calls during high intensity situations "Fox-3 times-2 Su-35 198-23 13-thousand hot"
This information should be relayed in your flight, not package. Only relay this information to package if the overall intensity level of the mission is low.
Example: BARCAP and encounter a single 2-ship threat, make tactical call on package to inform AWACS/GCI/All Flights of your missile shot. This is the only enemy you have encountered in the past 10 minutes.
It takes 4-8 seconds to relay this information, that's 4-8 seconds of limited communication for the other flights that during a high intensity battle could cost them not hearing a more important call. Brief engaged offensive calls are sufficient during these times.
4. Micro-Management from Package Leader "Sting1 move east to escort Lobo1, Falcon1 flow north and engage bandits 133-84, Cowboy2 SEAD Mud-6 west of target"
As a package leader you must rely on flights to handle the situation as they best see fit. Informing a flight to escort, a SEAD flight to engage MUD, or a Strike flight to engage the primary target should all have been pre-briefed. Taking 15 seconds to give needless orders on package comms greatly increases the OODA loop for everyone. Flight Leaders require package comms to be silent so they can coordinate on flight comms.
When package leading i'm absolutely guilty of clogging up UHF17. I made this mostly for takeaway mental notes after today's event, but also to share my thoughts with you guys.
Edited by Gusy, 2018-10-16 @ 17:58.