Event Documentation

• Rules for "Vectors to Copenhagen"
• VTC Briefings - Flow Controllers
• VTC Briefings - TWR Kastrup
• RIU 22R/22L - TWR + GND
• RIU 04R/04L - TWR + GND
• RIU 12/30 TWR+GND
• RIU ALL - DEL+S_GND
• VTC Briefings - APP Copenhagen
• RIU ALL - APPs
• RIU ALL - DEPs
• VTC Briefings - ACC Copenhagen
• All RIU - All ACCs
• Rules for "Proceed Direct to the Regionals"
• Statistics

Rules for "Vectors to Copenhagen"

Below are rules and guidelines for Vectors to Copenhagen. These must be adhered to and followed by every member to ensure a smooth event.

Booking

1.Do NOT crossbook

• This means if somebody has booked two positions (one early and one late) you shall NOT book the same two positions in reverse order
• This is because it would leave a gap inbetween changes

2. Do NOT book non-essential positions until all essential positions are booked for your rating class

• Exception may extraordinarily be taken to book Approach positions. there must be minimum three Approach controllers out of the four positions, (O, W, DEP, FINAL) but the delegation is up to the controller itself. this ONLY is valid for APP positions
  
• All solo endorsements are free to book non-essential positions, regardless of which essential positions are booked

3. Booking etiquette must be strictly observed

• If you cancel your booking less than 48 hours before the event (Saturday evening) Please write in the VTC staffing thread to make other members aware, so that they may rebook. 
• If you cancel your booking less than 24 hours before the event, take whatever actions needed to make sure your position is covered. Talk to people yourself, or suggest movement of roster. 
• While force majeure can happen you must be confident you can show up when you book a position. If you are not completely sure, book a less critical position (A_TWR, A_GND,W_APP,F_APP are critical)
• If a position opens up, show consideration to people on other booked positions and be just a tad respectful to people who booked before you.
  • EXAMPLE: D_TWR, A_TWR and non-essential C_TWR is booked. A_TWR cancel their booking. Give the two other booked controllers a chance to staff this position, and take their secondary position.
  • If in doubt? Write on the VTC thread to sort it out.
• Be ready to control at the time you have booked. Be 5 minutes early, not 5 minutes late. Inform others if you will be delayed

Controlling

1. Rules and Procedures

• Be properly familiar with the LAI for your position. 
• Read through the VTC briefing for each position where common pitfalls are highlighted
  • Read the briefings here or on next page
• Ensure you are not only qualified but also capable for the position you control
  • EXAMPLE: If you are fresh checked out followed by 3 months of inactivity, EKCH_F_APP on late will not be for you. use common sense

2. Switching of positions

• If you position closes after you switch, consider switching early (10 min before) to have everybody changed at 20.30
• If you sit at a less busy position be the one who take initiative to begin the changing 5 minutes before (20.25). It is a chain reaction and it must be started somewhere. Identify if you are in the best position to be that person. 
• relieving a controller should be done with the callsign XXXX_X1_XXX. Do not take priority over the frequency until relieved controller is ready

Software

1. Euroscope

• All controllers must have the latest sector files installed with the latest "approved" version of Euroscope by VATSIM-Scandinavia.

2. Plugins

• vStrips must be installed and used by all ground controllers
• CDM plugin must be used. Check documentation here
• vATIS must be updated before each use

VTC Briefings - Flow Controllers

If you have booked either EKDK_A_CTR or EKDK_E_CTR for any monday you are also part of the Flow Controller ACC team, and have additional duties.

Pre-Event

Did you book the VTC Manager position? Either one of you should. The VTC Manager position is the responsible entity for all the pre-event work, and they are as follows

Prepare Routings

Issue Simbrief Routings valid on the day. This needs to be done a few days in advance

Request f

Notice that these depend on the week because different events demands different restrictions. Normally identifiable on which of the cities Polaris have event in. Bergen or Oslo 

ENBR week:

• Mandatory Routing EDDL: MEVEL Y850 BASUM DCT DOSUR P729 TUDLO

 

VTC Briefings - TWR Kastrup

RIU 22R/22L - TWR + GND

EKCH_A_TWR

• You are in control of Cargo Apron and Hangar area. You may delegate to C_TWR if needed
• Familiarize yourself with Missed Approach procedure for the correct RWY!
  
• If getting RED conflicts, but it is clear the preceding will vacate before trailing touches down you are OK to continue. Issue TFC information with landing clearance 

---

Standard missed approach procedure MUST be given ALWAYS unless coordinated otherwise.

Missed approach 22L
Left heading 187, climb 3000’
Handover to EKCH_O_APP 118.455 

Missed approach should be announced as:
“Follow Standard Missed Approach procedure, Climb 3000” 
Or if the pilot is struggling:
"GO AROUND! Left turn NOW heading 187 climb 3000 ft." 

You should issue a Go- Around IF

• Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS
• Aircraft will touch down before the preceding has vacated.

Only give Go Around if needed. Every go around is a big strain on APP/F_APP.

---

Correlation with EKCH_C_TWR

BE AWARE of this to ease congestion and workload for the next controller 

Taxi Route	For gates	Handover to
Via B cross 30 hold short Z	All B,C,D,E,F + A7-A15	EKCH_A_GND
Via B hold short C	A4-A8 + A17-A34	EKCH_C_TWR
Via B hold short RWY30 (If vacating B5)
Via B, left onto RWY30 hold short D (If vacating B5)

Note that

• You can handover to EKCH_A_GND directly for traffic via B to hold short Z
• You must handover before reaching C for traffic to EKCH_C_TWR
• You can choose to taxi airplanes up to hold short D if congestion seems to be an issue at the B/30 intersection

