LETTER of AGREEMENT
IVAO ATC HQ / Maastricht UAC
IVAO NL Division / Amsterdam ACC
¶ 1 General
¶ 1.1 Purpose
This Letter of Agreement defines the coordination procedures to be applied between Maastricht UAC and London ACC when providing ATS to General Air Traffic and Operational Air Traffic. These procedures are supplementary to those specified in IVAO Documentation and/or Divisional website Documents.
¶ 1.2 Operational Status
Both Divisions shall keep each other advised of any changes in the operational status of their facilities and navigational aids, which may affect the procedures specified in this Letter of Agreement.
¶ 2 Areas of Responsibility for the Provision of ATS
¶ 2.1 Areas of Responsibility
The lateral and vertical limits of the respective areas of responsibility are as follows
¶ 2.1.1 Maastricht UAC
| Lateral limits: | Amsterdam (EHAA) UTA as specified in the AIP The Netherlands. Brussels (EBUR) UIR as specified in the AIP Belgium. Hannover (EDVV) UIR as specified in the AIP Germany. |
| Vertical limits: | FL245 - FL660 |
¶ 2.1.2 Amsterdam ACC
| Lateral limits: | Amsterdam (EHAA) FIR as specified in the AIP The Netherlands |
| Vertical limits: | GND - FL245 |
¶ 2.2 Areas for Cross-Border Provision of ATS (ATS Delegation)
The provision of ATS in respect of this LoA means the following services:
- Air Traffic Control Service (ATC)
- Flight Information Service (FIS) for controlled flights
- Alerting Service (ALRS)
¶ 2.2.1 Delegation of ATS from Maastricht UAC to Amsterdam ACC
Not applicable.
¶ 2.2.2 Delegation of ATS from Amsterdam ACC to Maastricht UAC
Not applicable.
¶ 2.2.3 Other Area's for Cross-Border Provision of ATS
Areas for Cross-Border Provision of ATS defined with other coordinating air traffic services units along the common boundary of the areas of responsibility of Maastricht UAC and Amsterdam ACC are described in Annex B to this Letter of Agreement.
¶ 2.2.4 Alerting Service
The ATS unit responsible for the provision of ATS, by delegation, shall provide alerting service and shall immediately notify the supervisor of the delegating ATS unit. The supervisor of the delegating ATS unit shall notify the appropriate rescue coordination centre as required.
¶ 2.2.5 Territorial Matters
Not applicable.
¶ 2.3 Special Provisions
Not applicable.
¶ Annex A - Definitions and Abbreviations
¶ A.1 Definitions
Area of Responsibility - An airspace of defined dimensions where a sole ATS unit has responsibility for providing Air Traffic Services (ATS).
Area of Common Interest - A volume of airspace as agreed between two ATS units, extending into the adjacent/subjacent Areas of Responsibility, within which airspace structure and related activities may have an impact on air traffic coordination procedures.
Approval Request - Request from an ATS unit to the ATS sector concerned for approval of:
- an aircraft not yet airborne, whenever the flying time to the transfer of control point is less than the agreed minimum prenotification time, or
- an aircraft in flight intending to operate under conditions other than those described in mutually agreed procedures.
Division Level - The flight level dividing two superimposed AoR for the provision of ATS.
General Air Traffic - All flights which are conducted in accordance with the rules and procedures of ICAO and/or the national civil aviation regulations and legislation.
Operational Air Traffic - All flights which do not comply with the provisions stated for GAT and for which rules and procedures have been specified by appropriate national authorities.
Reduced Vertical Separation Minima - A vertical separation minimum of 300 m (1 000 ft) which is applied between FL 290 and FL 410 inclusive, on the basis of regional air navigation agreements and in accordance with conditions specified therein.
RVSM Approved Aircraft - Aircraft that have received State approval for RVSM operations within the EUR RVSM airspace.
State Aircraft - For the purposes of EUR RVSM, only aircraft used in military, customs or police services shall qualify as State aircraft.
Release for Climb - An authorization for the accepting sector to climb (a) specific aircraft before the transfer of control.
Note: The transferring sector remains responsible within its Area of Responsibility for separation between the transferred aircraft and other aircraft unknown to the accepting unit unless otherwise agreed.
Release for descent - An authorization for the accepting sector to descend (a) specific aircraft before the transfer of control.
Note: The transferring sector remains responsible within its Area of Responsibility for separation between the transferred aircraft and other aircraft unknown to the accepting unit unless otherwise agreed.
Release for Turn - An authorization for the accepting sector to turn (a) specific aircraft away from the current flight path by not more than 45 o before the transfer of control
Note: The transferring sector remains responsible within its Area of Responsibility for separation between the transferred aircraft and other aircraft unknown to the accepting unit unless otherwise agreed.
¶ A.2 Abbreviations
| ACC | Area Control Center | NM | Nautical Mile |
| ACI* | Area of Common Interest | NM | EUROCONTROL Network Management |
| AIP | Aeronautical Information Publication | ||
| AoR* | Area of Responsibility | OAT* | Operational Air Traffic |
| APP | Approach Area / Approach ATS Unit | OLDI* | Online Data Interchange |
| ATC | Air Traffic Control | ORCAM | Originating Region Code Assignment Method |
| ATS | Air Traffic Services | ||
| ATZ | Air Traffic Zone | RTF | Radio Telephony |
| RVSM | Reduced Vertical Separation Minimum | ||
| CBA | Cross-Border Area | ||
| CDR | Conditional Route | SFC | Surface |
| COP* | Coordination Point | SID | Standard Instrument Departure |
| CRC | Control and Reporting Centre | SSR | Secondary Surveillance Radar |
| CTA | Control Area | STAR | Standard Instrument Arrival |
| CTR | Control / Enroute ATS Unit | ||
| CTZ | Control Zone | TMA | Terminal Maneuvering Area |
| TRA | Temporary Reserved Area | ||
| DFL* | Division Flight Level | TSA | Temporary Segregated Area |
| TWR | Aerodrome Control Tower | ||
| ETO | Estimated Time Over Significant Point | ||
| EUR | European | UAC | Upper Area Control Centre |
| UHF | Ultra High Frequency | ||
| FIR | Flight Information Region | UIR | Upper Flight Information Region |
| FLA* | Flight Level Allocation | UNL | Unlimited |
| FIS | Flight Information Services | UTC | Coordinated Universal Time |
| FL | Flight Level | ||
| VCS | Voice Communication System | ||
| GAT* | General Air Traffic | VFR | Visual Flight Rules |
| GND | Ground | VHF | Very High Frequency |
| ICAO | International Civil Aviation Organization | ||
| IFR | Instrument Flight Rules | ||
| KHz | Kilohertz | ||
| LoA* | Letter of Agreement | ||
| MHz | Megahertz |
Note: Abbreviations marked with an * are non-ICAO abbreviations.
¶ Annex B - Area of Common Interest
¶ B.1 Airspace Structure and Classification within the Area of Common Interest
The Airspace Structure within the ACI is shown in the Appendix of Annex B.
¶ B.1.1 Amsterdam UTA
¶ B.1.1.1 ATS by Maastricht UAC
| Area | Vertical Limits | Airspace Classification |
| UTA | FL245 - FL660 | C |
¶ B.1.1.2 ATS by Amsterdam ACC
| Area | Vertical Limits | Airspace Classification |
| UTA | FL195 - FL245 | C |
¶ B.1.2 Langen FIR
| Area | Vertical Limits | Airspace Classification |
| FIR | FL100 - FL245 | C |
Note: ATS by Langen ACC
¶ B.1.3 Bremen FIR
| Area | Vertical Limits | Airspace Classification |
| FIR | FL100 - FL245 | C |
Note: ATS by Bremen ACC
¶ B.1.4 Hannover UIR
| Area | Vertical Limits | Airspace Classification |
| UIR | FL245 - FL660 | C |
Note: ATS by Maastricht UAC
¶ B.2 Sectorization within the Area of Common Interest
The Sectorization within the ACI is shown in Appendix 1 of Annex B.
¶ B.3 Special Areas within the Area of Common Interest
¶ B.3.1 Areas for Cross-Border Provision of ATS defined by other ATS units within the ACI
¶ B.3.1.1 ATS Provision by Amsterdam ACC
The provision of ATS in accordance with the Airspace Classification is performed by Amsterdam ACC within the following areas:
¶ B.3.1.1.1 Emmen Area
| Lateral limits: | The part of the Nieuw Milligen TMA C linking the coordinates: N530000 E0071234 – along the Dutch-German border to N521414 E0070347 – N521757 E0064350 – N522534 E0062000 – N524550 E0062000 – N525457 E0062951 – N530000 E0071234 |
| Vertical limits: | FL095 - FL245 |
| Airspace Classification: | FL095 - FL195: B FL195 - FL245: C |
¶ B.3.1.1.2 Twenthe HI Area
| Lateral limits: | The part of the Bremen FIR west of the line linking the coordinates: N523925 E0070330 – N522350 E0070340 |
| Vertical limits: | FL095 - FL245 |
| Airspace Classification: | FL095 - FL100: E FL100 - FL245: C |
¶ B.3.1.1.3 TEBRO Area - See Appendix 2 of Annex B
| Lateral limits: | The part of the Langen FIR linking the coordinates: N521414 E0070347 – N521450 E0071559 – N515809 E0070629 – N515144 E0065808 – N514111 E0064055 – N513604 E0062955 – N513511 E0062137 – N513510 E0060801 – along the Dutch-German border to N521414 E0070347 |
| Vertical limits: | FL205 - FL245 |
| Airspace Classification: | C |
¶ B.3.1.1.4 KLEVE HI Area
| Lateral limits: | The part of the Langen FIR linking the coordinates: N514200 E0060142 – N514941 E0062727 – along the Dutch-German border to N514200 E0060142 |
| Vertical limits: | FL145 - FL205 |
| Airspace Classification: | C |
¶ B.3.1.1.5 MOLIX Area - See Appendix 2 of Annex B
| Lateral limits: | The part of the London FIR linking the coordinates: N532000 E0023000 – N531441 E0031102 – N531029 E0032158 – N523704 E0025356 – N524010 E0023000 – N532000 E0023000 |
| Vertical limits: | FL175 - FL245 |
| Airspace Classification: | FL175 - FL195: A FL195 - FL245: C |
¶ B.3.1.1.5 GODOS Area - See Appendix 2 of Annex B
| Lateral limits: | The part of the London FIR linking the coordinates: N534148 E0030000 – N533411 E0034222 – N531029 E0032158 – N531441 E0031102 – N531608 E0030000 – N534148 E0030000 |
| Vertical limits: | FL175 - FL245 |
| Airspace Classification: | FL175 - FL195: A FL195 - FL245: C |
¶ B.3.1.2 ATS Provision by Brussels ACC
The provision of ATS in accordance with the Airspace Classification is performed by Amsterdam ACC within the following areas:
¶ B.3.1.2.1 SASKI A Area - See Appendix 2 of Annex B
| Lateral limits: | The part of the Amsterdam FIR south of a parallel line 5 NM north of the ATS route L179/L608 and east of SASKI |
| Vertical limits: | FL055 - FL245 |
| Airspace Classification: | FL055 - FL195: A FL195 - FL245: C |
¶ B.3.1.3 ATS Provision by London ACC
The provision of ATS in accordance with the Airspace Classification is performed by London ACC within the following areas:
¶ B.3.1.3.1 SASKI B Area
| Lateral limits: | The part of the Amsterdam FIR linking the coordinates: N514245 E0021001 – N513000 E0020000 – N512720 E0023000 – N513813 E0023000 – N514245 E0021001 – N514245 E0021001 |
| Vertical limits: | FL215 - FL660 |
| Airspace Classification: | C |
¶ B.3.1.3.2 IBNOS A Area
| Lateral limits: | The part of the Amsterdam FIR linking the coordinates: N515702 E0022123 – N515757 E0031019 – N512850 E0031019 – N514245 E0021001 – N515702 E0022123 |
| Vertical limits: | FL245 - FL660 |
| Airspace Classification: | C |
¶ B.3.1.3.3 IBNOS B Area
| Lateral limits: | The part of the Amsterdam FIR linking the coordinates: N515710 E0022129 – N515827 E0024001 – N520027 E0031019 – N512850 E0031019 – N514245 E0021001 – N515710 E0022129 |
| Vertical limits: | FL215 - FL245 |
| Airspace Classification: | C |
¶ B.3.2 Other Areas
¶ B.3.2.1 SPY/PAM Area
| Lateral limits: | The lateral limits of the SPY/PAM Area correspond with the lateral boundaries of the Schiphol TMA 1 and Schiphol TMA 6. |
| Vertical limits: | 1500 ft / 3500 ft AMSL - FL660 |
| Airspace Classification: | 1500 ft / 3500 ft AMSL - FL195: A FL195 - FL660: C |
¶ B.3.2.2 EBTRA North B
| Lateral limits: | The airspace linking the coordinates: N511032 E0042037 – N512049 E0042812 – N512254 E0043326 – N512649 E0044320 – N512650 E0044925 – along the Belgian-Dutch border to N512651 E0050018 – N512651 E0050400 – N512603 E0050610 – N511857 E0052158 – N511654 E0052630 – along the Belgian-Dutch border to N510133 E0054629 – N505729 E0052350 – N505342 E0050316 – N505830 E0043650 – N511032 E0042037 |
| Vertical limits: | Within the Amsterdam FIR: FL095 - FL660 Within the Brussels UIR: FL195 - UNL |
| Airspace Classification within the Amsterdam FIR: |
FL095 - FL195: B FL195 - FL660: C |
| Airspace Classification within the Brussels FIR: | FL195 - FL660: C |
¶ B.4 Non-Published Coordination Points within the Area of Common Interest
Not applicable.
¶ Appendix 1 of Annex B
¶ Appendix 2 of Annex B
¶ Appendix 3 of Annex B
Not applicable.
¶ Annex C - Exchange of Flight Data
¶ C.1 General
¶ C.1.1 Basic Flight Plans
Basic flight plan data should normally be available to both ATS units.
¶ C.1.2 Current Flight Plan Data
Messages, including current flight plan data, shall be forwarded by the transferring ATS unit to the accepting ATS unit either by automatic data exchange to by private text to the appropriate position.
¶ C.1.2.1 Automatic Data Exchange
Automatic data exchange is done via the label. Enter cleared flight level. If applicable, enter the speed restriction and waypoint the traffic is flying direct to as well.
¶ C.1.3 Revisions
Any significant revisions to the flight data are to be transmitted to the accepting ATS Unit.
Changes to the coordinated levels within 5 minutes of the ETO for the Transfer of Control point are subject to an Approval Request.
¶ C.2 Means of Communication and their use
¶ C.2.1 Verbal Coordination
Use the Aurora intercom for this.
Start every communication with the internal callsign designated for your sector group.
¶ C.2.1.2 Internal Maastricht Callsigns
| Sectorgroup | Internal Callsign |
| Brussels | Maastricht Brussels |
| DeCo | Maastricht Deco |
| Hannover | Maastricht Hannover |
| CTR | Maastricht |
¶ C.2.2 Written Coordination
When required, communication can be performed by private text between the relevant sectors.
¶ Annex D - Procedures for Coordination
¶ D.1 General Conditions for Acceptance of Flights
- Coordination of flights shall take place by reference to the COP for the relevant route and in accordance with the appropriate flight levels specified for the relevant route (see para D.2 and D.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 written coordination, except if otherwise described in paragraphs D.2 or D.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 (e.g. COP, route or level) the transferring Unit shall initiate an Approval Request.
- 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 Unit shall notify the transferring Unit in the event that communication with the aircraft is not established as expected.
¶ D.2 ATS Routes, Coordination Points and Flight Level Allocation
Available routes, COPs to be used and flight level allocation to be applied, unless otherwise described in paragraph D.3, are described in the tables below.
¶ D.2.1 Flights from Maastricht UAC to Amsterdam ACC
Flights with a destination in the Amsterdam FIR shall be at FL260 not later than the Transfer of Coordination point as indicated in paragraph E.2.3.
¶ D.2.1.1 Flights from Maastricht UAC JEVER Sector to Amsterdam ACC Sector 1
| Route | COP | FL Allocation | Special Conditions |
| N125 / N872 / P174 / FRA DCT | EEL | FL260 | See D.2.1.1.1 |
¶ D.2.1.1.1 Transfer Conditions
These flights are released for descend and turns, subject to known traffic, after passing the Amsterdam FIR boundary.
¶ D.2.1.2 Flights from Maastricht UAC DELTA Sector to Amsterdam ACC
| Route | COP | FL Allocation | Special Conditions |
| BASNO DCT ALFEN | ALFEN | FL260 | See D.2.1.2.1 and D.2.1.2.2 |
| L620 / N872 / P62 / FRA DCT | PAM | ||
| N873 / P154 / Y12 / FRA DCT | SPY | ||
| FRA DCT | SUSET |
¶ D.2.1.2.1 Transfer Conditions
These flights are released for descend subject to known traffic. Amsterdam ACC shall ensure these flights meet the following level restrictions:
| Destination | Below FL245 |
| Amsterdam FIR, EDWE, EDWF, EDWI or EDWY | At SPY/PAM area exit |
| EDDL, EDDG, EDDK, EDFQ, EDGS, EDKB, EDLA, EDLE, EDLI, EDLM, EDLN, EDLP, EDLS, EDLV, EDLW, ETAD, ETNG or ETNN | Prior to RUHR/DELTA sector boundary |
| EHBK, Brussels FIR (except ELLX) or LFAC, LFAQ, LFAT, LFAV, LFQQ, LFQO or LFQT | Prior to 20 NM north of NIK |
| Inbounds Amsterdam FIR via LAMSO which are transferred from London AC to Amsterdam ACC | Prior to LAMSO |
| Inbounds Amsterdam FIR via TOPPA which are transferred from Scottish AC to Amsterdam ACC | Prior to 10 NM north of AMGOD |
¶ D.2.1.2.2 Separation of flights entering via ALFEN or SUSET
Maastricht UAC shall ensure that the combined flow of traffic entering via ALFEN and SUSET is separated.
¶ D.2.1.3 Flights from Maastricht UAC Hannover sectorgroup to Amsterdam ACC
| Route | COP | FL Allocation | Special Conditions |
| T281 / FRA DCT | NORKU | FL260 | See D.2.1.3.1 |
| L602 / L604 / L980 / FRA DCT | RKN | See D.2.1.3.1 |
Note: Inbounds EHAM shall route via NORKU. Other flights with destination in the Amsterdam FIR shall route via RKN.
¶ D.2.1.3.1 Transfer Conditions
- These flights are released for descend and turns, subject to known traffic, after passing 2.5 NM west of the lateral limits of the TEBRO area.
- Flights with destination EHAM via NORKU shall cross NORKU at or below FL280 descending to FL260. These flights are released for speed control, turns and descent, subject to known traffic, after passing 2.5 NM west of the lateral limits of the TEBRO area.
- Amsterdam ACC shall ensure that flights with a destination in the Amsterdam FIR are below FL245 prior to the Munster/Delta sector boundary or south abeam NARSO, whichever comes last.
¶ D.2.2 Flights from Amsterdam ACC to Maastricht UAC
In case Amsterdam ACC requires a higher level than the level allocation specified in the tables below, Amsterdam ACC shall coordinate with the accepting Maastricht UAC sector.
¶ D.2.2.1 Flights from Amsterdam ACC Sector 3 to Maastricht UAC Brussels sectorgroup
| Route | COP | FL Allocation | Special Conditions |
| N872 | WOODY | FL260 | See D.2.2.1.1 |
| N852 | BROGY | FL250 | See D.2.2.1.2 |
¶ D.2.2.1.1 Flights via N872
Flights departing from aerodromes within the Amsterdam FIR via N872 (WOODY) with a requested level above FL 245, shall meet the following level restrictions:
- HSD radial 090 at FL 250 or below;
- 10 NM DME north of NIK at or above FL 260.
These flights may cross the FIR boundary below FL 245 and enter Brussels ACC AoR without prior coordination provided that they are 10 NM DME NIK at or above FL 260.
In case a flight is unable to meet the level restrictions for N872, Amsterdam ACC shall coordinate the flight with Brussels ACC. Amsterdam ACC shall inform the NICKY controller that the flight will be transferred to Brussels ACC. This flight shall be transferred to Maastricht UAC at or climbing to FL 240 by Brussels ACC.
For N872 the following procedures apply south of HSD radial 090:
- Maastricht UAC Delta sector shall coordinate flights entering the lateral limits of Amsterdam ACC Sector 3 southbound at FL 260 with Amsterdam ACC Sector 3.
- Maastricht UAC Koksy sector shall coordinate northbound flights at FL 260 with Amsterdam ACC Sector 3.
¶ D.2.2.1.2 Flights via N852
Flights departing from aerodromes within the Amsterdam FIR via N852 (BROGY) with a requested level above FL 245, shall meet the following level restriction:
- VELED at or above FL 250.
In case a flight is unable to meet the level restriction for N852, Amsterdam ACC shall coordinate the flight with Brussels ACC. Amsterdam ACC shall inform Olno Controller that the flight will be transferred to Brussels ACC. This flight shall be transferred to Maastricht UAC at or climbing to FL 240 by Brussels ACC.
¶ D.2.2.2 Flights from Amsterdam ACC Sector 1 and 5 to Maastricht UAC JEVER Sector
| Route | COP | FL Allocation | Special Conditions |
| N873 | BEDUM | FL250 | See D.2.2.2.1 |
| M105 | EEL | ||
| Z708 | AGISU | ||
| Z733 | KONOM | ||
| M90 | ODASI | - |
¶ D.2.2.2.1 Flights departing from EHRD
Flights departing from EHRD with routing via ANDIK, which are expected to cross FL 245 before exiting the SPY/PAM area, shall only be cleared by Amsterdam ACC to FL 250 after verbal or written approval by Maastricht UAC Delta sector.
¶ D.2.2.3 Flights from Amsterdam ACC to Maastricht DELTA Sector
| Route | COP | FL Allocation | Special Conditions |
| L604 / P64 | TENLI | FL250 | See D.2.2.3.1 |
| N873 | DOFMU | See D.2.2.3.2 | |
| L620 | TULIP | - | |
| SIDs EHEH and SIDs EHBD via HAMZA | HAMZA | - | |
| N125 / N873 and SIDs EHGG via SPY | SPY | - | |
| L980 / N872 | PAM | See D.2.1.3.3 |
¶ D.2.2.3.1 Flights departing from aerodromes within the Langen FIR via RKN or SONEB
Amsterdam ACC will clear flights departing from aerodromes within the Langen FIR intending to enter the Maastricht UAC Delta sector via RKN, SONEB, or on a direct route, to FL 250 after passing the agreed common ATC boundary.
¶ D.2.2.3.2 Flights departing from aerodromes within the Brussels FIR
Flights departing from aerodromes within the Brussels FIR intending to enter the Maastricht UAC DELTA Sector will be cleared by Amsterdam ACC to FL 250 after passing the KOKSY/DELTA or NICKY/DELTA Sector boundary.
¶ D.2.2.3.3 Flights Departing from EHGG
Flights departing from EHGG routing via PAM shall only be cleared by Amsterdam ACC to FL 250 after verbal approval by Maastricht UAC Delta sector.
¶ D.2.2.4 Flights from Amsterdam Sector 2 to Maastricht UAC Hannover sectorgroup
| Route | COP | FL Allocation | Special Conditions |
| L620 | SONEB | FL250 | See D.2.2.4.1 |
| Z739 | NAPRO | See D.2.2.4.2 |
¶ D.2.2.4.1 Flights via L620
Flights departing from aerodromes within the Amsterdam FIR via L620 (SONEB) with a requested level above FL 245, shall meet the following level restrictions:
- SONEB at or above FL 210
- OLDOD at or above FL 250
In case a flight is unable to meet the level restrictions for L620, Amsterdam ACC shall coordinate the flight with Langen ACC. After coordination with Langen ACC, Amsterdam ACC shall only inform the relevant Maastricht UAC sector if the traffic shall be transferred to Langen ACC.
¶ D.2.2.4.2 Flights via Z739
Flights departing from aerodromes within the Amsterdam FIR via Z739 (NAPRO) with a requested level above FL 245, shall meet the following level restrictions:
- DEPAD at or above FL 210
- AMOSU at or above FL 250
In case a flight is unable to meet the level restrictions for Z739, Amsterdam ACC shall coordinate the flight with Langen ACC. After coordination with Langen ACC, Amsterdam ACC shall only inform the relevant Maastricht UAC sector if the traffic shall be transferred to Langen ACC.
After NAPRO FL 250 is not available as a cruising level for flights intending to proceed on T150/Z739.
¶ D.2.2.5 Use of FL250
Within the Amsterdam FIR, FL 250 shall be used exclusively as an intermediate level for the flights mentioned in paragraph D.2.2. In this respect, FL 250 shall be vacated as soon as possible. If FL 250 cannot be vacated, Maastricht UAC shall inform the relevant Amsterdam ACC sector.
¶ D.2.2.6 SPY/PAM Area
If flights, climbing to FL 250 and passing through the SPY/PAM area, reach FL 250 prior to entering the SPY/PAM area, then Maastricht UAC is responsible for separating these flights after transfer of communications. If FL 250 is not reached before entering the SPY/PAM area, Amsterdam ACC is responsible for separating these flights before transferring them to Maastricht UAC.
¶ D.3 Special Procedures
¶ D.3.1 Sequencing of Traffic
To avoid an undue accumulation of traffic, the transferring ATS Unit shall establish longitudinal radar separation between successive departing or arriving traffic, before transfer is effected.
If unable, traffic shall be handed over on parallel headings, using speed control techniques to establish appropriate longitudinal spacing.
Maastricht UAC also may use FL 270 and FL 280 for flights with a destination in the Amsterdam FIR entering via EEL, NORKU or RKN, and for flights with a destination in the Brussels FIR entering via ALFEN and SUSET. These flights are released for speed control, turns and descent.
¶ D.3.2 Flights descending to FL250
Within the lateral boundaries of the Amsterdam ACC Area of Responsibility and the Areas of Cross-border Provision of Amsterdam ACC excluding the MOLIX and GODOS areas, Maastricht UAC shall co-ordinate flights descending to FL 250 with the relevant Amsterdam ACC sector. Amsterdam ACC is responsible for separating these co-ordinated flights from flights under responsibility of Amsterdam ACC that will cross FL 245.
¶ Annex E - Transfer of Control and Transfer of Communications
¶ E.1 Transfer of Control
Transfer of control shall take place at the AoR boundary unless otherwise specified in paragraph E.3.
¶ E.2 Transfer of Communication
Transfer of communication shall take place not later than the transfer of control unless otherwise coordinated.
Transfer of CPDLC shall commence concurrently with transfer of voice communications.
¶ E.2.1 Frequency allocations and sector arrangement of Maastricht UAC
| Sector | Logon Code | VHF | Callsign |
| MBKN | EDYY_BKN_CTR EDYY_BRU_CTR EDYY_CTR EBBU_W_CTR EBBU_CTR |
132.755 MHz 132.855 MHz 135.960 MHz 131.100 MHz 131.100 MHz |
Maastricht Radar Maastricht Radar Maastricht Radar Brussels Control Brussels Control |
| MBOL | EDYY_BOL_CTR EDYY_BRU_CTR EDYY_CTR EBBU_E_CTR EBBU_CTR |
125.980 MHz 132.855 MHz 135.960 MHz 128.200 MHz 131.100 MHz |
Maastricht Radar Maastricht Radar Maastricht Radar Brussels Control Brussels Control |
| MDD | EDYY_DD_CTR EDYY_DEC_CTR EDYY_CTR EHAA_SW_CTR EHAA_CTR |
132.085 MHz 135.510 MHz 135.960 MHz 123.850 MHz 125.750 MHZ |
Maastricht Radar Maastricht Radar Maastricht Radar Amsterdam Radar Amsterdam Radar |
|
MDJH (EHAA) |
EDYY_DJH_CTR EDYY_DEC_CTR EDYY_CTR EHAA_NE_CTR EHAA_CTR |
129.785 MHz 135.510 MHz 135.960 MHz 124.880 MHz 125.750 MHZ |
Maastricht Radar Maastricht Radar Maastricht Radar Amsterdam Radar Amsterdam Radar |
|
MDJH (EDVV) |
EDYY_DJH_CTR EDYY_DEC_CTR EDYY_CTR EDWW_W_CTR EDWW_CTR |
129.785 MHz 135.510 MHz 135.960 MHz 123.925 MHz 125.025 MHZ |
Maastricht Radar Maastricht Radar Maastricht Radar Bremen Radar Bremen Radar |
| MHCS | EDYY_HCS_CTR EDYY_HAN_CTR EDYY_CTR EDWW_W_CTR EDWW_CTR |
131.380 MHz 122.185 MHz 135.960 MHz 123.925 MHz 125.025 MHZ |
Maastricht Radar Maastricht Radar Maastricht Radar Bremen Radar Bremen Radar |
|
MHRM (Muenster Sector) |
EDYY_HRM_CTR EDYY_HAN_CTR EDYY_CTR EDWW_W_CTR EDWW_CTR |
133.215 MHz 122.185 MHz 135.960 MHz 123.925 MHz 125.025 MHZ |
Maastricht Radar Maastricht Radar Maastricht Radar Bremen Radar Bremen Radar |
|
MHRM (Ruhr Sector) |
EDYY_HRM_CTR EDYY_HAN_CTR EDYY_CTR EDGG_W_CTR EDGG_CTR |
133.215 MHz 122.185 MHz 135.960 MHz 124.900 MHz 136.955 MHz |
Maastricht Radar Maastricht Radar Maastricht Radar Bremen Radar Bremen Radar |
¶ E.2.2 Frequency allocation and sector arrangement of Amsterdam ACC
| Sector | Logon Code | VHF | Callsign |
| EHAA Sector 1 | EHAA_1_CTR EHAA_NE_CTR EHAA_CTR |
134.375 MHz 124.880 MHz 125.750 MHz |
Amsterdam Radar Amsterdam Radar Amsterdam Radar |
| EHAA Sector 2 | EHAA_2_CTR EHAA_NE_CTR EHAA_CTR |
128.580 MHz 124.880 MHz 125.750 MHz |
Amsterdam Radar Amsterdam Radar Amsterdam Radar |
| EHAA Sector 3 | EHAA_3_CTR EHAA_SW_CTR EHAA_CTR |
130.955 MHz 123.850 MHz 125.750 MHz |
Amsterdam Radar Amsterdam Radar Amsterdam Radar |
| EHAA Sector 4 | EHAA_4_CTR EHAA_SW_CTR EHAA_CTR |
136.650 MHz 123.850 MHz 125.750 MHz |
Amsterdam Radar Amsterdam Radar Amsterdam Radar |
| EHAA Sector 5 | EHAA_5_CTR EHAA_SW_CTR EHAA_CTR |
119.175 MHz 123.850 MHz 125.750 MHz |
Amsterdam Radar Amsterdam Radar Amsterdam Radar |
| EHMC Upper Sector (MIL) |
EHMC_U_CTR EHMC_CTR EHAA_SW_CTR / EHAA_NE_CTR EHAA_CTR |
120.830 MHz 128.355 MHz 123.850 MHz / 124.880 MHz 125.750 MHz |
Dutch MIL Dutch MIL Amsterdam Radar Amsterdam Radar |
¶ E.2.3 Frequency Allocation and sector arrangement of neighbouring ACCs
| Sector | Logon Code | VHF | Callsign |
| EBBU East | EBBU_E_CTR EBBU_CTR |
128.200 MHz 131.100 MHz |
Brussels Control Brussels Control |
| EBBU West | EBBU_W_CTR EBBU_CTR |
131.100 MHz 131.100 MHz |
Brussels Control Brussels Control |
| SAC-U1 | EGPX_U1_CTR EGPX_CTR |
129.225 MHz 124.500 MHz |
Scottish Control Scottish Control |
| EKDK N | EKDK_N_CTR EKDK_CTR |
134.680 MHz 133.155 MHz |
Copenhagen Control Copenhagen Control |
| LAC-N | EGTT_N_CTR EGTT_CTR |
128.130 MHz 132.605 MHz |
London Control London Control |
| LAC-S | EGTT_S_CTR EGTT_CTR |
135.055 MHz 132.605 MHz |
London Control London Control |
¶ E.3 Specific Points for Transfer of Control and Transfer of Communications
¶ E.3.1 Transfer of Communications from maastricht UAC JEVER Sector to Amsterdam ACC
| Route | Entering via | Transfer of Communications |
| N125 / N872 / P174 / FRA DCT | EEL | At or before 15 NM prior to EEL |
¶ E.3.2 Transfer of Communications from Maastricht DELTA Sector to Amsterdam ACC
| Route | Entering via | Transfer of Communications |
| L620 / N872 / P62 / FRA DCT | PAM | At or before 8 NM south-east of PAM |
| Inbounds Brussels FIR (except ELLX), LFQQ, LFAQ and nearby airports via FRA DCT SUSET | SUSET | At or before SUSET |
| EHBK, Inbounds Brussels FIR (except ELLX), LFQQ, LFAQ and nearby airports via FRA DCT ALFEN | ALFEN | At or before ALFEN |
| Amsterdam FIR (except EHBK) | SPY/PAM | At or before entering the SPY/PAM area |
¶ E.3.3 Transfer of Communications from Maastricht UAC Hannover sectors to Amsterdam ACC
| Route | Entering via | Transfer of Communications |
| T281 / FRA DCT | NORKU | At or before NORKU |
| L602 / L604 / L980 / FRA DCT | RKN | At or before 15 NM prior to RKN |
¶ Annex F - ATS Surveillance-Based Coordination Procedures
¶ F.1 Separation Minima
¶ F.1.1 Radar Separation Minima
The Radar Separation Minima is 5 NM.
¶ F.1.2 Vectoring minimum distance
A minimum distance of 2.5 NM to the boundary line of responsibility shall be observed when vectoring aircraft, except when a transfer of radar control has previously been coordinated.
¶ F.2 Types of Transfer of Control
¶ F.2.1 Transfer of Control without systematic use of direct communication (Silent Transfer of Control)
Transfer of control may be effected without systematic use of bi-directional speech facilities provided the minimum distance between successive aircraft about to be transferred is 10 NM and constant or increasing.
The transferring controller shall inform the accepting controller of any level, speed or vectoring instructions given to aircraft prior to its transfer and which modify its anticipated flight progress at the point of transfer.
Note: When using Mach-number speed control, pilots concerned shall be instructed to report their assigned Mach-number to the accepting ATS Unit upon initial contact.
¶ F.2.2 Termination of Silent Transfer of Control
The accepting controller may terminate the silent transfer of control at any time, normally with advance notice of 10 minutes.
¶ F.2.3 Transfer of Control with use of direct communication
Transfer of control may be effected with the use of bi-directional speech facilities, provided the
minimum distance between the aircraft does not reduce to less than 5 NM, and:
- identification has been transferred to or has been established directly by the accepting controller;
- the accepting controller is informed of any level, speed or vectoring instructions applicable to the aircraft at the point of transfer;
- communication with the aircraft is retained by the transferring controller until the accepting controller has agreed to assume responsibility for providing ATS surveillance service to the aircraft. Thereafter, the aircraft should be instructed to change over to the appropriate frequency and from that point is the responsibility of the accepting controller.