# 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.

<p class="callout warning align-center">Missed approach 22L  
**Left heading 187, climb 3000’**  
Handover to EKCH\_O\_APP 118.455 </p>

Missed approach should be announced as:  
**<span style="text-decoration: underline;">“Follow Standard Missed Approach procedure, Climb 3000” </span>**  
Or if the pilot is struggling:  
<span style="text-decoration: underline;">**"GO AROUND! Left turn NOW heading 187 climb 3000 ft."** </span>

You should issue a Go- Around IF

- <span style="text-decoration: underline;">**Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS**</span>
- <span style="text-decoration: underline;">**Aircraft will touch down before the preceding has vacated.**</span>

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

---

#### <span style="color: rgb(52, 73, 94);">**Correlation with EKCH\_C\_TWR**</span>

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

<table border="1" id="bkmrk-taxi-route-for-gates" style="border-collapse: collapse; width: 100%; height: 148.125px; background-color: #ced4d9; border: 1px solid #34495E;"><colgroup><col style="width: 50.0618%;"></col><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col></colgroup><tbody><tr style="height: 36.7344px;"><td style="height: 36.7344px; border-color: rgb(52, 73, 94);"><sub>Taxi Route</sub></td><td style="height: 36.7344px; border-color: rgb(52, 73, 94);"><sub>For gates</sub></td><td style="height: 36.7344px; border-color: rgb(52, 73, 94);"><sub>Handover to</sub></td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">B</span>** cross 30 hold short **<span style="background-color: rgb(241, 196, 15);">Z</span>**</td><td style="height: 33.7969px; border-color: rgb(52, 73, 94);"><span style="background-color: rgb(45, 194, 107);">All B,C,D,E,F</span> + <span style="background-color: rgb(230, 126, 35);">A7-A15</span></td><td style="height: 33.7969px; border-color: rgb(52, 73, 94);">EKCH\_A\_GND</td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">B</span>** hold short **<span style="background-color: rgb(241, 196, 15);">C</span>**</td><td rowspan="3" style="height: 77.5938px; border-color: rgb(52, 73, 94);"><span style="background-color: rgb(230, 126, 35);">A4-A8 + A17-A34</span>  
</td><td rowspan="3" style="height: 77.5938px; border-color: rgb(52, 73, 94);">EKCH\_C\_TWR  
</td></tr><tr style="height: 10px;"><td style="height: 10px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">B</span>** hold short <span style="background-color: rgb(224, 62, 45); color: rgb(236, 240, 241);">RWY30</span> (If vacating **<span style="background-color: rgb(241, 196, 15);">B5</span>**)</td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">B</span>**, left onto <span style="background-color: rgb(224, 62, 45); color: rgb(236, 240, 241);">RWY30 </span>hold short **<span style="background-color: rgb(241, 196, 15);">D</span>** (If vacating **<span style="background-color: rgb(241, 196, 15);">B5</span>**)</td></tr></tbody></table>

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)

<table border="1" id="bkmrk-northwest-southwest-" style="border-collapse: collapse; width: 100%; background-color: #ecf0f1; border: 1px solid #34495E;"><colgroup><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col></colgroup><tbody><tr><td class="align-center" style="border-color: rgb(52, 73, 94);">Northwest</td><td class="align-center" style="border-color: rgb(52, 73, 94);">Southwest</td><td class="align-center" style="border-color: rgb(52, 73, 94);">Southeast</td><td class="align-center" style="border-color: rgb(52, 73, 94);">West</td><td class="align-center" style="border-color: rgb(52, 73, 94);">North</td></tr><tr><td class="align-center" style="border-color: rgb(52, 73, 94);">KEMAX</td><td class="align-center" style="border-color: rgb(52, 73, 94);">LANGO  
NEXEN  
KOPEX</td><td class="align-center" style="border-color: rgb(52, 73, 94);">SIMEG  
SALLO</td><td class="align-center" style="border-color: rgb(52, 73, 94);">ODN</td><td class="align-center" style="border-color: rgb(52, 73, 94);">GOLGA  
VEDAR</td></tr><tr><td class="align-center" colspan="5" style="border-color: rgb(52, 73, 94);">Contact EKCH\_W\_DEP: 120.255  
If EKCH\_DEP is Offline then contact:  
</td></tr><tr><td class="align-center" colspan="3" style="border-color: rgb(52, 73, 94);">EKCH\_O\_APP: 118.455</td><td class="align-center" colspan="2" style="border-color: rgb(52, 73, 94);">EKCH\_W\_APP: 119.805</td></tr></tbody></table>