EKCH_D_TWR (22R)

Northwest	Southwest	Southeast	West	North
KEMAX	LANGO NEXEN KOPEX	SIMEG SALLO	ODN	GOLGA VEDAR
Contact EKCH_W_DEP: 120.255 If EKCH_DEP is Offline then contact:
EKCH_O_APP: 118.455			EKCH_W_APP: 119.805

• See Wake Turbulence and Route separation below
• Check scenarios for PROP before JET
• Preceding MUST be past the Threshold before the next DEP CLR is given 

EKCH_C_TWR

ONLY use standard taxi routes unless coordinated with EKCH_A_GND

• K2+K3 are STANDARD for inbounds to A4-A34 (Not including A11-A15).
  • DO NOT ask before using
  • DO NOT accept wrong taxiways. Vacating B5 or missing C should still taxi up the runway for K3/K2 if needed. DO NOT overcrowd EKCH_A_GND

Flights taxiing via B to hold short Z does NOT need you. A_TWR will Cross them directly.  

You can use TWY D to any extend you like. Consider early coordination with TWR and GND

As aircraft crosses Runway 30, they should as good as you can be separated into South vs. North departures

You should assign a holding point for the departures. hand over to EKCH_D_TWR latest passing De-Icing platform A. Note that

• All WTC/H must use A1
• If a WTC/H is at A1, A2 is not usable
• If two airplanes are cleared to A1, traffic cannot pass behind.
• A4 is the last used holding point. A5 is only for extraordinary circumstances

EKCH_A_GND

Make sure you know standard taxi routes & pushback routes!

• Once handed from S_GND/DEL TSAT is out of the picture
• Agree with EKCH_C_TWR about the use of taxiway D, Ideas could be:
  • • • • Inbounds or Outbounds for C28-C36
        • Newbie pilots
• Adhere to “Release Points” to the greatest extent possible!
• Two WTC/H Aircrafts may not pass each other on Z/Y. Wingspan clearance is too little
• For split apron ops, adhere to 1 inbound 1 outbound at an intersection and observe hotspots:
• Do not use K3/K2 for outbounds, unless the situation specifically requires it. Coordinate before usage

EKCH_ D_GND

• Observe with split apron the Hotspots and how to manage without coordination
• Rule is, one controller has priority at a hotspot then the other controller taxies behind and the the first controller taxi as number three if more than two airplanes are at a hotspot
• EKCH_D_GND must observe no inbounds destined for that alley before commencing a pushback
• EKCH_A_GND must observe any ongoing pushbacks before taxiing into an alley
• HS1: Arrivals on Y goes first. Departures from Q/P goes behind. (NOTE different from 04R/04L)
• HS2: Arrivals must hold short Y and observe any ongoing pushback
• HS3: Arrivals on K3 must give way to first outbound and any subsequent blocking the ARR stand
• HS4: Departures from K must hold short J to give way to arrivals on K2.
• HS5: Departures from V must hold short of S to give way to first inbounds via K & R.
• HS5: Subsequent arrival should hold short of Y or Z to give way to beformentioned departure
• HS6: Departures from W must give way to first inbound at R & S

RIU 04R/04L - TWR + GND

EKCH_A_TWR

• Familiarize yourself with Missed Approach procedure for the correct RWY!
  
• If getting RED conflicts, but it is clear the preceding will vacate before trailing touches down you are OK to continue. Issue TFC information with landing clearance 

---

Standard missed approach procedure MUST be given ALWAYS unless coordinated otherwise.

Missed approach 04L
Left heading 347, climb 3000’
Handover to EKCH_W_APP 119.805 

Missed approach should be announced as:
“Follow Standard Missed Approach procedure, Climb 3000” 
Or if the pilot is struggling:
"GO AROUND! Left turn NOW heading 347 climb 3000 ft." 

You should issue a Go- Around IF

• Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS
• Aircraft will touch down before the preceding has vacated.

Only give Go Around if needed. Every go around is a big strain on APP/F_APP.

---

Correlation with EKCH_C_TWR

BE AWARE of this to ease congestion and workload for the next controller 

Taxi Route	For gates	Handover to
Via A cross RWY30 hold short Z	B4-B19 + A7-A15	EKCH_C_TWR* (see below)
Via A cross RWY30  via F , Hold short Z	B7-B9 + All C,D,E,F
Via A hold short RWY30	A4-A8 + A17-A34	EKCH_C_TWR

Note that

• You can handover to EKCH_A_GND directly for traffic via A and F if coordinated and agreed to by EKCH_C_TWR
• You must handover before reaching de-icing platform for traffic to EKCH_C_TWR
  

If airplanes vacate E3/E2 by mistake, either:

• Hand over to EKCH_D_TWR or taxi down B after coordination, only if traffic allows
• Turn via B to E3/E2 and cross the arrival runway again if taxiing via B is not an option.

EKCH_D_TWR

• See Wake Turbulence and Route separation below
• Check scenarios for PROP before JET
• Preceding MUST be past the Threshold before the next DEP CLR is given 

EKCH_C_TWR

ONLY use standard taxi routes unless coordinated with EKCH_A_GND

• K2+K3 are STANDARD for inbounds to A4-A34 (Not including A11-A15).
  • DO NOT ask before using
  • DO NOT accept wrong taxiways. Vacating B5 or missing C should still taxi up the runway for K3/K2 if needed. DO NOT overcrowd EKCH_A_GND

Coordinate as needed and desired with the two towers

As aircraft crosses Runway 30, they should as good as you can be separated into South vs. North departures

