Flow Management Position
For controllers subject to FMP, please see at the end of this page for abbreviated procedures you can expect.
ALB = Arrival Load Balancer
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
- Manage flow inbound to copenhagen by use of the "BIDE" Acronym
- Balance
- Interrogate
- Distribute
- Equalize
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
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, and has several pre-defined scenarios.
2.1 Standard Separation (Green Flow)
This scenario used from the beginning of event until hourly rate becomes more than 30/hr.
Arrival rate 150 flights / hr
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 30/hr) that the distribution of flights are negligeble.
Either via manual calculations, ALB or MAESTRO, fine tuning of timings, and speed restrictions can be utilized with this rate. Neither are mandatory, but may make APPs use of vectors more efficient.
2.2 IncreasedReduced Separationflow (Yellow Flow)
This scenario used from when ALB advise of an hourly rate of MORE than ~30/hr, but with TMA consitent load factor of 12 airplanes or less
Arrival rate 56 flights / hr
2.1.1 Required Rates
ALB has several scenarios for rates distribution based on the load factor for STARs.
Load factors are displayed in percent for the next 30 minutes.
The scenarios included are valid 95% of the time and are adjusted as follows:
Yellow2.1.2 Thoughts and considerations
Consider start negotiating with Upper ACCs in providing delay vectors in order to help achieving the required separation as early as possible
WEST:Invoke LOA point on EDYY and EDWW to increase separation to minimum 25nm.-
2.3 Peak Flow (RedFlow)
This scenario used from when ALB advise of a TMA load of 12 or more AND 30flight/hr. or more inbound.
Arrival rate 45 flights / hr
2.1.1 Required Rates
ALB has similar scenarios for Peak flow as well. 12 or more planes in TMA signifies that TMA has reached capacity and immediately action is required to reduce flow rate to a level that is sustainable and comparative to what the TMA can land
The scenarios included are valid 95% of the time and are adjusted as follows:
2.1.2 Thoughts and considerations
ThisConsiderratestartisnegotiatingbeingwithusedUpperwhenACCssoinlittleprovidingloaddelaywillvectorsbein order to help achieving the required separation as early as possibleInvoke LOA point on
the TMA (smaller than 30/hr) that the distribution of flights are negligeble.Either via manual calculations, ALB or MAESTRO, fine tuning of timings,EDYY andspeedEDWWrestrictionstocanincreasebeseparationutilizedtowithminimumthis25nm.rate. Neither are mandatory, but may make APPs use of vectors more efficient.2. Yellow operational rate scenario
When your operational rate changes 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
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 holdings are needed before BIDE. Advise them to be ready for it.
WEST FLOW
Start when it becomes apparent by taking a talk with EKDK_A_CTR and EKDK_V_CTR
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 STARs on same 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 the required separation
Peak traffic load
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*
*In case of high load on ESMM sector
Holding notes
Please in your holding list go 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?
- Apply 7.5 - 10nm separation:
- less than 7.5nm must be coordinated
- 7.5nm and above is PRE-COORDINATED by FMP
- Apply 7.5 - 10nm separation:
- another STAR on your side (East/West) is the subject?
- Stop all approaches. Hold indefinitely
- another STAR on opposite side (East/West) is the subject?
- EAT as assigned by EKDK_FMP. Keep a look out.
-
