# 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