Loading...
 

GenCtrl

General Controlling Directive





GENERAL

Directives

  • All facilities under the jurisdiction of ZLC ARTCC are considered "open" while appropriate ATC are online to control those facilities.
  • All military controlled facilities/airspaces (TOWERs and RAPCONs) that are controlled by the USDOD ATC in real life (not FAA) will be considered uncontrolled by ZLC ARTCC.
    • USDOD Facilities:
      • KHIF TWR
      • KMOU Mountain Home Airport TWR and RAPCOM (Approach)

ZLC Facility Files

  • Facility Files are defined as any files supporting the operations of ZLC, including but not limited to: ZLC Sector, POF, Alias, and vATIS files.
  • Any controller controlling or training on a ZLC position is required to be utilizing the most up to date Facility Files available.
  • If a member decides to modify any Facility Files for their own local copy, that member may utilize their custom file as long as no functionality/formatting from the ZLC original file is lost.

Discord

  1. While controlling, controllers are expected to be connected to the ZLC Discord server and respond in a timely manner.
  2. When in a designated controlling channel, all conversation must be pertinent to the controlling session at that time.
  3. Nicknames:
    • GENERAL
      • Names will be lowercase except the first letter of the first and last names.
        • Required Format:
          • (Full Name) | (VATSIM Rating)
          • Example:
            Joe Swanson | S1
    • STAFF
      • Staff members will have their staff position abbreviation at the end and their staff position abbreviation.
        Note - A prefixing “A” on a staff position indicates that the staff member is an “Assistant”.
          • Example:
            Brian Griffin | I3 | TA
            Meg Griffin | I1 | ATA
    • VISITORS
      • Visiting ATC are expected to put their facility abbreviation at the end.
          • Example:
            Peter Griffin | S2 | ZDV
      • Visiting Staff members will have their staff position abbreviation at the end and their staff position abbreviation.
          • Example:
            Tom Tucker | C1 | ZSE ATM

Callsign Use

  1. VATSIM Callsign during log-on is expected to be used per the Position Assumption/Relief Directive
  2. If a pilot refers to you as a position callsign appropriate for their phase of flight, but not necessarily matching the VASTIM callsign, ATC may refer to themselves as the callsign appropriate for that phase of flight.

    Note- This is to increase realism but should only be initiated by the pilot, not the ATC.

    Example: A pilot calls SLC_CTR as a pop-up IFR under the KBOI Class C outer shelf when BOI_APP is offline, but refers to SLC_CTR as “Bigsky Approach”. The ATC working SLC_CTR may continue to refer to themselves as Bigsky Approach as appropriate.

Coordination

  1. Prior to controlling any position within ZLC, all appropriate steps in the Position Assumption/Relief Directive will be followed.
  2. When able, utilized text coordination for general coordination.
  3. When text coordination is will not suffice, voice coordination will follow the following format:
    • Person initiating coordination: “(Facility name of person to be called), (facility name of person calling)”
    • Person being called: “go for (facility name)”
    • person initiating: “(message)”
    • (any further back and forth coordination)
    • person being called: “(controller initials)”
    • person initiating: “(controller initials)”

      Example:
      • SLC_TWR to GUNNISON SECTOR: "Gunnison. Salt Lake Local. Request."
      • GUNNISON SECTOR: "Gunnison."
      • SLC_TWR: "Air-Gun71 requests unrestricted climb to 17,000."
      • GUNNISON: "Unrestricted approved up to 10,000. I will get him higher later."
      • SLC_TWR: "Unrestricted approved up to 10,000."
      • GUNNISON: "KL"
      • SLC_TWR: "KF"

DP & STAR In-Scope Reference

  1. Though the DP & STAR In-Scope Reference system is not required to be utilized, conformance to the procedures within is required.

    Example: ATC providing Approach services to a pilot flying the LEEHY STAR during south OPS into KSLC, is expected to descend the aircraft via the STAR, advise the aircraft to expect runway 16R and will be at 210kts midfield prior to handoff to Final Approach. This information is easily found in the .LEEHYAPP command.

ScratchPad Use

  1. ScratchPad entries are mandatory for use, even while ATC are working alone. All scratchpad entries will be set per the ScratchPad Use Directive.

    Note-No waiver is given for use of ScratchPads because all ATC need to maintain their muscle memory skills for events and like traffic load. It also serves as a backup coordination tool in the event that the controller suddenly looses connection or must log off immediately.

