| Version | 2 |
| Created | 12/28/2015 02:03 |
| Last Updated | 11/24/2020 22:16 by Finn Hutter |
Communication Procedures
SOP-001
ZSE Senior Staff
Version 2.1
Amended 2019-10-23, changes noted in bold font.
1. PURPOSE
This Standard Operating Procedure (SOP) sets forth procedures to be used for simulated radio and telephonic equipment using the Virtual Radar Client (VRC), vSTARS, vERAM, as well as VATSIM network services. Also, this SOP will set forth position callsign naming conventions. Controllers will be required to understand and comply with these procedures.
2. ROLES AND RESPONSIBILITIES
This SOP shall be maintained, revised, updated or canceled by the ZSE Senior Staff, and shall be effective unless there is a conflict with the VATUSA/VATSIM policies in which case they shall supersede these procedures.
3. DISTRIBUTION
This SOP is to be read and used by all ZSE controllers.
4. BACKGROUND
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:
a. Air-to-ground voice radio using the VRC voice programs.
b. Ground-to-ground interphone calls with ASRC clients/VRC clients.
c. Ground-to-ground text interphone using the server network ATC Channel.
d. Controllers ATIS automatic messages to pilots.
e. Naming conventions to be used when logged onto the network.
5. COMMUNICATIONS EQUIPMENT PROCEDURES
a. Controller Information
No more than four lines of area operational information.
Information Not Allowed:
Controller's Name and or Rating
Raw METAR Data that has not been decoded.
b. ATIS Broadcast
Clearance Delivery - No ATIS is to be completed.
Ground - When Tower or above is not online, Ground may broadcast an ATIS with "suggested" runways. Tower or above may delegate FULL ATIS responsibility to Ground.
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 Tower is running ATIS for the airport and communicate what information is current. If Tower is not online, Approach shall set the FULL ATIS for their Primary Airport.
Center - If positions below are online, they should coordinate with other controllers running ATIS for the airport and communicate what information is current. If positions not online: FULL ATIS for SEA.
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%. Notice To Airmen. All aircraft must squawk mode Charlie on all runways and taxiways. Advise on initial contact, you have information %id%.
c. Ground to Ground interphone calls
The preferred method for communications between controllers (interphone calls) shall be via the Discord server. Additional methods of communication are private chat and the intercom feature using the VRC system. "Override" in the VRC system may be used during Large Events when using the VRC client. Communications to busy positions shall be restricted to operational messages of a non-routine nature. Use of the ATC Channel is discouraged for this purpose and restricted as described below.
d. Ground to Ground text messages over the server network "ATC Channel"
The server "ATC Channel", accessed by typing messages in the text window preceded by a "/". This generates significant network traffic, in that all messages sent on it are transmitted to every controller within a large range via each network server. Therefore, the 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: "SEA_APP: Open. South Ops. ")
To call for relief of Class B surface area TWRs, and all DEP, APP, CTR, and FSS positions 5-10 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: "SEA_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 callsign in use. (eg: "SEA_1_APP: Shift Change. Still South Ops")
During events designated as major events, controllers are asked to not talk about non-traffic topics in the Controlling Coordination portion of Discord. The ATC Channel shall only be used by the personnel designated as "Event CIC" or by the Air Traffic Manager/Deputy Air Traffic Manager. Controllers shall make no transmissions on the ATC Channel during major events unless it's an emergency.
e. Naming Conventions for Network Call Signs
i. Network call signs for operational positions will be composed of two or three groups, separated 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 the continental US, eg: SEA)
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 "SEA_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
ii. During online instruction and examination, the student shall use the "S" rating modifier (eg: "SEA_S_TWR"), authorized Mentors shall use the "M" rating modifier (eg: "SEA_M_TWR"), Staff Instructors shall use the "I" rating modifier (eg: "SEA_I_TWR").
iii. Observers will use a facility identifier, typically "ZSE" followed by their assigned operating initials, followed by the facility type "OBS" (eg: "ZSE_MD_OBS"). Instructors available for training sessions will use a similar format with a facility type of "INS" (eg: "ZSE_MD_INS"). Air Traffic Manager shall use ZSE_ATM. Deputy Air Traffic Manager shall use ZSE_DATM. Training Administrator shall use ZSE_TA.
f. Audio For VATSIM Requirements
Since _M, _I, _S, _1 callsigns aren't recognized by AFV, steps must to taken to ensure the use of the correct transceivers.
1. Log in to the controller client using the callsign of choice.
2. Prime up your frequency in the controller client.
3. In Audio for VATSIM, click the + icon and add the normal callsign. (SEA_CTR)
4. Click TX for the normal callsign.
5. Click RX to deselect the station you logged in as.
f. Discord Server
Controllers should connect to the Discord voice server while controlling. This will allow for expedited communications between different controllers and will also allow for more coordination. You can access Discord via https://zseartcc.org/discord Please contact the ATM/DATM if you have issues connecting. The server may be used 24/7.