1. Main
2. Standard Operating Procedures
3. SOP_007 VRC Equipment Procedures

VRC Equipment Procedures

 

SOP-007

ZSE Senior Staff

Version 3

 

Amended 2020-01-17, changes noted in bold font.

1. PURPOSE.

This Standard Operating Procedure (SOP) provides specific procedures to be used with VATSIM radar client programs.

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 applied by all ZSE controllers.

4. BACKGROUND

This SOP outlines procedures to ensure consistent use of VATSIM radar client to pass information between controllers.

5. PROCEDURES

a. Position File

Controllers will ensure that they have downloaded and installed their current client AIRAC file for ZSE ARTCC as published on the ZSE ARTCC Web Site under Downloads in the Controller Resources.

b. Beacon Code Assignment

1. For "standard" positions, beacon code ranges should be set by the position file. This will ensure beacon code ranges are chosen from the appropriate position when using a hotkey to assign a code.

2. Standard positions encoded in the position file are all center, TRACON, and primary airport tower, ground, and delivery positions.

3. For "non-standard" positions, the code range determined by SOP_004 shall be entered into the "settings" window.

c. Temporary Altitude Field

1. The temporary altitude field should be used, if available to communicate non-standard altitude assignments that arise due to traffic or other reasons, when these assignments deviate from the associated sector SOP. When an aircraft is climbed in accordance with SOP, the temporary altitude field should not be used, leaving their final request cruising altitude showing. When an aircraft is descended into an airport, the temporary altitude field may be used.

2. The temporary altitude field may be used by controllers as a reminder to themselves of unique altitude clearances. The field shall be cleared before hand-off.

d. Communications Indicator

Controllers shall ensure aircraft are properly tagged with the appropriate communications indicator by selecting the pilot's method of communication (Full Voice, Voice Receive or Text Only).

e. Scratch Pad Field

1. Personal Messages. The scratchpad field may be used by controllers as a reminder to themselves of unique routing or vectoring clearances. The field shall be cleared before hand-off if the message no longer applies.

2. Standard Optional Messages. The scratchpad field may optionally be coded to indicate the following conditions to adjacent facilities.

Code
Means...
Coordinating Action...

PTN
VFR Aircraft is in closed traffic pattern.
May be used by TWR for advisory to APP.

GA
Aircraft has declared/issued a go-around.
May be used by TWR for advisory to APP.

MA
IFR Aircraft has declared a missed approach.
Aircraft is on missed approach per SOP. Used by TWR in lieu of interphone call.

SUA
Aircraft/Flight Leader is operating within scheduled Special Use Airspace
None.

VFR
Aircraft are flying VFR in the area with no specific destination and has flight following.
None.

3. Coordinating Messages. The scratchpad field shall be coded during the time of handoff to indicate the following inter-facility coordination messages:

Code
Means...

(VOR Id)
Aircraft is proceeding direct to fix and will require further vectors on course.

(Fix Id, first 3 letters)
Aircraft is proceeding direct to fix and will require further vectors on course.

Hxx
(where xx = heading in 10x degrees. eg: H34 = Heading 340) Aircraft is proceeding on heading xx0.

Ixx
(where xx = last 2 digits of the runway. eg: I4C = ILS 34C) Aircraft is arriving on the ILS approach into runway xx.

Vxx
(where xx = last 2 digits of the runway. eg: V6L = Visual 16L) Aircraft is arriving on the Visual approach into runway xx.

Xxx
(where xx = last 2 digits of the runway. eg: X8R = RNAV 28R) Aircraft is arriving on the RNAV approach into runway xx.

Yxx
(where xx = last 2 digits of the runway. eg: Y6R = RNAV 16R) Aircraft is arriving on the RNAV approach into runway xx.

Zxx
(where xx = last 2 digits of the runway. eg: Z0R = RNAV 10R) Aircraft is arriving on the RNAV approach into runway xx.

Oxx
(where xx = last 2 digits of the runway. eg: O3R = VOR 13R) Aircraft is arriving on the VOR approach into runway xx.

Lxx
(where xx = last 2 digits of the runway. eg: L21 = LOC 21) Aircraft is arriving on the LOC approach into runway xx.

Dxx
(where xx = last 2 digits of the runway. eg: D03 = LDA 3) Aircraft is arriving on the LDA approach into runway xx.

 

S46 Common Scratchpad Uses:

Bxx
(where xx = last 2 digits of the runway. eg: B6C = Bay Visual 16C) Aircraft is arriving on the Bay Visual Approach Runway 16C Seattle.

Hxx
(where xx = last 2 digits of the runway. eg: H6L = Husky Visual 16L) Aircraft is arriving on the Husky Visual Approach Runway 16L Seattle.

Mxx
(where xx = last 2 digits of the runway. eg: M4R = Mall Visual 34R) Aircraft is arriving on the Mall Visual Approach Runway 34R Seattle.

 

P80 Common Scratchpad Uses:

Cxx
(where xx = last 2 digits of the runway. eg: C0L = Columbia Visual 10L) Aircraft is arriving on the Columbia Visual Approach Runway 10L Portland.

Mxx
(where xx = last 2 digits of the runway. eg: M8R = Mill Visual 28R) Aircraft is arriving on the Mill Visual Approach Runway 28R Portland.