Assign a holding point for each aircraft to make TWR’s task easier.

• All WTC/H must use B1
• a WTC/M and smaller may use B3 
• B4 only to be used upon pilot approval
• Use holding points to sequence traffic in north/south configuration.
• Handover to EKCH_D_TWR latest passing B4

2. You control All regional airports (Except EKOD & EKSB)
3. You are the coordinator with the overview and the guy with the big picture. Help!
4. Review HOLDING CONTIGENCY. Be ready to help other ACCs!

Arrivals

Only Give the expected STAR!

Arrival	Descend to	Next SCT
TESPI (all runways)	FL250	EKDK_D_CTR (133.155)
TUDLO (all runways)	FL290	EKDK_D_CTR (133.155)

NOTE* MONAK arrivals do NOT come to you, but directly to EKDK_B_CTR from EDWW_B

Regional Airports inbounds

Coordinate with local ATC. If local ATC is online descend to as prescribed.

Destination	Descend to	Directs available
EKYT	FL130	BAKIT(26R)/GIPUG(08L)/AAL
EKBI	FL130	GELBA/LOKSA (Final) GIVNA/UVINA (south) EPARA/ODNEV (north-base)
EKAH	FL70	URUPA(28L) MOMZE(10R) TL
EKKA	FL130	EBISO(09R from CH) (south base) RIKSU(27L from CH) (final)
EKSB	N/A (FL70 if from the West, 290 if from east)	LIBRI (32) / VIBEN (14) Propose direct to EKDK_D.
EKSP	FL70	DINUT(28R) / TISET (08L) / VO

EKDK_D_CTR

• Do not send aeroplanes into APP airspace on anything other than the cleared STAR with the required separation (specified below) unless specifically coordinated with EKCH_W_APP
• You need to ensure a Minimum of 15nm between arrivals on each STAR.
  • If you cannot do this, you must start issuing holds.
• APP may ask you for other kinds of separation
• Keep an eye on ERNOV arrivals to ensure W_APP is not getting overloaded.
• 15nm/STAR=5nm average (3STARs) and W_APP needs to deliver with 7-10nm, so be ready to increase to 20nm or even 30nm between STARs if ERNOV has heavy inbound
• You control EKOD & EKSB

Arrivals

Arrival	Minimum separation	Next SCT	XFL
TESPI	15 nm (20 nm if other STARs are busy)	EKCH_W_APP (119.805)	FL130
TUDLO		EKCH_W_APP (119.805)	FL120
EKBI (09+27)	FL130	EKDK_CTR / EKBI_APP	FL130

Ensure aircraft are reaching their altitude restrictions.

Departures

SID	Climb to	Next ACC
GOLGA	FL240	EKDK_CTR (136.485)
ODN	FL280	EKDK_CTR (136.485)

EKDK_B_CTR

• Do not send aeroplanes into APP airspace on anything other than the cleared STAR with the required separation (specified below) unless specifically coordinated with EKCH_E_APP
• You need to ensure a Minimum of 15nm between arrivals on each STAR.
  • If you cannot do this, you must start issuing holds.
• APP may ask you for other kinds of separation
• Keep an eye on TIDVU arrivals to ensure E_APP is not getting overloaded.
• 15nm/STAR=7.5nm average (2STARs) and E_APP needs to deliver with 7-10nm, so be ready to increase to 20nm between STARs if TIDVU has heavy inbound
• If the hold is filed up, consider sending aeroplanes to D_CTR for TUDLO arrival if their traffic permits.

Arrival	Initial descend	Next SCT	XFL
MONAK (22L)	FL100 Level by NEKSO	EKCH_O_APP (118.455)	FL90
MONAK (04L)	FL80 Level by NEKSO	EKCH_O_APP (118.455)	FL90

Do not use FL200 for holding to keep open for inbounds from NIKDA/KOSEB. If the holding is getting full above FL200, ask EDWW to do an en-route hold at NIKDA/KOSEB.

SID	Climb to	Next ACC
NEXEN	FL280	EKDK_C_CTR (128.215) or EKDK_A_CTR (135.290) if none of these is online, to EKDK_CTR (136.485)
LANGO
KOPEX

Holding Contingency

The holding Contingency Procedure is in effect when Holdings around ROSBI, LUGAS, and CDA get overloaded, and second-stage en-route holdings need to be taken into effect. ALL En-route holdings are assigned by EKDK_V_CTR (or C, S, N if online).

Concerned ACCs	Arrival via	Contingency Procedure
EKDK_B_CTR	Via NIKDA/KOSEB to MONAK	Coordinate with EDUU to enter En-route holdings at NIKDA & KOSEB. Procedure direction discretion of EDUU
EKDK_CTR EKDK_B_CTR	Via GESKA to MONAK	Coordinate with EDYY. Level off FL290, clear to ODN and enter ODN hold Descends only after reaching holding for separation with departing traffic via LANGO/NEXEN/KOPEX. Re-plan flight via TUDLO or TESPI as appropriate.
EKDK_CTR EKDK_C/A_CTR	Via TALSA to TUDLO	Enter en-route holding at TALSA 072/L. Handover to EKDK_D, when released for Xhold, cleared to FL290 or Holding altitude whichever is lower
	Via BAVTA to TUDLO
EKDK_CTR	Via AAL to TESPI	Direct and enter en-route holding at AAL 072/L. Handover to EKDK_D, when released for Xhold, cleared to FL250 or Holding altitude whichever is lower
	Via BAVTA to TESPI

EKCH_W_APP

Adhere to RNAV STARs and rules for handing over to EKCH_F_APP, and read the following carefully

