Approach Planner Position

For controllers subject to FMP, please see at the end of this page for abbreviated procedures you can expect.

1. StandardGeneral

separation scenario

This scenario used from the beginning of event until yellow operational rate is hitting

Copenhagen Approach planner (EKCO_APP) has primary frequency of 120.205 and is responsible for managing traffic and sequencing traffic into FINAL. Primary tasks are to establish the sequence, sorting flights based on WTC and ensure that the flow into FINAL are staggered and of an appropriate separation.

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

Consider taking ownership in "Sector Ownership Setup" in "Other Settings" menu of Euroscope to take ownership of all APP airspace. Your individual settings are local and LowerDOES NO

T interfere with anybody else.

2. Coordination with FINAL

Coordination with FINAL is your primary task

Tasks

• Determine sequence of flights, and communicate the sequence to FINAL where appropriate.
• Assign 22R for appropriate flights. (WTC or VREF restrictions).
  • EKCO 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.h

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

---

3. Coordiantion with W_APP+O_APP

You need to set the appropriate rate when needed, accomendate APP request when able, and remind them to stagger arrivals

EKDK_B:Choose appropriate separation requirement based on TMA experience,

• 10nm separation.= 40flight/hr = ability of our controllers on average. Aim for 10-15this in general
• EKDK_D:8nm 10nm= separation.42/hr Aim= Ability for 10-15
• EKDK_E:highly 10nmexperienced separation.FINAL Aim for 10-15

Upper

• EKDK_A: 15nm separation. Aim for 15nm, coordinate with EDYY to get as even a spread as possible.
• EKDK_V: 15nm separation. Aim for 15, try to get as evenly a spread as possible.

• EDYY_J/H: Min. 10nm separation. Try to as evenly spread as possible.
• EDWW_M: Min. 10nm separation. Try to as evenly spread as possible.

EKDK_A should coordinate with EDYY to the greatest extent possible.

2. Yellow operational rate scenario

When your operational rate turn away from white to yellowcontrollers, or red,when youfinals needare toshort move to this scenario

WEST FLOW

To choose appropriate scenario. This is tricky but important. Consider following things:

• Prefered rate at ERNOV is 1 every 10min. Is that possible?
• Is Approach not very busy and final (less than 12nm?10nm)
• Will12nm it= stay38/hr yellow= To create extra space for at least another 30-45 minutes?

If Yes to all? Take Variation 1

• ERNOV is very busy?
• Approach looks very loaded and final is quite long
• Relatively inexperienced controllers
• Red area is approaching fast
• Yellow area is very close to 42 movements aka. borderline turning red.

If Yes to just some? Take variation 2

Is the Red area approaching fast, or isstressed itFINAL controllers.

Advise FMP if a longprolonged stretch

Variation 1

This variation keeps a higher than capacity arrival rate (36/hr) to keep flow coming from TUDLO/TESPI while de-prioritizing ERNOV

Sector	Separation (nm)	Separation (Min.)	Or	Separation (nm)	Separation (Min.)
EKDK_E_CTR	20nm	4	Or	25*	5*
EKDK_D_CTR	20nm	4	Or	25*	5*
ESMM_K	--	10	Or	30*	6*

*Only in caseduration of load being heavily on ERNOV relative to TESPI and TUDLO. Not usual.

Variation 2

Sector	Separation (nm)	Separation (Min.)
EKDK_E_CTR	30nm	6
EKDK_D_CTR	30nm	6
ESMM_K	--	10

EAST FLOW

Sector	Separation (nm)	Separation (Min.)
EKDK_B_CTR	15nm	3
EDWW_M	25*
ESMM_L	--	10

Ask Muritz to start stacking to FL270 if 25nm cannot be maintained.

Considerations

Start asking EKDK_V, EKDK_A, EDYY for minimum speeds, as holdings will come.

Prepare EKDK_A and EKDK_V that when holdings are coming they should clear airplanes into holdings.

Consider diversions from EDYY to TUDLO to avoid MONAK chaos

Consider diversions from EDWW_M to TIDVU to avoid MONAK chaos

Continue to run this scenario until no longer possible, and holding will be needed "imminently"

---

3. Holdings (Red) scenario

When it becomes APPARENT to you that with the rate given EKDK_D/E/B cannot maintain separation, and holdings are needed!

You will know holdings38/hr are needed

before

4. BIDE.Coordination Advisewith themACC

FMP is overall responsible for flow. You role is to bepick readyindividual forholes it.

WESTdue FLOW

Startto when it becomes apparent by taking a talk with EKDK_A_CTRGAs and EKDK_V_CTRshort term struggles

Advise them to:

• Clear aircraft onto the arrival
• Clear aircraft into the hold
• Update the tag so aircraft enters holding list

Consider if holdings get very busy for EKDK_A/V to:

• Descend aircraft to the lowest available holding level
• Enter holds above Fl285, and handover as needed

Release and EATs.

Keep previous flow rate until APP appears very full.

The revert to flow rate as below

Sector	Separation (nm)	Separation (Min.)	Or	Separation (nm)	Separation (Min.)
EKDK_E_CTR	30nm	6	Or	40*	8*
EKDK_D_CTR	30nm	6	Or	40*	8*
ESMM_K	--	10	Or	30*	6*

Above table depend on ERNOV. Use MDI=10 for ERNOV unless conditions renders impossible

Ask all sectors to enter EATs as follows:

ERNOV

count 5-10 min from beginning of hold and then assign EATs with 10min interval independently of what goes on with EKDK_E/D

TUDLO/TESPI

Identify via the holding list the distribution of traffic on each arrival.

• ETOs are within approx 10min of eachother = Give the rate as pr. table above
• ETOs are heavily skewed to one of the other = Hold one completely and half the separation time for the other.

Example of skewity.

Lets pretend time is 1930z for first release:

Ask each BIDE sector over text to enter following information to their EATs

This scenario was the 6,6,10 scenario with only one holding at the time, meaning 3min release.

EAST FLOW

east flow we must take following considerations

• TIDVU will never be more busy than MONAK
• MONAK gets very difficult very fast
• Keeping MONAK holdings manageable is a top priority

When holdings are imminent, keep very vigilant of following:

• Get an overview if traffic from Muritz will be managable
• Prepare to give stacked levels to Muritz in accordance with the holding
• Get an overview of IF diversions to other STARs are needed
  • Divert to other STARs ONLY for the purpose of keeping holding managable. Dont worry about traffic balancing.

Sector	Separation (nm)	Separation (Min.)
EKDK_B_CTR	15nm	3
EDWW_M	25*/**
ESMM_L	--	10

*Ask Muritz to start stacking to FL270 if 25nm cannot be maintained.

*ensure Muritz employ minimum speed

Imbalance mitigation

It can happen that one particular STAR is so overloaded compared to others that immediate priority is needed to avoid overflow of holdings. this is mainly apparent when:

• MONAK early in the event
• TESPI when ENGM/ENBR traffic is heavy.

If condition allows then go a heavily prioritize the STAR needing direct priority. Do this for no more than 15 minutes to avoid overload at other STARs. In this case utilize following.

Sector	Separation (nm)	Pre-coordinated to minimum
Peak STAR	10nm	7.5
Other STAR on the side	Complete STOP	6
STARs on other side	--	6min EAT, given as needed from holdings

*15 min with that separation you can relieve almost 8 aircraft from a holding

Controller abbreviated procedures

As controllers expect following to be issued by EKDK_FMP

Low traffic load

All Sectors: Standard separation 10nm, min. 5nm only with verbal coordination

Medium traffic load

Depending on amount of aircrafts in the TMA.

If less than 10 aircraft in TMA expect following

Sector	Separation (nm)	Separation (Min.)	Or	Separation (nm)	Separation (Min.)
EKDK_E_CTR	20nm	4	Or	25*	5*
EKDK_D_CTR	20nm	4	Or	25*	5*
EKDK_B_CTR	15nm	3	Or	30*	6*

*In case of high load on ESMM sectors.

If 10 aircraft or more in TMA

Sector	Separation (nm)	Separation (Min.)	Or	Separation (nm)	Separation (Min.)
EKDK_E_CTR	30nm	6	Or	40*	8*
EKDK_D_CTR	30nm	6	Or	40*	8*
EKDK_B_CTR	15nm	3	Or	30*	6*

*In case of high load on ESMM sector

At all times shall you establish holdings in order to accommodate short term separation increases it may be needed to have a temporary hole, while not affecting the requiredFMP separationdesignated ACC handoff rate.

Peak traffic

• Advise load

Sector	SeparationFMP to create a 10nm (nm)	Separation2min) sequence gap when a missed approach has been executed with 22L in use if deemed necessary by EKCO. Advise FMP to create a 10nm (Min.)	Or	Separation2min) (nm)	Separationsequence (Min.)
EKDK_E_CTR	30nm	6	Or	40*	8*
EKDK_D_CTR	30nm	6	Or	40*	8*
ESMM_K	--	10	Or	30*	6*

*Ingap casewhen a missed approach has been executed with 04L in use if deemed necessary by EKCO.

Ask via FMP any ACC controller to skip a maximum of highone loadslot onwhen ESMMadditional sector

Holdingspace notes

Pleaseis needed in yourTMA holdingairspace.

Any listcoordination gowith ACC must be additional coordinated with FMP. FMP will relay the request or delegate it to "VIEW" and click on "EAT" to show EAT column. Please put in the EAT as directed by EKDK_FMP (EAT=Expected Approach time, and is the time you may clear an aircraft to pass the inbound fix (KOR,TNO,NEKSO).

Imbalance mitigation

For a duration of no more than 15min. imbalance mitigation can be used to correct for extreme load on one particular STAR.

• You STAR is the subject?
  • 7.5-10nm separation. less than 7.5nm muts be coordinated. 7.5 and above is PRE-COORDINATED by FMP.EKCO.
• another STAR on your side (East/West) is the subject?
  • Stop all approaches. hold indefinately
• another STAR on opposite side (East/West) is the subject?
  • EAT as assigned by EKDK_FMP. Keep a look out.