Maastricht UAC Operations Manual
IVAO ATC HQ
Maastricht UAC is responsible for the airspace of the Amsterdam FIR, the Brussels UIR and the Hannover UIR. Besides this, it also is responsible for a few bits of delegated airspace over France within the Paris UIR and over Germany within the Rhein UIR.
Maastricht UAC is responsible for all IFR movements within the following airspace above FL245:
|FIR / UIR
|Maastricht UAC levels
|Class C from FL 195 to FL 660
|FL245 - FL660
|Class C from FL 195 to FL 660
|Class C from FL 245 to FL 660 (Class C from FL 100 to FL 660 on airspace delegated from Bremen FIR and Rhein UIR)
VFR Operations are not permitted in the Maastricht UAC AoR, with the exception of OAT flights inside active Military Areas.
In Maastricht UAC, there are three sector groups, comprised of several sectors, all of them with Vertical Limits from FL 245 - FL 660.
The Following Sector configurations are possible, involving both West and East Sectors. The sectors may be opened in any order with smaller sectors taking control of their respective area from the larger sector if online.
Channel: 135.960 MHz
CPDLC Logon: EDYY
Sectors Under Responsibility: ALL
Channel: 132.855 MHz
CPDLC Logon: EDYB
Sectors Under Responsibility: Koksy - Nicky - Lux - Olno
Channel: 132.755 MHz
CPDLC Logon: EDYN
Sectors Under Responsibility: Koksy - Nicky
Channel: 125.980 MHz
CPDLC Logon: EDYO
Sectors Under Responsibility: Lux - Olno
Channel: 135.510 MHz
CPDLC Logon: EDYE
Sectors Under Responsibility: Delta - Jever - Holstein
Channel: 132.085 MHz
CPDLC Logon: EDYD
Sectors Under Responsibility: Delta
Channel: 134.075 MHz
CPDLC Logon: EDYJ
Sectors Under Responsibility: Jever - Holstein
Channel: 122.185 MHz
CPDLC Logon: EDYH
Sectors Under Responsibility: Celle - Muenster - Ruhr - Solling
Channel: 133.215 MHz
CPDLC Logon: EDYM
Sectors Under Responsibility: Muenster - Ruhr
Channel: 131.380 MHz
CPDLC Logon: EDYS
Sectors Under Responsibility: Celle - Solling
The operational language of Maastricht UAC is English. It shall be used in radio and in communication with other Units
The languages used shall be unambiguous and concise, and standard phraseology shall be used to the largest possible extent.
Standard lateral Radar Separation Minima based on the use of Radar Position Target and/or Primary Surveillance Radar blips shall be applied so that the distance between the centres of the Radar Position Targets and/or Primary Surveillance Radar blips, representing the positions of the aircraft concerned is never less than 5 NM.
The minimum Vertical Separation shall be 1000ft below FL290 and 2000ft above FL290. If both aircraft are RVSM equipped and approved, a minimum separation of 1000ft is applied between FL290 and FL410.
The standard Radar Separation is 5 NM, no matter the Wake Turbulence Category.
A formation flight is a set-up of more than one aircraft in which all succeeding aircraft maintain the following parameters to the formation leader:
Vertical Separation Minima between a formation flight and other traffic are as follows:
A minimum Radar Separation of 2.5 NM shall be applied to airspace boundaries of Adjacent Airspaces and to any Military Area.
To Adjacent Civil Airspace, the first level of the Sector can be used.
To Military Areas, a vertical separation shall be applied as follows:
Below FL290 a vertical distance of 500ft is sufficient if the published boundary is at an intermediate level (e.g. Fl105 or FL145).
Maastricht UAC and some adjacent units operate a Flight Level Allocation for flights entering and leaving the Maastricht Area. Those FLAs can be found on the respective LoAs and only apply at the Entry and Exit points.
This means that other Flight Level assignments may be used while the aircraft transits through the Maastricht AoR. However, the assignment shall be in principle assigned Flight Levels in accordance with the West-East Semi-Circular rule as described in Chapter 3.1.
Normally, traffic shall be cleared on published ATS routes and DCT in the context of the Free Route Airspace. Coordination can be made for flights to proceed on direct routes to relevant fixes inside other units, with the approval of all units/sectors concerned.
This does not apply to those directs that are already published in the relevant LoAs with the relevant unit to which further coordination is not required.
Transfer of Communications happens when there is no risk of a collision with other traffic and the traffic is relatively nearby the sector boundary.
Reduced Vertical Separation Minima (RVSM) permits the application of a 1000ft vertical separation minimum between suitably equipped aircraft in the level band FL 290 - FL 410 inclusive, thereby making available six additional usable flight levels.
Note: FL280 is the next usable level below RVSM airspace. FL430 is the next usable level above RVSM airspace.
Following the RVSM Procedure:
Note that State Aircraft are exempted from having to meet the RVSM requirements and can be accommodated in EUR RVSM airspace, provided that ATC maintains a minimum vertical separation of 2000ft between such aircraft and all other IFR aircraft. All operators of non-RVSM with RFL of FL290 or above shall insert “STS/NONRVSM” in item 18 of the IVAO Flight Plan.
Where SSR is used for identification, aircraft may be identified by one or more of the following procedures:
In case an aircraft does not have a discrete squawk code assigned, use the “REQ SSR" function and assign it.
If for any reason the controller has doubts as to the identification, the IDENT feature shall be used to verify the identity of the aircraft concerned.
PSR cannot be used to identify traffic on IVAOs Maastricht UAC.
Departures from Amsterdam FIR are released by the Delta Sector for turn and climb up to FL290 to the Jever Sector.
The Jever Sector shall deliver traffic with a destination in the Brussels FIR and Langen FIR Group (see EHAA LoA) to the Delta Sector at FL320 or below.
The Nicky Sector shall deliver traffic with the listed destination as per the following procedures:
The Olno Sector shall deliver traffic with destination EHAM, EHRD, EHLE, EHHV and EHKD to the Nicky Sector at FL320 or below.
The Luxemburg Sector shall deliver traffic with destination EHAM, EHRD, EHLE, EHHV and EHKD to the Nicky Sector at FL320 or below.
The Muenster Sector shall deliver traffic with destination EDDC-NOMKA group or EDDP to the Celle or Solling sector at FL350 or below.
Note: EDDC-NOMKA group: EDDC, EDAC, EDDN, EDAB, EDQC, EDGD, EDGQ, EDGQ, EDQM and EDQT.
The Solling Sector shall deliver traffic with destination:
EBBR-ABAMI group to the Muenster Sector at FL340 or below EHBK-HMM group to the Muenster Sector at FL280 or below
Note 1: EBBR-ABAMI group: EBBR/EBMB, EBAW, EBCI, EBCV, EBLG and ELLX
Note 2: EHBK-HMM group: EHBK, EHEH, EHTE, EHBD and EHLE
Eastbound traffic shall be transferred at an Odd Flight Level, Delta Sector is responsible for the separation.
Westbound traffic shall be transferred at an Even Flight Level, Nicky Sector is responsible for the separation.
The Koksy Sector and Nicky Sector shall deliver traffic with a destination listed below to the Delta Sector at FL330 or below.
Destinations: Amsterdam FIR, EDDL, EDDG, EDDK, EDFQ, EDGS, EDKB, EDLA, EDLE, EDLI, EDLP, EDLS and EDLW
The Koksy Sector shall transfer departures EBCI to the Delta Sector at or climbing to FL310.
Traffic is released for turns by not more than 20 degrees by the Delta Sector when passing abeam GISEB.
The Delta Sector shall deliver traffic with destination as described below:
Departures from Amsterdam FIR are released by the Delta Sector for turn and climb up to FL290.
The Ruhr Sector shall deliver traffic destination EBOS-SOGRI group, LFOB-SOGRI group, LFQQ-SOGRI group and EGMD to the Olno Sector at FL 340 or below
Note 1: EBOS-SOGRI group: EBOS, EBKT and EBFN
Note 2: LFOB-SOGRI group: LFOB, LFOH, LFRG, LFOI, LFOP, LFOE, LFOK, LFRC and LFRK
Note 3: LFQQ-SOGRI group: LFQQ, LFAC, LFAT, LFAQ, LFQT, LFQO, LFAV and LFQI
The Delta Sector shall deliver traffic destination:
Note 1: EDDF-LIMPI group: EDDF, EDFE, EDFZ and EDFH
Note 2: EDDV-OSN group: EDDV, EDDW, EDVK, EDWE and EDWI
The Ruhr and Muenster Sectors shall deliver traffic destination:
Note 1: LFOB-D group: LFOB, LFOH, LFRG, LFOI, LFOP, LFOE, LFOK, LFRC and LFRK
Note 2: LFQQ-D group: LFQQ, LFAC, LFAT, LFAQ, LFQT, LFQO, LFAV and LFQI
The Holstein Sector shall deliver traffic destination:
The Sector file is available in Aurora under the name “Maastricht UAC”. Be sure to enable the Auto Update function to keep the sector file updated.