• Cleared no more than within 45 degrees of the Vector point
• If on an old AIRAC vector downwind on or outside of the Vector fix route
• Speed 200-230, or as agreed with F_APP
• Minimum average 7 - 10nm. If it starts getting difficult you must alert EKDK & ESMM
• If you need breathing room, ask EKDK to adjust flow to a minimum of 20nm between arrivals
• You get aircraft with an average minimum of 15nm between from ACC

---

You should NOT talk to EKCH_F_APP. He is the Silent partner.

Talk to EKCH_O_APP and coordinate spacing as well as possible.

Don’t be silent towards EKCH_O_APP. Make sure airplanes come in a nice string with the following criteria fulfilled. 

---

Remember to:

• When transferring to EKCH_F_APP make sure they have 4000 and the correct speed as agreed upon
• Transfer by stating “Contact Final approach CALLSIGN ONLY 120.205”
• Transfer ideally before passing Abeam Airfield
• Keep the ACCs honest regarding minimum spacing

Handover to Final Approach

The handover to the Final approach is a sensitive subject and requires utmost care and coordination from either approach. The following procedures must be met when high-traffic loads are present:

Aircraft must be unless otherwise specifically requested by EKCH_F_APP via RTI:

• Cleared no later than the last point before the vector begins
• On average 7 - 10nm separated from other traffic, unless otherwise coordinated.
• If cleared to the last point before the vector begins the track MUST be within 45˚ of the vector to be followed, except for ERNOV2C arrivals
• If traffic cannot be within 45˚ of the vector, traffic must either be cleared to the waypoint before, or coordinated with F_APP
• SPD & ALT must correspond to the table below

RWY	Altitude	Inbound	Speed
22L/22R	4000 MSL	ABEGI / ADOVI or earlier	200 - 230 knt.
04L/04R		ERPUK / DOPEM or earlier
12		FEDJO / AGTIC or earlier
30		HUFO / COPHO or earlier

All handovers to Final should be uttered with the condition «Callsign Only» «SAS42E, Contact Final, Callsign only, 120.205» 

EKCH_F_APP may use the TAG and ROF TOPSKY functions to request specific headings and request frequencies for aircraft when desired.

EKCH_O_APP

Adhere to RNAV STARs and rules for handing over to EKCH_F_APP, and read the following carefully

• You get aircraft with an average minimum of 15nm between from ACC
• Cleared no more than within 45 degrees of Vector point
• If old AIRAC vector on downwind on or outside of Vector fix route
• Speed 200-230, or as agreed with F_APP
• Minimum average 7 - 10nm. If it starts getting difficult you must alert EKDK & ESMM
• If you need breathing room, ask EKDK/ESMM to adjust flow to a minimum of 20nm between arrivals

---

You should NOT talk to EKCH_F_APP. He is the Silent partner.

Talk to EKCH_W_APP and coordinate spacing as well as possible.

Don’t be silent towards EKCH_W_APP. Make sure airplanes come in a nice string with the following criteria fulfilled.

---

Remember to:

• When transferring to EKCH_F_APP make sure they have 4000 and the correct speed as agreed upon
• Transfer by stating “Contact Final approach CALLSIGN ONLY 120.205”
• Transfer ideally before passing Abeam Airfield
• Keep the ACCs honest regarding minimum spacing
• Caution climbing aircraft around ESJAH/NEKSO

Handover to Final Approach

The handover to the Final approach is a sensitive subject and requires utmost care and coordination from either approach. The following procedures must be met when high-traffic loads are present:

Aircraft must be unless otherwise specifically requested by EKCH_F_APP via RTI:

• Cleared no later than the last point before the vector begins
• On average 7 - 10nm separated from other traffic, unless otherwise coordinated.
• If cleared to the last point before the vector begins the track MUST be within 45˚ of the vector to be followed, except for ERNOV2C arrivals
• If traffic cannot be within 45˚ of the vector, traffic must either be cleared to the waypoint before, or coordinated with F_APP
• SPD & ALT must correspond to the table below

RWY	Altitude	Inbound	Speed
22L/22R	4000 MSL	ABEGI / ADOVI or earlier	200 - 230 knt.
04L/04R		ERPUK / DOPEM or earlier
12		FEDJO / AGTIC or earlier
30		HUFO / COPHO or earlier

All handovers to Final should be uttered with the condition «Callsign Only» «SAS42E, Contact Final, Callsign only, 120.205» 

EKCH_F_APP may use the TAG and ROF TOPSKY functions to request specific headings and request on frequencies for aircraft when desired.

EKCH_F_APP

• You must have a 7 - 10nm minimum average on handover from W/O_APP
  • If you do NOT get that, tell them immediately!! Or you will get buried
• Consider putting on final before the vector-fix to avoid accidental base turn
• Standard separation on the final should be between 3-5nm, however, try to maintain a sharp 3 nm.
• Ensure 3nm or greater before handing it over to TWR
• If you are NOT able to sequence an aircraft in, turn it back to approach, for sequencing

---

Speed control within 10nm on the ILS must be EITHER:
180 until 6DME or 160 until 4DME

---

Dependent parallel operations: Minimum 2nm between arrivals on parallel runways.

Advise aircraft of the aircraft landing on parallel, and remember to transfer to the correct TWR

If the final gets 20nm or more, you need to enforce a complete approach stop! Do everything in your power to avoid this!!

EKCH_R_DEP (22R)

• Know the hotspots for departure crossing arrivals.
• Use caution before clearing A/C ABOVE FL70, due to arrivals
• Consider using Vectors and Directs to optimize flow. use TIP

