Common use of COORDINATION PROCEDURES Clause in Contracts

COORDINATION PROCEDURES. DEP & ARR 6.1. CHANNEL ISLANDS TMA AD DEP ALT/FL DCT XFER Notes EGJ* ORIST - - EGJJ_C_APP → EGTT_CTR These departures are never handled by Brest Control GULDA FL130 BENIX EGJJ_C_APP → LFRN_APP See note below* LERAK EGJJ_C_APP → LFRB_APP LIZAD TUNIT LFRD LFRT LERAK /MINQI max FL100 or even level - LFRN_APP → EGJJ_C_APP AD ARR ALT/FL DCT XFER Notes EGJ* BIGNO - - EGTT_CTR → EGJJ_C_APP These arrivals are never handled by Brest Control TUNIT FL140 - LFRB_APP → EGJJ_C_APP See note below* MINQI (RWY 26 only) LFRN_APP → EGJJ_C_APP LFRD LFRT LERAK/MINQI FL110 - EGJJ_C_APP → LFRN_APP * These flights are not released for descent/climb (RFD/RFC). Therefore, Rennes, Iroise, and Jersey will anticipate the transfers to avoid a penalizing level-off, especially during descents, and will inform the receiving controller whether the traffic is released for descent/climb. During periods of low traffic, it is possible to coordinate and declare all RFD/RFC flights. AD ARR ALT DCT XFER Notes EGJ* vers LFRD - 3000ft - EGJJ_C_APP → LFRN_APP Local QNH provided upon entering the area of responsibility. LFRD vers EGJ* AGANO 4000ft LFRN_APP → EGJJ_C_APP For these flights, coordination of the route between the two controllers can be carried out either via a sector boundary point or by assigning a direct route to an Initial Approach Fix (IAF). 6.2. LONDON AREA EGLL ROXOG FL300 - LFRR_CTR → EGTT_CTR Standard routing viaREVTU (FL340) > BOLRO FL300 EGKK VASUX FL300 - LFRR_CTR → EGTT_CTR Standard routing via REVTU (FL330) > ODREP FL300 EGLC ▇▇▇▇▇ FL220 - LFRR_CTR → EGTT_CTR Levelled by ▇▇▇▇▇ EGGW TELTU FL340 - LFRR_CTR → EGTT_CTR Standard routing viaDIKRO (FL380) > LUGIS/KOTEM FL340 EGSS AVANT FL340 - LFRR_CTR → EGTT_CTR Standard routing viaDIKRO (FL380) > LUGIS/KOTEM FL340 6.3. RENNES FIC LFRK ▇▇▇▇▇ FL080 - LFRR_CTR → EGTT_CTR - LFRK ▇▇▇▇▇ FL090 - EGTT_CTR → LFRR_CTR