Towered and Non-Towered Facilities

  • All facilities under the jurisdiction of ZLC ARTCC are considered "open" while appropriate ATC are online to control those facilities.
    Note-If pilot wishes to simulate the towered field being closed, it is the appropriate time that the field would be non-towered in real world, and there is no other traffic that will be affected, ZLC ATC may simulate that field as non-towered for that pilot.
  • All military controlled facilities/airspaces (TOWERs and RAPCONs) are controlled by the USDOD ATC (not FAA) will be considered uncontrolled by ZLC ARTCC.
    • USDOD Facilities:
      • KHIF TWR
      • KMOU Mountain Home Airport TWR and RAPCOM (Approach)
  • Authorized VATSIM Designated Airspace within ZLC ARTCC, requiring special endorsement by ZLC Training Department to control:
    • SLC_CTR "Salt Lake City Center"
    • SLC_APP "Salt Lake City Approach"
    • SLC_DEP "Salt Lake City Departure"
    • SLC_TWR "Salt Lake City Tower"
    • SLC_GND "Salt Lake City Ground"
    • SLC_DEL "Salt Lake City Clearance"

ATIS

  • Review and understanding of the ZLC vATIS Utilization CBT is required prior to use by any ATC.
  • vATIS will be used for all ATIS broadcasts within ZLC ARTCC Boundaries.
  • ATC are to utilize the most up to date vATIS files released by vZLC management.
  • Inform pertinent ATC providing Ground, Tower (LOCAL), and Approach Control services of new ATIS only if it is the first ATIS being broadcast. The controllers that are notified are expected to then subscribe to the broadcast per the vATIS "vATIS Update Notifications" system.
  • Utilization/Activation of the NOTAM Pre-Defined Messages are to only be used when controller workload is of a high degree.
  • VMC: The field is eligible for visual approaches per the FAA JO Order 7110.65 7-4-2 (if the reported ceiling at the airport of intended landing is at least 500 feet above the MVA/MIA and the visibility is 3 miles or greater).
  • IMC: The field is not eligible for visual approaches per the FAA JO Order 7110.65 7-4-2.

Callsigns and Frequencies

  • All position frequencies may be found in the "Position / Frequency Info" directive.

ZLC Change Log

  • Prior to any controlling session, all controllers will check the Change Log on the Resource Center for any changes and ensure they are in compliance with any pertinent changes.
    • A “Controlling Session” is anytime a controller “primes” a frequency. If a controller unprimes their frequency for a quick one min break (due to being relieved by another controller), that controller must check the Change Log again before repriming their frequency.
  • The Change Log can be found at the top left of the Resource Center menus or by accessing the page via the in-scope command .changelog

Flight Following / Radar Services

  • Do not solicit a flight following request to pilots.
  • All flight following aircraft will be assigned the appropriate scratchpad for the requested service per the Scratchpad Use Directive.
  • Terminate radar services without a pilot request in the following manner:
    • Class B Field departure not requesting radar services: Once outside of the Mode-C Veil.
    • Class C Field departure not requesting radar services: Once 20 miles from the primary airport.
    • TRSA Field departure with a request for TRSA/Radar Services: If the pilots does not wish to continue radar services, terminate radar services once outside of the TRSA airspace.

VATUSA TMU Notices (N.T.O.S.)

  1. Found here: https://www.vatusa.net/tmu/notices
  2. This page is to be reviewed once every 15min during control sessions.
  3. Any Notices that apply to any traffic within ZLC ARTCC jurisdiction must be complied with, when possible.

Software/Program Manuals

  1. Prior to utilizing any software or program for controlling or assisting in your controlling duties, you are required be familiar with and have read the manual published by the developer.
  2. If the member does not understand a certain feature or section in the manual/documentation, that member is expected to reach out to a member of the ZLC training department immediately for clarification.










CLEARANCE DELIVERY

Squawk (Beacon) Codes

  1. Assign squawk codes to flight strips only as the clearance is being issued.

    Note- This is to prevent confusion if the DEL controlled has to suddenly log off/lost connection. With this procedure, the next controller automatically knows which pilot has received their clearance based on if they have an assigned squawk code.

Routing

  1. Always utilize the Letter of Agreement Quick Reference (LOAQR) to ensure routing is appropriate for all departures.
    1. When the destination airport is not listed in the LOAQR, use best judgement for route approval/creation.
  2. When referring to aircraft types for routing purposes, the following definitions will apply:
    • J - Jet Powered
    • M - Turbo-propeller Powered (Speed > 190knots)
    • P - Prop aircraft (Speed > 190 knots)
    • Q - Non-Turbojet Powered aircraft (Speed < 190 knots) and Helicopters
  3. Through-Clearances are not authorized in ZLC airspace due to limitations of software and resource simulation.

Pre-Departure Clearances (PDCs)

  1. Utilization of PDCs are not optional if the Facility Directive allows their use. Proper use and familiarization with how to issue a PDC is a requirement for all controllers at ZLC.
  2. ZLC recognizes the PDC system on VATSIM (by means of private message to the pilot) as a Controller-Pilot Data Link (CPDL) system. Real world FAA allows amended flight plan information to be cleared and issued by CPDL PDC.