SID	Primary next sector
NEXEN / LANGO / KOPEX	EKDK_B_CTR
ODN / GOLGA	EKDK_D_CTR
VEDAR / KEMAX	ESMM_K_CTR
SIMEG / SALLO	ESMS_APP

EKCH_R_DEP (04R)

• Know the hotspots for departure crossing arrivals.
• Use caution before clearing A/C ABOVE FL70, due to arrivals
• Consider using Vectors and Directs to optimize flow. use TIP
• Consider a right turn immediately for southbound. Give HDG as 185/175 to avoid confusion with cleared FL190 

SID	Primary next sector
NEXEN / LANGO / KOPEX	EKDK_B_CTR
ODN / GOLGA	EKDK_D_CTR
VEDAR / KEMAX	ESMM_K_CTR
SIMEG / SALLO	ESMS_APP

EKCH_A_TWR (22L)

• Familiarize yourself with Standard taxi routes for INBOUND traffic
• Familiarize yourself with Missed Approach procedure for the correct RWY!
• Determine if you are responsible for VFR and/or Cargo Apron
• If getting RED conflicts, but it is clear the preceding will vacate before trailing touches down you are OK to continue. Issue TFC information with landing clearance 

---

Standard missed approach procedure MUST be given ALWAYS unless coordinated otherwise.

Missed approach 22L
Left heading 187, climb 3000’
Handover to EKCH_O_APP 118.455 

Missed approach should be announced as:
“Follow Standard Missed Approach procedure, Climb 3000” 
Or if the pilot is struggling:
"GO AROUND! Left turn NOW heading 187 climb 3000 ft." 

You should issue a Go- Around IF

• Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS
• Aircraft will not be able to pass the threshold before the preceding has vacated.

Only give Go Around if needed. Every go around is a big strain on APP/F_APP

---

Correlation with EKCH_C_TWR

You should assign a stand for arriving aircraft, and send them via the correct taxiway as shown below.

BE AWARE of this to ease congestion and workload for the next controller 

For arrivals via B and to cargo apron to hold short Z, DO NOT hand over to C_TWR. Handover directly to EKCH_A_GND, or keep yourself for cargo apron

EKCH_A_TWR (04L)

• Familiarize yourself with Standard taxi routes for INBOUND traffic
• Familiarize yourself with Missed Approach procedure for the correct RWY!
• Transfer cargo airplanes to C_TWR before Runway 12/30. 

---

Standard missed approach procedure MUST be given ALWAYS unless coordinated otherwise.

Missed approach 22L
Left heading 347, climb 3000’
Handover to EKCH_W_APP 119.805 

Missed approach should be announced as:
“Follow Standard Missed Approach procedure, Climb 3000” 
Or if the pilot is struggling:
"GO AROUND! Left turn NOW heading 347 climb 3000 ft." 

You should issue a Go- Around IF

• Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS
• Aircraft will not be able to pass the threshold before the preceding has vacated.

Only give Go Around if needed. Every go around is a big strain on APP/F_APP

---

Correlation with EKCH_C_TWR

You should assign a stand for arriving aircraft, and send them via the correct taxiway as shown below.

BE AWARE of this to ease congestion and workload for the next controller 

If airplanes vacate E3/E2 by mistake, either:

• Hand over to EKCH_D_TWR only if traffic allows
• Turn via B to E3/E2 and cross the arrival runway again

EKCH_D_TWR (22R)

Northwest	Southwest	Southeast	West	North
KEMAX	LANGO NEXEN KOPEX	SIMEG SALLO	ODN	GOLGA VEDAR
Contact EKCH_DEP: 120.255 If EKCH_DEP is Offline then contact:
EKCH_O_APP: 118.455			EKCH_W_APP: 119.805

• see Wake Turbulence and Route separation below
• Check scenarios for PROP before JET
• Preceding MUST be past the Threshold before the next DEP CLR is given 

EKCH_D_TWR (04R)

• see Wake Turbulence and Route separation below
• Check scenarios for PROP before JET
• Preceding MUST be past the Threshold before the next DEP CLR is given 

EKCH_C_TWR

ONLY use standard taxi routes unless coordinated with EKCH_A_GND

• K2+K3 are STANDARD for inbounds to A4-A34 (Not including A11-A15).
  • DO NOT ask before using
  • DO NOT accept wrong taxiways. Vacating B5 or missing C should still taxi up the runway for K3/K2 if needed. DO NOT overcrowd EKCH_A_GND

Flights taxiing via B to hold short Z does NOT need you. A_TWR will Cross them directly.  

As aircraft crosses Runway 30, they should as good as you can be separated into South vs. North departures

• SOUTH TURNS:
  • NEXEN
  • LANGO
    
  • KOPEX
  • SIMEG
  • SALLO
  • KEMAX
• NORTH TURNS:
  • ODN
  • GOLGA
  • VEDAR

Assign a holding point for each aircraft to make TWR’s task easier.

Heavy Aircraft must be assigned A1/B1

EKCH_A_GND (04R/04L)

Make sure you know standard taxi routes & pushback routes

• Once handed from S_GND/DEL TSAT is out of the picture
• Adhere to proper use of Taxiway D

 

 

EKCH_D_GND