- 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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/mi6image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/mi6image.png)

## 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 <span style="text-decoration: underline;">**NOT**</span> 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 <span style="text-decoration: underline;">as good as you can</span> be separated into South vs. North departures

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/5ttimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/5ttimage.png)

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 &amp; pushback routes!](https://wiki.vatsim-scandinavia.org/books/lai/page/lai-3-apron-control)

- 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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/vHtimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/vHtimage.png)

## 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
- **<span style="text-decoration: underline;">HS1</span>**: Arrivals on Y goes first. Departures from Q/P goes behind. (NOTE different from 04R/04L)
- **<span style="text-decoration: underline;">HS2</span>**: Arrivals must hold short Y and observe any ongoing pushback
- **<span style="text-decoration: underline;">HS3</span>**: Arrivals on K3 must give way to first outbound and any subsequent blocking the ARR stand
- **<span style="text-decoration: underline;">HS4</span>**: Departures from K must hold short J to give way to arrivals on K2.
- **<span style="text-decoration: underline;">HS5</span>**: Departures from V must hold short of S to give way to first inbounds via K &amp; R.
- **<span style="text-decoration: underline;">HS5</span>**: Subsequent arrival should hold short of Y or Z to give way to beformentioned departure
- **<span style="text-decoration: underline;">HS6</span>**: Departures from W must give way to first inbound at R &amp; S

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/laaimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/laaimage.png)

# 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.

<p class="callout warning align-center">Missed approach 04L  
**Left heading 347, climb 3000’**  
Handover to EKCH\_W\_APP 119.805 </p>

Missed approach should be announced as:  
**<span style="text-decoration: underline;">“Follow Standard Missed Approach procedure, Climb 3000” </span>**  
Or if the pilot is struggling:  
<span style="text-decoration: underline;">**"GO AROUND! Left turn NOW heading 347 climb 3000 ft."** </span>

You should issue a Go- Around IF

- <span style="text-decoration: underline;">**Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS**</span>
- <span style="text-decoration: underline;">**Aircraft will touch down before the preceding has vacated.**</span>

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

---

#### <span style="color: rgb(52, 73, 94);">**Correlation with EKCH\_C\_TWR**</span>

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

