Letter of Agreement IVAO Division France Name: LOAFRLFBBLFRR_EN Date: July the 29 th 2016 Version: v2 Validity: permanent Contributors: FRAOC, FRAOAC LFBBCH, LFBBACH, LFRRCH, LFRRACH Contact: fraoc@ivao.aero ; fraoac@ivao.aero Object: LoA between the Bordeaux FIR (LFBB) and the Brest FIR (LFRR) 1. Purpose The purpose of this Letter of Agreement (LoA) is to define the ATC units and the coordination procedures to be applied between the Bordeaux FIR and the Brest FIR when providing Air Traffic Services (ATS) operating under IFR or VFR flight rule. The content of the agreement is approved by the concerned FIR Chiefs, the FRTD and the FR HQ and its application is mandatory for all IVAO member providing ATS within and active ATC position concerned by this LoA. 2. General procedures Traffic in sequence shall be handed over with minimum spacing of 10 NM. This separation must be constant (aircrafts restrained to the same speed) or increasing (succeeding aircraft is not faster). Coordination of speed control should be granted via entries in radar labels and does neither need approval nor acknowledgement by receiving sector. Traffic shall be handed over as soon as practical and, whenever possible, at latest 3000 ft before reaching the cleared flight level. Traffic in sequence shall be handed over properly separated and clear of any conflict. Unless the receiving ATC unit issue a clearance modifying the route, altitude or speed, the transferring sector remains responsible for separation.
3. ATC units description The ATC unit in charge of FIR and UIR airspaces under the responsibility of Bordeaux ACC is Bordeaux Control and consists in only one primary sector (LFBB_CTR). This ATC unit may be split into two subsectors (LFBB_W_CTR and LFBB_E_CTR) under the condition that both positions are open and FIR Chiefs are informed. The lateral and vertical boundaries of the airspace under the responsibility of the ACC are indicated in the figure and table below. The ATC unit in charge of FIR and UIR airspaces under the responsibility of Brest ACC is Brest Control and consists in only one primary sector (LFRR_CTR). This ATC unit may be split into two subsectors (LFRR_N_CTR and LFRR_S_CTR) under the condition that both positions are open and FIR Chiefs are informed. The lateral and vertical boundaries of the airspace under the responsibility of the CTR are indicated in the figure and table below.
One should note that an airspace delegation exists between the Paris FIR and the Brest FIR, which corresponds to the pink zone in the figure below and is defined within the LoA between the two FIR. In particular, whenever Paris Control and Brest Control are active, this airspace sector is delegated to Brest Control from FL295 up to UNL 1. This delegation is also valid, within the same vertical boundaries, whenever Brest Control is active while Paris Control is not. Whenever Brest Control is inactive, this airspace sector is not anymore delegated and is controlled by Paris Control from SFC up to UNL. 1 Whenever the Brest CCR is split into LFRR_N_CTR and LFRR_S_CTR the delegated airspace is controlled by LFRR_N_CTR. However, the two ATC may coordinate a partial responsibility of the South ACC as a function of the traffic fluxes.
The radio communication frequencies associated to the ACC positions are indicated below. ATC Position Callsign Frequency Remarks Primary Sector Bordeaux Control LFBB_CTR 125.100 SFCUNL ; SFCFL245 if LFBB_U_CTR is active Secondary Sectors Bordeaux Control (East) LFBB_E_CTR 125.100 SFCUNL ; SFCFL245 if LFBB_U_CTR is active Bordeaux Control (West) LFBB_W_CTR 129.100 SFCUNL ; SFCFL245 if LFBB_U_CTR is active Bordeaux Control (Upper) LFBB_U_CTR 127.675 FL245UNL Primary Sector Brest Control LFRR_CTR 119.825 SFCUNL Secondary Sectors Brest Control (North) LFRR_N_CTR 119.825 SFCUNL Brest South Control (South) LFRR_S_CTR 129.500 SFCUNL 4. Airspace delegations The SIV 2.3 Nantes and the portion of SIV 3.2 Nantes inside the Bordeaux FIR are controlled by Nantes Approach between FL115 and FL145 and by Brest Control below FL145 (see the pink triangle in the figures of section 3). The airspace underneath (SIV 1 La Rochelle) is controlled by La Rochelle Approach between the surface and FL115. Whenever Brest Control is not active, this airspace is controlled by Bordeaux Control below FL145. In the absence of La Rochelle Approach, the SIV 2.3 Nantes is delegated to Nantes Approach from the surface to FL145, excepting the ATS corresponding to La Rochelle Tower. Therefore, whenever La Rochelle Tower is active and La Rochelle Approach is not, La Rochelle departures via are transferred directly to Nantes Approach when leaving the CTR airspace. Similarly, La Rochelle arrivals from LUGEN and are transferred directly to La Rochelle Tower when established on the final runway axis. It is recalled that Brest and Bordeaux ACC inherit all inactive approach positions underneath. Therefore, whenever Bordeaux Control is active, La Rochelle departures via are transferred by Bordeaux Control to Nantes Approach cleared to FL60. Similarly, La Rochelle arrivals from LUGEN and are transferred from Nantes Approach to Bordeaux Control cleared DCT FL to FL60.
5. Coordination procedures Coordination procedures between the ATC under the responsibility of the Bordeaux 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. 5.1 Enroute coordination Coordination procedures between Bordeaux ACC and Brest ACC are defined as follows. One should note that the airspace delegation between the Paris ACC and Brest ACC induces specific transfer criteria indicates in the table below. Route Transfer point Cleared DCT Restrictions LFBB_CTR LFRR_CTR A25 OLERO G54 R66 FIR boundary LUGEN UM184 UN861 TUPAR TUPAR UY120 UN863 UT183 MANAK MANAK UY110 UN460 LEBRI UN470 DILRA UQ203 ETRAT UQ226 ANG Limite FIR UZ34 DESAB UN858 DEVRO UT158 AMB Transfer to LFFF_CTR if FL<295 UT182 KEPER LFRR_CTR LFBB_CTR A25 OLERO OLERO G54 R66 FIR boundary POI UM616 LUGEN TUPAR UN862 LAGOR SAU UP860 LEMKA BEBIX UN460 UN470 CNA UQ203 MAKOX/PUMAL FIR boundary UN858 BOKNO UN859 BALAN Only if FL>295 UZ34 SOMOS
5.2 Coordination of departures and arrivals Coordination procedures for the departure/arrival traffic management are defined as follows: Bordeaux towards Brest FIS SID/STAR Coordination procedures Remarks Departures (LFBB LFRR) LFBD CNA LFBD_APP LFBB_CTR (DCT ROYAN/CNA FL140) ROYAN LFBB_CTR LFRR_CTR (on climb FL320 max) LFBH LFBH_APP LFRS_APP (DCT FL60) LFRS_APP LFRR_CTR (FL140) Whenever La Rochelle is not active, Nantes takes responsibility from the CTR exit up to FL140. Whenever neither Brest nor Nantes are active, Bordeaux takes responsibility until the FIR exit LFBI ABSIE LFBI_APP LFRR_CTR (DCT LUGEN FL140) LFBL BALAN LFBL_APP LFBB_CTR (DCT BALAN FL140) LFBB_CTR LFRR_CTR (on climb FL200 max) Arrivals (LFBB LFRR) LFRN LFRS BALNI MANAK LUGEN LFBB_CTR LFRR_CTR (on descent FL340 max) LFRR_CTR LFRN_APP (DCT RISUD FL120) LFBB_CTR LFRR_CTR (on descent FL220 max) LFRR_CTR LFRS_APP (DCT LAROK FL150) Whenever Brest is not active, Bordeaux transfers to Nantes DCT LAROK FL150 Brest towards Bordeaux FIS SID/STAR Coordination procedures Remarks Departures (LFRR LFBB) LFRN LAGAB LFRN_APP LFRR_CTR (DCT GODAN FL110) LFRR_CTR LFBB_CTR (on climb FL330 max) LFRS LFBD LUGEN CNA ROYAN LFRS_APP LFRR_CTR (DCT LUGEN/ FL140) LFRR_CTR LFBB_CTR (on climb FL250 max) Arrivals (LFRR LFBB) LFRR_CTR LFBB_CTR (on descent FL330 max) LFBB_CTR LFBD_APP (DCT ETPAR/VAGNA FL150) Whenever Brest is not active, Nantes transfers to Bordeaux DCT LUGEN/ FL140
LFBH LUGEN LFRR_CTR LFRS_APP (on descent FL150 max) LFRS_APP LFBH_APP (DCT RL FL60) Whenever La Rochelle is not active, Nantes takes responsibility until the CTR entry LFBI ABSIE LFRR_CTR LFBI_APP (DCT PI FL150) LFBL BALAN LFRR_CTR LFBB_CTR (on descent FL210 max) LFBB_CTR LFBL_APP (DCT LOE FL150)