Could someone explain the designators in the middle of these callsigns please
EGKK_A_ATIS
EGKK_C_GND
EDDF_D_ATIS
EDDF_N_APP
PHX_S_TWR
Thanks
Hi Carl,
regarding those ATIS-stations, the suffix “_ D _” stands for “Departure ATIS” and “_ A _” stands for “Arrival ATIS”, meaning that there are two separate ATIS for departing and arriving traffic.
For ATC-stations, those suffixes may have a meaning in terms of “direction”, for example “EDDF_N_APP” is the approach station for the Northern part of the approach airspace. In this specific case of Frankfurt the default APP-station is “EDDF_N_APP” and he will manage the entire APP-airspace until a second APP-controller will join and open “EDDF_S_APP”. Only then will the APP-airspace be split in two for the NORTH and for the SOUTH. Clear?
The same goes for TWR-stations. Phoenix has runway North and South of the apron/ramp/terminal. Hence, PHX_S_TWR is the station that controls the Southern portion of the airport and probably will control the entire airport until a PHX_N_TWR will join. Clear as well, right?
Other suffixes will have another logic behind them, but this is done differently from country to country.
Also, you may sometimes see the XXX_S_XXX refer to a student. You may sometimes also see XXX_I_XXX for an Instructor.
Sometimes, you’ll see a number (e.g., XXX_34_CTR) – this usually refers to a sector number. For example, a FIR/ARTCC usually consists of at least a dozen sectors, which may be numbered.
The network doesn’t have hard and fast rules for these identifiers; latitude is given to the Divisions/Subdivisions to define the identifiers that work best.
1 Like
You can find the descriptor on the controller list of VATSpy, in most cases it is further specified. The region boundaries where controllers are active are less clear on VATSpy. Moreover, some controllers seem not to be listed on vpilot?