Letter of Agreement: Spain

Speed Restrictions

250Kias (350 on request) below FL100


All shared airbases (civil and militar traffic) are open to be under control giving priority to GAT over OAT except during events. LERT TWR (Navy base) just for OAT on request 15 days before.


All facilities (military or shared) could be opened as shown in the event document. FRAs as shown : FRA Link (note XXXX_CTR C1 between 00.00 and 16.00 local time and C2 between 16.00 and 00.00 local time)

Civilian facilities open to all users, Spanish or non-Spanish if GCA granted. Military facilities restricted and only available to Spanish OAT certified controllers or trainees and ONLY IF GAT controller is active ( in example: LECM_M_CTR will be activated if LECM_CTR is available)

OAT-GAT Coordination



  1. Check if there are local procedures for OAT aircraft departures ( IFR-VFR corridors).
  2. Coordinate SID, initial climb or any kind of departure
  3. If no IFR-VFR corridors are defined, make an agreement and define it for both OIFR and OVFR flights. To do this, consider that GAT has to have priority over OAT, and should be easily performed ( radial-distance-height from VOR, VFR point…) The procedures should not interfere the normal operations of the airfield.
  4. OAT traffic should assume delays if needed to give priority to GAT.
  5. Traffic will be handed off when airborne.
  6. If GAT APP facility is not available coordination will be set with GAT ACC.


  1. The same shown above plus:
  2. Hand off when OAT traffic is airborne if possible. If due traffic conditions makes impossible this, APP will keep assumed until cleared of traffic, finish SID or leave his airspace, whatever happens earlier.


  1. OAT controller will inform GAT controller about D, R or TSA active in his sector, with all the necessary data (FL, time of activation etc).
  2. OAT controller will avoid his traffics proceed along airways and will inform CAG controller how is going to provide separation with GAT traffics and when OAT traffics leave GAT sector.
  3. OAT controller will be in charge of provide the necessary separation between OAT and GAT traffics, if possible providing vertical separation. He will consider:
    1. If unable to inform CAG procedures to provide separation, if vertical separation is ensured, should provide in addition lateral separation of 15 nm. If vertical separation is not ensured, should provide 25nm of lateral separation.
    2. Will provide the following separation in RVSM airspace:
      • 2000ft between traffics with RVSM appr. And traffics without RVSM appr.
      • 2000ft between GAT and formation flights.
      • 2000ft between OAT and formation flights.
      • 2000ft between formations. (An escort is to be considered as a formation)
  4. ACC controller will ensure by vectoring or level changes a minimum separation of 2000ft with upper and lower D,R or TSA limits or 10 nm with its lateral limits.



5 minutes before reaching IAF, OAT controller will ask the requested app type by traffic. If CAG controller doesn´t know how to handle a typical OAT app procedure (TACAN APP, HIGH TACAN APP) will inform crew to expect a GAT APP type (VOR, NDB, ILS…).

  1. OAT controller will hand off traffics when entering APP airspace.
  2. If traffic is a formation, OAT controller will ask if GAT accepts formations, if not, will transfer each wingman with the necessary separation.
  3. If no GAT APP facility is available, traffics will be transferred to GAT ACC controller.