COORDINATION PROCEDURES. DEP & ARRARR‌ Coordination procedures between the ACC positions of London and Brest and the adjacent approach positions (APP) are defined as follows. They represent a general framework that does not replace the coordination between ATC. Any coordination procedure not mentioned in this LoA must be established on a case-by-case basis. Some of the transfer scenarios below have been simplified for clarity. Depending on the airspace structure around a position, it could be that a traffic must be transferred to a third-party position which is not listed in the table. When no direct is defined for departures in the table below, it can be assumed that the controller can give a direct to the first enroute FIX. 6.1. CHANNEL ISLANDS TMA TMA‌ AD DEP ALT/FL DCT XFER Notes EGJ* EGJJ ORIST - - EGJJ_C_APP EGJJ_CTR → EGTT_CTR These departures are never handled by Brest Control GULDA FL130 BENIX EGJJ_C_APP FL190 - EGJJ_CTR → LFRN_APP See note below* LERAK EGJJ_C_APP → LFRB_APP LIZAD TUNIT LFRD LFRT LERAK /MINQI max FL100 or even level LFRR_CTR - LFRN_APP → EGJJ_C_APP AD ARR ALT/FL DCT XFER Notes EGJ* EGJJ BIGNO - - EGTT_CTR → EGJJ_C_APP EGJJ_CTR These arrivals are never handled by Brest Control TUNIT FL140 BEVAV FL200 - LFRB_APP LFRR_CTR → EGJJ_C_APP See note below* MINQI (RWY 26 only) LFRN_APP → EGJJ_C_APP LFRD LFRT LERAK/MINQI FL110 - EGJJ_C_APP → LFRN_APP * These flights are not released for descent/climb (RFD/RFC). Therefore, Rennes, Iroise, and Jersey will anticipate the transfers EGJJ_CTR DCT to avoid IAF may be coordinated on a penalizing levelcase-off, especially during descents, and will inform the receiving controller whether the traffic is released for descent/climb. During periods of low traffic, it is possible to coordinate and declare all RFD/RFC flights. AD ARR ALT DCT XFER Notes EGJ* vers LFRD - 3000ft - EGJJ_C_APP → LFRN_APP Local QNH provided upon entering the area of responsibility. LFRD vers EGJ* AGANO 4000ft LFRN_APP → EGJJ_C_APP For these flights, coordination of the route between the two controllers can be carried out either via a sector boundary point or by assigning a direct route to an Initial Approach Fix (IAF).by-case basis 6.2. LONDON AREA AREA‌ EGLL ROXOG FL300 - LFRR_CTR → EGTT_CTR Standard routing viaREVTU via REVTU (FL340) > BOLRO FL300 EGKK VASUX FL300 - LFRR_CTR → EGTT_CTR Standard routing via REVTU (FL330) > ODREP FL300 EGLC ▇▇▇▇▇ FL220 - LFRR_CTR → EGTT_CTR Levelled by ▇▇▇▇▇ EGGW TELTU FL340 - LFRR_CTR → EGTT_CTR Standard routing viaDIKRO via DIKRO (FL380) > LUGIS/KOTEM FL340 EGSS AVANT FL340 - LFRR_CTR → EGTT_CTR Standard routing viaDIKRO via DIKRO (FL380) > LUGIS/KOTEM FL340 FL340 6.3. RENNES FIC LFRK DEAUVILLE FIC‌ AD DEP ALT/FL DCT XFER Notes LFRG ▇▇▇▇▇ FL080 - LFRR_CTR → EGTT_CTR - LFRK ▇▇▇▇▇ FL090 - EGTT_CTR → LFRR_CTR

