COORDINATION PROCEDURES a. Coordination shall be done by reference to sector ID or frequency, not callsign.
b. Chattanooga ATCT (CHA) departure/arrival transition area (DTA/ATA) operations and Birmingham ATCT departure/arrival fix operations (see Attachment D and Attachment E) shall be in effect when ZTL coordinates with ZME (for BHM) or CHA coordinates with ZME (for CHA).
c. ZTL and ZME must release control for 15 degree turns on aircraft 15NM on either side of the ZTL/ZME boundary.
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. 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 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. 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
6.1. CHANNEL ISLANDS TMA AD DEP ALT/FL DCT XFER Notes EGJJ ORIST - - EGJJ_CTR → EGTT_CTR These departures are never handled by Brest Control BENIX FL190 - EGJJ_CTR → LFRR_CTR - AD ARR ALT/FL DCT XFER Notes EGJJ BIGNO - - EGTT_CTR → EGJJ_CTR These arrivals are never handled by Brest Control BEVAV FL200 - LFRR_CTR → EGJJ_CTR DCT to IAF may be coordinated on a case-by-case basis
6.2. LONDON AREA EGLL ROXOG FL300 - LFRR_CTR → EGTT_CTR Standard routing via REVTU (FL340) > BOLRO FL300 EGKK VASUX FL300 - LFRR_CTR → EGTT_CTR Standard routing via REVTU (FL330) > ODREP FL300 EGLC XXXXX FL220 - LFRR_CTR → EGTT_CTR Levelled by XXXXX EGGW TELTU FL340 - LFRR_CTR → EGTT_CTR Standard routing via DIKRO (FL380) > LUGIS/KOTEM FL340 EGSS AVANT FL340 - LFRR_CTR → EGTT_CTR Standard routing via DIKRO (FL380) > LUGIS/KOTEM FL340 6.3. DEAUVILLE FIC LFRK XXXXX FL080 - LFRR_CTR → EGTT_CTR - LFRK XXXXX FL090 - EGTT_CTR → LFRR_CTR
COORDINATION PROCEDURES. DEP & ARR Coordination procedures between the ACC positions of Shanwick & Xxxxxxx 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 a. Deviations from procedures outlined in this agreement may be made only after completion of coordination, which defines responsibility in each case.
b. An automated radar handoff constitutes approval for aircraft climbing/descending to the altitude in the data block. Controllers are still responsible for pointouts if the aircraft will climb/descend through another controller’s stratum.
c. Inappropriate Altitude For Direction Of Flight (IAFDOF) must be coordinated, except for aircraft departing the Pensacola Terminal Area assigned an interim altitude of FL230.
d. Transponder codes may be changed without coordination on initial contact.
e. Aircraft routed via a STAR shall not be cleared past the transition of the arrival.
f. Anytime ZHU or ZJX is split, all controllers must be notified how the center is being split.
COORDINATION PROCEDURES. Coordination procedures between the ATC of Barcelona ACC and Xxxxx 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. LECB controllers will coordinate with DAAA_W_CTR / DAAA_C_CTR when available, otherwise with DAAA_CTR. Both DAAA and LECB controllers should know that a traffic will enter its airspace at least 5 NM before, by radar contact and/or coordination with the counterpart.
4.1. FROM BARCELONA TO XXXXX (LECB → DAAA)
(1) Traffic with destination Oran (DAOO) should be granted a descent by LECB_W_CTR, in coordination with DAAA.
4.2. FROM ALGER TO BARCELONA (DAAA → LECB)
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. 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 XXXXX AoR Boundary EGTT_CTR Even Level
