LFBB - Bordeaux <> LECB - Barcelona

Lettre d’Accord (LoA)

 

---

 

Barcelona ACC (LECB) and Bordeaux ACC (LFBB)

Nom: LoA-LECB-LFBB_FR

Date: 20 juin 2025

Version : v7.0

Validité : Permanente

INDEX

1. PRÉAMBULE 2

2. PROCÉDURES GÉNÉRALES 2

Annex A : Area of Common Interest 3

A.1. Airspace Structure and Classification within the Area of Common Interest 3

A.2. Sectorisation within the Area of Common Interest 4

Annex B : Procedures for coordination 5

B.1. General Conditions for Acceptance of Flights 5

B.2. ATS-Routes, DCTs, Coordination Points and Level Allocation 6

Annex C : Transfer of Control and Transfer of Communications 10

C.1. Transfer of Control 10

C.2. Transfer of Communications 10

C.3. Specific Points for Transfer of Control and Transfer of Communications 10

6. CONTRIBUTIONS 11

7. CHANGELOG 11

 

1. PRÉAMBULE

Cette lettre d’accord (LoA) a pour but de définir les procédures de coordination à appliquer entre le CCR de Barcelona et le CCR de Bordeaux dans le cadre de la fourniture des services de la navigation aérienne aux trafics opérant sous régime de vol IFR ou VFR.

Le contenu de cet accord a été approuvé par le Département des Opérations ATC et les Chefs de FIR concernés. Son application est obligatoire pour tous les membres d’IVAO fournissant des services de la navigation aérienne depuis une position active concernée par cette LoA.

2. PROCÉDURES GÉNÉRALES

Les trafics en séquence au même niveau de vol doivent être transférés avec une séparation minimale de 10 NM. 

Cette séparation doit être constante (trafics restreints à la même vitesse) ou croissante (trafic suiveur plus lent que le trafic meneur).

La coordination des autorisations de vitesse doit s’effectuer par la mise à jour des étiquettes et ne nécessite ni l’approbation, ni l’accusé de réception du secteur qui reçoit le transfert.

Les trafics doivent être transférés au plus tôt et, dans la mesure du possible, 3000 ft avant d’atteindre le niveau de vol autorisé. Dans le cas où aucun point de transfert n’est défini dans cette LoA, les trafics doivent être transférés au plus tard 10 NM avant la limite de la zone de responsabilité. 

Les trafics en séquence doivent être transférés séparés des autres trafics et libres de tout conflit. L’unité ATC qui reçoit un trafic ne peut pas modifier la route, l’altitude ou la vitesse (sauf coordination préalable) de celui-ci jusqu’au moment où il entre dans sa zone de responsabilité. L’unité ATC qui transfère un trafic reste responsable de la séparation de celui-ci jusqu’à ce qu’il sorte de sa zone de responsabilité.

Les procédures applicables par LECB et LFBB sont décrites dans les Annexes à cette Lettre d’Accord : 

Annexe A : Zone d’Intérêt Commun

Annexe B : Procédures de Coordination

Annexe C : Transfert de Contrôle et Transfert de Communication

Annex A : Area of Common Interest

A.1. Airspace Structure and Classification within the Area of Common Interest

A.1.1. LECB FIR/UIR

A.1.2. LFBB FIR/UIR

 

A.2. Sectorisation within the Area of Common Interest

LECB-LFBB FIR sectorisation (GND-FL195)

LECB-LFBB UIR sectorisation (FL195-UNL)

Annex B : Procedures for coordination

B.1. General Conditions for Acceptance of Flights

Coordinations of flights shall normally take place by reference to the coordination point (COP) and in accordance with the appropriate levels specified for the relevant route (see paragraphs B.2 and B.3)

Flights shall be considered to be maintaining the coordinated level at the transfer of control point unless climb or descent conditions have been clearly stated by use of verbal coordination or text message, except if otherwise described in paragraphs B.2 or B.3.

If the accepting ATS Unit cannot accept a flight offered in accordance with the conditions specified above, it shall clearly indicate its inability and specify the conditions under which the flight will be accepted.

For any proposed deviation from the conditions specified in this Annex (COP, route or level) the transferring ATS Unit shall initiate an approval request to the accepting ATS Unit.

The accepting ATS Unit shall not notify the transferring ATS Unit that it has established ground-air communications with the transferred aircraft unless specifically requested to do so. The accepting ATS Unit shall notify the transferring ATS Unit in the event that communication with the aircraft is not established as expected.

 

