Flow Management Position

1. Standard separation scenario

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

Lower

• EKDK_B: 10nm separation. Aim for 10-15
• EKDK_D: 10nm separation. Aim for 10-15
• EKDK_E: 10nm separation. 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_Y: 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 yellow or red, you need to 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?
• Will it stay yellow 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 is it a long 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 case 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	30nm15nm	63
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 yourit operationalbecomes APPARENT to you that with the rate turngiven awayEKDK_D/E/B fromcannot whitemaintain separation, and holdings are needed!

You will know holdings are needed before BIDE. Advise them to yellowbe orready red,for you need to move to this scenarioit.

WEST FLOW

ToStart choosewhen appropriateit scenario.becomes Thisapparent isby trickytaking buta important.talk Considerwith followingEKDK_A_CTR things:
and EKDK_V_CTR

Advise them to:

• PreferedClear rateaircraft atonto ERNOVthe is 1 every 10min. Is that possible?arrival
• IsClear Approachaircraft notinto 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 finalhandover lessas than 12nm?
• Will it stay yellow for at least another 30-45 minutes?needed

IfRelease Yesand EATs.

Keep previous flow rate until APP appears very full.

The revert 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 is it a long stretch

Variation 1

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

Sector	Separation (nm)	Separation (Min.)	Or	Separation (nm)	Separation (Min.)
EKDK_E_CTR	20nm30nm	46	Or	25*40*	5*8*
EKDK_D_CTR	20nm30nm	46	Or	25*40*	5*8*
ESMM_K	--	10	Or	30*	6*

*OnlyAbove intable casedepend 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 loadhold beingand 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 on ERNOV relativeskewed to TESPIone of the other = Hold one completely and TUDLO.half Notthe usual.

  separation time for the other.

VariationExample 2of skewity.

Sector	SeparationLets (nm)pretend time is 1930z for first release:	SeparationAsk (Min.)each BIDE sector over text to enter following information to their EATs
EKDK_E_CTR	30nmThis scenario was the 6,6,10 scenario with only one holding at the time, meaning 3min release.	6
EKDK_D_CTR	30nm	6
ESMM_K	--	10

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	30nm15nm	63
EDWW_M	25*/**
ESMM_L	--	10

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

Considerations

Start*ensure askingMuritz EKDK_V, EKDK_A, EDYY foremploy minimum speeds,speed

Imbalance asmitigation

It holdingscan will come.

Prepare EKDK_A and EKDK_Vhappen that whenone holdingsparticular areSTAR comingis theyso shouldoverloaded clear airplanes into holdings.

Consider diversions from EDYYcompared to TUDLOothers that immediate priority is needed to avoid overflow of holdings. this is mainly apparent when:

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

ConsiderIf diversionscondition fromallows EDWW_Mthen togo TIDVUa heavily prioritize the STAR needing direct priority. Do this for no more than 15 minutes to avoid MONAKoverload chaosat other STARs. In this case utilize following.

Sector	Separation (nm)	Pre-coordinated to minimum
ContinuePeak toSTAR	10nm	7.5
Other runSTAR thison scenariothe untilside	Complete noSTOP	6
STARs longeron possible,other andside	--	6min holdingEAT, willgiven beas needed "imminentlyfrom holdings EAST

EKDK_B:*15 15nmmin separation.with (3min)

ESMM_L: EAT 1 every 10 min. closer release as conditions allow.

EDWW_M: Min clean. 25nmthat separation asyou minimum.can

EDYY_J:relieve Minalmost clean.8 Keepaircraft anfrom eyea on which to divert to EKDK_A.

--------------------------

OVERLOAD EAST:

EKDK_B: 5-10nm

ESMM_L: Complete approach stop.

WEST SIDE: EAT one every 5 minutes collaboratively.

OVERLOAD WEST:

EKDK_D/E: 5-10nm

EKDK_E/D: APP STOP

ESMM_K: APP STOP or EAT 1 every 10 min. Depending on situation.

EAST SIDE: EAT one every 5 minutes collaboratively. holding

PEAK:

EKDK_D/E/K: 15nm between flights pr. holding.

EDYY_J: Min. 25nm separation. Min clean speed

EKDK_B/L: 15nm between flights pr. holding.

EDWW_M: Min. 25nm separation. Stack if possible up to FL270. Divert to ESMM_L if problematic. min clean speed if possible.

EDYY_J: Divert to sector A if possible. min clean speed