• Observe with split apron the Hotspots and how to manage without coordination
• Rule is, one controller has priority at a hotspot then the other controller taxies behind and the the first controller taxi as number three if more than two airplanes are at a hotspot
• EKCH_D_GND must observe no inbounds destined for that alley before commencing a pushback
• EKCH_A_GND must observe any ongoing pushbacks before taxiing into an alley
• HS1: Departure goes first onto D. Arrival holding short of Z goes as second. (NOTE different from 22R/22L)
• HS2: Arrivals must hold short Y and observe any ongoing pushback
• HS3: Arrivals on K3 must give way to first outbound and any subsequent blocking the ARR stand
• HS4: Departures from K must hold short J to give way to arrivals on K2.
• HS5: Departures from V must hold short of S to give way to first inbounds via K & R.
• HS5: Subsequent arrival should hold short of Y or Z to give way to beformentioned departure
• HS6: Departures from W must give way to first inbound at R & S

RIU 12/30 TWR+GND

RIU ALL - DEL+S_GND

EKCH_S_GND

Your main task is sequencing airplanes for startup, by use of TSATs

Pre- Clearance:

• As aircrafts are spawned, fill in the Squawks in Vstripsif possible
• Help reposition aircrafts that are spawned oddly on taxiway
• Review flightplans to confirm correctness!
• Log on CDM as “.cdm ekch master”

---

Post Clearance

• A/Cs transfers immediately to you, where you manage them and give them start up at correct times.
• When aircraft report ready for start:
  • Find aircraft in departure list
  • Press on RDY to mark airplane reported ready
  • If GREEN Aircraft is approved for startup
    • Move TAG to READY bay and transfer to EKCH_A_GND
  • If ORANGE Aircraft is NOT approved for startup
    • Move TAG to STANDBY bay until TSAT turns Green
    • When TSAT is green, move to READY and transfer to EKCH_A_GND

EKCH_DEL

• Write “.cdm master ekch” if S_GND is offline. Write “.cdm slave ekch” if S_GND is online
• Write “.cdm slave ekch” before logging off!!! Otherwise all times are lost
• IF EKCH_S_GND is offline Keep aircraft on your frequency until startup.
• Use CDM system to ensure proper sequencing and not to overload GND
• WHEN EKCH_S_GND is online
• With “readback correct” send aircraft immediately to EKCH_S_GND. He will sequence them

Check for correct departure. If wrong departure is filed, Re-clear on correct departure.

– No coordination needed: for A380/B748 clear off 22L/04R 
– Coordination needed: All other desired departures off non-active departure runway

FLOW Management when “Readback Correct” if no EKCH_S_GND online:

1. Tell pilot “Report Ready for startup”
   
2. Pilot advises ready for startup, click RDY and to stipulate time.

A/C ready for startup:

1. Find A/C in Startup list, and click RDY regardless of TSAT color.
2. If TSAT is displayed in GREEN the aircraft is approved for startup
   
3. If TSAT is displayed in ORANGE the TSAT window has not been reached.
4. If still ORANGE, aircraft must wait. Tranfer to STANDBY bay until TSAT is GREEN

NOTE: If EKCH_S_GND is online, transfer immediately after advising TSAT. Use phrase.
“Readback correct, TSAT at 1225z, report ready to Apron on 121.905”

IFR flights with no SID:
Follow procedures stated in the Non Standard IFR Clearance

More info regarding CDM and its use can be found here

VTC Briefings - APP Copenhagen

RIU ALL - APPs

EKCH_W_APP 

Adhere to RNAV STARs and rules for handing over to EKCH_F_APP, and read the following carefully

• Use Euroscope time estimates to predict who comes first! (right click on AFL)
• Cleared no more than within 45 degrees of the Vector point
• If on an old AIRAC vector downwind on or outside of the Vector fix route
• Speed 210-230, or as agreed with F_APP. Consider wind and traffic load and consider
  • • 230 only if traffic needs to be expedited e.g. due to space in front, but not behind
    • 220 if traffic load is "relatively" low and tailwind not extreme
    • 210 if traffic load is high or tailwind extreme
• Minimum average 7 - 10nm. If it starts getting difficult you must alert EKDK & ESMM for holdings.
• If you need breathing room, ask EKDK and ESMM to adjust flow to a minimum of 20nm between arrivals
• You get aircraft with an average minimum of 15nm between from ACC
  
• Respect that DEP has priority below FL75

---

You should NOT talk to EKCH_F_APP. He is the Silent partner.

Talk to EKCH_O_APP and coordinate spacing as well as possible.

Don’t be silent towards EKCH_O_APP. Make sure airplanes come in a nice string with the following criteria fulfilled. 

---

Remember to:

• When transferring to EKCH_F_APP make sure they are cleared to 4000 and the correct speed
• Transfer by stating “Contact Final approach CALLSIGN ONLY 120.205”
• Transfer ideally before passing Abeam Airfield
• Do not accept too little spacing, but at the same time fit as many airplanes in as you can. 

Handover to Final Approach

The handover to the Final approach is a sensitive subject and requires utmost care and coordination from either approach. The following procedures must be met when high-traffic loads are present:

Aircraft must be unless otherwise specifically requested by EKCH_F_APP via RTI:

• Cleared no later than the last point before the vector begins
• On average 7 - 10nm separated from other traffic, unless otherwise coordinated.
• If cleared to the last point before the vector begins the track MUST be within 45˚ of the vector to be followed, except for ERNOV2C arrivals
• If traffic cannot be within 45˚ of the vector, traffic must either be cleared to the waypoint before, or coordinated with F_APP
• SPD & ALT must correspond to the table below

RWY	Altitude	Inbound	Speed
22L/22R	4000 MSL	ABEGI / ADOVI or earlier	200 - 230 knt.
04L/04R		ERPUK / DOPEM or earlier
12		FEDJO / AGTIC or earlier
30		HUFO / COPHO or earlier

For Runway 12/30 in use all airplanes MUST have MINIMUM 10-12 nm in between!