<table border="1" id="bkmrk-taxi-route-for-gates" style="border-collapse: collapse; width: 100%; height: 148.125px; background-color: #ced4d9; border: 1px solid #34495E;"><colgroup><col style="width: 50.0618%;"></col><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col></colgroup><tbody><tr style="height: 36.7344px;"><td style="height: 36.7344px; border-color: rgb(52, 73, 94);"><sub>Taxi Route</sub></td><td style="height: 36.7344px; border-color: rgb(52, 73, 94);"><sub>For gates</sub></td><td style="height: 36.7344px; border-color: rgb(52, 73, 94);"><sub>Handover to</sub></td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">A</span>** cross <span style="background-color: rgb(224, 62, 45); color: rgb(236, 240, 241);">RWY30</span> hold short **<span style="background-color: rgb(241, 196, 15);">Z</span>**</td><td style="height: 33.7969px; border-color: rgb(52, 73, 94);"><span style="background-color: rgb(45, 194, 107);">B4-B19</span> + <span style="background-color: rgb(230, 126, 35);">A7-A15</span></td><td rowspan="2" style="height: 33.7969px; border-color: rgb(52, 73, 94);">EKCH\_C\_TWR\* (see below)  
</td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">A</span>** cross <span style="background-color: rgb(224, 62, 45); color: rgb(236, 240, 241);">RWY30 </span> via **<span style="background-color: rgb(241, 196, 15);">F </span>**, Hold short **<span style="background-color: rgb(241, 196, 15);">Z</span>**</td><td style="height: 77.5938px; border-color: rgb(52, 73, 94);"><span style="background-color: rgb(45, 194, 107);">B7-B9</span> + <span style="background-color: rgb(45, 194, 107);">All C,D,E,F</span></td></tr><tr style="height: 10px;"><td rowspan="2" style="height: 10px; border-color: rgb(52, 73, 94);">Via **<span style="background-color: rgb(241, 196, 15);">A</span>** hold short <span style="background-color: rgb(224, 62, 45); color: rgb(236, 240, 241);">RWY30</span>  
</td><td rowspan="2" style="border-color: rgb(52, 73, 94);"><span style="background-color: rgb(230, 126, 35);"><span style="background-color: rgb(230, 126, 35);">A4-A8 + A17-A34</span></span>  
</td><td style="border-color: rgb(52, 73, 94);">EKCH\_C\_TWR</td></tr></tbody></table>

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 **<span style="background-color: rgb(241, 196, 15);">E3</span>**/**<span style="background-color: rgb(241, 196, 15);">E2</span>** by mistake, either:

- Hand over to EKCH\_D\_TWR or taxi down B after coordination, only if traffic allows
- Turn via **<span style="background-color: rgb(241, 196, 15);">B</span>** to **<span style="background-color: rgb(241, 196, 15);">E3</span>**/**<span style="background-color: rgb(241, 196, 15);">E2</span>** 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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/jj8image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/jj8image.png)

## 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 <span style="text-decoration: underline;">as good as you can</span> be separated into South vs. North departures

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/5ttimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/5ttimage.png)

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

1. 
2. You control All regional airports (Except EKOD &amp; 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 <span style="text-decoration: underline;">expected</span> STAR!

<table border="1" id="bkmrk-arrival-descend-to-n" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 33.3333%;"></col><col style="width: 33.3333%;"></col><col style="width: 33.3333%;"></col></colgroup><tbody><tr><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Arrival**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Descend to**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Next SCT**</span></td></tr><tr><td>TESPI (all runways)</td><td>FL250</td><td>EKDK\_D\_CTR (133.155)</td></tr><tr><td>TUDLO (all runways)</td><td>FL290</td><td>EKDK\_D\_CTR (133.155)</td></tr></tbody></table>

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.

<table border="1" id="bkmrk-destination-descend-" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 33.3333%;"></col><col style="width: 33.3333%;"></col><col style="width: 33.3333%;"></col></colgroup><tbody><tr><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Destination**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Descend to**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Directs available**</span></td></tr><tr><td>EKYT</td><td>FL130</td><td>BAKIT(26R)/GIPUG(08L)/AAL</td></tr><tr><td>EKBI</td><td>FL130</td><td>GELBA/LOKSA (Final)  
GIVNA/UVINA (south)  
EPARA/ODNEV (north-base)</td></tr><tr><td>EKAH</td><td>FL70</td><td>URUPA(28L) MOMZE(10R) TL</td></tr><tr><td>EKKA</td><td>FL130</td><td>EBISO(09R from CH) (south base)  
RIKSU(27L from CH) (final)</td></tr><tr><td>EKSB</td><td>N/A (FL70 if from the West, 290 if from east)</td><td>LIBRI (32) / VIBEN (14)  
Propose direct to EKDK\_D.</td></tr><tr><td>EKSP</td><td>FL70</td><td>DINUT(28R) / TISET (08L) / VO</td></tr></tbody></table>

## 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 &amp; EKSB

### Arrivals

<table border="1" id="bkmrk-arrival-minimum-sepa" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 21.7553%;"></col><col style="width: 34.6106%;"></col><col style="width: 21.7553%;"></col><col style="width: 21.8789%;"></col></colgroup><tbody><tr><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Arrival**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Minimum separation**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Next SCT**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**XFL**</span></td></tr><tr><td>TESPI</td><td rowspan="2">**15 nm** (20 nm if other STARs are busy)  
</td><td>EKCH\_W\_APP (119.805)</td><td>FL130</td></tr><tr><td>TUDLO</td><td>EKCH\_W\_APP (119.805)</td><td>FL120</td></tr><tr><td>EKBI (09+27)</td><td>FL130</td><td>EKDK\_CTR / EKBI\_APP</td><td>FL130</td></tr></tbody></table>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/cYSimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/cYSimage.png)

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/S90image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/S90image.png)

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/QLZimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/QLZimage.png)