B.2. ATS-Routes, DCTs, Coordination Points and Level Allocation

Available routing via LFBB UIR is described in RAD ANNEX 2B (Local and Cross-Border Capacity and Structural Rules), RAD ANNEX 3A (Aerodrome Connectivity Options) and RAD ANNEX 3B (En-Route DCT Options).

Available routing via LECB FIR/UIR is described in SPANISH AIP ENR 3.1-3.3, RAD ANNEX 2B (Local and Cross-Border Capacity and Structural Rules) and RAD ANNEX 3B (En-Route DCT Options). HISPAFRA CELL 1 is defined FL245 up to FL660 (H24) in UIR Barcelona airspace.

Available FRA, DCTs, ATS-Routes and COPs to be used and flight level allocation to be applied are described in the tables below.

B.2.1. Flights from LECB to LFBB

B.2.1.1. Discrepancy in airspace structure

ANETO, OLOXO, RUTIP, NATPI and GEANT : there is no ATS-Route in LFBB FIR (i.e. below FL195)

B.2.1.2. MAMUK-OLOXO, SINDO-RUTIP, MOPAS/BARBO-GIROM, or SIDs OLOXO/NATPI for LEBL departures or SID NATPI for LERS departures

B.2.1.2.1 Two flights or more on 2 different COP : GIROM and NATPI, NATPI and RUTIP or NATPI and OLOXO

Two flights can be sent without coordination at same flight level providing : 

• Favourable weather conditions (absence of thunderstorms, turbulence)

• The minimum lateral separation is 10Nm, constant or increasing

Otherwise, GIROM and NATPI, NATPI and RUTIP, NATPI and OLOXO will be considered as a single COP.

B.2.1.2.2 Via RUTIP/OLOXO : traffic must be sent on LFBB frequency over at the latest : 

• LEBL departure : over OLOXO

• LERS departure : over RUTIP

• Overflights : over OLOXO

 

B.2.2. Flights from LFBB to LECB

B.2.2.1. Discrepancy in airspace structure : 

PERDU : there is no ATS-Route in LECB FIR (below FL215)

ANETO, IBRAP, GEANT : there is no ATS-Route in LFBB FIR (below FL195)

ALBER, KANIG : levels below FL195 are in LFMM FIR

B.2.2.2. PERDU-POSSY and ANETO-TURUV-LOBAR are not available for traffic destination LEBL, LERS, LELL, LEGE and Baleares_Group

B.2.2.3. Tracks exiting LFBB via PERDU and ANETO are considered as a single axis

B.2.2.4. LFBO/BP/BT/BF/BR/MK departure : if the flight can’t reach FL310 at the boundary, the possible reached odd level is coordinated to the receiving ATS Unit

B.2.2.5. Via PUMAL traffic destination LEPA only allowed below FL255, traffic with destination LEMH only allowed below FL295

B.2.2.6. LEBL, LELL, LEDA, LESU arrivals

Crossing the boundary at FL250 or below : 

• PUMAL : The simultaneous arrivals to LEBL will be transferred descending FL230, 10 between them with no coordination (8Nm with coordination)

• ALBER : The simultaneous arrivals to LEBL/LELL/LEDA/LESU will be transferred descending FL210, 10Nm between them with no coordination (8Nm with coordination)

• Maximum speed 300kts

B.2.2.7. KANIG

ATS-Route and DCT not available for traffic destination LEPA

B.3. Special Procedures

VFR Flights : 

Both centres will inform each other of the VFR flights crossing the border.

FL145 and FL195 are not available except at pilot request for meteorological conditions.
VFR flights are strictly prohibited above FL195

Annex C : Transfer of Control and Transfer of Communications

C.1. Transfer of Control

The transfer of control takes place at the AoR-Boundary, unless otherwise specified in paragraph C.3.

C.2. Transfer of Communications

The transfer of communications shall take place not later than the transfer of control and as specified in paragraph C.3, unless otherwise coordinated.

When Controller-Pilot Data Link Communications (CPDLC) is used in both ATS Units, the transfer of CPDLC shall commence concurrently with the transfer of voice communications.

Frequencies : 

From LFBB to LECB : 

From LECB to LFBB : 

C.3. Specific Points for Transfer of Control and Transfer of Communications

See B.2.1 and B.2.2

3. CONTRIBUTIONS

Ce document a été élaboré en coordination avec les Départements des Opérations ATC de la Division Espagne et France ainsi que les staffs des FIR de Barcelona et de Bordeaux.

4. CHANGELOG