ASRC Equipment Procedures
| Date | Code | Version | Contact |
|---|---|---|---|
| 2002-01-05 | SOP-020 | 1.00 | Facility Advisory Board (FAB) |
1. PURPOSE.
This Standard Operating Procedure (SOP) provides specific procedures to be used with the ASRC radar client program.
2. ROLES AND RESPONSIBILITIES
The Office of Primary Responsibility (OPR) for this SOP is the ZOA Facility Advisory Board. This SOP shall be maintained, revised, updated or cancelled by the ZOA Facility Advisory Board. Any suggestions for modification / amendment to this SOP should be sent to the FAB for review.
3. DISTRIBUTION
This SOP is to be read and applied by all ZOA controllers using the ASRC radar client.
4. BACKGROUND
This SOP outlines procedures to ensure consistent use of the ASRC client to pass information between controllers.
5. PROCEDURES
a. Position File
Controllers will ensure that they have downloaded and installed the current ASRC position file for ZOA ARTCC as published on the ZOA ARTCC Web Site.
b. Beacon Code Assignment
1. For "standard" positions listed in (2) below, beacon code ranges should be set by the position file. This will ensure beacon code ranges are chosen from the appropriate position when using the F9 function key 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 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 or descended in accordance with SOP, the temporary altitude field should not 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. Flight Progress Strips
1. The flight progress strip will be amended to reflect the initial cleared route and any amendments made thereafter.
2. The data tag will be modified via the F5 function key to show any changes to cruise altitude.
3. Therefore, pilots will not be required by ASRC controllers to modify flight plans.
e. Communications Indicator
Controllers shall ensure aircraft are properly tagged with the appropriate communications indicator ("v", "r", "t") using the F9 function key.
f. Scratch Pad Field
1. Personal Messages. The scratch pad 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.
2. Standard Optional Messages. The scratch pad 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. None. Clear prior to handoff. May be used by TWR for advisory to APP. GA Aircraft has declared a go-around. None. Clear prior to handoff. 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. VFF VFR Aircraft is proceeding under Flight Following. None. Maybe used by APP as advisory to adjacent sectors. Not to be used in lieu of interphone call to arrange for continued flight following. 3. Coordinating Messages. The scratch pad field shall be coded during 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. For DEP to CTR: if the fix is a standard "departure gate fix" this shall mean that aircraft has been instructed to "resume own navigation" when receiving the navaid.
(Fix Id, first 3 letters) Aircraft is proceeding direct to fix and will require further vectors on course. For DEP to CTR: if the fix is a standard "departure gate fix", this shall mean that aircraft has been instructed to "resume own navigation".
Hxx (where xx = heading in 10x degrees. eg: H34 = Heading 340) Aircraft is proceeding on heading xx0. For DEP to CTR: the aircraft has NOT been instructed to "resume own navigation". Maybe used when traffic situations did not allow DEP to turn the aircraft on course prior to climbing above DEP airspace.
BS2 Aircraft does not have STAR chart and is to be vectored along BSR2 path. GG4 Aircraft does not have STAR chart and is to be vectored along GOLDN4 path. MD2 Aircraft does not have STAR chart and is to be vectored along MOD2 path. PY1 Aircraft does not have STAR chart and is to be vectored along PYE1 path. RI4 Aircraft does not have STAR chart and is to be vectored along RISTI4 path. HD2 Aircraft does not have STAR chart and is to be vectored along HADLY2 path. LC1 Aircraft does not have STAR chart and is to be vectored along LOCKE1 path. ST1 Aircraft does not have STAR chart and is to be vectored along STINS1 path. MW4 Aircraft does not have STAR chart and is to be vectored along MADWN4 path. MV1 Aircraft does not have STAR chart and is to be vectored along MARNV1 path. PX2 Aircraft does not have STAR chart and is to be vectored along PXN2 path. CO1 Aircraft does not have STAR chart and is to be vectored along COMMO1 path. EC1 Aircraft does not have STAR chart and is to be vectored along ECA1 path. CA3 Aircraft does not have STAR chart and is to be vectored along CAPO3 path. HY5 Aircraft does not have STAR chart and is to be vectored along HYP5 path. BY1 Aircraft does not have STAR chart and is to be vectored along BRINY1 path. JW2 Aircraft does not have STAR chart and is to be vectored along JAWWS2 path. RO2 Aircraft does not have STAR chart and is to be vectored along ROBIE2 path. CC1 Aircraft does not have STAR chart and is to be vectored along CCR1 path. FL3 Aircraft does not have STAR chart and is to be vectored along FLUNK3 path. TU1 Aircraft does not have STAR chart and is to be vectored along TUDOR1 path. WR5 Aircraft does not have STAR chart and is to be vectored along WRAPS5 path. AN2 Aircraft does not have STAR chart and is to be vectored along ANAHO2 path. CN2 Aircraft does not have STAR chart and is to be vectored along CANN2 path. RY1 Aircraft does not have STAR chart and is to be vectored along RYANN1 path. SI3 Aircraft does not have STAR chart and is to be vectored along SIERR3 path. TV1 Aircraft does not have STAR chart and is to be vectored along TARVR1 path. VK1 Aircraft does not have STAR chart and is to be vectored along VIKES1 path.
END