<span style="text-decoration: underline;">Ensure aircraft are reaching their altitude restrictions.</span>

### Departures

<table border="1" id="bkmrk-sid-climb-to-next-ac" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 33.3333%;"></col><col style="width: 33.3333%;"></col><col style="width: 33.3333%;"></col></colgroup><tbody><tr><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**SID**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Climb to**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Next ACC**</span></td></tr><tr><td>GOLGA</td><td>FL240</td><td>EKDK\_CTR (136.485)</td></tr><tr><td>ODN</td><td>FL280</td><td>EKDK\_CTR (136.485)</td></tr></tbody></table>

## 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.

<table border="1" id="bkmrk-arrival-initial-desc" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 21.7553%;"></col><col style="width: 34.6106%;"></col><col style="width: 21.7553%;"></col><col style="width: 21.8789%;"></col></colgroup><tbody><tr><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Arrival**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Initial descend**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Next SCT**</span></td><td style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**XFL**</span></td></tr><tr><td>MONAK (22L)</td><td>**<span style="text-decoration: underline;">FL100</span>** Level by NEKSO  
</td><td>EKCH\_O\_APP (118.455)</td><td>FL90</td></tr><tr><td>MONAK (04L)</td><td>**<span style="text-decoration: underline;">FL80</span>** Level by NEKSO</td><td>EKCH\_O\_APP (118.455)</td><td>FL90</td></tr></tbody></table>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/0s3image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/0s3image.png)

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/5YTimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/5YTimage.png)

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.

<table border="1" id="bkmrk-sid-climb-to-next-ac-1" style="border-collapse: collapse; width: 100%; height: 135.188px;"><colgroup><col style="width: 33.3745%;"></col><col style="width: 33.3745%;"></col><col style="width: 33.3745%;"></col></colgroup><tbody><tr style="height: 33.7969px;"><td style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**SID**</span></td><td style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**Climb to**</span></td><td style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**Next ACC**</span></td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px;">NEXEN</td><td rowspan="3" style="height: 101.391px;">FL280  
</td><td rowspan="3" style="height: 101.391px;">EKDK\_C\_CTR (128.215) or EKDK\_A\_CTR (135.290) if none of these is online, to  
EKDK\_CTR (136.485)  
</td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px;">LANGO</td></tr><tr style="height: 33.7969px;"><td style="height: 33.7969px;">KOPEX</td></tr></tbody></table>

## 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).

