Communications Procedures
| Date | Code | Version | Contact |
|---|---|---|---|
| 2011-05-06 | SOP-001 | 2.10 | Facility Advisory Board (FAB) |
PURPOSE
ROLES AND RESPONSIBILITIES
DISTRIBUTION
BACKGROUND
COMMUNICATIONS EQUIPMENT PROCEDURES
VRC voice server connections
- The preferred primary VRC voice server is rw.liveatc.net.
- Other alternate VRC voice servers may be used if necessary. For a list of current active voice servers go to the VATSIM "Who is Online" page at http://stats.vatsim.net/who.html
- The VRC frequency specified shall be the full numeric frequency with 3 digits after the decimal (e.g. 121.800).
- The VRC vox channel specified for controller's air-to-ground communications shall be the facility position (e.g. SFO_GND).
- The VRC channel specified for controller's voice ATIS shall be the airport ICAO code followed by "_ATIS" (e.g. KSFO_ATIS).
- Refer to the Primary Airports (SOP-050) for the controller frequencies for ZOA airports.
Controller's ATIS message
Information Not Allowed in the Controller's ATIS message:
- Controller's Name or Rating
- Controller's Frequency
- Raw METAR Data that has not been decoded.
The controller position directly affects the ATIS type given.
- Clearance Delivery
No ATIS shall be provided. Optionally, you may have a one-line statment about availability & log off Time (UTC).
- Ground
Ground ATIS should refer pilots to the associated local tower (if online), or to the airport's voice ATIS broadcast frequency if that is available.
"ATIS available on freq 118.85"
If Tower or a higher position (Approach, Center) is not online, Ground cannot issue an ATIS.
- Tower
Tower must at all times provide a FULL ATIS for their airport.
- Approach
If Tower is Online, Tower should coordinate with Approach so that their Information Letters are the same, and also so that the ATIS identifies the correct approaches in use.
If Tower is not online, Approach shall issue the FULL ATIS for their Primary Airport.
- Departure
No ATIS shall be provided. Optionally, you may have a one-line statement about availability & log off Time (UTC).
"NORCAL Departure, logging off 1800 Zulu"
- Center
If positions below are online, then provide position, log off time (optional) and other remarks.
"Oakland Center, logging off 1320 Zulu"
If positions below are not online, provide position, log off time (optional), and FULL ATIS for KSFO.
- General FULL ATIS Format shall be:
[NAME OF AIRPORT] Airport Information %id% %time% Zulu. Wind $wind(%icao%) Vis %vis% Sky %clouds% Temp %temp% Dew %dew% Altimeter %alt% [Approach in use] %runways%. Readback all runway holding instructions Required. Advise on initial contact, you have information %id%.
Voice ATIS
The latest version of the VRC client software now supports a VOICE ATIS connection. This is the one and only sitation where a controller may have 2 connections to the VATSIM network.
Controllers who are otherwise responsible for providing a FULL ATIS, as described above, are encouraged to use the voice ATIS feature of VRC to create a recorded audio ATIS message that pilots can hear on the airport's published ATIS frequency. Refer to the Primary Airports (SOP-050) for the ATIS frequencies for ZOA airports.
Magnetic Variation
Due to magnetic variation between the METAR wind readings and runway headings, it is the controllers responsibility to subtract 20 degrees from all wind directions. For example, a wind reported in the METAR as 280 at 10 knots is recorded on the ATIS and broadcasted on frequency as wind "260 at 10". This rule is applicable to all airports within ZOA airspace.
- Ground to Ground interphone calls
The preferred method for voice communications between controllers is Teamspeak (see additional information below).
For ground-to-ground text communication, use the VRC controller chat feature. IMPORTANT: Use of the "ATC Channel" is discouraged for this purpose, and restricted as described below.
An alternative method for voice communications between controllers (interphone calls) is the intercom feature of VRC. Communications to busy positions shall be restricted to operational messages of a non-routine nature.
- Teamspeak Server
Controllers may prefer to connect to the Teamspeak server while controlling. This will allow for expedited communications between different controllers and will also allow for more coordination.
Teamspeak is also the preferred tool that instructors, mentors, and students use to communicate during training sessions. During large events, use of the Teamspeak server is strongly encouraged.
The address for the Oakland ARTCC Teamspeak server is: virtualzoa.com, port: 9987 and may be used 24/7. If you need the client, you may go to www.goteamspeak.com to download it, once setup, enter the server address and your full name, then connect.
The usage of the Oakland ARTCC Teamspeak server is restricted to Oakland ARTCC controllers and Oakland ARTCC visiting controllers. Permission to join the ZOA Teamspeak server for all other persons may be granted by the Oakland ARTCC ATM, DATM or TA only.
- Ground to Ground text messages over the server network "ATC Channel"
The server "ATC Channel", accessed in VRC by typing messages in the text window preceded by a "/", generates significant network traffic, in that all messages sent on it are transmitted to every controller within a large range, and to facilitate this, to each network server. Therefore, use of this channel is restricted by the following procedures, to minimize network bandwidth requirements.
The ATC Channel shall be used only for the following purposes:
To announce the opening of DEP, APP, CTR, of FSS positions (eg: "SFO_APP: Open.West Ops").
To call for relief of Class B surface area TWRs, and all DEP, APP, CTR, and FSS positions 10-15 minutes prior to closure. The call-for-relief should only be made after it has been determined there are potential replacements currently online. The call for relief shall serve as notification that the position shall be closing, thus a position closure message is not needed. (eg: "SFO_APP: Closing soon. Any takers?")
To announce position turnover to a new network call sign for Class B surface area TWR, DEP, APP, CTR, or FSS positions. Controllers assuming a position from another controller shall make the announcement, thus informing controllers of the new call sign in use. (eg: "SFO_1_APP: Shift Change").
All other communications between controllers should be made via Teamspeak or direct interphone calls in VRC (for voice), or via chat messages in VRC (for text).
During events designated as major events, these procedures shall be suspended. The ATC Channel shall only be used by personnel designated as "Event CIC" or by the Air Traffic Manager. Controllers shall make no transmissions on the ATC Channel during major events unless it's an emergency.
Naming Conventions for Network Call Signs
Network call signs for operational positions will be composed of two or three groups, separate by an underscore "_" as follows:
AAA_DDD
(or)
AAA_BC_DDD
Where:
AAA = The ICAO identifier for the field without the lead letter ("K" for continental US, eg: SFO) or a facility identifier as set forth by SOP (eg: BAY).
B = A rating modifier. This may be "S" for Student, "I" for Instructor, or "M" for mentor.
C = A numeral used to facilitate shift turnover. Eg: "1" for 1st shift turnover controller or "SFO_1_APP"
DDD = the appropriate facility type as follows:
- DEL = Clearance Delivery
- GND = Ground Control
- TWR = Tower (local control)
- DEP = Departure Control
- APP = Approach Control
- CTR = Center Enroute Control
- FSS = Oceanic Flight Service
During online instruction and examination, including self-monitored training (SMT), the student shall use the "S" rating modifier (eg: "SFO_S_TWR"), authorized mentors shall use the "M" rating modifier (eg: "SFO_M_TWR"), staff instructors shall use the "I" rating modifier (eg: "SFO_I_TWR").
Observers shall use a facility identifier, typically "ZOA" followed by their assigned operating initials, followed by the facility type "OBS" (eg: "ZOA_JC_OBS").
These authorized ZOA staff members shall use these designated callsigns when signed on as observers:
- ZOA_ATM - Air Traffic Manager
- ZOA_DATM - Deputy Air Traffic Manager
- ZOA_TA - Training Administrator
- ZOA_EC - Events Coordinator (for use ONLY during official ARTCC or VATUSA events)
Instructors available for training sessions shall use a similar format with a facility type of "INS" (eg: "ZOA_JC_INS").
Mentors available for training sessions shall use a similar format with a facility type of "MTR" (eg: "ZOA_JC_MTR").
This Standard Operating Procedure (SOP) sets forth procedures to be used for simulated radio and telephonic equipment using the Virtual Radar Client (VRC), as well as VATSIM network services. Also, this SOP will set forth position call sign naming conventions. Controllers will be required to understand and comply with these procedures.
This SOP shall be maintained, revised, updated or cancelled by the Facility Advisory Board, and shall be effective unless there is a conflict with the VATUSA/VATSIM policies in which case they shall supercede these procedures.
This SOP is to be read and used by all ZOA controllers.
There are several possible methods for accomplishing communications and configuring simulation software when connected to the VATSIM network. To achieve consistent use of simulated communications equipment this SOP will list specific procedures to be used for radio and telephonic communications.