All handovers to Final should be uttered with the condition «Callsign Only» «SAS42E, Contact Final, Callsign only, 120.205» 

EKCH_F_APP may use the TAG and ROF TOPSKY functions to request specific headings and request frequencies for aircraft when desired.

EKCH_O_APP

Adhere to RNAV STARs and rules for handing over to EKCH_F_APP, and read the following carefully

• Use Euroscope time estimates to predict who comes first! (right click on AFL)
• Cleared no more than within 45 degrees of the Vector point
• If on an old AIRAC vector downwind on or outside of the Vector fix route
• Speed 210-230, or as agreed with F_APP. Consider wind and traffic load and consider
  • • 230 only if traffic needs to be expedited e.g. due to space in front, but not behind
    • 220 if traffic load is "relatively" low and tailwind not extreme
    • 210 if traffic load is high or tailwind extreme
• Minimum average 7 - 10nm. If it starts getting difficult you must alert EKDK & ESMM for holdings.
• MONAK may come with as little as 10nm if there are no TIDVU arrivals. MONAK will be busy
• Respect that DEP has priority below FL75

---

You should NOT talk to EKCH_F_APP. He is the Silent partner.

Talk to EKCH_W_APP and coordinate spacing as well as possible.

Don’t be silent towards EKCH_W_APP. Make sure airplanes come in a nice string with the following criteria fulfilled.

---

Remember to:

• When transferring to EKCH_F_APP make sure they have 4000 and the correct speed as agreed upon
• Transfer by stating “Contact Final approach CALLSIGN ONLY 120.205”
• Transfer ideally before passing Abeam Airfield
• Keep the ACCs honest regarding minimum spacing
• Caution climbing aircraft around ESJAH/NEKSO

Handover to Final Approach

The handover to the Final approach is a sensitive subject and requires utmost care and coordination from either approach. The following procedures must be met when high-traffic loads are present:

Aircraft must be unless otherwise specifically requested by EKCH_F_APP via RTI:

• Cleared no later than the last point before the vector begins
• On average 7 - 10nm separated from other traffic, unless otherwise coordinated.
• If cleared to the last point before the vector begins the track MUST be within 45˚ of the vector to be followed, except for ERNOV2C arrivals
• If traffic cannot be within 45˚ of the vector, traffic must either be cleared to the waypoint before, or coordinated with F_APP
• SPD & ALT must correspond to the table below

RWY	Altitude	Inbound	Speed
22L/22R	4000 MSL	ABEGI / ADOVI or earlier	200 - 230 knt.
04L/04R		ERPUK / DOPEM or earlier
12		FEDJO / AGTIC or earlier
30		HUFO / COPHO or earlier

For Runway 12/30 in use all airplanes MUST have MINIMUM 10-12 nm in between!

All handovers to Final should be uttered with the condition «Callsign Only» «SAS42E, Contact Final, Callsign only, 120.205» 

EKCH_F_APP may use the TAG and ROF TOPSKY functions to request specific headings and request frequencies for aircraft when desired.

EKCH_F_APP

• at highest load you should get around 7-10nm between each airplane to fit them into a 3-4nm final
  
  • If you do NOT get that, tell them immediately!! Or you will get buried
• Consider putting on a vector before the vector-fix to avoid accidental base turn
• Standard separation on the final should be between 3-5nm, however, try to maintain a sharp 3 nm.
• Ensure 3nm or greater before handing it over to TWR
• If you are NOT able to sequence an aircraft in, turn it back to approach, for sequencing

---

Speed control before handover
ask for 220 for normal periods with tailwind not extreme
ask for 210 for periods with high load (more than 15nm finals) and extreme tailwind

Speed control
keep handover speed until turning base. Consider using 200, never less than 180
The slower the airplane the more backed up they will get, because subsequent airplanes are so much faster

Once on the ILS 180kts! 200kts if they need to catch up to airplane ahead. 160 kts once desired separation is achieved. Never minimum approach speed unless LOS is imminent

Speed control within 10nm on the ILS must be EITHER:
180 until 6-DME if they need to catch up to the guy ahead
otherwise 160 until 4-DME

---

Dependent parallel operations: Minimum 2nm between arrivals on parallel runways.

Advise aircraft of the aircraft landing on parallel, and transfer ALWAYS to EKCH_A_TWR for both runways

If the final gets 20nm or more, you need to enforce a complete approach stop! Do everything in your power to avoid this!!

For RIU 12/30 aim for 5nm finals to give space to departures and/or crossings

RIU ALL - DEPs

EKCH_R_DEP / EKCH_K_DEP (22R)

• Know the hotspots for departure crossing arrivals.
• Do NOT clear departures above FL70 until path is clear of arrivals
• Consider using Vectors and Directs to optimize flow.
• Respect that EKCH_W/O_APP have priority above FL75.
  
• R_DEP means controlling departures that passes Roskilde TMA
• K_DEP means controlling departures that are in Københavns TMA

Owner	SID	Primary next sector
K_DEP	NEXEN / LANGO / KOPEX	EKDK_B_CTR
R_DEP	ODN / GOLGA	EKDK_D_CTR
	VEDAR	ESMM_K_CTR
K_DEP	KEMAX
	SIMEG / SALLO	ESMS_APP

EKCH_R_DEP / EKCH_K_DEP (04R)

• Know the hotspots for departure crossing arrivals.
• Do NOT clear departures above FL70 until path is clear of arrivals
• Consider using Vectors and Directs to optimize flow.
• Respect that EKCH_W/O_APP have priority above FL75.
  
• R_DEP means controlling departures that passes Roskilde TMA
• K_DEP means controlling departures that are in Københavns TMA