<table border="1" id="bkmrk-concerned-accs-arriv" style="border-collapse: collapse; width: 100%; height: 354.156px;"><colgroup><col style="width: 33.3745%;"></col><col style="width: 33.3745%;"></col><col style="width: 33.3745%;"></col></colgroup><tbody><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px; background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Concerned ACCs**</span></td><td class="align-center" style="height: 33.7969px; background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Arrival via**</span></td><td class="align-center" style="height: 33.7969px; background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Contingency Procedure** </span></td></tr><tr style="height: 67.3906px;"><td class="align-center" style="height: 67.3906px;">EKDK\_B\_CTR</td><td class="align-center" style="height: 67.3906px;">Via NIKDA/KOSEB to MONAK </td><td class="align-center" style="height: 67.3906px;">Coordinate with **EDUU** to enter En-route holdings at NIKDA &amp; KOSEB. Procedure direction discretion of EDUU </td></tr><tr style="height: 117.781px;"><td class="align-center" style="height: 117.781px;">EKDK\_CTR  
EKDK\_B\_CTR</td><td class="align-center" style="height: 117.781px;">Via GESKA to MONAK</td><td class="align-center" style="height: 117.781px;">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. </td></tr><tr style="height: 33.7969px;"><td class="align-center" rowspan="2" style="height: 67.5938px;">EKDK\_CTR  
EKDK\_C/A\_CTR  
</td><td class="align-center" style="height: 33.7969px;">Via TALSA to TUDLO</td><td class="align-center" rowspan="2" style="height: 67.5938px;">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</td></tr><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px;">Via BAVTA to TUDLO</td></tr><tr style="height: 33.7969px;"><td class="align-center" rowspan="2" style="height: 33.7969px;">EKDK\_CTR  
</td><td class="align-center" style="height: 33.7969px;">Via AAL to TESPI </td><td class="align-center" rowspan="2" style="height: 33.7969px;">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   
</td></tr><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px;">Via BAVTA to TESPI</td></tr></tbody></table>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/yYeimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/yYeimage.png)

## 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 &amp; 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

---

<p class="callout info">You should NOT talk to EKCH\_F\_APP. He is the Silent partner.</p>

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 &amp; ALT must correspond to the table below

<table border="1" id="bkmrk-rwy-altitude-inbound" style="border-collapse: collapse; width: 100%; height: 168.984px;"><colgroup><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col></colgroup><tbody><tr style="height: 33.7969px;"><td class="align-center" style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**RWY**</span></td><td class="align-center" style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**Altitude**</span></td><td class="align-center" style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**Inbound**</span></td><td class="align-center" style="background-color: rgb(52, 73, 94); height: 33.7969px;"><span style="color: rgb(255, 255, 255);">**Speed**</span></td></tr><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px;">22L/22R</td><td class="align-center" rowspan="4" style="height: 135.188px;">4000 MSL  
</td><td class="align-center" style="height: 33.7969px;">ABEGI / ADOVI or earlier</td><td class="align-center" rowspan="4" style="height: 135.188px;">200 - 230 knt.  
</td></tr><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px;">04L/04R</td><td class="align-center" style="height: 33.7969px;">ERPUK / DOPEM or earlier</td></tr><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px;">12</td><td class="align-center" style="height: 33.7969px;">FEDJO / AGTIC or earlier</td></tr><tr style="height: 33.7969px;"><td class="align-center" style="height: 33.7969px;">30</td><td class="align-center" style="height: 33.7969px;">HUFO / COPHO or earlier</td></tr></tbody></table>

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 &amp; 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.

<p class="callout info">Talk to EKCH\_W\_APP and coordinate spacing as well as possible.</p>

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 &amp; ALT must correspond to the table below

<table border="1" id="bkmrk-rwy-altitude-inbound-1" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col><col style="width: 24.9691%;"></col></colgroup><tbody><tr><td class="align-center" style="background-color: rgb(52, 73, 94);">**<span style="color: rgb(255, 255, 255);">RWY</span>**</td><td class="align-center" style="background-color: rgb(52, 73, 94);">**<span style="color: rgb(255, 255, 255);">Altitude</span>**</td><td class="align-center" style="background-color: rgb(52, 73, 94);">**<span style="color: rgb(255, 255, 255);">Inbound</span>**</td><td class="align-center" style="background-color: rgb(52, 73, 94);">**<span style="color: rgb(255, 255, 255);">Speed</span>**</td></tr><tr><td class="align-center">22L/22R</td><td class="align-center" rowspan="4">4000 MSL  
</td><td class="align-center">ABEGI / ADOVI or earlier</td><td class="align-center" rowspan="4">200 - 230 knt.  
</td></tr><tr><td class="align-center">04L/04R</td><td class="align-center">ERPUK / DOPEM or earlier</td></tr><tr><td class="align-center">12</td><td class="align-center">FEDJO / AGTIC or earlier</td></tr><tr><td class="align-center">30</td><td class="align-center">HUFO / COPHO or earlier</td></tr></tbody></table>

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

