¶ LETTER of AGREEMENT
¶ IVAO ATC HQ IVAO GERMANY
MAASTRICHT UAC KARLSRUHE UAC
¶ 1. GENERAL
¶ 1.1 Purpose
The purpose of this Letter of Agreement is to define the coordination procedures to be applied between Maastricht UAC and Karlsruhe UAC 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.
PDF version of this LOA available at:
https://drive.google.com/file/d/14zQ8xHIa7Yn-XtLa_VqmDe7OhFyp1yMH/view?usp=sharing
¶ 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
In Maastricht UAC there are 3 Sectorgroups, comprised of several sectors, all of them with Vertical Limits from FL 245 – UNL.
¶ 2.1.1 Maastricht UAC
| Maastricht UAC | |
|---|---|
| Lateral limits: | Hannover MaastrichtUIR as published in the AIP Germany and Brussels UIR as published in the AIP Belgium |
| Vertical limits: | FL 245 – FL 660 |
ICAO airspace classification for the area of responsibility of Maastricht UAC along the common boundary of the areas of responsibility of Maastricht UAC and Karlsruhe UAC is described in Annex B to this Letter of Agreement.
¶ 2.1.2 Karlsruhe UAC
| Karlsruhe UAC | |
|---|---|
| Lateral limits: | Rhein Karlsruhe UIR as published in the AIP Germany |
| Vertical limits: | West and Central Sectors: FL 245 – FL 660 East Sectors except SAL: FL 285 – FL 660 SAL: FL 315 – FL 660 |
ICAO airspace classification for the area of responsibility of Karlsruhe UAC along the common boundary of the areas of responsibility of Maastricht UAC and Karlsruhe UAC is described in Annex B to this Letter of Agreement.
¶ 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 Karlsruhe UAC
Within the Hannover Maastricht UIR the provision of ATS to GAT and OAT in accordance with the airspace classification is performed by Karlsruhe UAC within the following area(s):
(See appendices 1 & 2)
| ARPEG Area (Class C) | |
|---|---|
| Lateral limits: | N0510631 E0083512 - N0511612 E0082440 N0510216 E0073315 - N0504508 E0073856 N0510631 E0083512 |
| Vertical limits: | FL 245 – FL 295 |
| ABGUS Area (Class C) | |
|---|---|
| Lateral limits: | N513400 E0104200 – N514530 E0110845 N514816 E0110825 – N514316 E0105905 N513400 E0104200 |
| Vertical limits: | FL 315 – FL 660 to Karlsruhe UAC (ABGUS HIGH Area) FL 245 – FL 315 to München ACC (ABGUS LOW Area) |
¶ 2.2.2 Delegation of ATS from Karlsruhe UAC to Maastricht UAC
Within the Rhein Karlsruhe UIR the provision of ATS to GAT and OAT in accordance with the airspace classification is performed by Maastricht UAC within the following area(s):
(See appendix 2)
| BITBU Area (Class C) | |
|---|---|
| Lateral limits: | N494833 E0063010 – N495604 E0063632 N501628 E0063903 – N502541 E0063751 Then along the Hannover/Rhein UIR boundary till N502000 E0062430 Then along the boundary line of the Brussels / Rhein UIR to N494833 E0063010 |
| Vertical limits: | FL 245 – UNL |
| KOSIT Area (Class C) | |
|---|---|
| Lateral limits: | N493805 E0062541 – N491649 E0064012 N491305 E0064240 – then along the boundary line of the Rhein/Reims UIR, then along the boundary line of the Rhein/Brussels UIR to – N493805 E0062541 |
| Vertical limits: | FL 245 – FL 660 |
| WARBURG Area (Class C) | |
|---|---|
| Lateral limits: | N511147 E0082929 – N510500 E0083651 – N510508 E0085435 – N510508 E0091443 N510508 E0092600 – N510549 E0092622 –N511008 E0092750 – N512000 E0093102 N512000 E0091000 – N512000 E0084600 – N511147 E0082929 |
| Vertical limits: | FL 245 – FL 660 |
| NOMKA Area (Class C) | |
|---|---|
| Lateral limits: | N512000 E0095610 – N512001 E0100334 N512002 E0102315 – N512913 E0103533 N513400 E0104200 – N512000 E0095610 |
| Vertical limits: | FL 245 – FL 660 |
| RISOK Area (Class C) | |
|---|---|
| Lateral limits: | N514816 E0110825 – N515028 E0111230 N515430 E0110739 – N514816 E0110825 |
| Vertical limits: | FL 285 – FL 660 to Karlsruhe UAC (RISOK HIGH Area) FL 245 – FL 285 to Bremen ACC (RISOK LOW Area) |
| SCHWERIN SOUTH Area (Class C) | |
|---|---|
| Lateral limits: | N541500 E0115334 – N524350 E0110626 N540800 E0111530 – N541745 E0113811 N541500 E0115334 |
| Vertical limits: | FL 285 – FL 660 to Karlsruhe UAC (SCHWERIN SOUTH HIGH Area) FL 245 – FL 285 to Bremen ACC (SCHWERIN SOUTH LOW Area) |
| KATCE Area (Class C) | |
|---|---|
| Lateral limits: | N0510617 E0101701 - N0512002 E0102315 - N0512000 E0093102 - N0510617 E0101701 |
| Vertical limits: | FL 255 – FL 660 |
¶ 2.2.3 Other Areas 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 Karlsruhe UAC 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 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.
¶ 2.2.5 Territorial Matters
- Not applicable -
¶ 2.3 Special Provisions
- Not applicable -
¶
¶ 3. Procedures
The procedures to be applied by Maastricht UAC and Karlsruhe UAC are detailed in the Annexes to this Letter of Agreement:
Annex A Definitions and Abbreviations
Annex B Area of Common Interest
Annex C Exchange of Flight Data
Annex D Procedures for Coordination
Annex E Transfer of Control and Transfer of Communications
Annex F ATS Surveillance Based Coordination Procedures
Annex G Checklist of Pages
¶
¶ 4. Revisions and Deviations
¶ 4.1 Revision of this Letter of Agreement
The revision of the present Letter of Agreement, excluding Annexes and their Appendices, requires the mutual written consent of the signatories.
¶ 4.2 Revision of the Annexes to the Letter of Agreement
The revision of Annexes to the present Letter of Agreement requires the mutual written consent of the representatives of the respective IVAO Divisions designated by the respective signatories, normally the ATC Operations Coordinator at the respective Division.
¶ 4.3 Temporary Deviations
When necessary, the ATC Department of the IVAO Divisions concerned may introduce, by mutual agreement and for a specified period of time, temporary modifications to the procedures laid down in the Annexes to the present Letter of Agreement.
¶ 4.4 Incidental Deviations
Instances may arise where incidental deviations from the procedures specified in the Annexes to this Letter of Agreement may become necessary. Under these circumstances air traffic controllers are expected to exercise their best judgement to ensure the safety and efficiency of air traffic.
¶
¶ 5. Cancellation
Cancellation of the present Letter of Agreement by mutual written agreement of the respective IVAO Divisions may take place at any time.
Cancellation of this Letter of Agreement by either IVAO Division is possible at any time, provided that the cancelling party declares its intention in writing to cancel the Letter of Agreement with a minimum pre-notification time of 6 months before the date the cancellation is to take effect.
¶
¶ 6. Interpretation and Settlement of Disputes
Should any doubt or diverging views arise regarding the interpretation of any provision of the present Letter of Agreement or in case of dispute regarding its application, the parties shall endeavor to reach a solution acceptable to both of them. Should no agreement be reached, each of the parties shall refer to IVAO HQ ATC Operations Department, to which the dispute shall be submitted for settlement.
¶
¶ 7. Validity
This LoA becomes effective 24 March, 2022 and supersedes the Letter of Agreement between Maastricht ACC and Karlsruhe ACC dated 1 April, 2021.
¶ Appendix 1
¶ Ap.1.1 ARPEG Area
¶
¶ Ap.1.2 ABGUS Area
¶ Annex A.
¶ Definitions and Abbreviations
¶
¶ A.1 Definitions
¶ A.1.1 Area of Responsibility
An airspace of defined dimensions where a sole ATC unit has responsibility for providing air traffic services.
¶ A.1.2 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.
¶ A.1.3 Approval Request
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.
¶ A.1.4 Division Level
The flight level dividing two superimposed AoR for the provision of ATS.
¶ A.1.5 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.
¶ A.1.6 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.
¶ A.1.7 Reduced Vertical Separation Minimum
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.
¶ A.1.7.1 RVSM Approved Aircraft
Aircraft that have received State approval for RVSM operations within the EUR RVSM airspace.
¶ A.1.8 Release
¶ A.1.8.1 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.
¶ A.1.8.2 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.
¶ A.1.8.3 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.1.9 State Aircraft
For the purposes of EUR RVSM, only aircraft used in military, customs or police services shall qualify as State aircraft.
¶
¶ 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* | 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 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 |
¶ 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 Appendix of Annex B.
¶ B.1.1 Hannover MaastrichtUIR and Brussels FIR/UIR
An airspace of defined dimensions where a sole ATC unit has responsibility for providing air traffic services.
| Area | Vertical Limits | Airspace Classification |
| Hannover UIR | FL 245 - FL 660 | C |
| Brussels UTA1) | FL 195 - FL 245 | C |
| Brussels UTA2) | FL 245 - FL 660 | C |
1) ATS provided by Brussels ACC.
2) ATS provided by Maastricht UAC.
¶ B.1.2 RheinKarlsruhe UIR
An airspace of defined dimensions where a sole ATC unit has responsibility for providing air traffic services.
| Area | Vertical Limits | Airspace Classification |
| Rhein UIR | FL 245 - FL 660 | C |
¶
¶ B.2 Sectorisation within the Area of Common Interest
The Sectorisation within the ACI is shown in Appendix 1 of Annex B.
¶
¶ B.3 Special Areas within the Area of Common Interest
The Airspace structure within the ACI is shown in Appendix of Annex B.
¶ B.3.1 Areas for Cross/Border Provision of ATS defined with other ATS Units within the ACI
¶ B.3.1.1 ATS provision by Langen ACC – Rhein UIR
Within the Rhein UIR, the provision of ATS in accordance with the airspace classification is performed by Langen ACC within the following areas:
¶ B.3.1.1.1 RASVO South Area – See Appendix 2 of Annex B
Lateral Limits: N502541 E0063751 – N503021 E0064855 – N503037 E0065055 – N501643 E0065526 – N501814 E0063848 – N502541 E0063751
Vertical limits: FL 245 – FL 265 (Class C)
¶ B.3.1.1.2 HILFE Area – See Appendix 2 of Annex B
Lateral Limits: N0512004 E0095538 - N0512000 E0093102 - N0510508 E0092609 - N0510455 E0101223 - N0510617 E0101701 - N0512002 E0102315 - N0512004 E0095538
Vertical limits: FL 245 – FL 255 (Class C)
¶ B.3.1.2 ATS provision by Copenhagen ACC – Hannover UIR
Within the Hannover UIR, the provision of ATS in accordance with the airspace classification is performed by Copenhagen ACC within the following area:
¶ B.3.1.2.1 Michaelsdorf Area – See Appendix 2 of Annex B
Lateral Limits: N542700 E0120000 – N541745 E0113811 – N543400 E0105900 – N543920 E0104000 – along FIR/UIR boundary to – N542700 E0120000
Vertical limits: GND – FL 660 (Class C starting at FL100 and up to UIR)
¶ B.3.1.3 ATS provision by Copenhagen ACC – Bremen FIR / Rhein UIR
Within the Hannover UIR, the provision of ATS in accordance with the airspace classification is performed by Copenhagen ACC within the following area:
¶ B.3.1.3.1 Schwerin North Area – See Appendix 2 of Annex B
Lateral Limits: N542700 E0120000 – N541500 E0115334 – N541745 E0113811 – N542700 E0120000
Vertical limits: FL 285 – FL 660 from Karlsruhe UAC to Copenhagen ACC (Class C)
FL 105 – FL 285 from Bremen ACC to Copenhagen ACC (Class C)
¶ B.3.1.4 ATS provision by Langen ACC – Hannover UIR
Within the Hannover UIR, the provision of ATS in accordance with the airspace classification is performed by Copenhagen ACC within the following area:
¶ B.3.1.4.1 DEVRU Area – See Appendix 2 of Annex B
Lateral Limits: N503021 E0064855 – N503614 E0065227 – N503637 E0070905 – N503500 E0070000 – N503310 E0065537 – N503021 E0064855
Vertical limits: FL 245 – FL 255 (Class C)
¶ B.3.1.4.2 RASVO Area – See Appendix 2 of Annex B
Lateral Limits: N502541 E0063751 – N502821 E0063729 – N503021 E0064855 – N502541 E0063751
Vertical limits: FL 245 – FL 265 (Class C)
¶ B.3.2 Other Areas
Not applicable.
¶
¶ B.4 Non-published Coordination Points within the Area of Common Interest
None.
¶ Appendix 1 of Annex B.
¶ Maastricht UAC Sectorization
¶ Karlsruhe UAC Sectorization
¶ Appendix 2 of Annex B
¶ RASVO South Area
¶ HILFE Area
¶ MICHAELSDORF Area
¶ SCHWERIN North Area
¶ KATCE Area
¶ DEVRU Area
¶ RASVO North Area
¶ Annex C.
¶ Exchange of Flight Data
¶
¶ C.1 General
¶ C.1.1 Basic Flight Plans
Basic Flight plan data should normally be available at 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 or by private text to the appropriate sector/position.
¶ 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 Voice Coordination
Aurora Intercom if all involved ATCOs are using Aurora taking into account software limitations. Else revert to Written Communication.
¶ C.2.2 Written Communication
When required, communication can be performed by private text between the relevant sectors or using semi-automatic systems depending on software capability.
¶ Annex D.
¶ Procedures for Coordination
¶
¶ D.1 General Conditions for Acceptance of Flights
D.1.1 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).
D.1.2 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.
D.1.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.
D.1.4 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.
D.1.5 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 (ATS) routes, COPs to be used and flight 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 Karlsruhe UAC
¶ D.2.1.1 Overflights
The following applies for transfer from All Maastricht UAC Sectors to All Karlsruhe UAC Sectors
Flight Level Allocation: Odd cruising levels:
| ATS-Route | COP | ATS-Route | COP | |
| UL607, DCT | MATUG | DCT | ROSOK | |
| M150 / UZ111, DCT | PITES | L23, DCT | BERIM | |
| UN858, DCT | BITBU | L619, DCT | BUMIL | |
| DCT | ASBON | P717, DCT | GARLU | |
| DCT | TIVUN | L980, DCT | HLZ | |
| DCT | GMH | DCT | LARET | |
| UN850, DCT | EDEGA | L986, DCT | POVEL | |
| UL126 / Z85, DCT | ANANO | Z94, DCT | ABGUS | |
| P605, DCT | KEMAD | L620, DCT | NOMKA | |
| UN858, DCT | LIMGO | Z870, DCT | NEBUN | |
| DCT, UZ210, UZ315 | LIRSU | DCT | KUMER | |
| TL2, TL3S | RISOK | DCT | AMISO | |
| DCT | LUWIL |
¶ D.2.1.2 Flights from Brussels Sectors to West Sectors
Departures:
|
Departure |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EBBR, EBMB, EBCV, EHEH |
Y863 |
OGLOR |
NTM |
At max. FL310 |
Note 1 |
|
M150, DCT |
PITES |
||||
|
EBCI (destinations LG**, LT**, EDDS, EDSB) |
Y863 |
OGLOR |
At max. FL310 |
||
|
M150 |
PITES |
||||
|
EBCI (all destinations except LG**, LT**, EDDS, EDSB) |
Y863 |
OGLOR |
At max. FL330 |
||
|
M150 |
PITES |
Note 1 - Traffic is released for climb to max. FL330, subject to known traffic.
Arrivals:
|
Destination |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDS, EDSB, EDVK, EDFQ, EDQG, ETHN |
Y863 |
OGLOR |
NTM |
max. FL310 |
|
|
UL607, DCT |
MATUG |
max. FL310 |
|||
|
Y180 |
BITBU |
max. FL310 |
|||
|
EDDS, EDSB |
M150, DCT |
PITES |
max. FL310 |
¶ D.2.1.2.1 General Procedures
A) Karlsruhe UAC shall be responsible to establish separation between traffic on
- UL607 and UN858/UZ111 converging overhead AMASI;
- converging traffic on Y863 and UN858
- converging traffic on Y863 and UZ111
- and converging traffic on UZ111 and UZ210 or UZ315.
B) Karlsruhe UAC shall be responsible to establish separation between traffic on
- UN858 and UZ210 converging overhead NOSPA
¶ D.2.1.2.1 General Directs
The following directs may be used without coordination:
| Waypoint | Sector | Special Conditions |
| GUBAX |
LNO |
|
| BOMBI | ||
| MOVUM | ARR EDDM only | |
| AMASI | ||
| EMGOD | ARR EDDS/EDSB only | |
| NONKO | ||
| LADAT-KRH |
LUX |
ARR EDDS/EDSB only |
| KRH |
LNO/LUX |
|
| TEDGO | ||
| LAMGO | ||
| VIBOM | ||
| MASEK |
LUX |
|
| BOMBI | ||
| MOVUM | ||
| SWALM |
SOL |
|
| OSBIT | Only via or east of BERXO |
¶
¶ D.2.1.3 Flights from Hannover Sectors to Central Sectors
Departures:
|
Departure |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDV |
DCT |
XAROL |
FUL |
FL270 |
|
|
EDVE |
DCT |
XAROL |
FL310 |
||
|
EDDV |
P605 |
WERRA |
FL260 |
Accepted climbing out of FL260 |
|
|
EDVE |
P605 |
WERRA |
FL290 |
||
|
EHEH, EHBK, EHBD |
Z841 |
GMH |
FL310 |
FUL shall consider the departures climbing out of FL260. |
|
|
EDLV, EDLS |
Z841 |
GMH |
FUL |
FL290 |
FUL shall consider the departures climbing out of FL260. |
Arrivals:
|
Destination |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDSB, LFST, LFGA |
DCT |
XAROL |
FUL |
Max. FL330 |
|
|
ELLX, LFJL, EDQG |
DCT |
XAROL |
max. FL290 |
||
|
EDMA, EDMO, EDJA, EDTY |
DCT |
XAROL |
max. FL370 |
||
|
EDDN, EDMA, EDMO, EDJA, EDTY |
DCT |
TIVUN |
max. FL350 |
||
|
EDDR, EDRZ, EDDS, EDSB, ETOR, LFST, LFGA |
DCT |
TIVUN |
max. FL310 |
||
|
EDFM, EDFV, EDRY |
DCT |
TIVUN |
max. FL290 |
||
|
EDDS, EDSB, EDJA, EDMA, EDMO, EDTY, EDTL, EDTM, ETSI, ETSL, ETSN |
DCT |
BERXO |
max. FL350 |
||
|
EDQG |
DCT |
BERXO |
max. FL290 |
||
|
EDMA, EDMO, EDJA, EDTY |
UN850, DCT |
OTMON |
max. FL370 |
||
|
LFST, LFGA |
UN850, DCT |
OTMON |
max. FL330 |
¶ D.2.1.3.1 General Directs
The following directs may be used without coordination:
| Waypoint | Sector | Special Conditions |
| TESGA | RHR | Clear of NTM sector unless coordinated |
| DODEN | RHR / SOL | Clear of NTM and FUL sector unless coordinated |
| TUSUK | RHR | Clear of NTM sector unless coordinated |
| OMOGI | SOL | Clear of FUL sector unless coordinated |
¶ D.2.1.4 Flights from Hannover Sectors to East Sectors
Departures:
|
Departure |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDW |
Z870 |
NEBUN |
HVL |
at FL290 |
|
|
L986, DCT |
POVEL |
max. FL330 |
|||
|
DCT |
LARET, ABGUS, KUMER, NOMKA |
SAL |
max. FL330 |
||
|
EDDH |
DCT |
LARET |
max. FL350 |
Arrivals:
|
Destination |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDC, EDAB |
HVL |
Only accepted by Karlsruhe UAC via COP within OSE sector |
|||
|
EDAH |
P717, DCT |
GARLU |
max. FL350 |
Via COP POVEL accepted at RFL |
|
|
Z870, DCT |
NEBUN |
||||
|
L619, DCT |
BUMIL |
¶ D.2.1.4.1 General Procedures
A) Maastricht UAC is responsible to transfer eastbound traffic planned to cross the boundary between BUMIL and HLZ separated of traffic planned via NEBUN / EMBOX.
B) Maastricht UAC is responsible to transfer eastbound traffic planned via NOMKA / KUMER separated of the southbound traffic planned via NEBUN / EMBOX.
¶ D.2.1.4.2 General Directs
The following directs may be used without coordination:
| Waypoint | Sector | Special Conditions |
| SUBIX |
CEL / SOL |
|
| ALUKA | ||
| BODLA | ||
| LASIS |
¶ D.2.2 Flights from Karlsruhe UAC to Maastricht UAC
¶ D.2.2.1 Overflights
The following applies for transfer from All Maastricht UAC Sectors to All Karlsruhe UAC Sectors
Flight Level Allocation: Even cruising levels:
| ATS-Route | COP | ATS-Route | COP | |
| L608 / UZ210, DCT | LIRSU | M726, DCT | ROSOK | |
| UL610, DCT | ADKUV | L23, DCT | BERIM | |
| UL984, DCT | NOSPA | M864, L619, DCT | BUMIL | |
| DCT | GMH | Z717, DCT | GARLU | |
| L604, DCT | MAPOX | L980, DCT | HLZ | |
| DCT | LUWIL | DCT | AMISO | |
| DCT | PEXAM | M852, DCT | LARET | |
|
DCT (after LIMGO DCT IDOSA) |
LIMGO | DCT | ABGUS | |
| DCT | KUMER | |||
| DCT (after BETEX DCT IDOSA) | BETEX | TL2, TL3S | RISOK | |
| DCT | ASBON | DCT | KATCE | |
| DCT | TIVUN | L986, DCT | POVEL | |
| DCT | NEBUN | DCT | OTMON | |
| UN851 | ELNAT | DCT | BEROX |
¶ D.2.2.2 Flights from West Sectors to Brussels Sectors
Departures:
|
Departure |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDF, EDFE, EDFZ, ETOU, EDFB, EDFC |
Y180 |
BITBU |
LUX |
max. 280 |
Released for climb max FL320 |
Arrivals:
|
Destination |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EBBR, EBMB |
DCT |
ADKUV |
OLN |
at FL300 |
|
|
L608, DCT |
ADENU |
at FL300 |
|||
|
EBFN, EBKT, EBOS, EGMD, LFAC, LFAT, LFAV, LFAQ, LFAY, LFOB, LFOE, LFOH, LFOI, LFOP, LFRC, LFRG, LFRK, LFQO, LFQQ, LFQT |
DCT |
ADKUV |
max. FL320 |
||
|
EBFN, EBKT, EBOS, EGMD, LFAY, LFOB, LFOE, LFOH, LFOI, LFOP, LFRC, LFRG, LFRK |
L608, DCT |
LIRSU |
max. FL320 |
||
|
LFLA, LFOB, LFOC, LFOJ, LFOX, LFOZ, LFPB, LFPG, LFPM, LFPN, LFPO, LFPT, LFPV, LFPY |
UL984, DCT |
NOSPA |
LUX |
max. FL380 |
|
|
DCT (LIMGO- IDOSA) |
LIMGO |
||||
|
DCT (BETEX-IDOSA) |
BETEX |
¶
¶
¶
¶
¶
¶
¶
¶
¶ D.2.2.2.1 General Directs
The following directs may be used without coordination:
| Waypoint | Sector | Special Conditions |
| BUB |
NTM |
Only for ARR EHAA FIR provided the flight path remains between ADKUV and NOSPA. |
| COA/DENUT or BUB | Only for DEST EBFN, EBKT, EBOS, EG** and beyond provided the flight path remains between ADKUV and NOSPA. Not applicable to DEP EDDF, EDFE, EDFZ, ETOU. |
|
| IDOSA | Only for traffic flight planned via COP NOSPA, BETEX and LIMGO, provided the flight path remains between BITBU and SUTAL. |
¶ D.2.2.3 Flights from Central Sectors to Hannover Sectors
Departures:
|
Departure |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDP, EDAC |
L602, DCT |
KEMAD |
SOL |
max. FL340 |
|
|
EDDF |
Y150, DCT |
OTMON |
SOL |
FL280 |
Released FL320 on contact |
Arrivals:
|
Destination |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDW, EDWE, EDWI |
UN851, DCT |
KEMAD |
SOL |
max. FL320 |
|
|
EDDB |
UN851, DCT |
KEMAD |
max. FL340 |
||
|
EHEH, EHBD, EHBK, EHTE, EHLE |
L604, DCT |
MAPOX |
MUN |
max. FL320 |
|
|
L602, DCT |
KEMAD |
SOL |
max. FL340 |
Note 1 – These arrivals are released for descent and turns.
¶ D.2.2.3.1 General Directs
The following directs may be used without coordination:
| Waypoint | Sector | Special Conditions |
| HMM |
FUL |
Traffic via L604, to be south of MAPOX |
| NORKU | Traffic along L602 or via SOPOD-PEXAM shall be transferred on centerline or north thereof. FUL shall establish separation between both flows | |
| RAVLO | ||
| SPY | ||
| RKN | ||
| MADOR | For ARR EDDH only | |
| GESKA | ||
| EKERN | ||
| NORTA |
¶
¶ D.2.2.4 Flights from East Sectors to Hannover Sectors
Departures:
|
Departure |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDDB |
L619 |
BUMIL |
CEL |
Between 300 and 360 |
|
|
Y203/Y200 |
HLZ |
||||
|
Y204/Q201 |
POVEL |
SOL |
Arrivals:
|
Destination |
Routing |
COP |
Receiving Sector |
FLA |
Special Conditions |
|
EDLP, EDVK, EDFQ, EDLI, |
DCT |
HLZ |
CEL |
max. FL300 |
|
|
Z717, DCT |
GARLU |
||||
|
M864, DCT |
BUMIL |
¶
¶
¶ D.2.2.4.1 General Procedures
A) Karlsruhe UAC is responsible to transfer westbound traffic planned via LARET / ABGUS separated of northbound traffic planned via LARET / ABGUS / KUMER.
B) Arrivals to EDDL, EDLV, EHEH and EHBK may be cleared direct to DENOL.
C) Arrivals to EDDK may be cleared direct to PODER.
D) Arrivals LFPx maybe cleared direct to NVO, if staying clear of FUL Sector.
E) Berlin departures are released for turn on transfer.
¶ D.3 Special Procedures
Not applicable.
¶ D.4 VFR Flights
Not applicable.
¶ Annex E.
¶ Transfer of Control and Transfer of Communications
¶
¶ E.1 Transfer of Control
E.1.1 Transfer of control shall take place at the AoR boundary, unless otherwise specified in paragraph E.3.
¶ E.2 Transfer of Communication
E.2.1 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.2 Frequency allocation and sector arrangement of Maastricht UAC
E.2.2.1 Maastricht UAC Brussels Sectors:
|
Receiving Sector |
Vertical Limits |
VHF |
|
Olno |
FL 245 – FL 660 |
125.980 MHz |
|
Luxembourg |
E.2.2.2 Maastricht UAC Hannover Sectors:
|
Receiving Sector |
Vertical Limits |
VHF |
|
Ruhr |
FL 245 – FL 660 |
133.215 MHz |
|
Muenster |
FL 245 – FL 660 |
|
|
Celle |
FL 245 – FL 660 |
131.380 MHz |
|
Solling |
FL 245 – FL 660 |
E.2.2.3 Maastricht UAC DeCo Sectors:
|
Receiving Sector |
Vertical Limits |
VHF |
|
Holstein |
FL 245 – FL 660 |
134.705 MHz |
¶ E.2.3 Frequency allocation and sector arrangement of Karsruhe UAC
E.2.3.1 Karlsruhe UAC West Sectors:
|
Receiving Sector |
Vertical Limits |
VHF |
|
Nattenheim |
FL 245 – FL 660 |
132.080 MHz |
E.2.3.2 Karlsruhe UAC Central Sectors:
|
Receiving Sector |
Vertical Limits |
VHF |
|
Fulda |
FL 245 – FL 660 |
136.305 MHz |
E.2.3.3 Karlsruhe UAC East Sectors:
|
Receiving Sector |
Vertical Limits |
VHF |
|
Saale |
FL 315 – FL 660 |
122.625 MHz |
|
Havel |
FL 285 – FL 660 |
128.235 MHz |
¶ E.3 Specific Points for Transfer of Control and Transfer of Communications
Not applicable.
¶ Annex F.
¶ ATS Surveillance Based Coordination Procedures
¶
¶ F.1 General
F.1.1 Transfer of identification and transfer of control between Maastricht UAC and Karlsruhe UAC will be subject to the serviceability of the respective surveillance systems.
F.1.2 In case of any doubt about the identity of an aircraft, nothing in the provisions of this Annex, prevents the use of other methods for the identification of an aircraft.
¶ F.2 Transfer of Aircraft Identification
F.2.1 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.
F.2.2 When discrete SSR codes are used for transfer of identification, they shall be assigned in accordance with ORCAM.
F.2.3 Any change of SSR code by the accepting ATS Unit may only take place after the transfer of control point.
F.2.4 The accepting ATS Unit shall be notified of any observed irregularity in the operation of SSR transponders or ADS-B transmitters.
F.2.5 In the In the event that the accepting ATS unit is unable to process code A1000, it shall immediately advise the transferring ATS unit. Thereafter, unless otherwise coordinated, the transferring ATS unit shall change relevant instances of A1000 to a discrete SSR code determined in accordance with ORCAM.
¶ F.3 Transfer of Control
F.3.1 Radar Separation minimum shall be 5 NM.
F.3.2 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.3.3 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.
F.3.3.1 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.3.3.2 The accepting controller may terminate the silent transfer of control at any time, normally with an advance notice of 10 minutes.
¶ F.3.4 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 ATCO;
- 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.