# Event Documentation

Statistics, rules and event related items are found here

# 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 similar positions every week

- Controllers may <span style="text-decoration: underline;">**not**</span> book the same position two weeks in a row, unless no other positions are available or directed by a staff member for operational reasons
- Controllers <span style="text-decoration: underline;">**shall aim**</span> not to book a position they have had on the same shift the last two weeks, unless no other is available or for operational reasons.

#### 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 10 minutes early, not 5 minutes late. Inform others if you will be delayed

#### 4. "ALL" event bookings

- EKCH\_O\_APP, EKCH\_F\_APP, EKDK\_A\_CTR, EKCH\_C\_TWR, EKBI and EKYT are "all event" bookable positions
- Any EKCH rated controller shall not occupy the regionals until all essential positions in EKCH are filled.
- Any controller who wish to begin each of these positions earlier, are free to do so, and shall write their intention in the chat.
- Any position not in any list of bookable positions, which a controller would like to sit on shall be advised via the chat. This shall only be done if all essential positions has been staffed.

## Controlling

#### 1. Rules and Procedures

- Be properly familiar with the LAI for your position.
- 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
- Show up in time to be briefed before your controlling time start (If on LATE or ALL positions only)

#### 2. Switching of positions

- If your 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

## Time of Closure

#### 1. Booking time

- Ending time of the booking on LATE must be respected unless it is clear that the position is not needed with the current traffic flow

#### 2. 15 minute buffer period

- All controllers MUST be able to stay a minimum of 15 minutes after their booking expire.
- This period shall be used to redirect any traffic still in the airspace
- ACC positions must 
    - Clear the holding, or agree with another controller to take over.
    - Divert and re-clear as directed.
    - Mark last airplane which will be released from the sector by writing in the TAG
- APP and GND positions must 
    - Coordinate with all adjacent positions.
    - Try to find a controller to take over if traffic load is high

## 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
- VaCDM plugin is encouraged to use
- vATIS must be updated before each use

# Rules for "Direct to Regionals"

## Booking

#### <span style="white-space: pre-wrap;">1. Do </span><u>**not**</u><span style="white-space: pre-wrap;"> book similar positions every week</span>

- Controllers should avoid booking the same position two weeks in a row, unless no other positions are available or they are directed to do so by a staff member for operational reasons.

#### 2. Booking etiquette must be strictly observed

- <span style="white-space: pre-wrap;">If you cancel your booking less than </span>**48 hours**<span style="white-space: pre-wrap;"> before the event (Tuesday evening), please write in the Direct to Regionals staffing thread to make others aware, so they may rebook.</span>
- <span style="white-space: pre-wrap;">If you cancel your booking less than </span>**24 hours**<span style="white-space: pre-wrap;"> before the event, you must take the necessary steps to ensure your position is covered. Contact people directly, or suggest adjustments to the roster.</span>
- <span style="white-space: pre-wrap;">While </span>**force majeure**<span style="white-space: pre-wrap;"> can occur, you must be confident that you can attend when you book a position.</span>
- If a position becomes available, show consideration for those already booked and be respectful toward controllers who booked before you.
- <span style="white-space: pre-wrap;">Be ready to control at your scheduled time. Be </span>**5 minutes early**, not 5 minutes late. Inform others if you will be delayed.

#### 3. Non-event positions

- As a rule of thumb, all positions officially related to the event (as presented in the Direct to Regionals thread) have priority and must be booked before opening any other positions.
- EKCH\_TWR (in all forms), EKCH\_GND (in all forms) and EKCH\_DEL may not be staffed during the Direct to Regionals event.
    - <span style="white-space: pre-wrap;">Exceptions may be made for TWR and / or GND staffing in cases of EKCH\_APP overload. Any such request must originate from EKCH\_APP and should only be used when absolutely necessary. </span>

#### 4. S1 controllers

- S1 controllers may book any position during Direct to Regionals unless explicitly stated otherwise.
- S1 controllers must ensure they are properly prepared and possess the necessary skillset to control efficiently before booking for the event.
- **S1 controller staffing is a privilege and will be revoked if we observe repeated failure to adhere to these guidelines.**

## Controlling

#### 1. Rules and Procedures

- Be properly familiar with the LAI for your position.
- <span style="white-space: pre-wrap;">Ensure that you are not only </span>**qualified** <span style="white-space: pre-wrap;">but also </span>**capable** of controlling the position you book.
- Show up on time so you can be briefed before your controlling period begins.

#### 2. Training during Direct to Regionals