For NEXEN/LANGO/KOPEX/SIMEG/SALLO a turn to 185/175 is good to do as soon as they check in to speed up traffic flow

VTC Briefings - ACC Copenhagen

All RIU - All ACCs

EKDK_CTR (136.485)

1. Make sure you are familiar with the airspace divide
2. Help D/E with managing Inbounds. And especially holdings
3. Help B/I by taking flights from EDYY aspr. Hold Contingency
4. You control All regional airports (Except EKOD & EKSB)
5. You are the coordinator with the overview and the guy with the big picture. Help!
6. Review HOLDING CONTIGENCY. Be ready to help other ACCs!

Arrivals

Only Give the expected STAR!

Arrival	Descend to	Next SCT
TESPI (all runways)	FL250	EKDK_D_CTR (133.155)
TUDLO (all runways)	FL290	EKDK_D_CTR (133.155)

NOTE* MONAK arrivals do NOT come to you, but directly to EKDK_B_CTR from EDWW_B

Regional Airports inbounds

Coordinate with local ATC. If local ATC is online descend to as prescribed.

Destination	Descend to	Directs available
EKYT	FL130	BAKIT(26R)/GIPUG(08L)/AAL
EKBI	FL130	GELBA/LOKSA (Final) GIVNA/UVINA (south) EPARA/ODNEV (north-base)
EKAH	FL70	URUPA(28L) MOMZE(10R) TL
EKKA	FL130	EBISO(09R from CH) (south base) RIKSU(27L from CH) (final)
EKSB	N/A (FL70 if from the West, 290 if from east)	LIBRI (32) / VIBEN (14) Propose direct to EKDK_D.
EKSP	FL70	DINUT(28R) / TISET (08L) / VO

EKDK_D_CTR (133.155) or EKDK_E_CTR (123.730)

• Do not send airplanes into APP airspace on anything other than the cleared STAR with the required separation (specified below) unless specifically coordinated with EKCH_W_APP
• You need to CLOSELY adhere to ACC LAI3 point 2.4.4
• APP may ask you for other kinds of separation
• Keep an eye on ERNOV arrivals to ensure W_APP is not getting overloaded.
  
• You control EKOD. 
• Arrivals into EKSB shall be cleared appropriately

Arrivals

Arrival	Minimum separation	Next SCT	XFL
TESPI	15 nm (20 nm if other STARs are busy) ACC LAI3 point 2.4.4	EKCH_W_APP (119.805)	FL130
TUDLO		EKCH_W_APP (119.805)	FL120
EKBI (09+27)	10nm	EKDK_CTR / EKBI_APP	FL130
EKSB (RIU 32)		EKDK_S_CTR/EKSP_APP/EKSB_I_TWR	3500'
EKSB (RIU 14)		EKDK_S_CTR/EKSP_APP	FL70

Departures

SID	Climb to	Next ACC
GOLGA	FL240	EKDK_CTR (136.485)
ODN	FL280	EKDK_CTR (136.485)

EKDK_B_CTR

• Do not send airplanes into APP airspace on anything other than the cleared STAR with the required separation (specified below) unless specifically coordinated with EKCH_W_APP
• You need to CLOSELY adhere to ACC LAI3 point 2.4.4
• APP may ask you for other kinds of separation
• Keep an eye on TIDVU arrivals.
  

If no TIDVU arrivals are inbound, reduce all the way to 10-15 nm separation to keep flow coming

• If CDA hold is filled up, consider sending airplanes to D_CTR for TUDLOU arrival if their traffic permits.
• Have EKDK_CTR or EKDK_A_CTR handle GESKA inbounds to keep above FL285 if chaos is extreme

Arrival	Initial descend	Next SCT	XFL
MONAK (22L)	FL100 Level by NEKSO	EKCH_O_APP (118.455)	FL90
MONAK (04L)	FL80 Level by NEKSO	EKCH_O_APP (118.455)	FL90

Do not use FL200 for holding to keep open for inbounds from NIKDA/KOSEB. If the holding is getting full above FL200, ask EDWW to do an en-route hold at NIKDA/KOSEB.

SID	Climb to	Next ACC
NEXEN	FL280	EKDK_C_CTR (128.215) or EKDK_A_CTR (135.290) if none of these is online, to EKDK_CTR (136.485)
LANGO
KOPEX

Rules for "Proceed Direct to the Regionals"

Statistics

Vectors to Copenhagen

Vectors to Copenhagen

A lot of statistics of VTC needs to be published, so we can see the data of our effort. The year started with the old format, which then moved to the new format. as you see in the long table below consider the following observations

• See the huge difference in traffic numbers between the old and new format (Remember the data shows arrivals in he 17z-22z period regardless). Expanding the event, expanded the traffic. 
• You see some huge dips once in a while on an event. Those are the times the event was not published on VATSIM event page, aka. half of our pilots at VTC comes because they are reminded of the event, the other half comes because they know monday is Copenhagen day! 
• There is a DIRECT correlation (data not shown) between fitting in A LOT of arrivals in the 21-22 local time window and the amount of traffic landing after 22.30. Therefore... The tighter the final and the more traffic we get in in that 21-22 window, the earlier the event finishes. the times of less than 32 arrivals an hour are often where you see a lot of the arrivals after 22.30. That's why we are adamant about less separation on final and effective traffic handling in event times

Table of departures and arrivals and timings

Graph of departures and arrivals

Arrivals and Departures 

Hopefully, nobody will be surprised that MONAK is the most popular inbound routing and NEXEN/LANGO the most popular outbound. Here are the exact tables