Rules for "Vectors to Copenhagen"
Table of Contents
- Booking
- Controlling
- Time of Closure
- Software
1. Booking
1.1. Cross-booking
1.1.1. Controllers must not cross-book positions.
1.1.2. Cross-booking means booking the same two positions as another controller, but in reverse order between the early and late shifts.
1.1.2.1. Example: If one controller has booked EKCH_A_TWR early and EKCH_D_TWR late, another controller must not book EKCH_D_TWR early and EKCH_A_TWR late.
1.1.3. This is not permitted, as it may create a gap during the position changeover.
1.2. Repeated Bookings
1.2.1. Controllers should avoid booking the same or similar positions every week.
1.2.2. Controllers may not book the same position two weeks in a row unless no other suitable positions are available, or unless directed to do so by a staff member for operational reasons.
1.2.3. Controllers should also aim not to book a position on the same shift if they have controlled that position during the previous two events, unless no other suitable position is available or operational reasons require it.
1.3. Booking Etiquette
1.3.1. Booking etiquette must be strictly observed.
1.3.2. Controllers must be confident that they can attend before booking a position. While force majeure can occur, bookings should be made with a clear expectation of attendance.
1.3.3. If a controller is unsure whether they can attend, they should book a less critical position. EKCH_A_TWR, EKCH_A_GND, EKCH_W_APP, and EKCH_F_APP are considered critical positions.
1.3.4. If a booking is cancelled less than 48 hours before the event, Saturday evening, the controller should write in the VTC staffing thread to make others aware, allowing the position to be rebooked.
1.3.5. If a booking is cancelled less than 24 hours before the event, the controller must take the necessary steps to ensure that the position is covered. This may include contacting people directly or suggesting adjustments to the roster.
1.3.6. If a position becomes available, controllers should show consideration for those already booked and be respectful toward controllers who booked before them.
1.3.6.1. Example: If EKCH_D_TWR, EKCH_A_TWR, and a non-essential EKCH_C_TWR are booked, and EKCH_A_TWR cancels, the other booked controllers should be given a chance to move to EKCH_A_TWR before another controller books it.
1.3.6.2. If in doubt, controllers should write in the VTC staffing thread to coordinate.
1.3.7. Controllers must be ready to control at their scheduled time. Controllers should be ten minutes early, not five minutes late, and must inform others if they expect to be delayed.
1.4. "All Event" Bookings
1.4.1. APPCO/FINAL, EKDK_FMP, EKDK_D_CTR, EKCH_GW_TWR, and EKBI are "all event" bookable positions.
1.4.2. Controllers holding an EKCH rating should not occupy regional positions until all essential EKCH positions are filled.
1.4.3. Controllers who wish to open one of these positions earlier than booked may do so, provided they write their intention in the event chat.
1.4.5. Any position not listed as bookable, which a controller wishes to staff, must be advised in the event chat. This should only be done once all essential positions have been staffed.
2. Controlling
2.1. Rules and Procedures
2.1.1. Controllers must be properly familiar with the LAI for their position.
2.1.2. Controllers must ensure that they are not only qualified, but also capable of controlling the position they book.
1.2.2.1. Example: A controller who has recently been checked out and then had three months of inactivity should not book EKCH_F_APP during the late shift. Controllers are expected to use common sense.
1.2.2.2. Controllers without recent experience on a given position, such as EKCH_F_APP, should notify the Training Department. A side-by-side session will then be facilitated to ensure proper techniques, tips and best practices for managing a high-workload session.
2.1.3. Controllers booked on late or all-event positions must show up in time to be briefed before their controlling period begins.
2.2. Position Changes
2.2.1. If a controller's position closes after a shift change, they should consider switching early, approximately ten minutes before the scheduled changeover, to help ensure that all position changes are completed by 20:30.
2.2.2. Controllers on less busy positions should take initiative to begin the changeover approximately five minutes before the scheduled time, usually around 20:25. The changeover is a chain reaction and must be started somewhere. Controllers should assess whether they are in the best position to initiate it.
2.2.3. When relieving another controller, the relieving controller should connect using the callsign format XXXX_X1_XXX or XXXX_X__XXX.
2.2.4. The relieving controller must not take priority over the frequency until the controller being relieved is ready.
2.3. Flow Management and Approach Coordination
2.3.1. Flow Management Personnel (FMP) and the Approach Coordinator (APPCO) retain all relevant authority regarding flow management and coordination during VTC.
2.3.2. Controllers should, to the utmost of their ability, follow and respect the instructions and decisions issued by these positions.
2.4. Training during Vectors to Copenhagen
2.4.1. Training during Vectors to Copenhagen is generally permitted on specified positions; see the Event Training Policy, point 2.
3. Time of Closure
3.1. Booking Time
3.1.1. The ending time of late bookings must be respected unless it is clearly evident that the position is no longer required due to the current traffic flow.
3.2. 15-Minute Buffer Period
3.2.1. All controllers must be able to remain online for a minimum of 15 minutes after their booking expires.
3.2.2. This period must be used to safely redirect, hand off, or resolve any remaining traffic within the airspace.
3.2.3. ACC controllers must:
a) Clear any holding traffic, or agree with another controller to take over.
b) Divert and re-clear traffic as directed.
c) Mark the last aircraft to be released from the sector by writing it in the tag.
3.2.4. APP and GND controllers must:
a) Coordinate with all adjacent positions.
b) Attempt to find another controller to take over if the traffic load remains high.
4. Software
4.1. EuroScope
4.1.1. All controllers must have the latest sector files installed and must use the latest approved version of EuroScope as designated by VATSIM Scandinavia.
4.2. Plugins
4.2.1. vATIS must be updated before each use.