GROUND CONTROL

Taxi Instruction Prerequisites

  1. Prior to issuing taxi instructions to a pilot, ensure the pilot:
      • Reports an accurate position on the field
      • Is squawking Mode-C Altitude Reporting if at an ASDE-X airport, along with squawking their correct assigned code
      • Reports the receipt of the latest ATIS report. If no ATIS is broadcasted, a general statement of receiving the latest METAR report will do such as "We have the numbers"

Aircraft Position Verification

  1. Issue taxi instructions based on pilot reported position. For inaccurate position reports or use of ASDE-X, refer to the Ground Use section of the Radar Use Directive.

ATIS

  1. When a controller above the GND position is online, it is encouraged that the GND controller post and maintain a working ATIS broadcast.

    Note- It is preferred that the DEL/GND controller maintain the ATIS because of the safety concern with a TWR controller having to stop communications with airborne traffic to record or maintain one.












TOWER/LOCAL CONTROL

IFR Releases and Rolling Calls

  1. CLASS D fields: A “Release Request” (.RR command) is required to be sent to the appropriate Departure Controller for all departing aircraft. The Departure Controller will then reply back with a “Release Approved” (.RA command) message with the approved time for release.
    1. A Release Request requires ATC to add the following minimum information to the command:
      • Assigned heading/RH, if applicable.
      • Radar Services Requested (VFR)
  2. CLASS D Fields: A "Rolling Call" (.RC command) is required to be sent to the appropriate Departure RADAR Controller to assist in the radar identification of the aircraft with the exception of HLN and TWF departures, as these are Non-RADAR facilities.
    1. In the event that the pilot begins takeoff roll, the rolling call was sent, but then rejects the takeoff, TWR must notify the departure controller ASAP. This may be done via the Rejected Takeoff command (.RT).
    2. If the aircraft begins the takeoff roll within three minutes after the prescribed release time, a Rolling Call is not required.
  3. CLASS B and C fields: These fields are assumed to operate Full RADAR Capabable towers and therefore do not require a call for release or rolling calls.


ATIS

  1. Barring any reasonable complications, it is expected that a TWR controller post and maintain a working ATIS broadcast.

    Note- APP/DEP/CTR controllers providing TWR/LC services are not required to post an ATIS. If a GND or DEL position is online and they are comfortable with ATIS broadcast standards, it is preferred that a GND or DEL controller maintain the ATIS for safety.












DEPARTURE CONTROL

DEP Use of DNM/RR

  1. Respond to Class D field Release Requests (RR) with the “Request Approved” message with the appropriate amount of time that the request is delayed from now. Refer to Command Reference Note # 1 for details.
    Note- The aircraft must be airborne within two minutes after of the prescripted release time.
    1. The RR is only valid for 2min after being received. If the aircraft is not departed by that time, that RR is expired and a new one will be generated by the TWR controller prior to aircraft departure.
  2. Respond to Class B and C field Departure Notification Messages (DNM) only when immediate action is required.
    1. If an immediate action is required, the departure controller must respond within 30 seconds of receiving the DNM. (Recommend utilizing the .M command)
    2. The DNM is only valid for 2min after being received. If the aircraft is not departed by that time, that DNM is expired and a new one will be generated by the TWR controller prior to aircraft departure.












APPROACH CONTROL

General

  1. Drop track control of IFR arrivals upon communication change to Local Control. This allows RADAR certified controllers at Full RADAR towers to acquire track control if needed (such as a missed approach).

Visual Approaches

  1. It is recommended that all IFR aircraft be assigned and vectored for a visual approach, on a workload permitting basis and when a visual approach would benefit traffic flow/efficiency.
    1. Pilots may refuse a visual approach assignment, in which ATC must then provide the pilot with an instrument approach clearance if one is available.

VFR Radar Services

  1. VFR radar services (Flight Following) will be provided to all pilots requesting said service, on a workload permitting basis.








CENTER/EN-ROUTE CONTROL

Weather Reporting

  1. Current local altimeter reports will be provided to all pilots below FL180, at minimum once every 100 nautical miles. When able, provide the altimeter report upon initial contact.
  2. SIGMET and other weather reporting services may be provided to pilots at controller's discretion.
    Note- Local METAR information is considered mandatory for controllers to report when appropriate.

Special Coordination

  1. Hi-ILS clearances required the destination Approach Control approval prior to issuance.

VFR Radar Services

  1. VFR radar services (Flight Following) will be provided to all pilots requesting said service, on a workload permitting basis.