COORDINATION PROCEDURES Clause Samples

COORDINATION PROCEDURES. Coordination procedures between the ATC under the responsibility of the London FIR and those under the responsibility of the Brest FIR 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.

COORDINATION PROCEDURES. A. the Aviation Department shall calculate the Terminal Building Rent and User Fee Rates to be effective October 1 of each year based upon the annual budget and estimates of arriving and departing aircraft seats and rentable space in the Terminal Building. Prior to the adoption of this budget by the Board, the Aviation Department will meet with the Miami Airline Affairs Committee (the “MAAC”) or its designated representative to review the proposed budget, the activity estimates, and the calculation of the Terminal Building Rent and User Fee Page 119 of 153 Rates. The Aviation Department shall give fair and prudent consideration to additions, deletions, or modifications recommended by the MAAC, recognizing that the Board of County Commissioners has sole responsibility for final approval of the annual budget.

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. The provision 4.2.4 of the HCM Agreement does not apply. For a preferential frequency, the field strength level shall not exceed the maximum value of 19 dBμV/m at 3 m above the ground on a 15 km line inside the other country.

COORDINATION PROCEDURES. DEP & ARR‌ Coordination procedures between the ACC positions of Shanwick & ▇▇▇▇▇▇▇ 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 en-route FIX. 6.1. BREST (IROISE) FIC‌ AD DEP ALT/FL DCT XFER Notes LFRB MATER - - LFRR_CTR → EGGX_SG_CTR or LFRR_CTR → EISN_CTR Aircraft departing from Brest (LFRB) wishing to enter the OCA must get their oceanic clearance while on ground after their initial departure clearance. NORBU

COORDINATION PROCEDURES. EN ROUTE‌ Coordination procedures between the ATC positions under the responsibility of the London ACC and those under the responsibility of the Brest 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 BREST (EGTT → LFRR)‌ 5.1.1. LOWER AIRSPACE (SFC-FL245) RTE DCT XFER PT XFER ATC Restrictions M605 XIDIL AoR Boundary LFRR_CTR Odd Level 5.1.2. UPPER AIRSPACE (FL245-UNL) RTE DCT XFER PT XFER ATC Restrictions UM605 XIDIL AoR Boundary LFRR_CTR Odd Level 5.2. FROM BREST TO LONDON (LFRR → EGTT)‌ 5.2.1. LOWER AIRSPACE (SFC-FL195) RTE DCT XFER PT XFER ATC Restrictions A34 SITET AoR Boundary EGTT_CTR Even Level 5.2.2. UPPER AIRSPACE (FL195-UNL) RTE DCT XFER PT XFER ATC Restrictions UZ273 ▇▇▇▇▇ AoR Boundary EGTT_CTR Even Level

COORDINATION PROCEDURES. The following are the guidelines for inter-regional coordination which are accepted by Region 8, Region 19 and Region 30. a. Each Region will announce when it is accepting applications and the parameters that it has established filing applications. b. Applications by eligible entities will be accepted within each Region’s parameters. c. Regional review and coordination of applications will be conducted. The review will include a technical review resulting in assignment of channels. d. After Regional review, a copy of those frequency-specific applications requiring adjacent Region approval, including a definition statement of proposed service area, shall then be forwarded to the adjacent Region(s) for review. This information will be sent to the adjacent Regional chairperson(s) using the CAPRAD database. e. The adjacent Region will review the application. If the application is approved, this Region will send a letter of concurrence, via the CAPRAD database, to the initiating Regional chairperson within thirty (30) calendar days of receipt of the application by the adjacent Region.

COORDINATION PROCEDURES. DEP & ARR 5.1. BALE APP & REIMS ACC LFSB TORPA/MOROK FL190 - LFSB_APP → LFEE_CTR - LFSB ARPUS FL200 ARPUS LFEE_CTR → LFSB_APP - 5.2. STRASBOURG APP & REIMS ACC AD DEP ALT/FL DCT XFER Notes LFST BERUG/EPIKO/ GTQ/MIRGU/ POGOL FL190 - LFST_APP → LFEE_CTR - LFJL EPL/▇▇▇▇▇/ PHALO FL190 - LFST_APP → LFEE_CTR MMD departures transferred to LFFF. AD ARR ALT/FL DCT XFER Notes LFST EPL/LUL FL200 23: BERUG 05: IZPIQ LFEE_CTR → LFST_APP - GTQ 23: SAV 05: BAKIX LFJL EPL/▇▇▇▇▇ FL200 22: GTQ 04: JL502 LFEE_CTR → LFST_APP RWY 04 : If not RNAV, keep on STAR 5.3. ▇▇▇▇▇▇▇▇ APP & STRASBOURG APP AD DEP ALT/FL DCT XFER Notes LFJL DIK/MAKOT FL70 - LFJL_APP → LFST_APP UNICOM, ELLX or EDGG transfer after coordination with LFST_APP MMD/▇▇▇▇▇ ▇▇▇▇▇/EPL FL70 - LFJL_APP → LFST_APP - AD ARR ALT/FL DCT XFER Notes LFJL Any FL80 IAF LFST_APP → LFJL_APP 22: GTQ / MTZ 04: ▇▇▇▇▇ / MTZ / JL503

COORDINATION PROCEDURES a. Handoffs shall be accomplished no later than 10nm from the ZJX/▇▇▇ ▇▇▇▇▇▇▇▇. b. It will not be necessary to coordinate inappropriate altitude for direction of flight on aircraft departing the Pensacola Terminal Area assigned an interim altitude of FL230. c. When using vERAM or VRC, mandatory radar handoffs suffice for coordination on aircraft climbing or descending to the altitude displayed in the data block. The altitude may be an interim altitude, or the altitude forwarded by the Controller Client. It will be the responsibility of the receiving controller to verbally impose any necessary restrictions for an aircraft for the purpose of separation, through the transferring controller. d. Transponder codes may be changed within 15nm of the mutual boundary without prior coordination provided both facilities are operating under EAS/ERAM.