Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
SECTION UPDATED ON VALID FROMType of file
orNo. of Pages
STATE STATUS
GENERAL DESCRIPTION (APPENDIX 1) 25/04/2019 20/06/2019 15 Introduction
APPENDIX 2 18/07/2019 12/9/2019 Excel File Area DefinitionsAPPENDIX 3
(ID numbers 4000 to 4999 ) 07/11/2019 2/1/2020 Excel File City Pair level Capping
APPENDIX 4(ID numbers 5000 to 5499
and 50000 to 54999 )/(ID numbers 1 to 99 and 400 )
07/11/2019 2/1/2020 Excel File DCTs / Limits NEW
APPENDIX 5(ID numbers 5500 to 5999 ) 07/11/2019 2/1/2020 Excel File Airport Connectivity NEW
APPENDIX 6(ID numbers 8000 - 8999) 07/11/2019 2/1/2020 Excel File Flight Profile Restrictions NEW
APPENDIX 7 07/11/2019 2/1/2020 Excel File FUA Restrictions NEWPAN EUROPE
(ID numbersCross-border 1000 - 1499
General 2000 - 3999 Military 7000 - 7499)
07/11/2019 2/1/2020 Excel File ECAC Airspace NEW
RAD 2001 Check ListValid From 02/01/2020
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 1 of 16
https://www.nm.eurocontrol.int/RAD/index.html
RAD GENERAL DESCRIPTION (European Route Network Improvement Plan - Part 1, Section 8)
1. INTRODUCTION 1.1. The Route Availability Document (RAD) is created based on:
a. COMMISSION REGULATION (EU) No 255/2010 of 25 March 2010 laying down common rules on air traffic flow management, Article 4 - General obligations of Member States, paragraph 4; and
b. COMMISSION REGULATION (EU) No 677/2011 of 7 July 2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions and amending Regulation (EU) No 691/2010, Annex I - The European Route Network Design (ERND) Function, Part B - Planning principle 5(d).
1.2. The RAD is a common reference document containing the policies, procedures and description for route
and traffic orientation. It also includes route network and free route airspace utilisation rules and availability.
1.3. The RAD is also an Air Traffic Flow and Capacity Management (ATFCM) tool that is designed as a
sole-source flight-planning document, which integrates both structural and ATFCM requirements, geographically and vertically.
2. BASIC PRINCIPLES 2.1. The objective of the RAD is to facilitate flight planning, in order to improve ATFCM, while allowing
aircraft operators’ flight planning flexibility. It provides a single, fully integrated and co-ordinated routeing scheme. Except where otherwise specified the RAD affects all areas where the Network Manager provides ATFCM services.
2.2. The RAD enables States/FABs/ANSPs to maximise capacity and reduce complexity by defining
restrictions that prevent disruption to the organised system of major traffic flows through congested areas with due regard to Aircraft Operator requirements.
2.3. The RAD is designed as a part of the Network Manager (NM) ATFCM operation. It is organising the
traffic into specific flows to make the best use of available capacity. Whilst, on its own, it will not guarantee the protection of congested ATC sectors during peak periods, it should facilitate more precise application of tactical ATFCM measures.
2.4. The RAD should also assist the Network Manager in identifying and providing re-routeing options.
Global management of the demand will, potentially, lead to an overall reduction of delays. It is important to note that to achieve this, some re-distribution of the traffic may be required through the implementation of Scenarios. This may result in modified traffic/regulations in some areas where, under normal circumstances, they would not be seen.
2.5. The content of the RAD shall be agreed between the Network Manager and the Operational
Stakeholders through an appropriate Cooperative Decision Making (CDM) process. 2.6. The RAD is subject to continuous review by the Network Manager and the Operational Stakeholders to
ensure that the requirements are still valid and take account of any ATC structural or organisational changes that may occur.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 2 of 16
https://www.nm.eurocontrol.int/RAD/index.html
2.7. The RAD is updated each AIRAC cycle following a structured standard process of:
a. Requirement; b. Validation; c. Publication by the Network Manager in cooperation/coordination with all Operational Stakeholders.
2.8. The RAD is only applicable to the IFR part of the Flight Plan. 2.9. Each State shall ensure that the RAD is compatible with their AIP with regard to the airspace
organisation inside the relevant FIR/UIR. 2.10. The NM is responsible for preparing of a common RAD reference document, collating, coordinating,
validating and publishing it, following the CDM process as described in this section. 3. STRUCTURE 3.1. Document structure 3.1.1. The RAD consists of:
a. General description; b. 6 (six) Appendices: Appendix 2 - Area Definition; Appendix 3 - Flight Level Capping limits; Appendix 4 - En-route DCT limits; Appendix 5 - Airport connectivity; Appendix 6 - Flight Profile Restrictions; Appendix 7 - FUA Restrictions
c. a Network wide Pan-European Annex; d. a separate Annex for special events, if necessary, containing restrictions of temporary nature (i.e.
European/World Sport Events, Olympic Games, large scale Military exercises, economic forums …). 3.1.1.1 General description
a. It defines the basic principles, general structure of the RAD, the structure of RAD restrictions, period of validity, application, amendment process, temporary changes, some flight planning issues, routeing scenarios, publication, tactical operations and RAD review process.
3.1.1.2 Appendix 2
a. It defines a number of airfields included in the RAD described by the following terms: “Group” - defines a number of 3 (three) or more airfields that may be subject to the same
restrictions. For example a major destination may have a number of minor satellite airfields in the vicinity; this constitutes a “Group”;
“Area” - defines as a number of airfields within the same region and may comprise several “Groups”, or individual airfields.
b. The definition of the Group or Area is the responsibility of the State/FAB/ANSP within which the Group or Area exists; however other States/FABs/ANSPs may use the definition.
c. If a State/FAB/ANSP wishes to use a defined Group or Area with the exclusion or inclusion of certain airfields, then this should be depicted as follows:
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 3 of 16
https://www.nm.eurocontrol.int/RAD/index.html
Fictitious Example
Change record ID Definition
A………. Group E_ _ _ / E_ _ _
B………. Area L _ _ _ / L _ _ _ C………. Y/Z Area L _ _ _ / L _ _ _
d. By using the above methodology, there can only be one definition of each Group/Area, thus reducing
confusion. e. However, it is the responsibility of the State/FAB/ANSP to ensure that when corrections are made to
Appendix 2 that these amendments are also applicable to any restriction using the defined Group/Area. The Network Manager will endeavour to notify relevant States/FABs/ANSPs of such changes.
3.1.1.3 Appendix 3
a. It defines FL capping limitations imposed by each State/FAB/ANSP and is applied from airport of departure (ADEP) to airport of destination (ADES).
Fictitious Example
Change record
ID Number FROM TO Condition FL Capping Restriction Applicability
E_4001 A….. Group B….. Group Via AAAAA Not above FL235 08:30 - 10:30 (07:30 - 09:30) E_4002 B….. Group A….. Group Via AAAAA Not above FL235 08:30 - 10:30 (07:30 - 09:30) L_4002 C….. Area L _ _ _ , E _ _ _ Via L _ _ _ UTA Not above FL315 04:00 - 23:00 (03:00 - 22:00) L_4003 L _ _ _ , E _ _ _ C….. Area Via L _ _ _ UTA Not above FL315 04:00 - 23:00 (03:00 - 22:00) L_4004 L_ _ _FIR E_ _ _FIR Except Type M Not above FL345 H24
3.1.1.4 Appendix 4
a. It defines the en-route DCT (Direct) flight plan filing limitations imposed by each State/FAB or ATC Unit in accordance with provisions of ICAO Doc 4444 - ATM (PANS-ATM);
b. It contains: DCT horizontal limits inside each ATC Unit; Cross-border horizontal DCT limits (between ATC Units); Vertically defined DCTs with availability “No” or “Yes”, with certain traffic flow limitations
and with defined Operational goal. Also part of these DCTs are: Free Route Airspace (FRA) DCTs.
c. It should contain, for DCTs with availability YES, all possible remarks concerning the airspace crossed by the allowed DCTs. Based on relevant State AIPs AOs shall be informed for DCTs passing by: Uncontrolled classes of airspace, Danger areas, Prohibited areas, Restricted areas, TSAs, TRAs, CBAs, CTRs, TMAs, etc.
d. It should not be considered as an airspace design tool creating a complimentary ATS route network in Europe;
e. Where DCT applies to Free Route Airspace (FRA) the definition of the FRA shall be found in the relevant AIP;
f. Each State shall insure that the DCTs are compatible with their AIP with regard to the airspace organisation inside the relevant ATC Units.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 4 of 16
https://www.nm.eurocontrol.int/RAD/index.html
Fictitious Example for DCT segments
Change record FROM TO
Lower Vertical Limit (FL)
Upper Vertical Limit (FL)
Available (Y) Not available
(N) Utilization DCT Time Availability
ID Number
Operational Goal Remark/s
Direction of
cruising levels
ATC Unit
AAAAA BBBBB 315 660 Yes Only available
for traffic …………...
H24 E _5001 Night time direct route …………...
Via TSAxxx EVEN E_ _ _ ACC
CCCCC DDDDD 045 245 Yes Only available
for traffic …………...
06:00 - 22:00 (05:00 - 21:00) L_5002
Traffic DEP … shall file …………...
Within Class G airspace
ODD L_ _ _ ACC
Fictitious Example for DCT vertical and horizontal limits
Change record
ATC Unit Name
ATC Unit Vertical Limit
DCT Horizontal
Limit Cross-border DCT
Limits ID Number DCT limit
ID Number Not allowed Cross-
border DCT -------------------------
Cross border country codes in ID number may be bi-
directional
E_ _ _ACC below FL115 50NM Allowed
except to/from …………...
E_1 E_E_400
L _ _ _ACC below FL245 0NM Not allowed
except to/from …………...
E _ _ _1 _ _E_400
3.1.1.5 Appendix 5
a. It defines the DCT (Direct) flight plan filing connections defined by each State/FAB/ANSP to/from the airports without SIDs/STARs or with SIDs/STARs which are not able to be complied due to certain aircraft limitations. This is done only to support/facilitate the processing of flight plans. Based on relevant State AIPs AOs shall be informed about the airspace organisation at/around the airports.
b. It contains: airport DCT horizontal limits; connecting points for ARR/DEP; additional compulsory FRA Departure (D) /Arrival (A) Connecting Point/s from/to a certain
TMA/airport and indications on their use for departures / arrivals from / to specific aerodromes; information for some flight plan filing limitations with regard to last/first SID/STAR points and
ATS route network, if required; information for AOs to comply with SIDs/STARs, if required.
Fictitious Example
Change Record DEP AD
Last PT SID / SID
ID
DCT DEP PT DEP Restrictions
DEP Restriction
Applicability DEP ID No DEP Operational Goal / Remarks
NAS / FAB
L _ _ _ (Note 1)
AAAAA (Only Jet)
Only available above FL065 Via CCCCC DCT LLLLL H24 L _ 5500 L _
Change Record ARR AD
First PT STAR /
STAR ID DCT ARR
PT ARR Restrictions ARR
Restriction Applicability
ARR ID No ARR
Operational Goal / Remarks
NAS / FAB
E _ _ _ (Note 1)
AAAAA (Only Jet)
Only available above FL065 Via CCCCC DCT LLLLL H24 E _ 5500 E _
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 5 of 16
https://www.nm.eurocontrol.int/RAD/index.html
3.1.1.6 Appendix 6
a. It defines the vertical profile elements of the LoAs between adjacent ATC Units. This purely operational data is not published through AIS;
b. It contains the restrictions which influence how the profile is calculated in NM systems and the Flight Plan will not be rejected (REJ) by IFPS even when there is no reference to the corresponding restriction in Field 15. The Operational Stakeholders are not required to file in the Flight Plan these restrictions. In this case it is the option of the filer to either include or exclude the restriction in the FUEL PLAN.
Note: If there is requirement to hard check any restriction, then the corresponding restriction shall be transferred to the Pan-European Annex.
Fictitious Example
Change record ID Number Flow Routing Utilization
Time Availability Operational Goal
L_8001 AAAAA Not available for traffic …. above FL235. H24 To comply with LoA.
E_8002 AAAAA T1 BBBBB Not available for traffic DEP/ARR X group via MMM below FL075.
00:01 – 04:50 (23:01 – 03:50) To force traffic via CCCCC.
3.1.1.7 Appendix 7
a. It defines the airspace restrictions (FUA restrictions) caused by restricted airspace (RSA) activation within each State/FAB/ANSP;
b. It contains: coded name identification of the relevant restricted airspace; information that restriction is valid only, when the airspace is allocated at EAUP/EUUP. specific conditions for the utilization of FRA Intermediate Point/s (I).
Fictitious Example
Change record
AIP RSA ID
CACD RSA ID
Restriction Applied during times and
within vertical limits allocated at EAUP/EUUP
ID Number Operational Goal
Affected ATS route/s / DCT/s
L_R24 L_R24
Not available for traffic L_R24R
Traffic is not allowed to flight plan across active military area.
AAA L1 BBBBB CCCCC M1 DDDDD DCT EEE - FFFFF
E_TRA51 E_T51
Only available for traffic 1. DEP/ARR E _ _ _ 2. Military GAT 3. Via AAAAA N3 BBBBB 4. Via CCCCC N3 DDDDD
E_TRA51R
Traffic is not allowed to flight plan across active military area except specified flows. For avoidance nearby FRA (I) point/s is/are: ZZZZZ, FFFFF, MMMMM.
AAA L1 BBBBB CCCCC M1 DDDDD GGGGG N1 HHHHH DCT RRRRR - TTTTT DCT NNNNN - LLLLL
3.1.1.8 Network wide Pan-European Annex
a. The Annex contains a list of restrictions valid for each States/FABs/ANSPs on specific: Significant point/s; or ATS route segment/s; or Airspace volume/s (ATC Unit, AoR of relevant ATC Unit - CTA/UTA, TMA, CTR or
individual control sector/s within an ATC unit).
b. The Annex also contains the relevant restrictions included in Letters of Agreement (LoA) between adjacent ATC Units requested to be “H” Hard checked. These restrictions are named “Cross-border”.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 6 of 16
https://www.nm.eurocontrol.int/RAD/index.html
Fictitious Example
Change record Airway FROM TO
Point or Airspace Utilization
Restriction Applicability ID Number Operational Goal Remark/s
ATC Unit
UL1 AAAAA BBBBB Not available for DEP … H24 L_E_1001 To segregate traffic E_ _ _ ACC
CCCCC Only available for traffic ARR … 23:00 - 05:00
(22:00 - 04:00) E_L_2033 To dualise the traffic … FRA application L_ _ _ ACC
Airspace E_ _ _ES Compulsory for traffic
DEP/ARR … 06:00 - 22:00
(05:00 - 21:00) E_2002 To force traffic … E_ _ _ ACC
3.2. Restriction structure 3.2.1. Each restriction is hierarchical and specific and has been arranged to facilitate parsing of the information
into computer systems. 3.2.2. For the usage of the restricted object (significant point, ATS route segment, defined DCT, airspace
volume (ATC Unit, AoR of relevant ATC Unit - CTA/UTA, TMA, CTR or individual control sector/s within an ATC unit), etc.) there are 3 (three) main types of restrictions: a. Not available for …
Flight planning via restricted object is forbidden for described flow(s). b. Only available for …
Flight planning via restricted object is allowed exclusively for described flow(s). c. Compulsory for …
Flight planning via restricted object is the only valid option for described flow(s). 3.2.3. For the combination of elements that define the flow of traffic, there are 2 (two) types of restrictions -
inclusive and exclusive:
a. INCLUSIVE restriction - traffic must meet ALL of the conditions to be subject to the restriction. The implicit logical operator between the listed conditions is an “AND” - Logical Conjunction.
Fictitious Example
Airway From - To Restriction
UL1 AAAAA - BBBBB
Not available or Only available or Compulsory for traffic Above FL275 With DEP … With ARR
b. EXCLUSIVE restriction - traffic only needs to meet ONE of the numbered sub-conditions to be
subject to the restriction. The implicit logical operator between the numbered conditions is an “OR” - Logical Disjunction.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 7 of 16
https://www.nm.eurocontrol.int/RAD/index.html
Fictitious Example
Airway From - To Restriction
UL1 AAAAA - BBBBB
Not available or Only available or Compulsory for traffic 1. ARR ….. 2. Via … Except
a. ARR …… b. DEP…..
3. Via … with ….. 3.2.4. Usage of combinations and terms in utilization expression
If circumstances allow or if it is required for better expression of the utilization, the 3 (three) usage types can be combined as follows:
a. “Only available” and “Compulsory” might be used in combination, resulting in “Only available and
Compulsory”.
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB Only available and Compulsory for traffic ARR ….
b. “Only available …” together with “Not available …”, are combined by using the formula: “Only available for … Except …”
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB Only available for traffic ARR …. Except Via…
c. Combining “Compulsory… ” with “Not available…. ” is NOT POSSIBLE. The TWO independent
numbered expressions shall be given within the same box.
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB
1. Compulsory for traffic ARR …. Via… Above FL245 at… 2. Not available for traffic DEP ….
d. term “Except” to define usage:
The expression “Not available for traffic except …” shall be avoided, “Only available for traffic…” shall be used instead.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 8 of 16
https://www.nm.eurocontrol.int/RAD/index.html
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB Not available for traffic Except DEP …. It is the same as below which is clearer.
UL1 AAAAA - BBBBB Only available for traffic DEP ….
e. The expression “Only available for traffic except” shall be used only if the combination of elements is inclusive.
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB
Only available for traffic ARR …. Via… Above FL245 at… Except DEP ….
f. If the combination of elements is exclusive, it can lead to two different ways of interpretation. To
have the required effect TWO (or more) independent numbered expressions shall be given within the same box.
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB
Only available for traffic 1. Except DEP …. 2. ARR ….Via… 3. ARR…Via…
Shall be expressed as:
UL1 AAAAA - BBBBB
1. Only available for traffic a. ARR ….Via… b. ARR… Via… 2. Not available for traffic DEP ….
g. The word “except” used in expression of utilization can also be used in between brackets to exclude
relevant destinations from Area/Group definitions; FIR/UIR; ACC/UAC; etc. used as terminal conditions.
Fictitious Example
Airway From - To Utilization
UL1 AAAAA - BBBBB Only available for traffic ARR nnnnnnn Group (except nnaa) Via…
h. The 2 (two) combination of elements types might also be used alone or in combination.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 9 of 16
https://www.nm.eurocontrol.int/RAD/index.html
3.2.5. The term Requested FL (RFL) is used for RAD purposes and refers to the actual requested cruising level
as specified in the ICAO flight plan field 15. Where it is used it shall be applied only to the State/FAB/ANSP in question unless otherwise specified. If a restriction specifies FL that is understood to be the flight level measured against IFPS calculated profile and is checked accordingly.
3.2.6. Restrictions for the same restricted object (significant point, ATS route segment, defined DCT, airspace volume (ATC Unit, AoR of relevant ATC Unit – CTA/UTA, TMA, CTR or individual control sector/s within an ATC Unit), etc) may be identified by more than one unique identifier. A single restriction should aim at containing all the flow elements that concerns a single operational goal or closely relation operational goals.
3.2.7. State/FAB/ANSP restrictions shall be uniquely identified by a 6 (six) digit alpha/numeric identifier
which comprises the ICAO nationality letters for location indicators assigned to the State of origin or 2 (two) letter Regional / FAB naming convention prefix code, together with a 4 (four) digit number (LF2016, DU2001, RE2001). Exception from above rules is allowed for DCT identification in Appendix 4 where a maximum 9 (nine) digit alpha/ numeric identifier containing 5 (five) digit number might be used (LF50001, DU52345, RE54999, DSYX50000) and FUA Restrictions in Appendix 7.
3.2.8. Cross-border (RAD) restrictions 3.2.9. FUA restrictions Identification
The FUA restrictions shall be identified as follows: Restricted Airspaces Identifier (RSA ID) as published in State AIP followed by 1 letter R, S, T,
U, V, W, X, Y (LBTSA11R); or Restricted Airspaces Identifier (RSA ID) as published in State AIP followed by 1 letter Z
indicating FBZ existence followed by 1 letter R, S, T, U, V, W, X, Y (LBTSA11ZR). Note: In case of more than 8 FUA restrictions per RSA the NM RAD Team in coordination with relevant NRC/s and/or other NMOC Team/s is authorised to use other letters starting with Q on reversed order (Q, P, N, M, etc. with no use of letters “O” and “I”).
When more than one FUA restriction is used for same RSA, the last letter shall be assigned based on the following rules: R - describes the most restrictive limitation/s in RSA availability; S - describes the less restrictive limitation/s different from those under letter “R”; T, U, V, W, X, Y - same descending logic as for letter “S”.
3.2.10. 3.2.8.1 Definition
RAD restrictions, except if otherwise mutually agreed by the States/FABs/ANSPs, shall be categorized as being cross-border when they are referenced to: a) boundary significant point; b) ATS route segment or DCT starting from or ending at boundary significant point; c) cross-border ATS route segment via boundary significant point or cross-border DCT.
3.2.8.2 The referenced significant point shall be located on common boundary between two adjacent airspaces.
The concerned airspaces might be FIRs/UIRs or ACCs/UACs or CTAs/UTAs or FABs or combination of them. These airspaces shall not be inside the same FAB, if FAB prefix code is used in identification.
3.2.8.3 Cross-border restrictions might be or might not be part of the relevant LoA. Clear explanation for that shall be given by the appropriate National RAD Coordinator (NRC) in Column “Operational Goal”.
3.2.8.4 For any State/FAB/ANSP restriction, not defined as cross-border and considered that has impact on adjacent State/FAB/ANSP clear explanation for that shall also be given by the appropriate National RAD Coordinator (NRC) in Column “Operational Goal”.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 10 of 16
https://www.nm.eurocontrol.int/RAD/index.html
3.2.8.5 Identification Cross-border restrictions shall be identified with an 8 (eight) digit alpha/numeric identifier as follows: a) twice ICAO nationality letters for location indicators assigned to the State followed by 4 (four)digit
number (EGEB1009); or b) twice 2 (two) letter Regional / FAB naming convention prefix code followed by 4 (four) digit
number (DUBM1001); or c) ICAO nationality letters for location indicators assigned to the State and 2 (two) letter Regional /
FAB naming convention prefix code or vice-versa followed by 4 (four) digit number (LWBM1001, DULY1001).
3.2.8.6 First two letters are identifying the State / FAB / ANSP performing the ATC action, while the second
two letters - State / FAB / ANSP affected by that action.
3.2.8.7 The Maastricht UAC restrictions are considered as cross-border and shall be identified as follows: a) inside AoR: ICAO nationality letters for location indicators assigned to the relevant State (EB, ED
EH) and 2 (two) letters “YX” followed by 4 (four) digit number (EBYX1009); b) outside AoR: 2 (two) letters “YX” and ICAO nationality letters for location indicators assigned to
the neighbouring State or 2 (two) letter Regional / FAB naming convention prefix code followed by 4 (four) digit number (YXED1001, YXIU1002).
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 11 of 16
https://www.nm.eurocontrol.int/RAD/index.html
3.2.8.8 Coordination
Cross-border restrictions shall be coordinated between the NRCs of the States/FABs/ANSPs concerned BEFORE submission for inclusion in the RAD. Any cross-border restriction discovered by the NM RAD Team that has not been coordinated will be removed from the RAD until the coordination process has been completed.
3.2.11. Identifiers shall be assigned at RAD document as per tables below:
Group ID Origin ID Restriction type Restriction subtype Publication
1 - 99 Country code or ATC Units or Regional / FAB ID DCT DCT limit inside ATC Units Appendix 4
400 Country code or ATC Units or Regional / FAB ID DCT Cross-border DCT limit Appendix 4
1000 - 1499 Country code or Regional / FAB ID(s) Traffic Flow Cross-border restrictions Pan-European Annex
2000 - 3999 Country code or Regional / FAB ID Traffic Flow State/FAB/ANSP restrictions
Pan-European Annex
4000 - 4999 Country code or Regional / FAB ID(s) Traffic Flow City pair level capping Appendix 3
5000 - 5499 50000 - 54999
Country code or Regional / FAB ID(s) Traffic Flow
Conditions on DCT segments Point-to-Point Appendix 4
5500 - 5999 Country code or Regional / FAB ID Traffic Flow Conditions on DCT segments to/from airfields Appendix 5
6000 - 6999 Country code or Regional / FAB ID(s) Traffic Flow Plain text notes Whole document
7000 - 7499 Country code or Regional / FAB ID(s) Traffic Flow Military restrictions Whole document
8000 - 8999 Country / FIR or Regional / FAB code ID Traffic Flow Flight Profile Restrictions Appendix 6
R, S,… Y RSA ID as per AIP FUA FUA Appendix 7
Prefix code Region / FAB / ANSP (State / ANSP) BL BALTIC FAB (Poland, Lithuania) BM BLUE MED FAB (Italy, Greece, Cyprus, Malta)
CE FAB CE - FAB CENTRAL EUROPE (Austria, Czech Republic, Croatia, Hungary, Slovakia, Slovenia, Bosnia and Herzegovina) DU DANUBE FAB (Bulgaria, Romania) DS DENMARK / SWEDEN FAB (Denmark, Sweden)
EC FABEC - FAB EUROPE CENTRAL (France, Germany, Switzerland, Belgium, Netherlands, Luxembourg, Maastricht UAC) NE NORTH EUROPEAN FAB (Estonia, Finland, Latvia, Norway) PE SOUTH WEST FAB (Spain / Portugal) IU UK / IRELAND FAB (United Kingdom, Ireland) YX Maastricht UAC RE Regional / Pan-European / Axis
3.2.12. Where date/time ranges are used these shall be considered as INCLUSIVE. When time periods are
expressed in column RESTRICTION or column UTILIZATION, restrictions are not applied outside those published times unless otherwise specified.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 12 of 16
https://www.nm.eurocontrol.int/RAD/index.html
3.2.13. A restriction shall not qualify for inclusion in the RAD unless it has a FLOW ELEMENT attached to it.
A FLOW ELEMENT is defined as affecting either: a. Departures from an Airfield/Group/Area; b. Arrivals to an Airfield/Group/Area; c. Traffic flying between Airfields/Groups/Area; d. Overflying traffic.
3.3. Time periods 3.3.1. The time periods are in Co-ordinated Universal Time (UTC) used by air navigation services and in
publications issued by the AIS. The expression “summer period” indicates that part of the year in which “daylight saving time“ is in force. The other part of the year is named the “winter period”. Times applicable during the “summer period” are given in brackets. Daylight saving time is UTC plus 1 hour. The “summer period” in Europe is introduced every year on the last Sunday in MAR at 01:00 UTC and ceases on the last Sunday in OCT at 01:00 UTC. For detailed description in each State the relevant AIP shall be checked.
3.3.2. Details of weekend periods, if and when used are included where relevant. The start and end time of the
periods relates to the entry to the segment concerned. 3.3.3. Additional periods can be declared as weekends (e.g. Busy Fridays, Nights, Bank Holidays), refer to
national publication and relevant annex for the details. 3.3.4. To access data regarding Public Holidays pertinent to each State, refer to GEN 2.1 of the respective AIP. 3.4. Definition of limits expressed by FL 3.4.1. The vertical limits shall be expressed as follows (ref. ERNIP Part 1):
a. above the lower limit or minimum en-route altitude and below FL290 - VFR flight levels in accordance with ICAO Annex 2, Appendix 3, page 1 (e.g. FL035 or corresponding altitude… FL285);
b. above FL290 and below FL410 in RVSM areas - number representing the layer/ intermediate level between IFR flight levels ending on ..5 (e.g. FL295 …FL405);
c. above FL410 or above FL290 in non RVSM areas - number representing the layer/ intermediate level between IFR flight levels ending on ..0 (e.g. FL420 …FL500 … ).
3.5. Expression of abbreviated words meaning Departure and Destination 3.5.1. In all Appendixes and Pan-European Annex, if and when used and required the expression of
abbreviated words meaning Departure and Destination from/to certain airport/s or in/outside FIR/UIR / ACC/UAC / ATC Units shall be used based on ICAO Doc. 8400 - Abbreviations and Codes as follows: a. DEP - code meaning “Depart” or “Departure”; b. ARR - code meaning “Arrive” or “Arrival”.
4. PERIOD OF VALIDITY 4.1. The routeing organisation is permanently effective and applies daily H24, except where otherwise
specified. When it can be identified that capacity is surplus to demand the RAD restrictions may be relaxed from the H24 time constraints.
4.2. The RAD may be suspended, or temporarily relaxed, in cases where it has an abnormally adverse impact
upon the traffic flows. This action will always be co-ordinated through the CDM process between the Network Manager and its Operational Stakeholders.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 13 of 16
https://www.nm.eurocontrol.int/RAD/index.html
5. APPLICATION 5.1. The RAD will be fully integrated into the Network Manager Operational systems, including IFPS,
through the Route Restrictions computer model. Any changes to the Pan-European Annex will automatically be checked provided the relevant notification period has been observed.
5.2. Changes agreed outside the AIRAC cycle will not be handled automatically by IFPS until such time as
the system can be updated at the appropriate AIRAC date. 6. CDM PROCESS 6.1. Amendments to the General Description of the RAD, or the period of validity, shall be co-ordinated
between the Network Manager and the Operational Stakeholders via the RAD Management Group (RMG) and approved by NETOPS team. Inclusion or withdrawal of additional Annexes or Appendixes shall follow the same process.
6.2. The Operational Stakeholders shall provide their request for changes to the NM RAD Team, taking into
account agreed publication and implementation dates, in accordance with AIRAC procedures and Handbook Supplement for the Provision of Environment data.
6.3. All new RAD restrictions, amendments and changes will be checked by the NM RAD Team versus
airspace organisation in the area. Any possible discrepancies will be notified to the States/FABs/ANSPs concerned as soon as possible.
6.4. Suspension of NAVAIDS, and/or replacement by temporary mobile units will be promulgated via the
Pan-European Annex. States should ensure that the NM RAD Team is notified of these changes. 6.5. The final content of any amendment to the RAD shall be positively agreed between the NM RAD Team
and State/FAB/ANSP concerned. This agreement shall be reached in a form of e-mail confirmation, meeting report/minutes or any other means reflecting final mutual agreement for change. These agreements will be properly recorded by the Network Manager.
6.6. Amendments will be published by the NM RAD Team as follows:
a. 28 34 days in advance of the relevant AIRAC cycle; b. Until the establishment of an automated RAD process amendments will be highlighted in
RED/BLUE BOLD and will be annotated by abbreviation NEW/AMD; c. Restrictions that have been removed will be annotated abbreviation DEL; d. “Last minute” changes: are changes required due to exceptional circumstances and/or only when they have a significant
impact on operational requirements; shall be:
announced by the NRCs as ordinary amended or new RAD requirements; exceptionally annotated as such; sent via e-mail to the NM RAD Team in accordance with ERNIP Part 4;
will be promulgated on the NM NOP portal via the “Increment File”. will be announced by the NM RAD Team via e-mail to the Operational Stakeholders similarly
as RAD distribution.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 14 of 16
https://www.nm.eurocontrol.int/RAD/index.html
7. TEMPORARY CHANGES 7.1. Temporary changes due to exceptional circumstances (e.g. major equipment failure, industrial action or
large-scale military exercises) may necessitate the suspension of part of the RAD for specified periods, and additional routeings will be activated where possible following co-ordination with the relevant FMPs and AOs.
7.2. Temporary changes will be published by AIM giving details of the traffic affected, the period of
activation and the corresponding routeings. 8. FLIGHT PLANNING 8.1. The RAD defines restrictions on routes/points, through specified areas during the published period of
validity. Aircraft operators planning flights through these areas must flight-plan in accordance with these route restrictions, taking into account any change of validity.
8.2. When a route is restricted between two points it must be understood that all segments, between the
recorded points, are included in the restriction. 8.3. An operator who has submitted a flight plan for a route and wishes to change to another route must
either; send a CHG (Change) message giving the new route or; cancel the existing flight plan and submit a new flight plan following the replacement flight plan procedure. This applies equally to re-routeing proposed by the Network Manager and to changes made at the initiative of the AO.
8.4. When filing flight plans, AOs must comply with any flight level limitation published in the RAD. AOs
shall be aware that when receiving the confirmed FPLs the FLs used are NOT checked against the Flight Level Orientation Scheme (FLOS) applied by the State concerned.
8.5. AOs shall also be aware that when receiving the confirmed FPLs using DCT options from Appendixes 4
and 5 these flight plans are NOT checked against Minimum Sector Altitudes (MSA) or Minimum En-route Altitudes (MEA) published by the States in the relevant parts of their AIPs. In accordance with provisions of ICAO Doc 4444 - ATM (PANS-ATM) AOs remains responsible with the checking of MSA and/or MEA. Note: Refer to IFPS User’s Manual for full details.
9. ROUTEING SCENARIOS 9.1. For each area expected to be critical, a number of flows could be identified, for which other routeings
are available, that follow the general scheme, but avoid the critical area. These are known as routeing scenarios.
9.2. When, during the planning phase, the Network Manager identifies the risk of major imbalance between
demand and capacity, it may be decided, after agreement with all FMPs concerned, to make part (or all) of the alternative routeings mandatory for the period expected to be critical.
9.3. Scenarios may be identified which require the temporary suspension of route restrictions within the
RAD for a particular traffic flow. 9.4. The list of available scenarios is promulgated on the NM NOP portal.
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 15 of 16
https://www.nm.eurocontrol.int/RAD/index.html
10. PUBLICATION 10.1. The RAD is created in accordance with ICAO publication procedures and is published on the NM NOP
website, 28 34 days in advance prior to the relevant AIRAC cycle. 10.2. Each State may promulgate the RAD by any one of the following methods:
a. Publish the RAD in its entirety as an AIP Supplement (the onus is on the State to ensure that the RAD is kept up to date);
b. Publish relevant Appendices and State/FAB/ANSP part of the Pan-European Annex of the RAD as an AIP Supplement;
c. Publish reference to the NM NOP website in the AIP.
DAY PROCESS ACTION
D-63 Notification to States/FABs/ANSPs "One week to Cut-off". NM
D-56 Finalisation of States/FABs/ANSPs requirements. States/FABs/ANSPs Cut-off date. States/FABs/ANSPs provide amendments to the NM. Three weeks to compile the RAD and to resolve errors/conflicts. NM
D-28 34 Publication. NM Two weeks to assess impact of new restrictions.
D-14 Results of impact assessment of new restrictions.
NM Changes/amendments to be promulgated via the “Increment File” on the NM NOP Portal.
D-10 Freeze of ENVironment tape for AIRAC. NM
10.3. Where applicable, publication of route availability in national aeronautical information publications
shall be fully consistent with this common reference document. 11. TACTICAL OPERATIONS 11.1. The Network Manager in conjunction with the FMPs will monitor the actual situation during the day of
operation to ensure the RAD is achieving the balance of traffic required. 11.2. During periods of unanticipated high demand the Network Manager may co-ordinate an extension to the
period of validity of routeing scenarios with the relevant FMPs. This will be published by AIM, giving at least three hours notice.
11.3. During periods of significant improvement to the ATFCM situation, the Network Manager will co-
ordinate with the relevant FMP, a reduction in the period of validity of scenarios. This will be published by AIM.
11.4. If, due to a major unexpected event, there is a significant disturbance to traffic patterns, after co-
ordination with the relevant parties (FMPs and AO’s), the Network Manager may suspend part of the RAD and provide alternative routeings.
11.5. With effect from AIRAC -6 day (D -6), implemented RAD Data is considered as Operational.
Management of such changes to the RAD is the responsibility of the NRC of the originating State
Updated on 25/0431/08/19
RAD General Description Introduction
Valid from 20/0612/09/19
Page 16 of 16
https://www.nm.eurocontrol.int/RAD/index.html
11.6. If, after AIRAC -6 day (D -6), a State discovers an error or omission to the RAD that is SAFETY
RELATED, then it is the responsibility of the NRC to contact the NM RAD Team to request a live update of the NM CACD in order to correct the problem. The safety related RAD error or omission shall be exceptionally annotated as such and shall be sent via e-mail to the NM RAD Team in accordance with ERNIP Part 4. The NM RAD Team will only act after consultation with the NRC or his designated Deputy. Following the consultation process the NM RAD Team shall create the necessary DMR and the change shall be promulgated via the “Increment File”. During the weekend, the ACC shall contact the Current Operations Manager and the matter shall be handled MANually. A second alternative is to request that the restriction in question be DISABLED in ENVironment so that there will not be a check at IFPS.
12. RAD REVIEW 12.1. The NM RAD Team is responsible for coordination of the entire RAD review process. 12.2. The RAD review is required to ensure that all data contained within the RAD is current and correct. The
review is also the opportunity to ensure that any modifications, within the incremental update to the Network Manager Operational systems, are reflected in the construction of RAD restrictions.
12.3. A RAD review for each and every Annex/Appendix, including cross-border restrictions, shall be
completed annually during designated meetings and as a rolling process by the NM RAD Team. The existing South West, South East, North West, North East or Ski - Airspace or ATFCM meetings could be used for RAD review purposes. Additional ad-hoc RAD review meetings could be organised in case of any urgent issues to be discussed.
12.4. The outcome of each RAD review shall be properly documented through the report or minutes. The
reports/minutes will be stored by the NM RAD Team. 12.5. Each State/FAB/ANSP shall convene an internal RAD review with the airlines concerned. Such an
internal review shall be announced to the NM RAD Team and shall cover as minimum the validity of all restrictions; the timeliness of restrictions; the completeness of all restrictions. The NM RAD Team may offer items to be covered. The results of such an internal review shall be passed to the NM RAD Team as soon as possible.
12.6. For each cross-border RAD review the NM RAD Team shall perform a RAD impact assessment on each
relevant restriction. This analysis shall be carried out together with the Operational Stakeholders. 12.7. The NM RAD Team shall maintain a List of proposed/requested by the AOs RAD restrictions for
consideration by the States/FABs/ANSPs. The List shall contain the restrictions traceability and shall record the proposal’s status as change/removal/update till RAD restriction resolution or deletion.
RAD 1911 Appendix 2Area Definitions
Valid From 10/10/2019
Changerecord ID Definition Remark OWNER
AMD LILLE_GROUP LFAC, LFAQ, LFAT, LFAV, LFAYLFQQ, LFQO, LFQT LF
BREST_GROUP LFRB, LFRU, LFRO, LFRJ LF
SEVERN_GROUP
EGFF, EGFHEGGDEGSY EG
BERLIN_YZ_GROUP EDAE, EDAV, EDAY, EDBW, EDON ED
GENEVA_AREA
LSER, LSEZLSGB, LSGC, LSGE, LSGK, LSGN, LSGR, LSGS, LSGT, LSGYLSEA, LSEC, LSEG LSMPLSTB, LSTO, LSTR, LSTS, LSTZ
LS
OUTSIDE_GROUP
BG**,BI**,C***,K***,M***,P***,R***,V***,Z***,D***,F***,H***,O***,W***,Y***,A***,N***,S***,T***,UA,UE**,UH**,UI**,UL**,UO**,UR**,US**,UT**,UU**,UW**,GA**,GB**,GF**,GG**,GL**,GO**,GQ**,GS**,GU**,GV**,UN** NM
VALENCIA_GROUP
LEALLELCLEVCLEMI
LE
NAT_GROUP {Traffic crossing Reykjavik BIRDFIR, Shanwick EGGXFIR, Santa Maria LPPOFIR, Gander CZZZFIR, New YorkKZWYFIR airspace} NM
HAVEL_GROUP
EDAD, EDAE, EDAI, EDAP, EDAS, EDAV, EDAYEDBE, EDBF, EDBG, EDBK, EDBO, EDBQ, EDBWEDCE, EDCF, EDCL, EDCQ, EDCSEDHCEDOC, EDOD, EDOG, EDOI, EDOJ, EDOL, EDOM, EDON, EDOR, EDOV, EDOY, EDOZEDUA, EDUF, EDUG, EDUS, EDUZ
ED
NANTES_GROUP LFRE, LFRI, LFRS, LFRZ, LFFI, LFOU, LFEY LFBRNO_GROUP LKTB, LKKU, LKNA LK
BASEL_GROUP
LFGALFGBLFSBLFSM
LF
LIMOGES_GROUP
LFBL, LFBK, LFBULFLDLFOALFSL
LF
BERN_GROUPLSMA, LSMELSZB, LSZG, LSZC LS
Changerecord ID Definition Remark OWNER
FRANKFURT_GROUPEDDFEDFEETOU
ED
FRANKFURT_YZ_GROUPEDEF, EDELEDFA, EDFB, EDFC, EDFD, EDFG, EDFO, EDFP, EDFU, EDFY, EDFZEDGP
ED
ZURICH_AREA
LSMA, LSMD, LSME, LSMF, LSML, LSMM, LSXILSZA, LSZB, LSZC, LSZG, LSZH, LSZL, LSZR, LSZSEDNYEDTD, EDTM
LS
OSTGOTA_GROUP
ESCFESKK, ESKNESOEESSL, ESSPESVK
DS
METZ_GROUP
LFJLLFOKLFQA, LFQBLFSN
LF
NURNBERG_AREA
EDDNEDQA, EDQC, EDQD, EDQE, EDQF, EDQH, EDQI, EDQK, EDQM, EDQN, EDQO, EDQP, EDQR, EDQS, EDQT,EDQW, EDQX, EDQY, EDQZETEB ETICETOI
ED
MALMO_AREA ESGF, ESGM, ESGVESMG, ESMU, ESMV, ESMX, ESMY DS
GOTHENBURG_AREA
ESFAESGF, ESGN, ESGRESIAESMF, ESMH, ESMT, ESMUESTA, ESTL
DS
STOCKHOLM_AREA
ESCFESGJESIAESKG, ESKK, ESKN, ESKTESOE, ESOLESQOESSC, ESSD, ESSG, ESSI, ESSK, ESSL, ESSP, ESSWESVA, ESVB, ESVK, ESVQEFMA
DS
Changerecord ID Definition Remark OWNER
DUBLIN_GROUPEIDG, EIDWEIMEEIWT
EI
SATENAS_GROUP
ESENESFRESGL, ESGO,ESGTESIB
DS
BARCELONA_GROUP
LEBLLEDALEGELERSLELL
LE
FRIESLAND_GROUP
EDVHEDWE, EDWF, EDWG, EDWH, EDWI, EDWJ, EDWK, EDWL, EDWM, EDWQ, EDWR, EDWS, EDWU, EDWX,EDWY, EDWZEDXI, EDXL, EDXP, EDXQ, EDXS, EDXU, EDXZ
ED
PARDUBICE_GROUP LKPD, LKCV, LKHK LK
TRONDHEIM_GROUPENRTENTRENVA
EN
CANTABRICO_GROUP
LEBBLEBGLEPPLERJLESOLEVTLEXJ
LE
HAMBURG_GROUP EDDHEDHI, EDHL ED
SHANNON_GROUP
EICK EIDL EIKNEIKY EINNEISG EIWF
EI
Changerecord ID Definition Remark OWNER
AZORES_GROUP
LPAZLPCRLPESLPFLLPGRLPHRLPLALPPDLPPILPSJ
LP
AJACCIO_GROUP LFKF, LFKG, LFKJ, LFKO LF
AMSTERDAM_GROUP
EHAMEHHVEHKDEHLEEHRDEHTX
EH
BALEARES_GROUP
LEIBLEMHLEPALESB, LESJ, LESL
LE
BASTIA_GROUP LFKB, LFKC, LFKS LF
BEAUVAIS_GROUP LFOB, LFOE, LFOH, LFOK, LFOPLFRC, LFRG, LFRK LF
BELFAST_GROUP EGAA, EGAC, EGAD, EGAE, EGAL EG
BIARRITZ_GROUPLFBY, LFBZLFCZLESO
LF
BORDEAUX_GROUPLFBC, LFBD, LFBE, LFBG, LFBS, LFBXLFCH, LFCYLFDI
LF
BRIZE_GROUPEGBJEGDLEGVA, EGVN
EG
BRUSSELS_GROUP
EBAWEBBREBCI, EBCVEBMB
EB
Changerecord ID Definition Remark OWNER
BUDAPEST_GROUP
LHBP, LHBSLHDKLHEMLHFHLHGDLHHHLHTL
LH
CHAMBERY_GROUPLFHM, LFHULFKA, LFKXLFLB, LFLE, LFLJ, LFLP
LF
CLERMONT_FERRAND_GROUPLFHA, LFHQLFKMLFLC, LFLV, LFLZ
LF
COPENHAGEN_GROUP
EKCHEKFREKGH, EKGLEKHE, EKHK, EKHOEKRH, EKRK, EKRS
EK
CYCLADES_GROUP
LGMKLGNXLGPALGSO
LG
DEAUVILLE_GROUP LFRC, LFRG, LFRKLFOH LF
DUESSELDORF_GROUP
EDDG, EDDK, EDDLEDGSEDKB, EDKLEDLA, EDLE, EDLM, EDLN, EDLP, EDLV, EDLWETNG, ETNN
ED
EAST_ANGLIAN_GROUPEGSHEGUL, EGUNEGYM
EG
FARNBOROUGH_GROUP
EGHLEGLF, EGLKEGTD, EGTFEGVO
EG
FARRIS_GROUP
ENFZENJBENLUENRK, ENRYENSNENTO
EN
Changerecord ID Definition Remark OWNER
GALICIA_GROUPLECOLESTLEVX
LE
GENEVA_GROUPLSGG, LSGL, LSGPLFLILFHN
LS
GOTHENBURG_GROUP
ESFRESGA, ESGC, ESGD, ESGE, ESGG, ESGH, ESGI, ESGJ, ESGK, ESGL, ESGM, ESGP, ESGT, ESGU, ESGVESIBESMG, ESMV, ESMYESSI
ES
GRONINGEN_GROUP
EHGGEHHOEHLWEHTE
EH
HAAMSTEDE_GROUP
EHBDEHEHEHGREHMZEHRDEHSEEHVKEHWO
EH
IONIAN_GROUP
LGADLGKC, LGKF, LGKL, LGKRLGPZLGRXLGZA
LG
ISTANBUL_GROUP LTBA, LTBR, LTBWLTFJ LT
JERSEY_GROUP EGJA, EGJB, EGJJ EG
KARLSTAD_GROUP
ESEUESGA, ESGN, ESGS, ESGU, ESGYESHVESKH, ESKO, ESKU, ESKVESOH,ESOKESSM, ESSTESTF
ES
KJEVIK_GROUPENARENCNENGK
EN
Changerecord ID Definition Remark OWNER
LISBON_GROUP
LPARLPCSLPMTLPPT
LP
LONDON_GROUP
EGGWEGKB, EGKKEGLC, EGLLEGMCEGSC, EGSSEGTOEGWU
EG
LONDON_SOUTH_GROUP
EGGWEGKB, EGKKEGLC, EGLLEGMCEGTOEGWUFARNBOROUGH GROUP
EG
LYON_GROUP
LFHJ, LFHS, LFHV, LFHWLFKL, LFKYLFLG, LFLL, LFLM, LFLS, LFLU, LFLYLFMHLFXA
LF
MADRID_GROUP
LECULEGTLEMDLETOLEVS
LE
MALAGA_GROUP
LEAMLEGRLEMGGEML
LE
MALMO_GROUPESFAESME, ESMF, ESMH, ESMI, ESMJ, ESMK, ESML, ESMS, ESMTESTA, ESTL, ESTT
ES
MANCHESTER_GROUPEGCCEGGPEGNR
EG
MIDLANDS_GROUP EGBB, EGBEEGNX EG
MILANO_GROUP LIMA, LIMB, LIMC, LIME, LIMF, LIMG, LIMJ, LIML, LIMN, LIMP, LIMS, LIMW, LIMZLSZA, LSZL, LSZS LI
MONTPELLIER_GROUP LFMT, LFMULFNG LF
Changerecord ID Definition Remark OWNER
MUNICH_GROUP EDDM, EDDNEDMA, EDMO ED
NICE_GROUP LFMD, LFMF, LFMNLFTZ LF
ORLY_GROUP LFAILFPM, LFPN, LFPO, LFPV LF
OSLO_GROUP
ENDHENEGENGMENHA, ENHSENKJENLXENRH, ENRV, ENRXENSIENUH
EN
PADOVA_GROUPLIPA, LIPB, LIPC, LIPD, LIPE, LIPG, LIPH, LIPI, LIPK, LIPL, LIPN, LIPO, LIPQ, LIPR, LIPS, LIPU, LIPV, LIPX,LIPY, LIPZLIRP, LIRQ {only for traffic DEP,Overfly LOVVFIR, LJLAFIR, LDZOFIR, LIBBFIR, EDMMFIR}
LI
PALMA_GROUP LEPALESB, LESJ LE
PARIS_GROUP LFPB, LFPC, LFPG, LFPN, LFPO, LFPT, LFPV LF
POITIERS_GROUP LFBI, LFBNLFLX LF
PRAGUE_GROUPLKKBLKPRLKVO
LK
PROVENCE_GROUP LFMA, LFML, LFMO, LFMQ, LFMV, LFMYLFNE, LFNF, LFNT LF
PYRENEES_GROUPLFBA, LFBP, LFBTLFCNLFDH
LF
RENNES_GROUP LFRN, LFRD, LFRT LF
RHONE_GROUPLFHOLFME, LFMI, LFMSLFTW
LF
ROISSY_GROUP LFPB, LFPC, LFPG, LFPT LFROME_GROUP LIRA, LIRE, LIRF, LIRU LI
SCOTTISH_GROUP EGPF, EGPG, EGPH, EGPK, EGPNEGQL EG
SEVILLE_GROUP
LEJRLEMOLERTLEZL
LE
Changerecord ID Definition Remark OWNER
SAINT_YAN_GROUP
LFGM, LFGNLFHYLFLN, LFLOLFQF
LF
STOCKHOLM_GROUP
ESCMESKCESOWESSA, ESSB, ESSE, ESSN, ESSU, ESSX, ESSZ
ES
STRASBOURG_GROUP
LFGCLFQPLFSTEDSB, EDSK, EDSWEDTB, EDTL, EDTO
LF
TOULON_GROUP LFMCLFTF, LFTH LF
TOULOUSE_GROUP
LFBF, LFBO, LFBRLFCI, LFCK, LFCL, LFCQ, LFCXLFDB, LFDG, LFDJLFIR, LFITLFMG, LFMK, LFMW
LF
DUESSELDORF_YZ_GROUP EDKA, EDKB, EDKW, EDKZEDLA, EDLE, EDLM, EDLS ED
MUERITZ_YZ_GROUP
EDAN, EDAXEDBN, EDBP, EDBU, EDBV, EDBYEDCA, EDCP, EDCR, EDCU, EDCV, EDCW, EDCXEDOWEDUW
ED
STUTTGART_YZ_GROUP
EDFVEDGOEDMB, EDMC, EDMG, EDMH, EDMTEDND, EDNE, EDNG, EDNL, EDNT, EDNO, EDNQ, EDNWEDPA, EDPB, EDPJ, EDPM, EDPT, EDPU, EDPYEDRYEDSA, EDSH, EDSWEDTB, EDTF, EDTH, EDTN, EDTO, EDTW, EDTX, EDTY
ED
Column content explanation
“Change record”Describes current status of each AREA/GROUP/YZ_GROUP definition. It might be either "BLANK BOX" or AMD or NEW or DEL.“ID” “Area Definition ” or “Group Definition” or “Y/Z Group Definition” Describes the name ID of each relevant AREA or GROUP or Y/Z YZ_GROUP. It contains either city names or geographical location names followed by _AREA, _GROUP or _YZ_GROUP. “Definition” “Area Airports” or “Group Airports” or “Y/Z Group Airports” Describes the airports aerodromes or aerodrome sets in each relevant AREA or GROUP or YZ_GROUP. It contains full 4 letter ICAO location indicator for all the airports aerodromes. The airports aerodromes and aerodrome sets are ordered on alphabetical order and on new rows inside thesame box differentiated by either second or third letter. The airports with same three first letters “Owner”It contains the owner NRC CODE of the RAD Aerodrome Set. A RAD Aerodrome Set can only be changed
Legend for "Change record" column:
BLANK BOX - existing Area Definition
AMD - Area Definition amended.The row blank box will be replaced by abbreviation AMD. Amendments are depicted in RED/BLUE BOLD text depending on internal procedures,if previously published in RAD Increment file they will be depicted in BLACK BOLD text.NEW - Area Definition new.The row abbreviation is NEW and whole row is depicted in RED/BLUE BOLD text depending on internal procedures,if previously published in RAD Increment file they will be depicted in BLACK BOLD text.If there are NO amendments in next RAD edition the row abbreviation NEW will be withdrawn and blank box will DEL - Area Definition deleted.The row blank box will be replaced by abbreviation DEL. Deletion is presented as RED/BLUE BOLD "Strikethrough" text depending on internal procedures,if previously published in RAD Increment file they will be depicted in BLACK BOLD text.
Note: The abbreviations above are used only for the RAD purposes.
RAD 1913 Appendix 3Flight Level Capping limits
Each FL capping limitation is applied for the entire flight from airport of departure (ADEP) until airport of destination (ADES)
Valid From 05/12/2019
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
AMD EG4054 EGTTFIR except (MANCHESTER_GROUP, EGCN/NM/NV) (PARIS_GROUP, LFOB/OP/RG) Not above FL295 H24
AMD LF4296 (LFLL/LS/LY/LB/LP) (LFPO) Not above FL185
1st FEB..1st MARLast AIRAC JAN
SAT..SUN06:00..18:00
SKI
DEL YX4005 (EHAM/RD) (LFP*, LFOB/OK) Not above FL245 AIRAC MAR..AIRAC OCTH24
DEL YX4047 (LFP*, LFOB/OK) (EHAM/RD) Not above FL245 AIRAC MAR..AIRAC OCTH24
NEW EP4017 EP** EP** Not above FL365 OCT..MAY05:00..21:00(04:00..20:00)
To prevent entering high layer of ACC sectors in EPWW FIR for a short period of time
NEW LS4124 ELLX (LFMA/MC/ML/MO/MQ/MV/MY/NE/NF/NT/TF/THXI) Via LSAGUAC Not above FL315 H24EH4005 (EHAM/LE) (EHBD/BK/EH/RD) Not above FL075 H24EH4010 (EHBD/BK/EH/RD) (EHAM/LE) Not above FL075 H24
EG4088 (FARNBOROUGH_GROUP, LONDON_GROUP, MIDLANDS_GROUP, EGHH/HI) (EHBK, HAAMSTEDE_GROUP except (EHRD)) Not above FL215 H24
EG4042 (FARNBOROUGH_GROUP, LONDON_GROUP, MIDLANDS_GROUP, EGHH/HI/TK) EHRD Not above FL195 H24
LF4061 (PARIS_GROUP, BEAUVAIS_GROUP) (LESO, LFBBFIR except (LFCR, BORDEAUX_GROUP)) Not above FL365 AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)To offload LFBBACC upper sectors
LF4096 (LONDON_GROUP, FARNBOROUGH_GROUP) (LFBBFIR, LFLC, LESO) Not above FL335 03:00..23:00 (02:00..22:00) To offload LFRRACC and LFBBACC upper secTors
LO4052 LOWW (LOWK, LOWS) Not above FL165 AIRAC APR..AIRAC OCT H24LO4053 (LOWK, LOWS) LOWW Not above FL165 AIRAC APR..AIRAC OCT H24
LFEG4053 (PARIS_GROUP, LFOB) JERSEY_GROUP Not above FL195 H24 LOA LFRR/LFFFLFEG4054 JERSEY_GROUP (PARIS_GROUP, LFOB) Not above FL195 H24 LOA LFRR/LFFF
LS4087 (NICE_GROUP, LFTH) (EDDR/RZ/SB/TL, ELLX, LFJL/SG/SN/ST) via PENDUNot above FL345---------------------Not above FL365
AIRAC MAR..AIRAC OCTH24
------------------------------------------AIRAC NOV..AIRAC FEB
H24 LS4088 (LFHS/HV/LL/LM/LN/LO/LS/LY/MH) (LFJL/SG/SN/ST) via (ARBOS, PENDU) Not above FL285 H24LF4393 LFMN LFMD Not above FL075 H24LF4394 LFMD LFMN Not above FL075 H24
ED4177 EDMA EDVE via BAMAS Z109 Not above FL195 AIRAC APR..AIRAC OCTH24to offload EDMMBBG sector
YX4057 HAMBURG_GROUP EKCH except via ROSOK Not above FL245 H24
ED4131 (EDDT, EDDB, EDDH, EDDV, EDDW) (LSZH, LFSB) Not above FL355 H24
To off-load upper sectors of EDUUUTA.Further restrictions apply during eNM19. (RAD Pan Europe: RE2095, RE2150)
YX4059 HAMBURG_GROUP EKBI Not above FL245 H24LF4391 LFSD EGTTFIR Not above FL345 H24LF4392 (BREST_GROUP,JERSEY_GROUP) TOULOUSE_GROUP Not above FL355 H24 To offload LFRRNU sector
ED4181 EDDB, EDDT LFSB, LSZHvia 1. BAMKI Z117 KEGOS2. VAGAB
Not above FL285 H24
To reduce complexity in Munich ACC. Traffic of listed citypairs via listed routings cannot enter EDUUUTAE above FL315 and shall not climb higher than FL285. Furthermore ARR LSZH have to descent below EDUUUTAC during eNM19.
LS4015 (GENEVA_AREA, GENEVA_GROUP) (LFMC/MD/MF/MN/TF/TH/TZ) Not above FL235 05:00..21:00 (04:00..20:00)
LF4120 (MONTPELLIER_GROUP, PROVENCE_GROUP, RHONE_GROUP) (EDNY, LS**, LFEEFIR)Not above FL305-----------------------Not above FL325
AIRAC MAR..AIRAC OCTH24
----------------------------------------------AIRAC NOV.. AIRAC FEB
H24
Loa LFMM/LSAGTo avoid aberrant profile that lowen capacity
LFLS4236 (AJACCIO_GROUP, BASTIA_GROUP, MONTPELLIER_GROUP, NICE GROUP, PROVENCE GROUP, RHONE GROUP ,TOULON GROUP) (BRUSSELS_GROUP, EBLG) Not above FL345AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)
MAC
EG4155 EGSH EHAM Except if LAMSO/MOLIX Not above FL215 H24To ensure correct sector coordination and achieve realistic planning levels
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
LE4065 BALEARES_GROUP LFBD, PYRENEES_GROUP, TOULOUSE_GROUP Not above FL345 H24AIRAC MAR..AIRAC OCTTo reduce complexity in GO sectors
RE4053 EDDH EDDF Not above FL275 05:00..21:00 (04:00..20:00) AIRAC APR..AIRAC OCTMUAC
EG4141 EGBJ/BP/GD LONDON_GROUP Not above FL155 H24 To reflect standing agreements and ensure correct sector capture.
LF4084 (BASEL_GROUP, LSGG/ZH)(EBAW/BR/CI/KT/MB/ZW, EDDF/DG/DK/DL/FE/FM/FZ/LA/LE/LM/LP/LV/LS/LW/VK/WO,EHBD/EH/GR/VK/WO, ETNG/NN/OU)
via LFEECTAE Not above FL315 H24to follow LoA requirements
LF4175 (CHAMBERY_GROUP, LYON_GROUP) (EBAW/BR/CI/KT/MB/ZW, EDDF/DG/DK/DL/FE/FM/FZ/LA/LE/LM/LP/LV/LS/LW/VK/WO,EHBD/EH/GR/VK/WO, ETNG/NN/OU)
via PENDU Not above FL325 H24
to follow LoA requirements
LF4250 (GENEVA_GROUP, LYON_GROUP, LSZH/ZB, BASEL_GROUP) (EBLG, EHBK, EDFH/LN, ELLX, ETAD, ETSB, EBSP) via sect:LFEECTAE Not above FL305 H24 to follow LoA requirements
EP4016 (LZIB/TT, UKLL, UMBB/GG, EYKA/VL VI, UMKK) EPWWFIR Not above FL365 H24To prevent entering high layer of ACC sectors in EPWW FIR for a short period of time
ED4130 (EDDM/MA/MO, ETSI) (EDDL, EDDG, EDLV) Not above FL325 AIRAC NOV..AIRAC MARH24
To off-load EDUUUTAC and reduce complexity, note other more restrictive level cap for DEP EDDM with ARR DUESSELDORF_GROUP (day, summer) or RE2101
ED4095 EDDM (EBBR, EHEH) Not above FL345 H24
ED4061 EDDM EDDL except via (ARNIX, TEKTU) Not above FL245 AIRAC NOV..AIRAC MARH24
ED4054 (EDDM/MA/MO, ETSI) (EDKZ/LA/LP/LW/VK) Not above FL305 H24 Note, in summer subject to RE2101 (stay below EDUUUTA)
RE4027 LFTH/ML/MT LFPO/PV/PN Not Above FL325 AIRAC APR..AIRAC OCTH24
To offload higher and intermediate sectors in LFEE, internal code : MAC19_LFEE_22eNM19
LF4150 (LFBBFIR, LESO) (BEAUVAIS_GROUP, ROISSY_GROUP) Not above FL345 AIRAC MAR.. AIRAC OCT03:00..23:00 (02:00..22:00)To offload LFBBACC upper secTors
LF4193 (LFBBFIR, LFLC, LESO) except (BORDEAUX_GROUP) NANTES_GROUPNot above FL295---------------------Not above FL335
AIRAC MAR..AIRAC OCTH24
----------------------------------------------AIRAC NOV.. AIRAC FEB
H24
to offload LFBBACC upper sectors-------------------due to FDPS limitations
LF4192 (LFBBFIR, LFLC, LESO) RENNES_GROUPNot above FL295--------------------- Not above FL335
AIRAC MAR..AIRAC OCTH24
----------------------------------------------AIRAC NOV.. AIRAC FEB
H24
To offload LFBBACC and LFRRACC upper secTors
LF4281 (PARIS_GROUP, LFOB/LX) (LFBBFIR, LFMP/MT/ML/MI/MV/MU, LEBB/SO) via LFBBCTA Not above FL295 AIRAC MAR..AIRAC OCT09:20..13:20SW Axis ManagementTo offload LFBBACC upper secTors
LF4313 LFMMFIR (LFBBFIR, LESO) Not above FL345 AIRAC MAR..AIRAC OCT 06:00..21:00 MAC
LF4312 (EBCI, LILLE_GROUP) (LFBBFIR, LESO) via RESMI Not above FL345 AIRAC MAR..AIRAC OCT 09:00..13:00 MAC
LF4315 (BARCELONA_GROUP, LEBB/SO, LFBBFIR) (EB**, EDFH/DR/LN/RT/RZ, EHBK, ELLX, ETAD/AR/SB, LFJL) via LFBBCTA Not above FL345 AIRAC MAR..AIRAC OCT06:00..21:00
SW Axis management, MAC measure to offload LFBBUAC upper sectors
LF4261 (LFBBFIR, LFOT, LESO) GENEVA_GROUP Not above FL345 03:00..23:00 (02:00..22:00) To offload LFBBACC upper secTorsLF4157 (LFBBFIR, LFLC) BARCELONA_GROUP Not above FL345 03:00..23:00 (02:00..22:00) To offload LFBBACC upper secTors
LO4050 (EDDF/EDDN/EDDS, EDTY, EDQ*, EDJA/EDNY, LSZH/LSZR/LSZS/LSMD) LHBP via LOVVCTA Not above FL355 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
for traffic balancing
LO4051 (EDDF/EDDN/EDDS, EDTY, EDQ*, EDJA/EDNY, LSZH/LSZR/LSZS/LSMD) LJLJ via LOVVW15, LOVVB15 Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
for traffic balancing
ED4176 EDDN EDVK via SULUS L604 Not above FL195 AIRAC APR..AIRAC OCTH24to offload EDMMBBG sector
EG4153 (EGHQ, EGTE) SEVERN_GROUP Not above FL095 H24 To reflect realistic profile and ensure correct sector capture.
EG4154 (SEVERN_GROUP) (EGHQ, EGTE) Not above FL095 H24 To reflect realistic profile and ensure correct sector capture.
ED4178 EDDM (EDDL, EDDG, EDLP) via TESDU Not above FL305 AIRAC APR..AIRAC OCT H24
To reduce complexity in EDUUUTA, Excluded from summer measure RE2101 to off-load Langen ACC
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
ED4179 EDDM (EDDL, EDDG, EDLP) except via TESDU Not above FL245 AIRAC APR..AIRAC OCT H24
To reduce complexity in EDUUUTA, Excluded from summer measure RE2101 to off-load Langen ACC but only via TESDU
ED4180 (EDDL, EDLP) EDDM Not above FL315 AIRAC APR..AIRAC OCTH24eNM19 support (exclusion in RE2101 to off-load Langen ACC)
LF4318 DEP (EBCI, LILLE_GROUP, LFOB) (LFBBFIR, LFMP/MT/ML/MI/MV/MU, LEBB/SO) via RESMI Not above FL345 AIRAC APR..AIRAC OCT09:00..13:00MAC
LF4316 (LFBBFIR, LESO) LIM* Not above FL345 Last AIRAC MAR..AIRAC OCT06:00..21:00
SW Axis management, MAC measure to offloard LFBBX4 sector at critical hour
LF4340 NANTES_GROUP (LFBBFIR except (BORDEAUX_GROUP), LFLC, LESO)Not above FL295---------------------Not above FL335
AIRAC MAR..AIRAC OCTH24
----------------------------------------------AIRAC NOV.. AIRAC FEB
H24
to offload LFBBACC upper sectors-------------------due to FDPS limitations
LF4341 RENNES_GROUP (LFBBFIR, LFLC, LESO)Not above FL295--------------------- Not above FL335
AIRAC MAR..AIRAC OCTH24
----------------------------------------------AIRAC NOV.. AIRAC FEB
H24
To offload LFBBACC and LFRRACC upper secTors
LF4319 (LFBBFIR, LESO) (LONDON_SOUTH_GROUP, SEVERN_GROUP, EGSS/SC) Not above FL345 AIRAC MAR..AIRAC OCT09:00..13:00SW Axis management MAC 18
LF4320 (LFBBFIR, LESO) (EDDF/DG/DL/FM/LP/LV/LW, EH** except EHBK) Not above FL345 AIRAC MAR..AIRAC OCT06:00..21:00SW Axis management MAC 18
LF4351 (LFBBFIR, LESO) LFMMFIR Not above FL345 AIRAC MAR..AIRAC OCT 06:00..21:00 MAC
LF4349 GENEVA_GROUP (LFBBFIR, LFOT, LESO) Not above FL345 03:00..23:00 (02:00..22:00) To offload LFBBACC upper secTorsLF4366 BARCELONA_GROUP (LFBBFIR, LFLC) Not above FL345 03:00..23:00 (02:00..22:00) To offload LFBBACC upper secTorsLF4329 EB** (LFBBFIR, LESO) Not above FL355 H24LF4330 LILLE_GROUP (LFBBFIR, LESO) Not above FL335 H24LF4256 (LFRS/RN/RB) (EDDF/DG/DK/FM/DL/LP/LV/LW, EH** except (EHBK) via LFRRCTA Not above FL345 05:00..00:00 (04:00..23:00) SW Axis managementLF4387 (EDDF/DG/DK/FM/DL/LP/LV/LW, EH** except (EHBK) via LFRRCTA (LFRS/RN/RB) via LFRRCTA Not above FL345 05:00..00:00 (04:00..23:00) SW Axis management
LF4352 (LFBBFIR, LESO) LFRS/RN via LFRRCTA Not above FL325 05:00..00:00 (04:00..23:00) SW Axis management, MAC measure
ED4174 EDDF (EDDB, EDDT) via RELKO T728 NOTGO Not above FL235 AIRAC APR..AIRAC OCTH24To reduce complexity
ED4175 (EDDB, EDDT) EDDF via MAG Z20 ORTAG Not above FL225 AIRAC APR..AIRAC OCTH24To reduce complexity
LS4123 (EDNY, EDTM, LSZR) (EDNY, EDTM, LSZR) Not above FL105 H24LF4390 (LYON_GROUP, CHAMBERY_GROUP) (PARIS_GROUP, LFOB) Not above FL305 03:00..23:00 (02:00..22:00)YX4058 EDDF (EGGW/KB/KK/LC/MC/MD/SC/SH/SS/TC/TO/UL/UN/YM) via OBOKA Not above FL365 H24
EDYX4042 (EDDW, HAMBURG_GROUP) EDDM Not above FL295 AIRAC APR..AIRAC OCTH24
LS4096 MILANO_GROUP except (LIMJ) (EB**, EDDR/RZ/SB/TL, EH**, EL**, LFJL/SG/SN/ST) via PENDU Not above FL345 AIRAC APR..AIRAC SEP04:00..20:00
EDLO4000 LSZH LJLJ, LOWG, LOWL, LOWS via LOVVCTA, EDUUALP1L Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19to off-load EDUUALP1L sector (replacing former ED3556)
EDLO4001 LJLJ, LOWG, LOWL, LOWS LSZH via LOVVCTA, EDUUALP1L Not above FL305 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19to off-load EDUUALP1L sector (replacing former ED3556)
LS4027 (LFMD/MN/TH/TZ) (LFGJ/SD, LSZH/ZR, EDNY/TD/TM, BASEL_GROUP, LFEEFIR) via LSAGUAC Not above FL305 05:00..21:00 (04:00..20:00)
LS4043 (EDDS/NL/SB, EDT*) (LIRP/RQ, LIP*) Not above FL335 05:00..21:00 (04:00..20:00)
RE4026 LFTH/ML/MT LONDON_GROUP, FARNBOROUGH_GROUP, EGHH, EGHI via LFEE5R Not Above FL345 in LFMMCTAAIRAC APR..AIRAC OCT
H24
To offload higher sectors in LFEE, expects flight to be descended to FL300 in LFFFUS sector for handover in LFEEURinternal code : MAC19_LFEE_21eNM19
RE4046 LFTH/ML/MT LONDON_GROUP, FARNBOROUGH_GROUP, EGHH, EGHI via LFEE5R Not Above FL315 in LFEECTA
AIRAC APR..AIRAC OCT10:00..17:00 (09:00..16:00)
H24
To offload higher sectors in LFEE, expects flight to be descended to FL300 in LFFFUS sector for handover in LFEEURinternal code : MAC19_LFEE_21eNM19
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
LF4358 (LFKJ, BASTIA_GROUP) (NICE_GROUP, TOULON_GROUP) Not above FL145 AIRAC MAR..AIRAC OCTH24
LS4118 (ETAR, LFST) (LIRP/RQ, LIP*) Except via MOROK UN852 GILIR Not above FL335 05:00..21:00 (04:00..20:00)
LS4119 (LFMD, LFMN, LFTH, LFTZ, LIMF, LIMW, LIMZ) (ELLX EDDR, EDRZ) Via LSAGUAC Not above FL305AIRAC APR..AIRAC SEP
04:00..20:00
LS4120 LFEEFIR (LFMD, LFMN, LFTH, LFTZ) Via LSAGUAC Not above FL315AIRAC APR..AIRAC SEP
04:00..20:00
LS4121 (LFMD, LFMN, LFTH, LFTZ)
(LFP*, LFOB, ETSI, LOWI, EDDS, LSZS, EDFM, EDNL, EDSB, EDTB, EDTO, EDTX,EDTY, EDTL, EDJA, ETHL, LFST, EDTK, EDTF, EDTN, EDTR, EDTS, EDTZ, MUNICH_GROUP)
Via LSAGUAC Not above FL325AIRAC APR..AIRAC SEP
04:00..20:00
LS4122 (LFMD/MN/TH/TZ) EH** via PENDU Not above FL345 AIRAC MAR..AIRAC OCT05:00..21:00 (04:00..20:00)
LF4279 ELLX (EGHH/HI/HL/LF/LK/TF/VO/TD, EGKB/KA/LC/LD/MC/MD/SG/SX/TO/TR) via sect:LFEE5RNot above FL345-----------------------Not above FL305
AIRAC NOV..AIRAC FEBH24
-----------------------------------------------AIRAC MAR..AIRAC OCT
H24
LF4285 (BASEL_GROUP, LS** except (LSGG)) (EGKB/HH/HI/LC/LF/KA/LD/MC/MD/SG/SX/TF/TO/TR/HL/HO/HQ/HR/LK/VO/TD) via sect:LFEECTA Not above FL345AIRAC APR..AIRAC OCT
H24
LF4282 LSGG (EGKB/HH/HI/LC/LF) via sect:LFEECTA Not above FL345 AIRAC MAR..AIRAC OCT 14:00..21:00EG4128 EGFH/GD/SY EGKB/LC Not above FL175 H24
EB4007 EHAM LFST/LFGA/EDTL via EBBUCTA Not above FL215 H24
To deconflict flows due to the eNM19 measures onload. Restriction may be switched back to the original after the summer period.
LS4114 (GENEVA_AREA, GENEVA_GROUP) (LFGJ/SD) Not above FL185 05:00..21:00 (04:00..20:00)
LS4099 (LFMD/MN/TH/TZ) (EDDS/FM/JA/NL/SB/TB/TF/TK/TL/TN/TO/TR/TS/TX/TY/TZ, ETHL, LSZS , LFST) via LSAGUTANot above FL345----------------------Not above FL325
AIRAC NOV..AIRAC FEB05:00..21:00 (04:00..20:00)
------------------------------------------AIRAC MAR..AIRAC OCT05:00..21:00 (04:00..20:00)
LS4098 (GENEVA_AREA, GENEVA_GROUP, CHAMBERY_GROUP, LFLL/LS/LU/LY) (EDDS/FM/JA/NL/SB/TB/TF/TK/TL/TN/ TO/TR/TS/TX/TY/TZ, ETHL, LFST) except via ARBOSNot above FL345----------------------Not above FL325
AIRAC NOV..AIRAC FEB05:00..21:00 (04:00..20:00)
------------------------------------------AIRAC MAR..AIRAC OCT05:00..21:00 (04:00..20:00)
RE4011 (EDDF/DS/DN/FM/SB/TY) (LIPH/PX/PZ) except via LS Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00) eNM19EDUU95
RE4000 EHAM LOWW via EDUUUTAC Not above FL355 AIRAC APR..AIRAC OCTH24
eNM19 EDUUTo off-load upper sectors of EDUUUTAC
ED4162 (DUESSELDORF_GROUP) (LSZH/ZR) Not above FL245 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19 EDUU11/12/13To off-load EDUUUTA and prevent on loading EDYYUTASee also RE2101
ED4072 EDDF (EDDB/DT) Not above FL295 AIRAC NOV..AIRAC MARH24
ED4036 DUESSELDORF_GROUP EDDC Not above FL335 AIRAC NOV..AIRAC MARH24
ED4163 (EDDV/VE) EDDS via (ANANO/EDEGA/KEMAD) Not above FL245AIRAC NOV..AIRAC MAR
H24
ED4164 EDDF (EDDB, EDDT) via LASGA T202 MILGU Not above FL275 AIRAC APR..AIRAC OCTH24To offer alternative routing higher than FL245 during summer
ED4165 EDDM ELLX Not above FL245 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)To off-load EDUUUTAC
ED4120 EDDN LFPG Not above FL245 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19 EDUU30To off-load EDUUUTA
RE4039 EDDS EHAM Not above FL245 AIRAC APR..AIRAC OCTH24
eNM19 EDUU63aTo off-load sectors of EDYY and EDUUUTA
RE4023 EHAM EDDF Not above FL245AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
MUAC
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
ED4166 ELLX EDDM via EDUUUTA Not above FL245 AIRAC APR..AIRAC OCTH24eNM19 EDUU28To off-load sectors of EDUUUTA
RE4040 LFPG EDDN Not above FL245 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19 EDUU31To off-load EDUUUTA
ED4167 LKPR DUESSELDORF_GROUP via RAPET Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19 EDUU42To off-load EDUUERL1L, EDUUFUL1U sectors.
RE4007 LKPR LIPA, LIPH, LIPO, LIPU, LIPX, LIPZ via BAMTA Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19 EDUUTraffic is limited as DEP to climb below EDUUDON1D and EDUUCHI1K (below FL315). In the next sector EDUUALP1L the descent below FL315 is already required.
ED4115 LSZH DUESSELDORF_GROUP Via ALAGO Not above FL245 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00) eNM19
EDUU114ED4168 EDDS (EDDB/DT, BERLIN_YZ_GROUP) via TABAT, PEROX Not above FL275 H24 To off-load EDUUUTA
RE4010 EHAM EDDM Not above FL355 AIRAC APR..AIRAC OCTH24
eNM19 EDUUTo off-load upper sectors of EDUUUTAC
ED4087 (EDDF/DS/DN/FM/SB/TY) LO** Not above FL315 05:00..21:00 (04:00..20:00) AIRAC APR..AIRAC OCTeNM19 EDUU96
RE4042 DUESSELDORF_GROUP EDDP/DC Not above FL245 AIRAC APR..AIRAC OCTH24MUAC
RE4043 EDDF EHAM Not above FL245 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)MUAC
LKED4018 (EDDB/DT/DV) LOWW Not above FL305 AIRAC APR..AIRAC OCT H24
RE4052 (LIPH/PX/PZ) (EDDF/DS/DN/FM/SB/TY) except via LS Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00) eNM19 EDUU
ED4096 LSZH (DUESSELDORF_GROUP, EDDV, EDDW) via ETAGO Not above FL345 H24Note: Further level caps apply during Summer / eNM19
LK4048 (EPKK/KT/PO/LL) via LKAAFIR (ED**, ETSI, LO**) via LKAAFIR Not above FL355 H24
RE4024 EGKK/LL/GD/FF LPPR/PT If via as:LF Not above FL355 AIRAC APR..AIRAC OCT05:00..09:00 (04:00..08:00)
To offload LFRRAU. Traffic should file through LFRRASI (same route, FL350 or below)internal code : MAC19_LFRR_10eNM19
RE4025 LFL* EH** If via sect:LFEE5R Not above FL305 AIRAC APR..AIRAC OCT10:00..22:00 (09:00..21:00)
To offload LFEEKHR. Traffic should file through LFEEUR(same route, FL300 or below)internal code : MAC19_LFEE_20eNM19
RE4028 EB** LIMC/ML/ME/MP/PH/PX if via BEGAR or MOROK Not above FL335 AIRAC APR..AIRAC OCT06:00..23:00 (05:00..22:00)
To offload higher sectors in LFEEinternal code : MAC19_LFEE_23eNM19
RE4029 LFP* LFMN Not above FL355 AIRAC APR..AIRAC OCT05:00..23:00 (04:00..22:00)
To offload higher sectors in LFMMinternal code : MAC19_LFMM_24eNM19
RE4030 LFBO/BP/BT ORLY_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_01eNM19
RE4031 NANTES_GROUP, LFRN LYON_GROUP, Geneva_Group Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_02 & 04eNM19
RE4032 LYON_GROUP, Geneva_Group NANTES_GROUP, LFRN Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_02 & 04eNM19
RE4033 LFBZ ORLY_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_03eNM19
RE4034 BORDEAUX_GROUP GENEVA_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_05eNM19
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
RE4035 GENEVA_GROUP BORDEAUX_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_05eNM19
RE4036 PARIS_GROUP BORDEAUX_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_06eNM19
RE4037 MONTPELLIER_GROUP NANTES_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_07eNM19
RE4038 NANTES_GROUP MONTPELLIER_GROUP Not above FL295AIRAC APR.. AIRAC OCT
9:30..11:00, 18:30..20:30 (08:30..10:00, 17:30..19:30)
To offload LFBBR2 sectorinternal code : MAC19_LFBB_07eNM19
LS4116 (LFMD/MN/TH/TZ) (EDMA/MO) via LSAGUTANot above FL345 ----------------------Not above FL325
AIRAC NOV..AIRAC FEB05:00..21:00 (04:00..20:00)
------------------------------------------AIRAC MAR..AIRAC OCT05:00..21:00 (04:00..20:00)
EDYX4041 (EDDW, HAMBURG_GROUP) (EDDC/DN) Not above FL245 AIRAC APR..AIRAC OCTH24
RE4041 (LFOB, LFP*) LDDU/SP/ZD, LI**, LYPGvia 1. GAMSA2. EDUUUTAW
Not above FL315 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19EDUU88
replacment of former ED3553
RE4012 EDDF LONDON_GROUP Time refer to Departure time EDDF Not above FL225AIRAC APR..AIRAC OCT05:00..08:00 (04:00..07:00)
eNM19EDUU109
RE4013 LFP*, LFOB ED**, ET**, LK**1. via (as: EDUUUTAW, EDUUUTAC)2. via BATEL
Not above FL355 05:00..21:00 (04:00..20:00) AIRAC APR..AIRAC OCT
eNM ANSPs summer 2019EDUU111
Note, some more restricting cappings apply.
ED4169 ED**, ET** LOWW Not above FL355 AIRAC APR..AIRAC OCT H24
To reduce complexity and due to new seasonal LoA agreements for transfer of all ARR LOWW at intermediate levels to downstream ACCs.Note: more restrictive levelcaps might overlap, such as LK4042 or ED4087.
ED4170 EDDH PRAGUE_GROUP Not above FL285 AIRAC APR..AIRAC OCT H24
To reduce complexity and due to LoA agreements for transfer of ARR Prague groupoff-loading EDUUHVL1H sector in summer
ED4171 EDDH PRAGUE_GROUP Not above FL295 AIRAC NOV..AIRAC MAR H24
To reduce complexity and due to LoA agreements for transfer of ARR Prague group
RE4047 BASEL_GROUP (EDDM, EDM*, EDJA/NL, ETHL/SA/SI/SL, LOWI) via LSAZCTA Not above FL245 AIRAC APR..AIRAC OCT H24eNM19 measures (LSAZ_1) to offload LSAZM12.
RE4048 (EDDM, EDM*, EDJA/NL, ETHL/SA/SI/SL, LOWI) BASEL_GROUP via LSAZCTA Not above FL245 AIRAC APR..AIRAC OCT H24eNM19 measures (LSAZ_1) to offload LSAZM12.
RE4049 LFPG/LFPO LIP* except (LIPR/PY) via LSAZUTA Not above FL355 AIRAC APR..AIRAC OCT H24eNM19 measures (LSAZ_2) to offload LSAZM5.
RE4050 LIP* except (LIPR/PY) LFPG/LFPO via LSAZUTA Not above FL355 AIRAC APR..AIRAC OCT H24eNM19 measures (LSAZ_2) to offload LSAZM5.
RE4003 EPWR/KT/KK/RZ/KA/LB/RA/LL LJLJ/LDZA/SP/PL/RI/ZD/OS, LQSA/TZ/BK/MO, LYBE via LHCCCTA, LZBBCTA Not above FL355 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
RE4004 LJLJ/LDZA/SP/PL/RI/ZD/OS, LQSA/TZ/BK/MO, LYBE EPWR/KT/KK/RZ/KA/LB/RA/LL via LHCCCTA, LZBBCTA Not above FL345 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
RE4005 LZIB, LZNI, LZKZ, LZSL, LZTT LJLJ/LDZA/SP/PL/RI/ZD/OS, LQSA/TZ/BK/MO, LYBE/NI Via LHCCCTA Not above FL355 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
RE4006 LJLJ/LDZA/SP/PL/RI/ZD/OS, LQSA/TZ/BK/MO, LYBE/NI LZIB, LZNI, LZKZ, LZSL, LZTT Via LHCCCTA Not above FL345 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
RE4008 EDDM/DS/DN LYBE, LRAR/TR/OD/SM/CL/BM via LHCCCTA, LOVVCTA Not above FL355 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
RE4009 LYBE, LRAR/TR/OD/SM/CL/BM EDDM/DS/DN via LHCCCTA, LOVVCTA Not above FL345 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)eNM19
RE4001 LSZH DUESSELDORF_GROUP via as:LF Not above FL285 AIRAC APR..AIRAC OCT05:00..21:00 (04:00..20:00)
eNM19Complementary to ED4115 avoiding
on-load if via LF.EDUU114
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
RE4002 EDDF LONDON_GROUPVia GOPAS(Time refer to Departure time EDDF)
Not above FL225 AIRAC APR..AIRAC OCT12:00..23:00 (11:00..22:00)
eNM19EDUU109
Higher level available via OBOKA routing (or via RAPOR within as:LF)
ED4172 (EKCH/RK/RN, ESMS) (EDDB/DT) Not above FL285 AIRAC APR..AIRAC OCTH24eNM19EDUU
ED4173 PRAGUE_GROUP EDDHNot above FL285---------------------Not above FL325
AIRAC APR..AIRAC OCTH24
------------------------------------------AIRAC NOV..AIRAC MAR
H24
eNM19EDUU
RE4051 LHBP EDDT/DB via LKAAFIR Not above FL345 AIRAC APR...AIRAC OCT H24eNM19
LS4035 (BASEL_GROUP, LSMD/ZH) (GENEVA_GROUP, GENEVA_AREA except (LSGS), LFLB/LP/LJ) via ULMES Not above FL155 05:00..21:00 (04:00..20:00)YX4007 EHAM (LFSB, LSGG, ZURICH_AREA, LYON_GROUP) Not above FL335 H24
LF4308 (GENEVA_GROUP, LYON_GROUP, LFLB/LP) BASTIA_GROUP except via TOP Not above FL345 AIRAC NOV..AIRAC FEBH24
LF4301 (NICE_GROUP, TOULON_GROUP) (AJACCIO_GROUP, BASTIA_GROUP) Not above FL245 AIRAC NOV..AIRAC FEBH24
LF4305 (NICE_GROUP ,TOULON_GROUP) ROME_GROUP Not above FL345 AIRAC NOV..AIRAC FEBH24
LF4187 LFBBFIR except (BIARRITZ_GROUP, TOULOUSE_GROUP) (CHAMBERY_GROUP, CLERMONT_FERRAND_GROUP, LYON_GROUP)Not above FL295----------------------Not above FL345
AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)
----------------------------------------------AIRAC NOV.. AIRAC FEB03:00..23:00 (02:00..22:00)
To offload LFBBACC upper sectors
LF4344 BASTIA_GROUP (GENEVA_GROUP, LYON_GROUP, LFLB/LP) except via TOP Not above FL345 AIRAC NOV..AIRAC FEBH24
LF4357 (AJACCIO_GROUP, BASTIA_GROUP) (NICE_GROUP, TOULON_GROUP) Not above FL245 AIRAC NOV..AIRAC FEBH24
LF4361 ROME_GROUP (NICE_GROUP ,TOULON_GROUP) Not above FL345 AIRAC NOV..AIRAC FEBH24
LF4362 (CHAMBERY_GROUP, CLERMONT_FERRAND_GROUP, LYON_GROUP) LFBBFIR except (BIARRITZ_GROUP, TOULOUSE_GROUP)Not above FL295----------------------Not above FL345
AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)
----------------------------------------------AIRAC NOV.. AIRAC FEB03:00..23:00 (02:00..22:00)
To offload LFBBACC upper sectors
LFLS4138 (EDDS/NY, LS**, LFS*, LFJL) (MONTPELLIER_GROUP, PROVENCE_GROUP, RHONE_GROUP) Not above FL315 AIRAC MAR..AIRAC OCTH24
LF4321 (BARCELONA_GROUP, LEBB, LFBD/BE/BO/BT/BZ/CR/MK/SL) (EDDF/DG/DL/FM/LP/LV/LW, EH** except EHBK) via LFRRCTA Not above FL345 AIRAC MAR..AIRAC OCT09:00..13:00SW Axis management MAC 18
LF4322 (BARCELONA_GROUP, LEBB) (EDDF/DG/DL/FM/LP/LV/LW, EH** except EHBK) via LFBBCTA Not above FL365 AIRAC MAR..AIRAC OCT06:00..21:00SW Axis management MAC 18
LF4287 BARCELONA_GROUP (SEVERN_GROUP, FARNBOROUG_GROUP, EGKB/KK/LC/LL/MC/TO/WU) via LFRRCTA Not above FL345 AIRAC MAR..AIRAC OCT09:00..13:00
SW Axis ManagementTo offload LFBBACC and LFRRACC upper secTors
LF4324 (BARCELONA_GROUP, LFBZ, LEBB) (EGSS/GW/SC) via LFRRCTA Not above FL365 AIRAC MAR..AIRAC OCT09:00..13:00SW Axis management MAC 18
LF4290 (EHAM/EH/RD) LYON_GROUP via LESDO Not above FL295 AIRAC APR..AIRAC OCTH24
LF4265 (PARIS_GROUP, LFOB) (EDDS/TD) via LUPEN Not above FL295 AIRAC NOV..AIRAC FEBH24Seasonal procedure
LF4306 (BASTIA_GROUP) (MONTPELLIER_GROUP, PROVENCE_GROUP) Not above FL325 AIRAC NOV..AIRAC FEBH24
LF4149 LFBBFIR except (LFBO/BP/BT/BZ) ORLY_GROUP Not above FL295----------------------- Not above FL345
AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)
----------------------------------------------AIRAC NOV..AIRAC FEB03:00..23:00 (02:00..22:00)
To offload LFBBACC upper secTors
LF4238 (LFBO/BP/BT) ORLY_GROUPNot above FL345----------------------Not above FL365
AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)
----------------------------------------------AIRAC NOV.. AIRAC FEB03:00..23:00 (02:00..22:00)
To offload LFBBACC upper secTors
LF4127 TOULON_GROUP (EDNY, LS**, LFSB/SM) via LTPNot above FL305----------------------Not above FL345
AIRAC MAR..AIRAC OCTH24
----------------------------------------------AIRAC NOV.. AIRAC FEB
H24
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
LFLS4237 (LFSB, LSMD/ZA/ZH/ZR/ZS) BARCELONA_GROUP Not above FL355 AIRAC NOV..AIRAC FEB04:00..22:00SEE LFLS4083
LE4005 BARCELONA_GROUP MADRID_GROUP Not above FL295 H24LE4029 (LEMH/SL) LEGE Not above FL245 H24LE4004 (BARCELONA_GROUP) CANTABRICO_GROUP Via LECBACC Not above FL295 H24LE4040 CANTABRICO_GROUP (BARCELONA_GROUP) via LECBACC Not above FL305 H24LE4041 MADRID_GROUP (BARCELONA_GROUP) Not above FL305 H24LE4031 (BARCELONA_GROUP) (BARCELONA_GROUP) Not above FL195 H24
LF4179 (GENEVA_GROUP, LYON_GROUP, LFLB/LC/LP) BASTIA_GROUP except via TOP Not above FL305 AIRAC MAR..AIRAC OCTH24
LF4325 LFRS (LFMP/TW) Not above FL345 AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)To offload LFBBACC upper sectors
LF4326 (LFRS, LFOT) (MONTPELLIER_GROUP, PROVENCE_GROUP, RHONE_GROUP, BARCELONA_GROUP) Not above FL345AIRAC MAR…AIRAC OCT
06:00…21:00SW Axis management, MAC measure to offload LFBBUAC upper sectors
LF4311 (LFK*, NICE_GROUP) LFBO Not above FL305 AIRAC MAR..AIRAC OCT 09:00..13:00
MAC measures to offload the elementary sectors M in the layer
number 2
LF4314 (LFRN/RS) (EB**, EDFH/DR/LN/RT/RZ, EHBK, ELLX, ETAD/AR/SB, LFJL) via LFRRCTA Not above FL325 05:00..00:00 (04:00..23:00) SW Axis management, MAC measure
LF4035 LFMMFIR BARCELONA_GROUP Not above FL305 AIRAC MAR..AIRAC OCTH24To offload LFMMACC and LFBBACC upper sectors
LF4170 (NICE_GROUP ,TOULON_GROUP) ROME_GROUP Not above FL305 AIRAC MAR..AIRAC OCTH24
LF4177 (CHAMBERY_GROUP, LYON_GROUP, SAINT_YAN_GROUP) (MONTPELLIER_GROUP, NICE_GROUP, PROVENCE_GROUP, RHONE GROUP, TOULON GROUP) Not above FL295AIRAC MAR..AIRAC OCT
H24
LF4302 (NICE_GROUP, TOULON_GROUP) (AJACCIO_GROUP except (LFKF), BASTIA_GROUP) Not above FL145 AIRAC MAR..AIRAC OCTH24
LF4303 (NICE_GROUP, TOULON_GROUP) LFKF Type (Piston, Turboprop) Not above FL195 AIRAC MAR..AIRAC OCTH24
LF4304 (NICE_GROUP, TOULON_GROUP) LFKF Type Jet Not above FL245 AIRAC MAR..AIRAC OCTH24
LF4159 (NICE_GROUP, TOULON_GROUP) LIE* Not above FL305 AIRAC MAR..AIRAC OCT04:00..22:00
LF4343 BASTIA_GROUP (GENEVA_GROUP, LYON_GROUP, LFLB/LC/LP) except via TOP Not above FL305 AIRAC MAR..AIRAC OCTH24
LF4347 (LFMP/TW) LFRS Not above FL345 AIRAC MAR..AIRAC OCT03:00..23:00 (02:00..22:00)To offload LFBBACC upper sectors
LF4348 (MONTPELLIER_GROUP, PROVENCE_GROUP, RHONE_GROUP, BARCELONA_GROUP) LFRS, LFOT Not above FL345AIRAC MAR…AIRAC OCT
06:00…21:00SW Axis management, MAC measure to offload LFBBUAC upper sectors
LF4350 LFBO (LFK*, NICE_GROUP) Not above FL305 AIRAC MAR..AIRAC OCT 09:00..13:00
MAC measures to offload the elementary sectors M in the layer
number 2
LF4353 BARCELONA_GROUP LFMMFIR Not above FL305 AIRAC MAR..AIRAC OCTH24To offload LFMMACC and LFBBACC upper sectors
LF4354 ROME_GROUP (NICE_GROUP ,TOULON_GROUP) Not above FL305 AIRAC MAR..AIRAC OCTH24
LF4355 (MONTPELLIER_GROUP, NICE_GROUP, PROVENCE_GROUP, RHONE GROUP, TOULON GROUP) (CHAMBERY_GROUP, LYON_GROUP, SAINT_YAN_GROUP) Not above FL295AIRAC MAR..AIRAC OCT
H24
LF4359 LFKF (NICE_GROUP, TOULON_GROUP) Type (Piston, Turboprop) Not above FL195 AIRAC MAR..AIRAC OCTH24
LF4360 LFKF (NICE_GROUP, TOULON_GROUP) Type Jet Not above FL245 AIRAC MAR..AIRAC OCTH24
LF4379 LIE* (NICE_GROUP, TOULON_GROUP) Not above FL305 AIRAC MAR..AIRAC OCT04:00..22:00
LF4241 (AJACCIO_GROUP, LIEA/EO) (LYON_GROUP, GENEVA_AREA, GENEVA_GROUP, LFLB/LP) via PIGOS Not above FL345 AIRAC MAR..AIRAC OCT04:00..22:00
LF4242 (LYON_GROUP, GENEVA_AREA, GENEVA_GROUP, LFLB/LP) (AJACCIO_GROUP, LIEA/EO) via KOLON Not above FL355 AIRAC MAR..AIRAC OCT04:00..22:00
LF4327 (BARCELONA_GROUP, LEZG) LF** via LFBBCTA Not above FL345AIRAC MAR…AIRAC OCT
06:00…21:00
SW Axis management, MAC measure to offload LFBBUAC upper sectors
LFLS4238 (AJACCIO_GROUP, BASTIA_GROUP, MONTPELLIER_GROUP, NICE GROUP, PROVENCE GROUP, RHONE GROUP , TOULON GROUP) BRUSSELS_GROUP except via LSAGUAC Not above FL345AIRAC NOV..AIRAC FEB03:00..23:00 (02:00..22:00)
linked with LFLS4236
LF4277 (EDDL/DF/FH/DK/LP/DG/LV/LW/FM/LA/WO/LS/VK/FE/FZ, ETNG/OU, ELLX, LFST) (LFO*, LFRG/RK/RM/JR/LX/QG/LD/LA, EGJJ/JB) Not above FL315AIRAC MAR..AIRAC OCT
H24
ChangeRecord ID Number FROM (ADEP) TO (ADES) Condition FL Capping Restriction Applicability Remark
LF4079 LFRRFIR (BASEL_GROUP, STRASBOURG_GROUP) Not above FL305-----------------------Not above FL275
AIRAC NOV..AIRAC FEB03:00..23:00 (02:00..22:00)
---------------------------