LETTER of AGREEMENT
IVAO ATC HQ / Maastricht UAC
IVAO DE Division / Langen ACC
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.
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.
The lateral and vertical limits of the respective areas of responsibility are as follows:
| Lateral limits: | Hannover (EDVV) UIR as specified in the AIP Germany |
| Vertical limits: | FL 245 - FL 660 |
| Lateral limits: | Langen (EDGG) FIR as specified in the AIP Germany |
| Vertical Limits: | GND - FL 245 |
Not Applicable
Within the Hannover UIR the provision of ATS in accordance with the airspace classification is performed by Langen ACC within the following areas(s):
| Lateral Limits: | N0503021 E0064855 - N0503614 E0065227 - N0503623 E0070744 - N0503500 E0070000 - N0503021 E0064855 |
| Vertical Limits | FL 245 - FL 255 |
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 Langen ACC and Maastricht UAC are described in Annex B to this Letter of Agreement.
The ATS unit responsible for the provision of ATS, by virtue of delegation, shall provide alerting service and shall notify immediately the supervisor of the delegating ATS unit. The supervisor of the delegating ATS unit shall notify the appropriate rescue coordination centre as required.
Not applicable.
Not applicable.
An airspace of defined dimensions where a sole ATC unit has responsibility for providing air traffic services.
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.
Request from an ATS-unit to the ATS sector concerned for an 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.
The flight level dividing two superimposed AoR for the provision of ATS.
All flights which are conducted in accordance with the rules and procedures of ICAO and/or the national civil aviation regulations and legislation.
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.
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.
Aircraft that have received State approval for RVSM operations within the EUR RVSM airspace.
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.
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.
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.
For the purposes of EUR RVSM, only aircraft used in military, customs or police services shall qualify as State aircraft.
| 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* | On-Line 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 Minima | ||
| CBA | Cross-Border Area | ||
| CDR | Conditional Route | SFC | Surface |
| COP* | Coordination Point | SID | Standard Instrument Departure |
| CRC | Control and Reporting Centre | SSR | Secondary Survaillance Radar |
| CTA | Control Area | STAR | Standard Terminal Arrival Route |
| CTR | Control / Enroute ATS Unit | ||
| CTZ | Control Zone | TMA | Terminal Manouvering Area |
| TRA | Temporary Reserved Area | ||
| DFL* | Divisional 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 Information Region |
| FLA* | Flight Level Allocation | UNL | Unlimited |
| FIS | Flight Information Services | UTC | Universal Time Coordinated |
| 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 | WEF | With Effect From |
| IFR | Instrument Flight Rules | ||
| KHz | Kilohertz | ||
| LoA* | Letter of Agreement | ||
| MHz | Megahertz |
| Area | Vertical Limits | Airspace Classification |
| Langen FIR | GND - FL 245 | Above FL100: C Below FL 100: G, E, D, C |
| Area | Vertical Limits | Airspace Classification |
| Amsterdam FIR | FL 245 - FL 660 | C |
| Brussels UIR | FL 245 - FL 660 | C |
| Hannover UIR | FL 245 - FL 660 | C |
Not applicable.
Not applicable.
Basic flight plan data should normally be available to both ATS units.
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.
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.
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.
Use the Aurora intercom for this.
Start every communication with the internal callsign designated for your sector group.
| Sectorgroup | Internal Callsign |
| Brussels | Maastricht Brussels |
| DeCo | Maastricht Deco |
| Hannover | Maastricht Hannover |
| CTR | Maastricht |
When required, communication can be performed by private text between the relevant sectors.
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.
| Destination | Routing | COP | Receiving Sector | FLA | Special Conditions | Release conditions |
| EDDF, EDFE, EDFZ, ETOU | SPI-T180, DIK-T856 | NIVNU | PFA | FL250/FL260 | NIVNU see D.2.1.1.1 | Released for descent and right turns |
| PITES-Z111 | PITES | FL250 | PITES at FL260 | Released for right turns | ||
| ETAR, EDFM, EDFV, EDRY | SPI-T180 | TOBOP | FL250/FL260 | TOBOP see D.2.1.1.1 |
Released for descent and right turns when passing TOBOP Langen ACC shall stay on T180/T847 or north of it |
|
| EDDL | DIK-ARCKY-T853 | IBESA | NOR | FL250/FL260 | Hohes-Veen-line see D.2.1.1.2 and D.2.1.1.3 | Released when passing Hohes-Venn-Line |
| KOMOB-T859 | LENDO | |||||
| SPI-Y862 | PODEN | |||||
| EDLV | DIK-ARCKY-T853 | IBESA | Hohes-Veen-line see D.2.1.1.2 | |||
| KOMOB-T859 | LENDO | |||||
| EDVK | DIK-T856 | DEPOK | FL270 | |||
| EDLW, EDDG, EDLP, EDLA, EDWO, EDLS | DIK-T856 | DEPOK | ||||
| KOMOB-T859 | LENDO | FL250/FL260 | Hohes-Veen-line see D.2.1.1.2 and D.2.1.1.4 | |||
| SPI-Y862 | PODEN |
On handover from Maastricht UAC to Langen ACC, when feasible, the following aircraft types are preferred at a higher flight level than all other aircraft: A380, B747, MD11, DC10, A124, A225, L101, C5, C17 and KC35, including all subtypes. This is due to landing restrictions on the northern runway at EDDF and Langen ACC having to deliver two different flight level streams to EDDF Approach. MUAC shall endeavour to transfer flights with destination ETAR at FL250. If possible, these flights will be:
Transfer of communications for flights to NOR-sector via T856 (DEST EDVK, EDLW; EDDG, EDLP, EDLA, EDWO, EDLS) shall be effected latest at/abeam NIVNU. Transfer of communications for all other flights to NOR-sector shall be effected latest at Hohes-Venn-Line.
NOR-sector shall descend traffic into AoR of Langen ACC before entering Ruhr sector.
Traffic to EDLV may be transferred DCT HEFOP if traffic crosses Hohes-Venn-Line south of PODEN.
Traffic with routing via NVO may be transferred DCT NVO if traffic crosses Hohes-Venn-Line south of PODEN.
The routing DEPOK AFNAF DCT BIKMU is available as tactical re-routing to EDDL when required by Maastricht UAC. Maastricht UAC shall inform the NOR sector about the aircraft that will use this tactical re-routing.
The routing T856 is available as tactical re-routing to EDLW, EDDG, EDLP, EDLA, EDWO, EDLS and EDVK by Maastricht UAC in case of bunching. Maastricht UAC will inform the NOR sector about the aircraft that will use this tactical re-routing.
| Destination | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EBBR, EBAW, EBCI, EBCV, EBLG, EBMB, ELLX | ROBER/ LARBU/ TOLGI/ PIROT/ BASUM/ RORUS/ POVEL/ ENUGA/TOLTA - DCT | ABAMI | DLD | FL250 | ABAMI see D.2.1.2.1 |
| EDDF, EDFE, EDFH, EDFZ | DIXAT-T149 | LIPMI | TAU | FL260 | LIPMI see D.2.1.2.2 |
Arrivals to airports in the Brussels FIR via ABAMI shall be handed over from Maastricht UAC to Langen ACC descending to FL250. If this cannot be established, Maastricht UAC will coordinate subject aircraft at or descending to different flight levels.
The following procedure shall be applied:
Arrivals to EDDF, EDFE, EDFH and EDFZ via LIPMI shall be handed over from Maastricht UAC to Langen ACC descending to FL260 under the following conditions:
Maastricht UAC ensures that subject aircraft cross LIPMI at FL250, Transfer of communications not later than LIPMI. Traffic is released for descent.
| Destination | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EHTE, EHBD, EHBK, EHLE | BIGGE-T281, KATCE-DCT | HMM | HMM | FL250 | See D.2.1.3.1 |
| EHEH | BIGGE-DCT DOMEG, KATCE-DCT DOMEG | DOMEG | FL260 | See D.2.1.3.2 |
Traffic shall be handed over to Langen ACC descending to FL250 to be at level 20NM prior HMM. Langen assures that subject flights cross HMM at FL240 or below. Traffic is released for descent.
Traffic shall be handed over to Langen ACC descending to FL250 to be at level 20NM prior DOMEG. Langen assures that subject flights cross DOMEG at FL240 or below. Traffic is released for descent.
| Destination | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EDDK | LARBU-Z189, POVEL-Q201, TOLTA-DCT | PODER | HMM | FL250 | PODER see D.2.1.4.1 |
| EDDF, EDFE, ETOU, EDFZ | DCT | RIMET | GED | FL250 | RIMET see D.2.1.4.2 |
Traffic destination EDDK shall be handed over to Langen ACC descending to FL250 to reach that level not later than PODER. Traffic is released for descent. Langen ACC assures that Solling / Muenster sector boundary will be crossed at FL240 or below.
Arrivals to EDDF, EDFE, ETOU and EDFZ shall be handed over by Maastricht UAC to Langen ACC descending to FL250 to be level at RIMET. Transfer of communication shall have taken place not later than Bremen/Langen FIR boundary.
| Destination | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EDDL, EDLV, EDLN, EDLE, EHBK, EHBD, EHEH | PIROT-T851 | DENOL | HMM | FL250 | DENOL see D.2.1.5.1 |
| EHEH | PIROT-DENOL-DOMEG | DENOL see D.2.1.5.2 |
Traffic shall be handed over to Langen ACC descending to FL250 to reach that level not later than DENOL. Traffic is released for descent.
Langen ACC assures that the Celle / Muenster sector boundary will be crossed at FL240 or below.
Traffic shall be handed over to Langen ACC descending to FL250 to reach that level not later than DENOL. Traffic is released for descent.
Langen ACC assures that the Celle / Muenster sector boundary will be crossed at FL240 or below.
D.2.2.1 Silent transfer:
In general, Langen ACC shall coordinate a transfer level with the receiving sector of Maastricht UAC, for flights with FLA 245.
For flights with FLA 241 Langen ACC may coordinate a transfer level with the receiving MUAC sector if necessary. If not required, Langen ACC shall transfer these flights climbing to FL240 to the receiving MUAC sector without further verbal coordination.
In such a case
| Departure | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EDLW, EDLA, EDWO, EDVK | Y841-KENUM | NVO | Olno | FL 245 | |
| EBBU FIR | N853-ONUNE | ELDAR | Ruhr | FL 245 | See D.2.2.2.1 |
| EDDF, EDFE, ETOU, EDFZ | Z29-TORNU | ROCUH | Ruhr | FL260 | See D.2.2.2.1 |
| EDDF, EDFE, ETOU, EDFZ | Z28-DIBIR | OLPEX | Ruhr | FL260 | See D.2.2.2.1 and D.2.2.2.2 |
| ETAR, ETAD, ETSB | Q760-MILGI, DCT TINIK | INLAR | Ruhr | FL245 | See D.2.2.2.3 |
Langen NOR sector is responsible to separate departures EDDF, EDFE, ETOU and EDFZ planned via Z28 / Z29 and:
NOR sector may clear respective departures within the confines of the Ruhr sector direct to TORNU and DIBIR. During JOJO activity, Ruhr sector shall inform the NOR sector to cancel the direct to TORNU.
If NOR sector is unable to ensure EDDF, EDFE, ETOU, EDFZ departures at or abeam NEREL FL260, the clearance into MUAC AoR is cancelled. NOR sector shall coordinate with Ruhr sector to obtain a new clearance into upper airspace.
| Departure | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EHEH, EHBK | L179-MEVEL, DCT HALME | LUSIX | Ruhr | FL 241 | See D.2.2.3.1 |
| EHAM | Z739-MISGO | AMOSU | Ruhr | FL 250 | |
| EDLP, EDDG, EDLS, EDLI | N853-QATJA-Y841-KENUM | ONUNE | Ruhr | FL 245 | See D.2.2.3.2 |
| ETNG | GAT | LUSIX | Ruhr | FL245 | See D.2.2.3.3 |
Departures may be cleared by Langen ACC - without further coordination - direct to OSDIK, HMM and GMH.
Maastricht UAC shall issue the clearance into the upper airspace to Langen ACC BOTP to enable climb into the upper airspace before entering sector NOR.
| Departure | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EHAM | L620-HMM, Z718-OSN | SUVOX | Münster | FL 250 | |
| EDDL, EDLN, EDLV | L179-MISRI, Y850-ARTER | MEVEL | Münster | FL 241 | See D.2.2.4.1 |
| EDLP, EDGS, EDFQ | HMM-L602-RKN | HMM | Münster | FL 245 |
In case, flights via ARTER – BASUM or direct BASUM are not available, Maastricht Supervisor shall inform Langen Supervisor North accordingly. Subject flights have to be re-routed by Langen ACC via OSN-BASUM.
Departures may be cleared by Langen ACC - without further coordination - direct to OSDIK and EXOBA.
| Departure | Routing | COP | Receiving Sector | FLA | Special Conditions |
| EDLS, EDLV | Z841-GMH | TUVTI | Ruhr | FL 245 | See D.2.2.5.1 |
| EDDF, EDFE, EDFZ, ETOU, EDDS | Z850-ABILU | BADGO | Münster | FL 245 | |
| EDDK | PELUN DCT ANZIV DCT WRB | ANZIV | Solling | FL 245 | See D.2.2.5.2 |
Subject flights shall be able to cross GMH at FL260 or above. Whenever a clearance to a flight level above FL250 is issued by Maastricht UAC, the standard condition to cross GMH at FL260 or above shall apply.
Traffic is approved to cross the Muenster sector unless otherwise specified by the Solling sector.
Whenever a requested release, a direct routing or a change of transfer conditions affects additional sectors/units the partners shall agree on who is responsible for the further coordination.
Not applicable.
The Transfer of Control takes place at the AoR boundary.
The transfer of communications shall take place not later than the transfer of control unless coordinated otherwise.
| Sector | Logon Code | VHF | Callsign |
| Ruhr | EDYY_HRM_CTR EDYY_HAN_CTR EDYY_CTR EDGG_W_CTR EDGG_CTR |
133.215 MHz 122.185 MHz 135.960 MHz 135.650 MHz 136.955 MHz |
Maastricht Radar Maastricht Radar Maastricht Radar Langen Radar Langen Radar |
| Münster | 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 |
| Solling | 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 |
| Sector | Logon Code | VHF | Callsign | Other combinations |
| HMM | EDGG_HMM_CTR EDGG_HD_CTR EDGG_CTR |
129.300 MHz 119.110 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_HMM_CTR can also be combined with EDGG_NDH_CTR (125.225 MHz), EDGG_N_CTR (135.650 MHz), EDGG_WH_CTR (128.505 MHz) and EDGG_NW_CTR (133.425 MHz) |
| DLD | EDGG_DLD_CTR EDGG_HD_CTR EDGG_CTR |
121.355 MHz 119.110 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_DLD_CTR can also be combined with EDGG_DN_CTR (125.680 MHz), EDGG_NDH_CTR (125.225 MHz), EDGG_N_CTR (135.650 MHz), EDGG_WH_CTR (128.505 MHz) and EDGG_NW_CTR (133.425 MHz) |
| NOR | EDGG_NOR_CTR EDGG_DN_CTR EDGG_CTR |
127.365 MHz 125.680 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_NOR_CTR can also be combined with EDGG_NDH_CTR (125.225 MHz), EDGG_WH_CTR (128.505 MHz) and EDGG_NW_CTR (133.425 MHz) |
| PFA | EDGG_PFA_CTR EDGG_W_CTR EDGG_CTR |
129.675 MHz 124.900 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_PFA_CTR can also be combined with EDGG_WH_CTR (128.505 MHz), EDGG_NW_CTR (133.425 MHz), EDGG_SP_CTR (131.300 MHz) and EDGG_SPE_CTR (132.155 MHz) |
| TAU | EDGG_TAU_CTR EDGG_E_CTR EDGG_CTR |
127.625 MHz 127.725 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_TAU_CTR can also be combined with EDGG_N_CTR (135.650 MHz), EDGG_NW_CTR (133.425 MHz), EDGG_SE_CTR (127.050 MHz) and EDGG_SPE_CTR (132.155 MHz) |
| GED | EDGG_GED_CTR EDGG_E_CTR EDGG_CTR |
124.430 MHz 127.725 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_GED_CTR can also be combined with EDGG_N_CTR (135.650 MHz), EDGG_NW_CTR (133.425 MHz), EDGG_SE_CTR (127.050 MHz) and EDGG_SPE_CTR (132.155 MHz) |
| NKR | EDGG_NKR_CTR EDGG_S_CTR EDGG_CTR |
129.355 MHz 123.280 MHz 136.955 MHz |
Langen Radar Langen Radar Langen Radar |
EDGG_NKR_CTR can also be combined with EDGG_SP_CTR (131.300 MHz), EDGG_SE_CTR (127.050 MHz) and EDGG_SPE_CTR (132.155 MHz) |
Not applicable.
The Radar Separation Minima is 5 NM.
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.
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. Procedure to follow is separation is less than that?
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.
The accepting controller may terminate the silent transfer of control at any time, normally with advance notice of 10 minutes.
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: