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 | 30nm | 6 |
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 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 | 30nm | 6 |
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
EAST
EKDK_B: 15nm separation. (3min)
ESMM_L: EAT 1 every 10 min. closer release as conditions allow.
EDWW_M: Min clean. 25nm separation as minimum.
EDYY_J: Min clean. Keep an eye 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.
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