You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, when a controller sends a message over their frequency, their messages are addressed to multiple frequencies. In particular, it seems that the message is transmitted over both the controller's primary frequency and their ATIS frequency.
Example:
A controller has the frequency 118.100, and an ATIS frequency of 132.850
Messages will appear to be addressed to @18100&@32850
e.g. #TMXXX_TWR:@18100&@32850:Insert message here
From the data currently available, it seems that this does not occur with CTR controllers. However, the above-mentioned issue may simply not have surfaced yet, due to FCOM users mainly receiving text messages while far away from the airport the ATIS is associated with.
The text was updated successfully, but these errors were encountered:
Sometimes, when a controller sends a message over their frequency, their messages are addressed to multiple frequencies. In particular, it seems that the message is transmitted over both the controller's primary frequency and their ATIS frequency.
Example:
118.100
, and an ATIS frequency of132.850
@18100&@32850
#TMXXX_TWR:@18100&@32850:Insert message here
From the data currently available, it seems that this does not occur with CTR controllers. However, the above-mentioned issue may simply not have surfaced yet, due to FCOM users mainly receiving text messages while far away from the airport the ATIS is associated with.
The text was updated successfully, but these errors were encountered: