# Upper ACC / ACC Planner

<p class="callout info">This section is about the responsibility of ACC planners</p>

<p class="callout warning">All UPPER ACCs are ACC Planners</p>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/scaled-1680-/8o9image.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/8o9image.png)

## EKDK\_A\_CTR

<p class="callout info">Planner for EKDK\_B\_CTR</p>

### 1 General

#### 1.1 Responsibilities

<span style="white-space: pre-wrap;">Sitting on EKDK\_A\_CTR you have are generally responsible for climbs to NEXEN, and enroute traffic in Sector A/UA. While you have quite little traffic load your responsibility is </span><u><span style="white-space: pre-wrap;">heavy </span></u>as you need to coordinate and plan traffic into the Brave sector. Something which is quite demanding

#### 1.2 Sector Ownership

<span style="white-space: pre-wrap;">With EKDK\_C\_CTR online you may be advised to take Hybrid sector EKDK\_A\_CTR which gives you responsibility of EKDK\_I\_CTR to handle departures. </span>

In case of arrivals above FL285 you are in charge of the holding.

### 2. Arrivals

<p class="callout danger">Always have close cooperation with your Active ACC Sector (EKDK\_B\_CTR) and Flow Manager (EKDK\_FMP)</p>

#### 2.1 General

Handling of arrivals are of significant important with emphasis on following situations

- Stacking of arrivals to FL270 from Mueritz to avoid LOS
- Re-Routing of EDYY arrivals as needed to avoid stacked holdings.
- Re-Routing of DWM arrivals far east via BAKLI-TIDVU
- <span style="white-space: pre-wrap;">Establish secondary holds at MEGAR and coordinate sequence. </span>
    - When holding established above FL280
    - EDDH arrivals at FL230

#### 2.2 Stacking for DWM

<span style="white-space: pre-wrap;">When you see flights from DWM at FL200 to MONAK starts getting difficult, stacking up to and including FL270 needs to be in effect. In that case contact EDWW\_M\_CTR and advise aircraft callsign and level. if flights are still at cruise level you may be able to do it directly via the TAG. </span>

If you decide to stack flights above FL270 you will need to establish secondary holdings from EDYY/EDWW arrivals

Note that enroute holdings at NIKDA and KOSEB are NOT allowed due to proximity of OLPIB hold

#### 2.3 Secondary holding at MEGAR

Flights from EDDH at FL230, and flights from EDYY when holding is stacked above FL280 is crucial. In this case you shall coordinate with EKDK\_B\_CTR to re-clear and hold at point "**MEGAR**<span style="white-space: pre-wrap;">". This will ensure clearance to OLPIB without busting EDWW/EDYY airspace. </span>

<span style="white-space: pre-wrap;">You can choose to coordinate with EKDK\_B or ask for the flights yourself to manage that holding. </span>

<p class="callout warning">At no times should more that ~10 aircraft be in OLPIB hold. If so, keep them on your frequency and hold them until load decrease at OLPIB.</p>

<span style="white-space: pre-wrap;">When aircraft are holding at MEGAR, you MUST note and communicate to EKDK\_B\_CTR where in the sequence they fit in. Effectively this can be done by "Highlighting" the aircraft in OLPIB hold the aircraft in MEGAR hold will be </span><u><span style="white-space: pre-wrap;">Preceding. </span></u><span style="white-space: pre-wrap;">This allows EKDK\_B to keep a hole in the holding at the level of the MEGAR hold, and then squeeze that aircraft into OLPIB hold when his turn in sequence as come. </span>

#### 2.4 Re-Routings

<p class="callout warning">All Re-Routings MUST happen in communication with Flow Manager FMP</p>

<p class="callout info">Re-Routing MAY also be directed by Flow Manager FMP</p>

Re-Routings normally are either:

<details id="bkmrk-re-routings-from-edy"><summary>Re-Routings from EDYY/EDWW to TUDO</summary>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/scaled-1680-/ViYimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/ViYimage.png)

</details><details id="bkmrk-re-routings-from-dwm"><summary>Re-Routings from DWM to BAKLI-TIDVU</summary>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/scaled-1680-/6JWimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/6JWimage.png)

</details>**It is prohibited to execute these re-routings without the clear consent from EKDK\_FMP (if online)**

## EKDK\_C\_CTR

<p class="callout info">Planner for EKDK\_D\_CTR</p>

### 1 General

#### 1.1 Responsibilities

<span style="white-space: pre-wrap;">Sitting on EKDK\_C\_CTR you have are generally responsible for climbs to LANGO, ODDON, and enroute traffic in Sector C/UC. </span>

#### 1.2 Sector Ownership

<span style="white-space: pre-wrap;">With EKDK\_D\_CTR NOT online you may be advised to take Hybrid sector EKDK\_C\_CTR which gives you responsibility of EKDK\_D\_CTR to handle TUDLO arrivals all the way down. </span>  
With EKDK\_A\_CTR is NOT online you will also be given responsibility of ACC Copenhagen Sector I.

In case of arrivals above FL285 you are in charge of the holding.

### 2. Arrivals

<p class="callout danger">Always have close cooperation with your Active ACC Sector (EKDK\_D\_CTR) and Flow Manager (EKDK\_FMP)</p>

#### 2.1 General

Handling of arrivals are of significant important with emphasis on following situations

- Ensure not more that ~8-10 aircraft are under control of EKDK\_D\_CTR
- At high traffic situations, "Pre-Clear" aircraft on arrival and into holdings"
- Stay at close contact and help you EKDK\_D\_CTR as you see fit

#### 2.2 Holdings

It is vital that EKDK\_D\_CTR is not overloaded by holdings. ~8-10 aircraft is maximum that should be in EKDK\_Ds holding at any time. In order to help him out, stand holdings in excess of 8-10 above FL280. If space above FL280 gets tight, descent aircraft into EKDK\_D\_CTRs airspace while keeping control, and handover an ad-hoc basis

<p class="callout success">Altitude in the holding is always LESS critical than amount of aircrafts on the frequency</p>

#### 2.3 Lower Holdings

If you can see that inbound traffic rush is imminent, coordinate with FMP to establish holds at TUDLO below FL130 down to a minimum to FL80

#### 2.4 Secondary holding at TALSA

<span style="white-space: pre-wrap;">In very heavy traffic situations and situations where we close down EKCH airspace for arrivals introduce TALSA hold on "current inbound track" with Right turns, 1.5 minute legs. </span>

Here you start stacking aircrafts as needed until they can be released into ACC Lower East

#### 2.5 Re-Routings

<p class="callout warning">All Re-Routings MUST happen in communication with Flow Manager FMP</p>

<p class="callout info">Re-Routing MAY also be directed by Flow Manager FMP</p>

<span style="white-space: pre-wrap;">No regular Re-Routings are used from EKDK\_C\_CTR, but on Ad-Hoc basis flights may be re-cleared to either TESPI or MONAK if traffic situation demands it. </span>

**It is prohibited to execute these re-routings without the clear consent from EKDK\_FMP (if online)**

## EKDK\_V\_CTR

<p class="callout info">Planner for EKDK\_E\_CTR</p>

### 1 General

#### 1.1 Responsibilities

<span style="white-space: pre-wrap;">Sitting on EKDK\_V\_CTR you have are generally responsible for climbs to GOLGA, and enroute traffic in Sector V/N/UN. </span>

#### 1.2 Sector Ownership

NIL

### 2. Arrivals

<p class="callout danger">Always have close cooperation with your Active ACC Sector (EKDK\_D\_CTR) and Flow Manager (EKDK\_FMP)</p>

#### 2.1 General

Handling of arrivals are of significant important with emphasis on following situations

- Ensure not more that ~8-10 aircraft are under control of EKDK\_E\_CTR
- At high traffic situations, "Pre-Clear" aircraft on arrival and into holdings"
- Stay at close contact and help you EKDK\_E\_CTR as you see fit
- Enforce Ground stop at EKBI, EKYT, EKAH, EKKA in coordination with FMP.
    - If local ATC is online INFORM them on event start that all ATC clearances are subject to release by either you or EKDK\_FMP (to be coordinated internally)

#### 2.2 Holdings

It is vital that EKDK\_E\_CTR is not overloaded by holdings. ~8-10 aircraft is maximum that should be in EKDK\_Es holding at any time. In order to help him out, stand holdings in excess of 8-10 above FL240. If space above FL240 gets tight, descent aircraft into EKDK\_E\_CTRs airspace while keeping control, and handover an ad-hoc basis

#### 2.3 Lower Holdings

If you can see that inbound traffic rush is imminent, coordinate with FMP to establish holds at TESPI below FL130 down to a minimum to FL90

<p class="callout success">Altitude in the holding is always LESS critical than amount of aircrafts on the frequency</p>

#### 2.4 Secondary holding at AAL

<p class="callout info">Aircraft from ACC Polaris (ENOR, ENOS, ENSV)</p>

In very heavy traffic situations and situations where we close down EKCH airspace for arrivals introduce AAL hold on "**263 track**<span style="white-space: pre-wrap;">" with Right turns, </span>**1.5 minute legs.**

Here you start stacking aircrafts as needed until they can be released into ACC Lower East

#### 2.5 Secondary holding at BAVTA

<p class="callout info">Aircraft from ACC Scottish (EGPX)</p>

In very heavy traffic situations and situations where we close down EKCH airspace for arrivals introduce BAVTA hold on **"current inbound track"** with Right turns, **1.5 minute legs.**

Here you start stacking aircrafts as needed until they can be released into ACC Lower East

#### 2.4 Re-Routings

<p class="callout warning">All Re-Routings MUST happen in communication with Flow Manager FMP</p>

<p class="callout info">Re-Routing MAY also be directed by Flow Manager FMP</p>

<details id="bkmrk-re-routings-from-dk_"><summary>Re-Routings from DK\_V to ERNOV</summary>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/scaled-1680-/eYFimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-10/eYFimage.png)

</details><span style="white-space: pre-wrap;">On an Ad-Hoc basis aircraft can be re-routed from TESPI to TUDLO </span>

**It is prohibited to execute these re-routings without the clear consent from EKDK\_FMP (if online)**