COORDINATION PROCEDURES. EN ROUTE‌ Coordination procedures between the ATC positions under the responsibility of the London ACC and those under the responsibility of the Paris ACC are defined as follows. They represent a general framework that does not replace the coordination between ATC. Any coordination procedure not mentioned in this LoA must be established on a case-by- case basis. A direct further than the area of responsibility must be coordinated. 5.1. FROM LONDON TO PARIS (EGTT → LFFF)‌ 5.1.1. LOWER AIRSPACE (SFC-FL245) RTE DCT XFER PT XFER ATC Restrictions L10 RINTI AoR Boundary LFFF_CTR Odd Level 5.1.2. UPPER AIRSPACE (FL245-UNL) RTE DCT XFER PT XFER ATC Restrictions L10 RINTI AoR Boundary LFFF_CTR Odd Level 5.2. FROM PARIS TO LONDON (LFFF → EGTT)‌ 5.2.1. LOWER AIRSPACE (SFC-FL195) RTE DCT XFER PT XFER ATC Restrictions B3 RINTI AoR Boundary EGTT_CTR Even Level 5.2.2. UPPER AIRSPACE (FL195-UNL) RTE DCT XFER PT XFER ATC Restrictions UL613 RATUK AoR Boundary EGTT_CTR Even Level 6. COORDINATION PROCEDURES – DEP & ARRARR‌ Coordination procedures between the ACC positions of London and Paris and the adjacent approach positions (APP) are defined as follows. They represent a general framework that does not replace the coordination between ATC. Any coordination procedure not mentioned in this LoA must be established on a case-by-case basis. Some of the transfer scenarios below have been simplified for clarity. Depending on the airspace structure around a position, it could be that a traffic must be transferred to a third-party position which is not listed in the table. When no direct is defined for departures in the table below, it can be assumed that the controller can give a direct to the first enroute FIX. 6.1. CHANNEL ISLANDS TMA AD DEP ALT/FL DCT XFER Notes EGJ* ORIST LONDON AREA‌ EGLL ALESO FL380 - - EGJJ_C_APP LFFF_CTR → EGTT_CTR These departures are never handled by Brest Control GULDA FL130 BENIX EGJJ_C_APP ABNUR/KESAX FL360 or below EGKK KUNAV FL320 - LFFF_CTR → LFRN_APP See note EGTT_CTR KESAX FL320 or below EGLC SOVAT FL220 - LFFF_CTR → EGTT_CTR RATUK FL220 or below EGLF ELDAX FL280 - LFFF_CTR → EGTT_CTR SOSUN/KESAX FL280 or below* LERAK EGJJ_C_APP 6.2. PARIS AREA‌ LFOB OPALE FL260 KESAX LFFF_CTR → LFRB_APP LIZAD TUNIT LFRD LFRT LERAK /MINQI max FL100 or even EGTT_CTR Early transfer to avoid level - LFRN_APP → EGJJ_C_APP AD ARR ALT/FL DCT XFER Notes EGJ* BIGNO - off LFPG BIBAX FL260 - EGTT_CTR → EGJJ_C_APP These arrivals are never handled by Brest Control TUNIT FL140 - LFRB_APP → EGJJ_C_APP See note below* MINQI (RWY 26 only) LFRN_APP → EGJJ_C_APP LFRD LFRT LERAK/MINQI FL110 - EGJJ_C_APP → LFRN_APP * These flights are not released for descent/climb (RFD/RFC). Therefore, Rennes, Iroise, and Jersey will anticipate the transfers to avoid a penalizing level-off, especially during descents, and will inform the receiving controller whether the traffic is released for descent/climb. During periods of low traffic, it is possible to coordinate and declare all RFD/RFC flights. AD ARR ALT DCT XFER Notes EGJ* vers LFRD - 3000ft - EGJJ_C_APP → LFRN_APP Local QNH provided upon entering the area of responsibility. LFRD vers EGJ* AGANO 4000ft LFRN_APP → EGJJ_C_APP For these flights, coordination of the route between the two controllers can be carried out either via a sector boundary point or by assigning a direct route to an Initial Approach Fix (IAF). 6.2. LONDON AREA EGLL ROXOG FL300 - LFRR_CTR → EGTT_CTR Standard routing viaREVTU (FL340) > BOLRO FL300 EGKK VASUX FL300 - LFRR_CTR → EGTT_CTR Standard routing via REVTU (FL330) > ODREP FL300 EGLC ▇▇▇▇▇ FL220 - LFRR_CTR → EGTT_CTR Levelled by ▇▇▇▇▇ EGGW TELTU FL340 - LFRR_CTR → EGTT_CTR Standard routing viaDIKRO (FL380) > LUGIS/KOTEM FL340 EGSS AVANT FL340 - LFRR_CTR → EGTT_CTR Standard routing viaDIKRO (FL380) > LUGIS/KOTEM FL340 6.3. RENNES FIC LFRK ▇▇▇▇▇ FL080 - LFRR_CTR → EGTT_CTR - LFRK ▇▇▇▇▇ FL090 LFFF_CTR XIDIL FL260 LFPO BOBSA FL290 - EGTT_CTR → LFRR_CTRLFFF_CTR SITET FL290 to avoid LFRR airspace LFOB VELOL FL240 - EGTT_CTR → LFFF_CTR XIDIL FL240