Communications Procedures

Date Code Version Contact
2006-12-06 SOP-001 2.00 Facility Advisory Board (FAB)

1. PURPOSE

This Standard Operating Procedure (SOP) sets forth procedures to be used for simulated radio and telephonic equipment using the Advanced Simulated Radar Client (ASRC), 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.

2. ROLES AND RESPONSIBILITIES

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.

3. DISTRIBUTION

This SOP is to be read and used by all ZOA 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 "ASRC VCSC voice programs.

b.      Ground-to-ground interphone calls with ASRC 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. VRC "preferred" servers

Information Not Allowed in the ATIS:

      1. Controller's Name and or Rating
      2. Controller's Frequency
      3. Raw METAR Data that has not been decoded.

      Now, controller position directly effects the ATIS type given.

      1. Clearance Delivery
        1. None. Optionally, you may have a one-line statment about:
          1. Availability & Log off Time (UTC)
      2. Ground
        1. Ground ATIS should refer pilots to the associated local tower.
          1. "ATIS Available from Tower"
          2. If Tower not online, Ground must issue a FULL ATIS.
      3. Tower
        1. Tower must at all times provide a FULL ATIS for their airport.
      4. Approach
        1. If Tower is Online, Tower should coordinate with Approach so that their Information Letters are the same.
        2. If Tower is not online, Approach shall set the FULL ATIS for their Primary Airport.
      5. Departure
        1. None. One line statement about Position Name.
          %callsign%, NORCAL Departure. (Example)
      6. Center
        1. If positions below are online, then:
          1. Position, Log off time (Optional) and other remarks.
            1. Oakland Center, Logging off 1320Z
        2. If positions not online:
          1. Position, Log Off time, and Full ATIS for SFO.
      7. 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%.

c. Ground to Ground interphone calls

The preferred method for communications between controllers (interphone calls) shall be via the intercom feature using the ASRC VSCS system during normal controlling sessions, use "Override" in the ASRC VSCS system during Large Events when using the ASRC 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"

    1. The server "ATC Channel", accessed in ASRC 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.
      1. The ATC Channel shall be used only for the following purposes:
      2. To announce the opening of Class B surface area TWRs
      3. To announce the opening of DEP, APP, CTR, of FSS positions (eg: "SFO_APP: Open.West Ops. ")
      4. 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?")
      5. 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.")
      6. To summon the assistance of a supervisor.
      7. All other communications between controllers should be made via direct "interphone" calls via "chat box" or VSCS under ASRC.
    2. 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.

e. Naming Conventions for Network Call Signs

i. 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

ii. During online instruction and examination, the student shall use the "S" rating modifier (eg: "SFO_VS_APP"), authorized CTR Mentors shall use the "M" rating modifier (eg: "SFO_VM_APP"), Staff Instructors shall use the "I" rating modifier (eg: "SFO_VI_APP").

iii. Observers will use a facility identifier, typically "ZOA" followed by their assigned operating initials, followed by the facility type "OBS" (eg: "ZOA_JC_OBS"). Instructors available for training sessions will use a similar format with a facility type of "INS" (eg: "ZOA_JC_INS").

f. Teamspeak Server

Controllers should connect to the Teamspeak server while controlling. This will allow for expedited communications between different controllers and will also allow for more coordination. The server for this address is: Oakartcc.com and may be used 24/7. If you need the client, you may go to www.goteamspeak.com to download it, once setup, simply plug in the server and your name, and you're ready to connect!

This site is NOT affiliated with the FAA, the real Oakland ARTCC or any of the airlines listed. The information contained in this site should NOT be used for real world navigation.

Copyright ©2009 Oakland ARTCC on VATSIM