---

<p class="callout warning align-center">Speed control within 10nm on the ILS must be EITHER:  
<span style="text-decoration: underline;">**180 until 6DME**</span> or **<span style="text-decoration: underline;">160 until 4DME</span>**</p>

---

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*

<p class="callout danger">If the final gets 20nm or more, you need to enforce a complete approach stop! Do everything in your power to avoid this!!</p>

## 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

<table border="1" id="bkmrk-sid-primary-next-sec" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 50%;"></col><col style="width: 50%;"></col></colgroup><tbody><tr><td class="align-center" style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**SID**</span></td><td class="align-center" style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Primary next sector**</span></td></tr><tr><td class="align-center">NEXEN / LANGO / KOPEX</td><td class="align-center">EKDK\_B\_CTR</td></tr><tr><td class="align-center">ODN / GOLGA</td><td class="align-center">EKDK\_D\_CTR</td></tr><tr><td class="align-center">VEDAR / KEMAX</td><td class="align-center">ESMM\_K\_CTR</td></tr><tr><td class="align-center">SIMEG / SALLO</td><td class="align-center">ESMS\_APP</td></tr></tbody></table>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/wqSimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/wqSimage.png)

## 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

<table border="1" id="bkmrk-sid-primary-next-sec-1" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 50%;"></col><col style="width: 50%;"></col></colgroup><tbody><tr><td class="align-center" style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**SID**</span></td><td class="align-center" style="background-color: rgb(52, 73, 94);"><span style="color: rgb(255, 255, 255);">**Primary next sector**</span></td></tr><tr><td class="align-center">NEXEN / LANGO / KOPEX</td><td class="align-center">EKDK\_B\_CTR</td></tr><tr><td class="align-center">ODN / GOLGA</td><td class="align-center">EKDK\_D\_CTR</td></tr><tr><td class="align-center">VEDAR / KEMAX</td><td class="align-center">ESMM\_K\_CTR</td></tr><tr><td class="align-center">SIMEG / SALLO</td><td class="align-center">ESMS\_APP</td></tr></tbody></table>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/fLPimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/fLPimage.png)

## 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.

<p class="callout warning align-center">Missed approach 22L  
**Left heading 187, climb 3000’**  
Handover to EKCH\_O\_APP 118.455 </p>

Missed approach should be announced as:  
**<span style="text-decoration: underline;">“Follow Standard Missed Approach procedure, Climb 3000” </span>**  
Or if the pilot is struggling:  
<span style="text-decoration: underline;">**"GO AROUND! Left turn NOW heading 187 climb 3000 ft."** </span>

You should issue a Go- Around IF

- <span style="text-decoration: underline;">**Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS**</span>
- <span style="text-decoration: underline;">**Aircraft will not be able to pass the threshold before the preceding has vacated.**</span>

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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/BJhimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/BJhimage.png)

For arrivals via B and to cargo apron to hold short Z, <span style="text-decoration: underline;">DO NOT</span> 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.

<p class="callout warning align-center">Missed approach 22L  
**Left heading 347, climb 3000’**  
Handover to EKCH\_W\_APP 119.805 </p>

Missed approach should be announced as:  
**<span style="text-decoration: underline;">“Follow Standard Missed Approach procedure, Climb 3000” </span>**  
Or if the pilot is struggling:  
<span style="text-decoration: underline;">**"GO AROUND! Left turn NOW heading 347 climb 3000 ft."** </span>

You should issue a Go- Around IF

- <span style="text-decoration: underline;">**Separation is LESS than 2NM (Yellow Conflict sticker) while both aircraft are still on the ILS**</span>
- <span style="text-decoration: underline;">**Aircraft will not be able to pass the threshold before the preceding has vacated.**</span>

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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/aEzimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/aEzimage.png)

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)

