vacs
VATSIM ATC Communication System (vacs)
is an open-source, cross-platform Ground-To-Ground Voice Communication System for VATSIM.
In some situations Discord may still be the desirable coordination tool as it most closely resembles face-to-face coordination, as it is done where controllers IRL sit next to each other.
Handover coordinations are preferably done in Discord.
Download vacs
vacs v2 automatically loads the appropriate profile for your position.
No local profiles are needed, the dataset (including profiles) is kept "in the cloud".
See vacs User Manual for more information
Verbal Coordination Etiquette
-
Before initiating a call, select the appropriate call source for that specific call (see VACS User Manual above!).
Pressing the button corresponding to the source station makes the button light up in light orange (when the source is temporary, i.e. to be used for for the next call only). Pressing the button twice makes the call source fixed, i.e. the same source will be used for all outgoing calls (the button lights up in dark orange).
It is highly recommended to configure a fixed call source representing the station you most frequently call from. This ensures that outgoing calls use the correct caller by default and avoids the need to manually select a call source for every call.
If a call source is not selected, the incoming call will show up with the VATSIM login callsign, i.e. ESOS 1 CTR instead of OS 1.
-
When initiating a call, select the station/sector you want to reach; the call will automatically be routed to the correct controller.
-
The controller picking up should respond with the name of the position shown in bright green. This is the station the initiating caller selected and is expecting to talk to.
Example:
ESSA_E_APP and ESOS_1_CTR are online. ESSA_E_APP covers the whole TMA, i.e. positions ARR-E, ARR-W, APP-S and DEP positions. ESOS_1_CTR covers ESOS sectors 12346789.
How do you make a call concerning a flight to ESSA around ELTOK?
1. The traffic would be in ESOS sector 8.
2. The traffic will enter the TMA in sector W, i.e. covered by ARR-W.
This means that if ACC wants to call APP concerning this traffic, the call source should be selected as ESOS 8 (OS 8) and ARR-W should be the selected destination station. This way both controllers know even before starting the call that the coordination concerns sectors ARR-W and ESOS sector 8 and should identify themselves accordingly, i.e. as "Arr West" and "[Sector] 8" (not "Arr East" or "Stockholm sector 1" as could be implied from the login callsigns ESSA_E_APP/ESOS_1_CTR). -
When responding, the unit name (Stockholm/Malmö/Göteborg etc.) may be omitted when there is no risk for confusion.
-
Identify the traffic you are talking about, with as much detail as needed e.g. "inbound ELTOK, SAS123" or "east of your TMA, transponder 7000, indicating 2000 ft" with response "identified/radar contact", as we are unable to physically point out traffic on the screen of the other controller.
-
Be clear and concise, keep coordination brief and use standard ICAO/TSFS phraseology.
"Sharing" positions
When more than one controller is active on the same position simultaneously, all will receive the same inbound calls, the first controller to respond will be connected to the call, in that moment the incoming call is ended for all other controllers on the same position.
This functionality allows both mentors and students to be connected to vacs during training, or to use it in a E/P (Executive/Planner) configuration if desired.
Group calls are not available, but is planned to be added in a future version.
Phone Directory / Direct Calls
If you want to call a controller not shown to you on any tab, they can be found in the phone directory: ☎️->Dir.
Calls can also be initiated using the Dial Pad, entering a controllers CID.