- <span style="white-space: pre-wrap;">Training is generally permitted. For details, see </span>[**Guidelines for Training During Events**](https://wiki.vatsim-scandinavia.org/books/training-department/page/guidelines-for-training-during-events)<span style="white-space: pre-wrap;">. </span>

## Time of Closure

#### 1. Booking Time

- The ending time of a booking must be respected unless it is clearly evident that the position is no longer required given the current traffic situation.

#### 2. 15-Minute Buffer Period

- All controllers must be able to remain online for a minimum of 15 minutes after their booking expires.
- This period must be used to safely hand off or redirect any remaining traffic within the airspace.

## Software

#### 1. Euroscope

- All controllers must have the latest sector files installed and must use the latest approved version of EuroScope as designated by VATSIM-Scandinavia.

#### 2. Plugins

- vATIS must be updated before each use.

# FMP and Approach Planner

# Approach Planner Position

## 1. General

<p class="callout success">This scenario used from the beginning of event until yellow operational rate is hitting</p>

Copenhagen Approach planner (EKCH\_P\_APP) has primary frequency of 131.405, and monitors 120.205. It is responsible for managing traffic and sequencing traffic into FINAL. Primary tasks are to:

- <span style="white-space: pre-wrap;">Establish the sequence, </span>
- <span style="white-space: pre-wrap;">Sort flights based on WTC </span>
- Ensure that the flow into FINAL is staggered and with appropriate separation.

This must be done by use of close coordination and monitoring of FINAL, and proactively act as an authority to establish the appropriate flow.

APPCO and FINAL will swap positions approximately every 40-50 minutes. This is done by:  
<span style="white-space: pre-wrap;">1. </span><span style="background-color: rgb(191, 237, 210);">APPCO -&gt; FINAL</span><span style="white-space: pre-wrap;"> tuning 120.205 as primary</span>  
<span style="white-space: pre-wrap;">2. </span><span style="background-color: rgb(248, 202, 198);">FINAL -&gt; APPCO</span><span style="white-space: pre-wrap;"> tuning 131.405 as primary</span>  
<span style="white-space: pre-wrap;">3. </span><span style="background-color: rgb(191, 237, 210);">APPCO -&gt; FINAL</span><span style="white-space: pre-wrap;"> assuming the 120.205 frequency on voice</span>  
<span style="white-space: pre-wrap;">4. </span><span style="background-color: rgb(248, 202, 198);">FINAL -&gt; APPCO</span><span style="white-space: pre-wrap;"> transferring all tags to </span><span style="background-color: rgb(191, 237, 210);">APPCO -&gt; FINAL</span><span style="white-space: pre-wrap;"> </span>

The involved controllers shall retain their original logon to the network (EKCH\_F\_APP / EKCH\_P\_APP) - these don't affect the sector position so controllers should not reconnect in order to facilitate efficient sector transfer.

## 2. Coordination with FINAL

<p class="callout success">Coordination with FINAL is your primary task</p>

### Tasks

- Determine sequence of flights, and communicate the sequence to FINAL where appropriate.
- Assign 22R for appropriate flights. (WTC or VREF restrictions).
    - APPCO must instruct W and O to write in the tag when an airplane is for 22R.
        - Communicate to TWR-DEP inbounds to 22R are approaching.\*
- Proactively support FINAL to send aircraft back for resequencing when needed.
- Monitor and advise FINAL of this he may have forgotten.

**\*Using euroscope .point \[Callsign from Controller list in Euroscope\] \[click on the airplane in question\].**

---

## 3. Coordination with W\_APP + O\_APP

<p class="callout success">You need to set the appropriate rate when needed, accommodate APP request when able, and remind them to stagger arrivals</p>

<span style="white-space: pre-wrap;">Choose appropriate separation requirement based on TMA experience, </span>

- 10nm = 40flight/hr = ability of our controllers on average. Aim for this in general
- 8nm = 42/hr = Ability for highly experienced FINAL controllers, or when finals are short (less than 10nm)
- 12nm = 38/hr = To create extra space for inexperienced or stressed FINAL controllers.

<p class="callout danger">Advise FMP if a prolonged duration of 38/hr is needed</p>

<span style="white-space: pre-wrap;">Determine periods where the sequence from O\_APP and W\_APP to FINAL may be unbalanced: </span>

- 5nm vs 15nm (1:2 ratio) - Use for a missed approach or to fill a gap in a feeder sector
- 8nm vs 12nm (2:3 ratio) - Use to manage a period of unbalanced sequence in coordination with FMP

Communicate the sequence as appropriate, to deliver the correct separation to final. This is especially important if using an unbalanced flow.

## **4.** Coordination with ACC

<p class="callout success">FMP is overall responsible for flow. You role is to pick individual holes due to GAs and short term struggles</p>

In order to accommodate short term separation increases it may be needed to have a temporary hole, while not affecting the FMP designated ACC handoff rate.

- Advise FMP to create a 10nm (2min) sequence gap when a missed approach has been executed with 22L in use if deemed necessary by APPCO.
- Advise FMP to create a 10nm (2min) sequence gap when a missed approach has been executed with 04L in use if deemed necessary by APPCO.
- Ask via FMP any ACC controller to skip a maximum of one slot when additional space is needed in TMA airspace.
- Any coordination with ACC must be additional coordinated with FMP. FMP will relay the request or delegate it to APPCO.
- Establish unbalanced flow to final based on ACC load

# Flow Management Position

<p class="callout info">**For controllers subject to FMP, please see at the end of this page for abbreviated procedures you can expect.**</p>

<p class="callout success"><span style="white-space: pre-wrap;">ALB = Arrival Load Balancer. </span>[For tutorial of ALB see here](https://wiki.vatsim-scandinavia.org/attachments/470)</p>

## 0. Setup

Before logging on make sure you do following steps in your Euroscope

1. <span style="white-space: pre-wrap;">Load Profile DK\_AIR </span>
2. Open a CTR ASR file
3. Go to "Other Settings" and "Display Settings" find "Regions" and enable EKDK FMP.
4. Make sure ALB is loaded as your plugin. write in ES command line ".alb open" to start the program.

## 1. Objective and Responsibilities

As Flow Manager (EKDK\_FMP) Your objectives and responsibilities in the time period FMP active traffic flow is in sequence of succession:

- Establish Flow rates via ALB consistent with traffic demands.
    - Chapter 2
- <span style="white-space: pre-wrap;">Manage flow inbound to copenhagen by use of the </span><u>**"BIDE"**</u><span style="white-space: pre-wrap;"> Acronym</span>
    - **B**alance
    - **I**nterrogate
    - **D**istribute
    - **E**qualize
- Modify the ACC sector allocation following traffic peaks

Details of how to achieve all is specified below and is continuously updated.

Please refer to this documentation every time before you log onto EKDK\_FMP

## 2. Flow Rates into TMA

<span style="white-space: pre-wrap;">Adjusting the flow rate of aircraft handed over from the 5 ACC sectors (DK\_E, DK\_D, DK\_B, MML, MMK) into TMA. They are managed and communicated via the ALB. </span>

- As FMP you start off with the "Standard Separation"
- At &gt;36 arrivals/hr you start planning the move to "Managed Separation"
- <span style="white-space: pre-wrap;">At full holdings everywhere you may choose to expand it with "Selected Separation" </span>

### 2.1 Standard Flow

<p class="callout success">This scenario used from the beginning of event until hourly rate becomes more than 36/hr.</p>

<p class="callout info">Arrival rate 150 flights / hr</p>

#### 2.1.1 Required Rates

All ACCs have standard handovers as pr. LAI/LOA of 10nm with leading aircraft faster, or 5nm with leading aircraft fast if prior coordination has been obtained.

This is valid for all sectors.

#### 2.1.2 Thoughts and considerations

This rate is being used when so little load will be on the TMA (smaller than 36/hr) that the distribution of flights are negligible.

<span style="white-space: pre-wrap;">In this scenario, there </span>

### 2.2 Managed Flow

<p class="callout warning">This scenario used from when ALB advise of an hourly rate of MORE than ~36/hr.</p>

<p class="callout info">Arrival rate aim: 42-50/hr.</p>

#### 2.1.1 Required Rates

As inbound flow increase beyond 36/hr, it will be time to start planning ahead to assign Arrival rates individually per STAR to assure balanced feeding to the TMA.

Rates should be set to fit with the expected inbound rush for ~30 minutes in the future.

<p class="callout warning">Hourly inbound rate should ONLY be used as a marker for moving from "Standard" to "Managed" flow, NOT as a method of setting Arrival Rate (AR).</p>

T+0min. Setting the sequence.

![Group 104.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/scaled-1680-/4LNgroup-104.png)T+30min. Evaluating the sequence

[![Group 107.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/scaled-1680-/group-107.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/group-107.png)

#### 2.1.1 Slow Arrival Rates and Holdings other places

If you have a STAR with very little traffic and others that are employing holdings, you must make sure that the very low traffic STAR just sent people in without holding.

- The AR must be added from when first airplane hits the holding fix, if other STARs have full holds
- <span style="white-space: pre-wrap;">SAS123 arriving at TIDVU at 2035z with a 10min AR, shall enter the holding at can be released at 2045z, if OLPIB are holding flights. </span>

### 2.3 Expanded Flow

<p class="callout danger">This scenario used when two or more STARs on a side is having significant holdings</p>

#### 2.1.1 Required Rates

<span style="white-space: pre-wrap;">With full holdings at two STARs on the same side or more, the ALB prediction becomes very complex because it includes people in the holding. </span>

<span style="white-space: pre-wrap;">You should do the following as soon as holdings starts to build up. </span>

- Assign the AR based on the hourly expectation (with full holdings, the destribution over 15min doesn't matter anymore)
- Check the holding lists under ETO to identify if there are significant differences in holding time (+/- 5min).
- If there is an imbalance, move the full rate over to the STAR that has longer holds.
- If there is no imbalance, stick to the rate.

#### 2.1.2 Required Rates

Your logic must be to release a certain amount of aircraft from one hold before then releasing a certain amount from another hold.  
  
**Aircraft must be released with the rate given in ALB!**[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/wHdimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/wHdimage.png)

In this example you have the three holdings on WEST STREAM, and you are individually releasing from ETO. Make following observations

- LUGAS has the oldest time at 0753
- ROSBI has a lot of planes in the holding
- ERNOV only has a few ones, and is not worth too much effort

#### 3.5.3 Method

<p class="callout info">**For this scenario we will keep the ERNOV EAT at 15min for simplification, but if a large holding persist at ERNOV it must also be included. oldest ERNOV plane is 0807, which is 15min after oldest LUGAS plane and 12min after oldest TESPI plane, so a 15min EAT is appropriate!.** </p>

**In this scenario we have an AR of 6 min from TUDLO and TESPI**

1. combined rate is 3min from TUDLO/TESPI. Shift that to keep 3 min on one of the STARs.
2. <span style="white-space: pre-wrap;">Identify oldest airplane </span>**BAW816**
3. Release all airplanes up until the first one which is later than the oldest of the next STAR
    - In this case SAS78C is 0757 and SAS2856 is 0756, meaning SAS78C is the last to be released
4. Tell EKDK\_D\_CTR to release all airplanes up to and including SAS78C.

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

4\. Tell EKDK\_E\_CTR to hold all aircraft indefinitely.

5\. Tell EKDK\_E\_CTR that after SAS2856 to release everybody with the rate until SAS445 (**0803**) to the revert back to D\_CTR to release SAS031 and BAW822 respectively

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

5\. EKDK\_D will release SAS031 and BAW822 as point 3-5, back to DK\_E who will release until DLH33, and then it head back to DK\_D-

6\. MMK will meanwhile release at EATs you are specifying. The rate takes into consideration an ERNOV every 15 minutes, so delay for an appropriate gap

## 3. Misc. Management

<p class="callout success">Use the Acronym BIDE to remember your tasks</p>

### 3.1 "BIDE"

<span style="white-space: pre-wrap;">In addition to managing the flow rate, you need to manage different aspects of the night in regards to traffic. For an attempt to make it easier to remember the acronym </span>**BIDE** can be used, to remember the four different areas you must manage.

- Balance
    - Prioritise a specific stream via the ALB when load is disproportionally heavy
- Inform
    - Keep APP-CO in the loop of any balancing of arrival streams that they have to take into consideration.
- Distribute
    - Re-Route from East to West and West to East.
- Extend gaps
    - Allow an extra 10-15 from a STAR to facilitate a go-around.

All is explained in Detail below

### 3.2 Balance

#### 3.2.1. Balanced or prioritized flow

<span style="white-space: pre-wrap;">From the very beginning of the event you need to identify, via ALB or your screen a potential situation where you need to switch the vast majority of the flow to one STAR or Side, in order to avoid a total collapse on that sector. </span>

[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/scaled-1680-/YNcimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/YNcimage.png)

- With a split of ~40/60 or worse, significant steps should be taken to have a higher arrival rate on that side
- <span style="white-space: pre-wrap;">OLPIB may sometimes need to be prioritized in order to avoid total collapse. </span>
- 2 min can be assigned at fastest rate.

#### 3.2.2. Priorities

- For EAST priority, OLPIB STARs can be taken at lower separation or OLPIB flights re-routed to EKCH\_W\_APP
- For WESTpriority, TUDLO STARs can be re-routed to EKCH\_O\_APP

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

### 3.3 Inform

Always keep close contact to APP-CO about your plans. advise him of any imbalance that would result in change of standard separation from O/W to FINAL.

### 3.4 Distribute

#### 3.4.1 General

This is about distributing flights to which arrivals, or more precise when to REdistribute arrivals to other STARs.

We want to have an ~55/45 split on EAST/WEST. You should consider distributing flights to other STARs when you:

- See an imbalance or empty STARs with other STARs full but no extreme enough to warrant a "Prioritized flow".
- A potential overload situation can happen on a STAR if immediate action is not taken
- Tactical distribution for reasons of your discretion

#### 3.4.2 Techniques

<span style="white-space: pre-wrap;">Changing a STAR must ALWAYS adhere to the following. </span>

- Ask the Sector which will get the aircraft to request a tactical direct to their sector
- <span style="white-space: pre-wrap;">Ask the sector to change the flightplan route to be only the point of the new STAR. </span>

When coordinating a re-routing please strongly consider using the "point" command to make the controller aware by writing

- ".point \[X\]" click the aircraft to point out.
    - <span style="white-space: pre-wrap;">X is the 1-3 letter Idenfier of the station you are coordinating with </span>
    - IMPORTANT: Do not use the callsgin (EDWW\_M\_CTR), use the 1-3 letter identifier (DWM) (found in controller list)

![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/6g2image.png)#### 3.4.2 Recommended distribution changes

Following flights are highly effective an recommended

1\. EDYY via MONAK - Distribute to TUDLO/TESPI

- Largest threat to the flow is the overload on MONAK. If you see a large amount entering via DWM (Muritz) take immediate action to get some of the GESKA arrivals from EDYY distributing to other STARs.
    - Coordinate with DK\_A to re-clear via Euroscope to either a vector or another point.

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

1\. EDDH via MONAK - Distribute to TUDLO/TESPI

- EDDH flies at FL230 and hence creates all sorts of issues for DK\_B. Consider distributing to TUDLO or TESPI depending on which STAR has the most space (Can be issues as an ECFMP as well)
- Consider whether to keep af FL230 or climb to FL290 to be distributed to DK\_A

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

2\. EDWW via MONAK from T208

- <span style="white-space: pre-wrap;">In a potential MONAK overload situation flights via T208 can be effectively rerouted to TIDVU for holding there. A good direct to propose is </span>**"BAKLI"**<span style="white-space: pre-wrap;"> as this is a valid point for the direction</span>

<span style="white-space: pre-wrap;"> </span>[![image.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/hPCimage.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/hPCimage.png)

3\. ESMM via ERNOV - Distribute to TIDVU

- <span style="white-space: pre-wrap;">If high load persist on WEST STREAM and you want to get aircraft to EAST STREAM the most effective way is distributing ERNOV arrivals to TIDVU. This is </span><u>**especially** </u><span style="white-space: pre-wrap;">ERNOV arrivals from ESSA and EFHK, as they have a good angle. Coordinate with ESMM </span>
    - This is preferable to distributing TUDLO arrivals to MONAK, as long as ESMM or similar is online.
    - Avoid distributing ERNOV arrivals from ENGM via L996.

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

3\. EKDK via TESPI - Distribute to ERNOV

- For extreme load on TESPI, consider distributing a few to ERNOV to keep hold managable. This is especially useful if you have high load from ENGM/ENBR combined with several flights crom EGPX

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

### 3.5 Evaluate

### 3.5.1 General

<p class="callout danger">Choose the right sector for the right controller</p>

We have a lot of flexibility depending on where the "Extreme load" is expected. Sectors should be considered as follows

- EKDK\_B\_CTR is INflexible, and will always stay.
- EKDK\_V\_CTR (or EKDK\_N\_CTR) is INflexible and will always stay
- EKDK\_E\_CTR can be flexible but should be avoided if at all possible, and hence should stay.
- EKDK\_D\_CTR is flexible
- EKDK\_UC is highly flexible

### <span style="white-space: pre-wrap;">3.5.1 Starting the event. </span>

<span style="white-space: pre-wrap;">The four above mentioned are the default starting setup for a VTC event. In that case they are established in ownership as follows. </span>

- EKDK\_V\_CTR covers all area WEST
- EKDK\_E\_CTR, EKDK\_B\_CTR covers their respective sectors
- EKDK\_D\_CTR covers sectors D and I.
- EKDK\_UC\_CTR covers Sectors A, C, UA, UC (Note there is NO difference between UC and UA AOR wise)

[![Group 109.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/scaled-1680-/group-109.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/group-109.png)

<p class="callout success">This setup is normally the most efficient and should be used unless one of the cases below demands it</p>

### 3.5.1 Overload on Sector D

3.5.5.1 Condition

First change is if there is such amounts of traffic to Sector Delta, that we need to relieve EKDK\_D\_CTR

3.5.5.2 Change

<span style="white-space: pre-wrap;">FMP will in this case ask EKDK\_UC\_CTR to change his position to EKDK\_A\_CTR. This way </span>

- New EKDK\_A\_CTR keeps same AOR as EKDK\_UC\_CTR
- New EKDK\_A\_CTR takes over control of Sector I.
- This results in EKDK\_D\_CTR not having to deal with any departures. EKDK\_A\_CTR now keeps NEXEN, LANGO, KOPEX departures from FL190 to RFL.

[![Group 111.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/scaled-1680-/group-111.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/group-111.png)

### 3.5.1 Underload on Sector D and/or Overload on Sector B

**3.5.5.1 Condition**

If there is such low traffic amounts inbound to TUDLO that controller can be spared to other places.

<span style="white-space: pre-wrap;">This may be correlated with an overload on Sector B in order to have a planner, that the EKDK\_D\_CTR controller can switch to EKDK\_A\_CTR. </span>

**3.5.5.2 Change**

<span style="white-space: pre-wrap;">FMP will in this case ask EKDK\_UC\_CTR to change his position to EKDK\_C\_CTR. This way </span>

- New EKDK\_C\_CTR keeps same AOR as EKDK\_UC\_CTR
- New EKDK\_C\_CTR takes over control of Sector D, when EKDK\_D\_CTR gets relocated.
- This results in EKDK\_C\_CTR keeping TUDLO arrivals from RFL to FL120
- <span style="white-space: pre-wrap;">EKDK\_D\_CTR can choose to Relocate </span>

[![Group 113.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/scaled-1680-/group-113.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2026-01/group-113.png)

# FMP Notes

## 05.08.2025

<span style="white-space: pre-wrap;">ENGM event. Overload on TESPI. </span>

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

With this, know that chaos is imminent. Divert flights from West towards TUDLO if possible.

# VTC Event Endorsment Briefing material

# VTC Event Endorsement

From a date which is to be specified, all controllers must have completed the VTC Event Endorsment on moodle in order to man a position at VTC.

## Access to Course

Course can be accessed below.

NO LINK. COURSE NOT YET COMPLETED

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

# Kastrup Departure Position

## 1. General

Copenhagen Departure is an overflow sector during busy events. For much of the departing aircraft's trajectory, you will be a guest in the APP sector's airspace. This means coordination and tactical vectoring is very important.

Though the LAI states APP/DEP airspace is split at FL75, in practise DEP must position aircraft to climb above FL70, and APP needs to descend traffic in order to cross abeam the landing threshold at 5000ft. DEP is responsible for identifying the suitable crossing point - where departures pass above arrivals - and coordinating this with the relevant APP sector.

Consider the following factors:

#### Arrival Load.

Before taking a departure off the SID, look to see how the arrivals are being vectored and determine where departures will cross the flow.

If departures remain below the inbound flow, leave sufficient space for APP to descend traffic.

#### Performance.

<span style="white-space: pre-wrap;">The SIDs in Copenhagen all require a 6.6% climb gradient to FL70 - that's 400ft per nautical mile, or a climb rate of ~1700ft/min at 250kts. </span>

At this angle, a departure will reach FL70 approximately 17nm after take-off. FL100 will be reached 25nm after take-off.

<span style="white-space: pre-wrap;">Most </span>**medium jets**<span style="white-space: pre-wrap;"> can manage ~2500ft/min, which delivers a gradient of roughly 10%, or 600ft/nm. Such departures will reach FL100 approximately 17nm after lift off.</span>

With this considered, determine which strategy you will use for each departure:

- Shortest Route / Stepped Climb: relevant where a level-off is required to remain below arrivals. Use high speed below FL70 to reduce the climb gradient.
- <span style="white-space: pre-wrap;">Longer Route / Continuous Climb: relevant where the opportunity exists to pass above arrivals, even if departure routing is slightly longer. Instruct 250kt to maintain the 10% gradient until clear of the conflicting arrival. </span>

## 2. Procedures - Runway 04

[![DEP_04.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/dep-04.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/dep-04.png)

Departures should avoid routing below FL70 in the red shaded area unless coordinated with APP

<details id="bkmrk-r-dep-%28w-app%29-oddon-"><summary>GM for R DEP (W APP)</summary>

- ODDON
- GOLGA / VEDAR

<span style="white-space: pre-wrap;">Two climb opportunities exist, the one you use depends on traffic load under radar vectors in the TMA </span>**and** density of ERNOV arrivals.

1. HDG 350 until above ERNOV flow then DCT - separated from all arrivals, requires high climb gradient to FL110
2. SID or HDG 290 after until passing ERNOV flow then DCT - shorter route, lower required gradient but interaction with downwind traffic and W APP vectoring area

</details><details id="bkmrk-k-dep-%28o-app%29-kemax-"><summary>GM for K DEP (O APP)</summary>

- KEMAX
- SIMEG / SALLO
- NEXEN / KOPEX / SALLO

All conflicting departures must climb above O APP arrivals before passing abeam CH845.

1. <span style="white-space: pre-wrap;">HDG 100-140 until above TIDVU flow then HDG 180-210 until above MONAK flow </span>  
    \**- shorter route but interacts with arrivals, requires at least 2500ft/min to FL100**
2. <span style="white-space: pre-wrap;">Remain on SID until above FL80 then DCT </span>  
    \**- longer route, standard gradient must be maintained**
3. <span style="white-space: pre-wrap;">HDG 040-070 until above FL60, then follow option 1. </span>  
    \**- use where the 6.6% gradient cannot be maintained, or when O APP has vectored arrivals north of CH845**

</details>## 3. Procedures - Runway 22

[![DEP_22.png](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/dep-22.png)](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2025-09/scaled-1680-/dep-22.png)

Departures should avoid routing below FL70 in the red shaded area unless coordinated with APP

<details id="bkmrk-r-dep-%28w-app%29-oddon--1"><summary>GM for R DEP (W APP)</summary>

- ODDON
- GOLGA / VEDAR

Thread the departures through the arriving traffic - coordinate the crossing point with W APP based on the arrival load

1. <span style="white-space: pre-wrap;">HDG 250-270 until above TUDLO / TIDVU flow then DCT </span>  
    \**- separated from all arrivals, requires high climb gradient to FL130**
2. <span style="white-space: pre-wrap;">SID until after passing TUDLO/TESPI flow then DCT </span>  
    \**- appropriate when TUDLO flow are skipping CH645, so you pass under them**
3. <span style="white-space: pre-wrap;">HDG 290-310 until passing TESPI arrivals then DCT </span>  
    \**- shorter route, lower required gradient but interaction with downwind traffic and W APP vectoring area**

</details><details id="bkmrk-k-dep-%28o-app%29-kemax--1"><summary>GM for K DEP (O APP)</summary>

- KEMAX
- SIMEG / SALLO
- NEXEN / KOPEX / SALLO

All KEMAX departures must climb above O APP arrivals before turning north

- HDG 180-210 or SID to CH818 until: 
    - KEMAX: DCT when above FL60. SID is not separated from MONAK flow.
    - SALLO / SIMEG: DCT when above FL100
- <span style="white-space: pre-wrap;">SID until passing MONAK flow then DCT - for SALLO/SIMEG </span>**only**

</details>

# VTC Event - Recency

Apart from have completed the training material for the position desired, following recency rules are in effect when sitting at Vectors to Copenhagen

## EKCH\_F\_APP

<span style="white-space: pre-wrap;">For controllers wishing to man EKCH\_F\_APP during VTC during official bookable times, following extra requirements are in effect: </span>

- Controller must have been online during VTC on an S3 position or higher during the preceeding 3 events before the event where he desires to book EKCH\_F\_APP

## EKDK\_B\_CTR

<span style="white-space: pre-wrap;">For S3 controllers with </span><u>****EKDK SOLO ENDORSEMENT**** </u>wishing to sit on EKDK\_B\_CTR during VTC during official bookable times, following extra requirements are in effect:

- MML endorsement must have been taken during S3 period

# FINAL

<iframe height="519" src="https://www.youtube.com/embed/9oDXI_JPQto" width="926"></iframe>

## Speed Control

Speed control is different from executing base turns

It is Much easier to do!

It is much harder to trust!

<span style="white-space: pre-wrap;">To succeed to must be able to give proper speed control. Not too much, not too little, but preferibly EXCACTLY as I will now describe it... Its a step by step recipe devided into </span>

- Downwind checking in
- Turning Base more than 10 miles
- Turning Base less than 8 miles
- Intercepting ILS
- Established ILS
- Within 10nm
- Within 6nm

Lets begin! The different topics are short.

#### Downwind checking in

<span style="white-space: pre-wrap;">Airplanes SHOULD be handed over by EKCH\_W\_APP/EKCH\_O\_APP maintain 220kts. if less then its for small corrections, and will make no difference. </span>

you first principle lesson is this:

### <u>***DO NOT change that speed!!!*** </u>

<span style="white-space: pre-wrap;">The video explained it, I will not explain it again, do not reduce speed so early. It creates troubles you cannot yet see. </span>

220 should be kept until the very moment a base turn is commenced, and should only be different if you have a VERY good reason and is a skilled F\_APP controller.

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9090/mod_lesson/page_contents/1389/image.png)

#### Turning Base more than 10 miles

Normally (Almost always) when you give a base turn it will be for a minimum of 8 mile final or longer from 2500 feet or higher, and in this case...

**The base turn is where you reduce the speed to 200kts.**

Don't do less, don't do more, but trust that this is a great speed to work with!

**By the way remember to descend them to platform altitude no later than here. preferibly descend them even when they check in**

**Are there any cases where I should NOT use 200kts on base???**

Glad you asked... Yes there is! You may consider less or more when:

- Crosswind of more than 15 knots expected
    - e.g. 22L in use wind 150 at 16 knots. You can expect strong tailwind on right base
- In above case assign 180-190 on the segment with high tailwind base
- Keep 200 on the headwind base
    - Consider 210 in really strong crosswind.
- Other case where you should use another speed is the case described below

#### Turning Base less than 8 miles

<span style="white-space: pre-wrap;">Sometimes we give a 6 miles final @ 2000' or even 5 miles final @ 1500'. In this case the base leg is situated around 8 miles from the runway, and thats just too close to the runway to have 200kts. </span>

In this case, reduce straight away to 180, or at least be ready to reduce to 180 when established on base.

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9090/mod_lesson/page_contents/1389/image%20%281%29.png)

#### Intercepting ILS

When intercepting the ILS is the next thing thats a lesson in trust!

<span style="white-space: pre-wrap;">Do NOT change the speed until he is established, and you can see excactly how close you are to the 3nm separation between airplanes. </span>

<span style="white-space: pre-wrap;">Only if you see you are below 3nm on an intercept should you reduce speed. Like here: </span>

#### Established ILS

Once established on the ILS, it is probably time to reduce the speed.

<span style="white-space: pre-wrap;">It depends however on the distance to the aircraft in front. </span>

If aircraft in front is still far ahead?

<span style="white-space: pre-wrap;">Keep 200 until 10dme, and then reduce to 180, or 160. </span>

If aircraft in front is a factor

<span style="white-space: pre-wrap;">Reduce to 180 when on the localizer, to allow to keep distance to preceeding. Eventually preceeding will slow to 160, and he will catch up to 3nm separation. </span>

If aircraft in front is 3nm ahead

<span style="white-space: pre-wrap;">Match the speed to him. But do not go 160 until within 10nm final, otherwise you will slow the aircrafts behind too much. </span>

#### Within 10nm

Regardless of separation, and aircraft should be reduced to 180 no later than 10nm final

#### Within 6nm

<span style="white-space: pre-wrap;">Regardless of separation, and aircraft MUST be reduced to 160 no later than 6nm final as pr. ICAO DOC 4444. </span>

Issuing 160 until 4DME is always the best thing!

180 until 6DME is also an approved option

## Base turns

<span style="white-space: pre-wrap;">Giving the base turn at the perfect moment is tricky, but you have to first of all train yourself to not hesitate. It is earlier than you think. </span>

Remember to be ready to put an aircraft on a vector, if you base turn appears later than the Vectors fix (ABEGI,ADOVI,ERPUK,DOPEM)

Regular base turn

The regular base turn is the easierst and most predictable. However, it also takes away a lot of flexibility. Once he is on base, he is easily more commited to the final turn.

Therefore knowing WHEN to issue that base turn to have a perfect 3nm separation is important. Lets look at some different situations to help you.

#### 1 - Basic Base turn with preceding already on final

This is by far the easiest. Situations is

BMA2060 on base, speed 220

NSZ81E on final, speed 200

<span style="white-space: pre-wrap;">BMA2060 Radar target (Square) is passing NSZ81Es point of his 3nm arrow pointer. </span>

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image.png)

Thats when to turn base. You have a window of +/- 5 seconds to issue the instruction.

<span style="white-space: pre-wrap;">You can even issue it slightly before if you like. Especially if you feel it is a slow pilot. </span>

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%281%29.png)

<span style="white-space: pre-wrap;">Now BMA2060 is on base, As you see in red you have to evaluate his arrow pointer to the radar target of NSZ81E. Normally it will be enough to an almost immediately turn to intercept. </span>

<span style="white-space: pre-wrap;">Blue denotes his 3nm pointer if he had turn directly inbound. There would still have been distance to spare. </span>

<span style="white-space: pre-wrap;">Therefore do not hesitate. Give him the inbound turn. </span>

Note at this point NZS81E is 180 as he should be on localiser, and BMA2060 is 200 as he should be on base, so the speed difference will help!

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%282%29.png)

<span style="white-space: pre-wrap;">As the inbound turn is given the distance is 3.3nm. </span>

NSZ81E speed is 160 until 4DME

<span style="white-space: pre-wrap;">BMA2060 is reduced to 180 as he is inside of 10nm final. </span>

<span style="white-space: pre-wrap;">The speed difference will equalize to the fact that becuase BMA2060 has still an intercept heading, separation would normally increase. </span>

<span style="white-space: pre-wrap;">Keep BMA2060 on 180 until he is established. </span>

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%283%29.png)

They are established, separation is 3.2 nm. Thats fine!!

<span style="white-space: pre-wrap;">Reduce to 160 and handover to TWR. Thats it! </span>

**Remember!**

**When aircraft target passes preceedings 3nm arrow point, turn base!!**

#### 2 - Base turn with preceding on intercept

This is relatively easy. You do the same as above, because on intercept there is so little extra track miles, that its a matter of seconds for the turns. Just keep it simple and stick to same procedure as above.

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%284%29.png)

Again, its fine to issue the instruction even a few seconds before!!

3 - Basic Base turn with preceding also on base

This is tricky. You have two different scenarios. From same side or opposide side

Opposite side

Here you have two airplanes on same downwinds, BEL5EP already has base turn instructed. WHEN do you turn in TSA1631??

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%285%29.png)

<span style="white-space: pre-wrap;">You just gotta get a feeling for it. Learn how long time it takes for people to start their base turn after instruction is given. and then you must: </span>

<span style="white-space: pre-wrap;">Issue the instruction so that base turn from TSA1631 is </span><u>**COMMENCED**</u> when is passing the extended base path of BEL5EP

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%286%29.png)

Now they should be flying towards eachother but a slight offset. Be carefull with altitudes here. It is easy to mistakenly create Loss of Separation here.

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%287%29.png)

<span style="white-space: pre-wrap;">As you turn BEL5EP. BE READY!! To turn TSA1631 inbound right after. It is very difficult to judge but use best judgement on where the 3nm arrow of TSA1631 is, to judge. Lets go through it. </span>

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%288%29.png)

<span style="white-space: pre-wrap;">AAs soon as BEL5EP starts the turn, you can see that TSA1631 already has more than 3nm. This is normally because: </span>  
  
Since TSA1631 was number 2 it was likely turned on base slightly later, hence is further from Localizer than BEL5EP. Take into consideration the ~2nm offset, then the difference in location from localizer gives the last mile, and you can turn TSA1631 in immediately after

![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%289%29.png)

<span style="white-space: pre-wrap;"> </span>![](https://moodle.vatsim-scandinavia.org/pluginfile.php/9089/mod_lesson/page_contents/1388/image%20%2810%29.png)

It worked!!