<table border="1" id="bkmrk-northwest-southwest-" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col><col style="width: 20.0247%;"></col></colgroup><tbody><tr><td class="align-center">Northwest</td><td class="align-center">Southwest</td><td class="align-center">Southeast</td><td class="align-center">West</td><td class="align-center">North</td></tr><tr><td class="align-center">KEMAX</td><td class="align-center">LANGO  
NEXEN  
KOPEX</td><td class="align-center">SIMEG  
SALLO</td><td class="align-center">ODN</td><td class="align-center">GOLGA  
VEDAR</td></tr><tr><td class="align-center" colspan="5">Contact EKCH\_DEP: 120.255  
If EKCH\_DEP is Offline then contact:  
</td></tr><tr><td class="align-center" colspan="3">EKCH\_O\_APP: 118.455</td><td class="align-center" colspan="2">EKCH\_W\_APP: 119.805</td></tr></tbody></table>

- 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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/mi6image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/mi6image.png)

## 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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/jj8image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/jj8image.png)

## 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 <span style="text-decoration: underline;">**NOT**</span> need you. A\_TWR will Cross them directly.

As aircraft crosses Runway 30, they should <span style="text-decoration: underline;">as good as you can</span> be separated into South vs. North departures

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

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/5ttimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/5ttimage.png)

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

<span style="text-decoration: underline;">Heavy</span> Aircraft must be assigned A1/B1

## EKCH\_A\_GND (04R/04L)

Make sure you know [<span style="text-decoration: underline;">standard taxi routes &amp; pushback routes</span>](https://wiki.vatsim-scandinavia.org/books/lai/page/lai-3-apron-control)

- Once handed from S\_GND/DEL TSAT is out of the picture
- Adhere to proper use of Taxiway D

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/Zdhimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/Zdhimage.png)

## 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
- **<span style="text-decoration: underline;">HS1</span>**: Departure goes first onto D. Arrival holding short of Z goes as second. (NOTE different from 22R/22L)
- **<span style="text-decoration: underline;">HS2</span>**: Arrivals must hold short Y and observe any ongoing pushback
- **<span style="text-decoration: underline;">HS3</span>**: Arrivals on K3 must give way to first outbound and any subsequent blocking the ARR stand
- **<span style="text-decoration: underline;">HS4</span>**: Departures from K must hold short J to give way to arrivals on K2.
- **<span style="text-decoration: underline;">HS5</span>**: Departures from V must hold short of S to give way to first inbounds via K &amp; R.
- **<span style="text-decoration: underline;">HS5</span>**: Subsequent arrival should hold short of Y or Z to give way to beformentioned departure
- **<span style="text-decoration: underline;">HS6</span>**: Departures from W must give way to first inbound at R &amp; S

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/scaled-1680-/9mRimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/9mRimage.png)

# RIU 12/30 TWR+GND

<iframe frameborder="0" height="651" scrolling="no" src="https://1drv.ms/p/c/387e4c7793fbec64/IQNs4MUt4xBhRag2VVxM6priAZMvpf-MrbO6jOh9YhoeVII" width="800"></iframe>

# 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](https://wiki.vatsim-scandinavia.org/books/software-manuals/page/cdm-4gD) 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 <span style="background-color: rgb(45, 194, 107); color: rgb(255, 255, 255);">GREEN</span> Aircraft is approved for startup 
        - Move TAG to READY bay and transfer to EKCH\_A\_GND
    - If <span style="background-color: rgb(230, 126, 35); color: rgb(255, 255, 255);">ORANGE</span> 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 ](https://wiki.vatsim-scandinavia.org/books/software-manuals/page/cdm-4gD)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.

– **<span style="text-decoration: underline;">No coordination needed</span>**: for A380/B748 clear off 22L/04R   
– **<span style="text-decoration: underline;">Coordination needed</span>**: 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](https://wiki.vatsim-scandinavia.org/books/quick-reference-be0/page/non-standard-ifr-clearance)

More info regarding CDM and its use can be found [here](https://wiki.vatsim-scandinavia.org/books/software-manuals/page/cdm-4gD)