Shift Procedures
| Date | Code | Version | Contact |
|---|---|---|---|
| 2006-12-07 | SOP-002 | 2.00 | Facility Advisory Board (FAB) |
1. PURPOSE:
This Standard Operating Procedure (SOP) sets forth procedures to be used when assuming a position, ending a shift, or turning over control to a relief controller. 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:
Several procedures should be followed by controllers when assuming a shift to insure that appropriate facilities are manned in priority. Also, an orderly transfer of control should occur at the termination of a shift to insure pilots and adjacent controllers maintain situational awareness. Also, at times unauthorized controllers may attempt to assume positions, and this can lead to operational problems. This SOP shall set forth these procedures.
5. SHIFT PROCEDURES:
- Shift Supervisor Definition
- When any ZOA controller is logged on to a ZOA position, a Shift Supervisor is assigned as follows. The Shift Supervisor is defined as the highest ranking position online. Generally speaking, the Shift Supervisor will be the Center, if he is online. If he is not online, it shall move down the list to the next position, which would be Approach, then to Tower, and then to Ground. If two positions are online at the same rank, then the one who has the higher controller rank (If this is the same) then the one, who has been online the longest, shall assume the “Shift Supervisor” position. When this person leaves, the next person shall take over.
- The shift supervisor is responsible for:
- Assigning personal to positions appropriate to meet traffic needs.
- Validating that controllers meet certification requirements for positions.
- Contacting network Supervisors in the event of conflicts or disputes.
- Approving special situations, such as runway or airport closures, as permitted by CPS_011.
- Prior to assuming a position
- When logging on to work a position, a controller must log on as observer prior to assuming an active position.
- If controller will become the new shift supervisor, because of grade or staff position, he shall inform the current shift supervisor that he will assume that role, and advise him which position he will be taking.
- Otherwise, the controller shall request a desired position from the shift supervisor, if one is present, prior to manning a position. The shift supervisor may assign an alternate position at his discretion based on traffic conditions. The shift supervisor also has the discretion to revert to a "lower" position and assign the controller to the supervisors current position. This procedure is approved to allow a supervisor to open CTR as a priority and then maintain the option of reverting to an APP or lower position. The shift supervisor is responsible for assigning a position that the controller is rated to assume.
- Staff Instructors and Mentors must inform the shift supervisor of any training activity on manned positions prior to starting the training and/or moving students to new positions.
- Closing a position without relief
- A controller shall make a call-for-relief from observers or adjacent controllers as appropriate, prior to closing the position. The call should be made in accordance with the Communications Equipment Procedures SOP. If a higher facility will be assuming control of the airspace, the procedures for turnover described below should be followed. If no relief is obtained, and no higher facility will be assuming control of the airspace, all pilots should be informed via text and voice, that:
- The position is being closed.
- Frequency change is approved.
- Radar service is terminated (if applicable).
- Turning over control of a position
- A controller turning over operational control of his position shall conduct a position turnover briefing MUST COVER shall include the following elements, IN THE FOLLOWING ORDER. The preferred method for this, is on Teamspeak.
- Review:
- Current Positions Staffed (P)
- Weather Information
- Weather Trends (T)
- Current Weather (C)
- Significant Weather
- METARS
- Winds
- Altimeters
- PIREPS
- SIGMETS / CWAs (S)
- Airports
- Conditions/status
- Airport Configurations
- Flow Control
- Flow Control Restrictions
- Flow Control NOTAMS
- Special Activities, instructions or restrictions.
- Non-Standard Configurations
- Military Operations
- Active airspace
- Special Interest Flights
- Emergencies
- Training Positions
- NOTAM’s
- Traffic
- Individual Handoffs
- Traffic Situations
- Non-RVSM
- Point Out Aircraft
- Holding Aircraft
- Aircraft released but not yet airborne
- VFR aircraft
- Aircraft standing by for service
- Special Problems, requests, instructions.
- Delays
- Phraseology:
- Relief Controller: “Ready for Brief, PTCS”
- Leaving Controller: “Airports, [Normal, Noise, Southeast, West] Ops.
- … Flow Control
- If none, ”No Flow “
- …Hot Areas, Special Activities, Restrictions
- If none, “ No Special Activities or Restrictions”
- … [Instructor / Mentor] currently training [Student] on [Position].
- … If none, “No Training”
- … [Cite NOTAMS]
- If none, “No NOTAMS”
- … Traffic:
- Individual Handoffs: “AAL1028, (enroute, landing, departing, on the ground at [airport], holding short [runway], on vectors for [waypoint or procedure], missed approach [runway, airport]), Altitude (If necessary).
- Non-RVSM:
- “NWA10, IADOF [Cruise Alt], [Destination]” (IADOF = Invalid Altitude Direction of Flight)
- If none: “No IADOF”
- Point Out Aircraft:
- USA3817, Point out to [Position Name], Altitude, Procedure.
- NWA1018, Point out from [Position Name], Altitude, Reason (if needed)
- If none: “No Point outs”
- Holding Aircraft
- PWA187, Holding on [FIX], [Altitude], [EFC]
- If none, “No Holds”
- Aircraft Released
- N2571M, Released IFR [airport], [Initial Alt], [Beacon Code], [Clearance Void Time (If Applicable)]
- If none, “None Released”
- VFR Aircraft
- N19U, VFR [Direction or Destination], [Altitude], [Other]
- If none, “No VFR”
- Aircraft Standing by for Service
- AAL17, Waiting [Airport], [Destination], [Time Elapsed]
- If none, “No Waiting”
- Special Problems, requests, Instructions
- [Brief Comments about any irregularities or abnormal routes]
- If none, “No Special”
- … LAX CTR No Handoffs until [Time]
- If none, “No Delays”
- … Any questions?
- Relief Controller: “None.”
- Leaving Controller: “ [Initials]”
- Relief Controller: “ [Initials]
4. Unauthorized Controllers
-
- At times, controllers may attempt to assume positions for which they are not authorized. This situation is the responsibility of the shift supervisor only. The shift supervisor should follow these steps:
- Verify appropriate certification based on the roster information.
- Contact the controller, and determine whether the controller meets certification requirements per SOP and policy.
- If it has been determined that the controller does not meet requirements, ask the controller to disconnect, and review the appropriate web based SOP and policy pages. Report this information directly to the ATM or DATM as soon as possible.
- If the controller does not comply with this request, the shift supervisor should seek to turn the situation over to the ATM, DATM, or TA if available, or call for a VATSIM Supervisor via the ATC Channel, or WALLOP command.
- If none of these resources are available, the shift supervisor should take no further online action, but should record the controller’s name, and time of the occurrence, and forward this information to the ATM or DATM, immediately.
- The shift supervisor must remain professional and courteous in all interactions.
