Leaderboard

First: Each of the AWOs (WDs) listens to four external nets; more often than not they are not the same net and every bit of information which is transmitted to Wizard isn't shared among the controllers or the rest of the crew (I'm sure you can imagine the amount of information which comes across 13 different UHF let alone 2 satcom, 3 vhf, 3 hf, etc...) So when BoneXX radio checks AC-1 he may be talking to someone, potentially not a controller, who doesn't share that non-mission essential bit of information with the rest of the crew and our training supports that. Do we make sure that things like TICs, CSAR/SAR, tanker information is shared amongst the crew? Absolutely and our crew TTPs/contracts are set up to support that information flow. Imagine for a second that you, your copilot and your loadmaster (or engineer or other crew position XX) each listened to 4x different nets. Do you think all information passed among those 8-12 nets would get shared even with two-three crewmembers? If you're a single seat guy imagine if all of your wingman were listening to 3x different nets with a single common? Second: We're system limited as to the # of SIF we can load to have the computer display your callsign when it senses your unique SIF. I'm positive that every aircraft which takes off in the AOR uses their ATO assigned mission # and has a valid M4 (sarcasm) While M4 doesn't mean much in certain theaters it means quite a bit in others. While that comm interaction is commical, thereby meeting the intent of the thread, I'm sure that there is no way someone could have loaded the incorrect mode 2/3 or stepped to spare and didn't reset the modes (sarcasm) thereby increasing the chances that the AWO (WD) would think Bone XX is airborne when in fact it was Bone XY. Third: Wouldn't you rather have that comm instead of not having it and potentially swapping paint? Not likely but then again I'm positive that everyone, everywhere (sarcasm) is always on their ACO/ACP/SPINS/COF assigned altitude and in their corridor. I'd prefer the controller has the SA to not make that call in the first place but I'd rather that piece of extraneous SAFETY related comm instead of not having it. Waldo