AWACS and… who?
-
During a interception mission yesterday, Chalice disappeared halfway through (just as I merged with the first of two groups, typical!). I’m guessing end of station time, shot down, or something like that. Out of range doesn’t make sense to me as he didn’t become available when I RTB’d. Even though Chalice was unresponsive, another callsign fed me with sporadic bogey bullseye info (I forget what the callsign was), but this one did not respond to any declare queries or picture requests. Who could this be? Is there GCI present in BMS?
-
was the new radio chatter identifying AD threat? And you could have lost awacs due to being shot down. Often they fly too close to the FLOT at campaign start and easily downed. Check their flight paths and change them if so. In campaign I have seen recently awacs disappear for a mission or two also.
-
Yes, slightly different voice file with different callsign fed me bogey info once or twice per minute. He directed the info to my flight callsign, and the bullseye info matched the bogeys I was engaging (I’m lucky they were old school bogeys considering my relative loss of SA between the clouds without direct support). The question isn’t why the AWACS stopped responding, but what/who continued to provide me sporadic info after that event? And when it is feeding me this info on all UHF package channels (and team), why can’t I communicate with it through the AWACS radio menu?
-
AWACS can be out of range or off station and don’t provide the normal service but still in existence somewhere and providing the other calls. You can also overhear flights other than AWACS on certain frequencies. In a general setting if I’m U6/V1 for example I don’t hear AWACS messages unless I’m on a specific mission that requires directive calls like an escort or intercept.
-
BTW, it is Chalis, not Chalice.