Professional Documents
Culture Documents
E1 RAD ALL en PDF
E1 RAD ALL en PDF
E1 RAD ALL en PDF
ANNEX LU Moldova
ANNEX NAT
EASTBOUND
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
1. INTRODUCTION
1.2. Each State is the sole owner of the contents of the RAD
Annexes/Appendices applicable to them. The CFMU is responsible for
collating, coordinating, validating and publishing the RAD.
1.4 The RAD is only applicable to the IFR part of the Flight Plan.
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 CFMU airspace
2.2. The RAD enables 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.4. The RAD should also assist the CFMU 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 RAD will be subject to continuous review by the CFMU and the ANSPs
to ensure that the requirements are still valid and take account of any ATC
structural or organisational changes that may occur. Further reviews may be
initiated at the request of the States or the User organisations.
Updated on 10/03/11 APPENDIX 1 Introduction
Valid from 05/05/11 RAD Page 2 of 10
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
3. | STRUCTURE
3.4 In Appendix 4 the lower vertical limits of the DCTs shall be expressed as
VFR flight levels e.g. FL355, 335, 295, 155 etc. This enables a clear
distinction of the lowest level that can be flown (in the case of FL155 above,
the lowest level that can be flown is FL160). It is the ultimate responsibility
of the Flight Dispatcher/Pilot in Command to ensure adequate terrain
clearance at all times. Where MSFL (Minimum Safe Flight Level) is
mentioned, this corresponds to the Minimum Safe Altitude (MSA) corrected
for ambient pressure.
3.5 The RAD includes all route flow restrictions valid for the State concerned
together with any relevant restrictions included in LOAs between adjacent
ACCs/UACs.
Updated on 10/03/11 APPENDIX 1 Introduction
Valid from 05/05/11 RAD Page 3 of 10
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
3.6 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.7 The structure of each restriction is hierarchical and specific and has been
arranged in a fashion to facilitate parsing of the information into computer
systems.
3.8. There are 3 main types of restrictions, the inclusive, exclusive and
compulsory, examples of which are given below:
INCLUSIVE restriction
UN869 LERGA-OLRAK Not available for traffic
Above FL270
With Dep. LSAGFIR, Chambery Group, Lyon Group
With Dest. LFBBFIR, LFRRFIR
Traffic must meet ALL of the conditions to be subject to the restriction
EXCLUSIVE restriction
UL976 OBATO - RONAX Not available for traffic
1. Dest. LFPG/B
2. Via MMD
Except Dest. ELLX, EBLG, EHBK,
EDDR/FH/LN, ETAR/AD/SB, LFJL/SF
3. Via CHW
With Dest. EBBUFIR
Except Dest. EBLG, ELLX
Traffic only needs to meet ONE of the conditions to be subject to the
restriction.
COMPULSORY restriction
UL865 BOL – TAQ Compulsory for traffic
Dep. LIML
With Dest. LICJ
Traffic has no other option; it shall fly this route segment
Updated on 10/03/11 APPENDIX 1 Introduction
Valid from 05/05/11 RAD Page 4 of 10
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
3.9 The TERM RFL is used to determine the actual flight plan (Field 15)
requested Flight Level. Where it is used it shall be applied only to the
state in question unless otherwise specified. If a restriction specifies FL
that is understood to be the level measured against the CFMU
calculated profile and is checked accordingly
Restriction
Restriction subtype Publication Origin ID Group ID
type
City pair level capping RAD APPENDIX 3 Country code ID 4000 to 4999
Conditions on DCT
RAD APPENDIX 4 Country code ID 5000 to 5499
segments Point-to-Point
Conditions on DCT
RAD APPENDIX 5 Country code ID 5500 to 5999
segments to/from Airfields
Country/FIR code
Traffic Flow Flight Profile Restrictions RAD Appendix 6 8000 to 8999
ID
RAD Annexes RAD DOC Country code ID 2000 to 3999
RAD Annexes cross border
RAD DOC Country code ID(s) 1000 to 1499
Restrictions
Military Restrictions RAD DOC Country code ID(s) 7000 to 7499
Plain text notes RAD DOC Country code ID(s) 6000 to 6999
3.10 In Annexes where date/time ranges are used these shall be considered
as INCLUSIVE
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.
Updated on 10/03/11 APPENDIX 1 Introduction
Valid from 05/05/11 RAD Page 5 of 10
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
5. CFMU APPLICATION
5.1 The RAD will be fully integrated into the CFMU systems, including IFPS,
through the Route Restrictions computer model. Any changes to an 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. AMENDMENT PROCESS
6.1 Permanent amendments to the RAD, or the period of validity, will be co-
ordinated by the CFMU with the States concerned together with the AO
Organisations. All States concerned shall provide their request for changes
to CFMU, taking into account agreed publication and implementation dates, in
accordance with AIRAC procedures and CFMU Handbook (Provision of
Environment data).
c) Restrictions that have been removed will be annotated at the end of the
relevant Annex under the heading “Withdrawn restrictions.”
7. TEMPORARY CHANGES
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
8. NOTAM Series F
9.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. Cross-
border restrictions shall be recorded in the Annex relevant to the State/FIR
responsible for the restriction. Where joint requirements exist cross-border,
the restriction shall be recorded in the Annex relevant to the State/FIR
within which the first point of that restriction lies.
9.3 When filing flight plans, aircraft operators must comply with any flight
level limitation published in the RAD.
9.4 An operator who has submitted a flight plan for a route and wishes to
change to another route must either; send a CHG 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 CFMU and to changes made at the initiative of the
AO.
10.2 When, during the planning phase, the CFMU 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.
10.4 The list of available scenarios are promulgated on the CFMU website
Updated on 10/03/11 APPENDIX 1 Introduction
Valid from 05/05/11 RAD Page 8 of 10
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
12. | PUBLICATION
12.1 The RAD is created in accordance with ICAO publication procedures and
is published by the CFMU via the CFMU Website and the EAD, 34 days
prior to the relevant AIRAC cycle.
12.2 Each State may promulgate the RAD by any one of the following
methods:
a) Publish the Part I or Part II of 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 Annexes/Appendices of the RAD as an AIP
Supplement.
c) Publish reference to the CFMU website in the AIP.
D -56 RAD Cut-off date. States provide amendments to CFMU OpsD States
Three weeks to compile the RAD and to resolve errors/conflicts CFMU OpsD
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
13.2 During periods of unanticipated high demand the CFMU 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.
13.5 With effect from AIRAC -6, implemented RAD Data is considered as
Operational. Management of NOTAM changes to the RAD is the
responsibility of the NRC of the originating State. CFMU does not track
NOTAMs and will not automatically update the ENV system on the basis
of NOTAM information.
13.6 If, after AIRAC -6, a State discovers an error or omission to the RAD
that is SAFETY RELATED, then a NOTAM shall be issued by the
State/ACC after coordination with the NRC. It is the responsibility of the
NRC to contact the CFMU RAD Team to request a live update of the ENV
System in order to correct the problem. The CFMU RAD Team will only
act after consultation with the NRC or his designated Deputy. Following
the consultation process the CFMU RAD Team shall create the necessary
DMR and the change shall be promulgated on the “What is New” website.
During the weekend, the ACC shall contact the IFPS Supervisor 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.
Updated on 10/03/11 APPENDIX 1 Introduction
Valid from 05/05/11 RAD Page 10 of
https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html
14.1 A RAD Review for each and every Annex/Appendix shall be completed
annually, normally in the Autumn/Winter/Spring period. Each state is
responsible for an internal RAD Review with the airlines concerned. The
CFMU is responsible for arranging Cross-Border RAD Reviews to cover
all states.
14.2 The internal Review shall cover: 1. The validity of all restrictions;
2. The timeliness of restrictions; 3. The completeness of all restrictions.
The CFMU may offer items to be covered in the Annual Internal RAD
Review. The results of such Reviews shall be passed to the CFMU as soon
as possible after the Review has been completed.
14.3 The Reviews are 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 CFMU systems, are
reflected in the construction of RAD restrictions. The CFMU RAD Team
shall create an Agenda for each Cross-Border Review.
14.4 The venue for RAD Reviews shall alternate between the State and
Brussels on alternate years. During the Winter of 2006/7 the Reviews were
held in Brussels.
14.5 For each Cross-Border RAD Review the CFMU shall perform a RAD
Impact Assessment on each relevant restriction, using the RAD Impact
Assessment Methodology (RADIAM), this analysis shall be carried out
together with the ACC(s) concerned. Such assessments shall be completed
before the Review in order for the participants to familiarise themselves
with the results
• RMG Wednesday/Thursday of the 1st week in March - day 2 with the AOs
• RMG Thursday of the last week in June
• RMG Wednesday/Thursday of the 1st week in November - day 2 with NRC.
Updated on 05/05/11 RAD Area Definitions
Valid from 30/06/11 APPENDIX 2 - Area Definitions Page 1 of 2
Withdrawn:
Updated on 28/07/11 RAD City Pair Level Caps
Valid from 22/09/11 APPENDIX 3 - CITY-PAIR LEVEL CAPPING Page 1 of 14
Note 1: Between 05.00 (04.00) and 21.00 (20.00) Times quoted are Winter times, Summer times are in Brackets ( )
Note 2: Between 05.00 (04.00) and 20.00 (19.00) Times quoted are Winter times, Summer times are in Brackets ( )
Note 3: Between 05.00 (04.00) and 22.00 (22.00) Times quoted are Winter times, Summer times are in Brackets ( )
Note 4: Between 03.00 and 23.00 UTC
Note 5: Traffic may be Tactically Level Capped during busy periods
Note 6: Between 10.00 (09.00) and 16.00 (15.00) Times quoted are Winter times, Summer times are in brackets ()
Note 7: Between 09.00 (08.00) and 13.00 (12.00) Times quoted are Winter times, Summer times are in brackets ()
Updated on 28/07/11 RAD City Pair Level Caps
Valid from 22/09/11 APPENDIX 3 - CITY-PAIR LEVEL CAPPING Page 14 of 14
Note 8: Between 06.30 (05.30) and 21.30 (20.30) Times quoted are Winter times, Summer times are in brackets ()
Note 9: Ski Season is from AIRAC December until AIRAC April
Note 10: Between 06.00 (05.00) to 08.00 (07.00) Times quoted are Winter times, Summer times are in brackets ()
Note 11: Traffic can plan OKASI SID even if level capped FL190. OKASI SID is also available for traffic above FL195
Note 12: Traffic Dep. LFP* shall be able to plan via OKASI SID even when level-capped FL190 (SID normally available above FL195)
Note 13: Between 06.30-09.00 Winter and 05.30-13.30 Summer
Note 14: Between 08.00-17.00
RADAN EB:
EBBUFIR Max DCT Below FL115 = 50nms EBBU40001
Above FL115 = 0nms EBBU40001
EBURUIR Max DCT = 0nms EBUR40002
DCT Cross border = Allowed except to/from EH**below FL245 EHEB400
| RADAN EE:
EETTFIR/UIR Max DCT = 0nms Above FL095 (Except Type Helicopter) EETT1, EETT2
= 999nms Below FL095
DCT Cross border = NOT allowed (EEU 400, EEEV400, EEES400) except EF** below FL095 EEEF400
RADAN EF:
EFINFIR/UIR Max DCT = 200nms. EFIN1
DCT Cross border = Allowed from/to ES**, EN**
= Allowed from/to EE** below FL095 EEEF400
The State border between Finland and Russia shall be crossed by using published ATS routes. EFU 400
| RADAN EG:
EGPX/TTFIR Below FL105 Max DCT = 100nms EGPX40020, EGTT40020
EGPX/TTFIR FL105-FL245 Max DCT = 50nms EGPX40020, EGTT40020
EGPX/TTUIR Max DCT = 30nms EGPX40021, EGTT40021
DCT Cross border = Allowed except to/from EH** (EHEG400) (except as listed below)
Exceptions = Traffic Type MIL
1. For Eastbound traffic crossing 09º30’W landfall fix/61ºN boundary with RFL above FL285 Between 00.01-04.50 winter (23.01-03.50 summer) and then via
LAMSO/LARDI /LONAM/TOPPA It is Compulsory to follow one of the Night Time Fuel Saving Routes:
2. For Eastbound traffic via OSBOX/KESIT/BEGID/SOVED/MOGLO crossing IBROD/MIMKU/KUGUR/NIBOG with RFL above FL285 Between 00.01-04.50 winter (23.01-03.50
summer) and then via LAMSO/LONAM/TOPPA It is Compulsory to follow one of the Night Time Fuel Saving Routes:
3. For Eastbound traffic via NETKI/KOKIB/BEXET/OLGON/XETBO/GISTI/RILED/LEKVA/ELSOX Crossing EI/EGTTUIR border with RFL above FL285 Between 00.01-05.20
(23.00-04.20 summer) and then via KONAN/LAMSO/REDFA It is Compulsory to follow one of the Night Time Fuel Saving Routes:
4. For Eastbound traffic via EPUNA/ATSUR/BIMGO/NERTU Crossing EI/EGTTUIR border with RFL above FL285 Between 00.01-05.10 (23.00-04.10 summer) and then via
KONAN/REDFA It is Compulsory to follow one of the Night Time Fuel Saving Routes:
Note:
1. 17.00 (16.00) - 09.00 (08.00) Mon - Fri. (Times in brackets = Summer)
2. 17.00 (16.00) Fri - 09.00 (08.00) Mon. (Times in brackets = Summer)
3. 17.00 (16.00)-10.00 (09.00) Mon-Fri
4. 17.00 (16.00) Fri – 10.00 (09.00) Mon
5. Not available for traffic a) crossing SAMON after 05.10 (04.10 summer ), b) During activation of area EGD125
RADAN EH:
EHAAFIR Below FL065 Max DCT = 50nms EHAA40030
EHAAFIR Above FL065 Max DCT = 0nms EHAA40030
DCT Cross border = Not allowed except above FL245 EHEB400, EHED400, EHEG400, EHEK400
RADAN EI:
EISNFIR Max DCT = 500NM EI1
EISNUIR Max DCT = 600NM EI2
DCT Cross border = NOT Allowed EIEG400
| RADAN EK:
EKDKFIR Max DCT = 999nms (unlimited) EKDK40023
DCT Cross border = Allowed
RADAN EN:
EN**FIR Max DCT = 999nms (unlimited) EN1
DCT Cross Border = Allowed from/to BG**/BI**/EG**/EF**/EK**/ES** ENU 400
RADAN EP:
EPWWFIR Max DCT above FL095 = 0nms except Type Mil DCT = 50nms (Soft Check) EPWW40028
EPWWFIR Max DCT with RFL below FL095 = 50nms EPWW40028, EPWW1
DCT Cross border = NOT Allowed EPED400, EPES400, EPEY400, EPLK400, EPU 400, EPUK400, EPUM400
| En-route DCT Applicable only between 22.00-04.00 UTC Summer 23.00-05.00 Winter
RADAN ES:
ES**FIR/UIR Max DCT above FL095 = 999nms ESAA2
ES**FIR Max DCT below FL095 = 200nms/30mins flying time ESAA1
DCT Cross Border = Allowed from/to EF**, EN**, EK** ESEV400, ESU 400
RADAN EV:
EVRRFIR/UIR Max DCT = 0nms Above FL095 (Except Type “X”)
= 200nms Below FL095
DCT Cross border = NOT Allowed
RADAN EY:
DCT Cross border = NOT Allowed EYES400, EYEV400, EYU 400, EYUM400 EPEY400
| RADAN LA:
LAAAFIR Max DCT = 0nms LAAA40035
DCT Cross border = NOT Allowed LALG400,LALI400,LALW400,LYLA400
RADAN LB:
LBSRFIR Max DCT = 0nms LBSR40037
DCT Cross border = NOT Allowed LBLG400, LBLR400, LBLW400, LBLY400, LTLB400, UKLB400
Updated on 28/07/11 RAD DCT Limits
Valid from 22/09/11 APPENDIX 4 Page 65 of 99
RADAN LC:
LCCCFIR Max DCT = 0nms LCCC40039
DCT Cross border = NOT Allowed LCHE400, LCLG400, LCLL400, LCOL400, LCOS400, LTLC400
RADAN LD:
LDZOFIR Max DCT = 0nms LDZO40040
DCT Cross border = NOT Allowed LDLH400, LDLI400, LDLQ400, LDLY400, LJLD400
| RADAN LE:
LECMFIR/UIR Max DCT = 0nms LECM3, LECM4
LECBFIR/UIR Max DCT = 0nms LECB40041, LECB40042
GCCCFIR/UIR Max DCT = Unlimited LE1, LE3
DCT Cross border = Allowed (except GM**, DA**)
En-route DCT Applicable only between 23.00-04.00 (summer) 00.01-05.00 (winter) LE5000
RADAN LF:
LFFFFIR Max DCT = 50nms LFFF10
LFBBFIR Max DCT = 50nms LFBB10
LFEEFIR Max DCT = 0nms LFEE10
LFMMFIR Max DCT = 30nms LFMM10
LFRRFIR Max DCT = 50nms LFRR10
LFFFUIR Max DCT = 0nms LF2
DCT Cross border = Allowed (except from/to LI**, LS**) LILF400, LSLF400
RADAN LG:
LGGGFIR/UIR Max DCT = 0nms LGGG40051, LGGG40052
DCT Cross border = NOT Allowed LALG400
Exceptions : Military and Training Flights
RADAN LH:
LHCCFIR Max DCT = 0nms LHCC40053
DCT Cross border = NOT Allowed LDLH400, LJLH400, LOLH400, LRLH400, LYLH400, LZLH400, UKLH400
RADAN LI :
LIRRFIR Max DCT = 0nms LIRR40058, LIRR40059
LIBBFIR Max DCT = 0nms LIBB40054, LIBB40055
LIMMFIR Max DCT = 0nms LIMM40056, LIMM40057
DCT Cross Border = NOT Allowed LALI400, LDLI400, LGLI400, LIDT400, LILF400, LILS400, LJLI400, LMLI400, LOLI400, LYLI400.
Training flights departing/arriving from/to aerodromes where no SIDs and STARs are published (except RAD Appendix 5 item A and B) shall file en-route DCTs (max 30 NM) to join
the first/last RP of a STAR/SID to an instrument aerodrome
RADAN LJ :
LJLAFIR Max DCT = 0nms LJLA40060
DCT Cross border = NOT Allowed LJLD400, LJLH400, LJLI400, LJLO400
RADAN LK :
LKAAFIR Max DCT = 0nms LKAA40061
DCT Cross border = NOT Allowed EDLK400, EPLK400, LOLK400, LZLK400
RADAN LM:
LMMMFIR/UIR Max DCT = 0nms LMMM40062, LMMM40063
DCT Cross Border = NOT Allowed (Except as described below) LGLM400, LMDT400, LMHL400, LMLI400
RADAN LO:
LOVVFIR Max DCT = 0nms LOVV40064
DCT Cross border = NOT Allowed LJLO400, LOED400, LOLH400, LOLI400, LOLK400, LOLS400, LPLO400, LZLO400
RADAN LP:
LPPCFIR/UIR Max DCT Below FL245 = 300nms LPPC40065
LPPCFIR/UIR Max DCT Above FL245 = 999nms
LPPOFIR Max DCT = 999nms
DCT Cross border = Allowed except to/from GCCCFIR/UIR/GMMMFIR/GVSCFIR/LECMFIR/UIR LPGC400, LPGM400, LPGV400
RADAN LQ :
LQSBFIR Max DCT = 0nms
DCT Cross border = NOT Allowed LDLQ400, LYLQ400
RADAN LR :
LRBBFIR Max DCT = 0nms LRBB40068
DCT Cross border = NOT Allowed LBLR400, LRLH400, LRLU400, LYLR400, UKLR400
RADAN LS:
LSASFIR/UIR Max DCT = 0nms LSAS40069, LSAS40070
DCT For training, HMU test, NAV AID test, Military and Photographic flights contact Geneva or Zurich
DCT Cross Border = NOT Allowed except Dep. LFGA via BASUD with RFL above FL105 (LS5024) EDLS400, LILS400, LOLS400, LSLF400
RADAN LT:
DCT only allowed within the confines of the TMAs LTBB40071, LTBB40072
DCT Cross Border = NOT Allowed LTLB400, LTLC400, LTLG400, LTOI400, LTOR400, LTOS400, LTU 400, LTUD400, LTUG400, LTUK400
RADAN LU :
LUUUFIR/UIR Max DCT = 0nms LUUU40073
DCT Cross border = Allowed
| RADAN LW :
LWSSFIR Max DCT = 0nms LWSS40074
DCT Cross border = NOT Allowed LALW400, LBLW400, LGLW400, LYLW400
RADAN LY :
LYBAFIR/UIR Max DCT = 0nms LYBA40075, LYBA40076
DCT Cross border = NOT Allowed LBLY400, LDLY400, LYLA400, LYLH400, LYLI400, LYLQ400, LYLR400, LYLW400
RADAN LZ :
LZBBFIR Max DCT = 0nms LZBB40077
DCT Cross border = NOT Allowed LZEP400, LZLH400, LZLK400, LZLO400, LZUK400
Updated on 28/07/11 RAD DCT Limits
Valid from 22/09/11 APPENDIX 4 Page 87 of 99
Withdrawn:
RADAN EK
RADAN EB:
The use of SID/STARs is compulsory for traffic Dep./Dest. EBBR/MB/CI with RFL above FL065
AD Departures/Arrivals DCT = 50nms
DCT Departures/Arrivals ELLX = 10nms
RADAN ED:
AD Departures DCT = 10nms
AD Arrivals DCT = 30nms
EDAH/BC/CD/DB/DF/DH/DM/DP/DT/DV/DW/HI/HK/NY/OP/SB/TL Departure/Arrival DCT = 0nms
EDAC/BH/BM/DC/DE/DN/DS/HL/VE/VK Departure DCT = 0nms
ET** Departure/Arrival DCT = 40nms
RADAN EE:
The use of SID/STARs is mandatory where published. Exemptions PPR SUP-Tallinn ACC
SIDs/STARs shall be completely followed within EETTFIR, leaving or joining at an intermediate point is not
permitted.
AD Departures/Arrivals DCT = 80nms
EETN Departures/Arrivals DCT = 0nms except local Training flights.
RADAN EF:
Departures/Arrivals DCT = 0nms
Arrivals for EFJY/KU/OU/PO/RO/TP/TU/VA
The first Reporting Point of the STAR shall be used as the last Reporting Point of the filed route.
For traffic unable to comply with the minimum level defined in the published STARs, the following connecting
points are available:
EFHK: LAKUT Below FL065
INTOR Below FL075
OKLOR/PEXEN Below FL095
EFJY: DEXIT/DIPAR/LUKAT/MISMU/PELAK/XEDOG Below FL095
EFKU: APROV/GASKU/NUNVA/OTLAT/RIMPU Below
FL095
EFOU: AKOVU Below FL065
ATNIS/EPESA/IPLOT/LUKAS/OSTOS/SISPO/SOPRI/ULTOS/UPMOT Below FL095
EFPO: PEKUS/TUSKU Below FL065
IPSUL/PERIL Below FL095
EFRO: ARNUR/ASKUS/BABUX/KEKOX/KULUS/LEKRA/SITSO/UVIKO/VAPOT Below FL095
EFTP: GIMIS/TURUX/VELUN Below FL065
LEKSU/LERSA/NIKRU/SORUK/UBELO/USEPU Below FL095
EFTU: ALIBA/NIRPU/SITMU/GIMUL/MEDOT Below FL065
ABIKI/GUPLO/OSMIN Below FL095
EFVA: OMELU Below FL065
ETANI/GELSO/NALIX Below FL095
Updated on 28/07/11 RAD Airfield Connecting Points
Valid from 22/09/11 APPENDIX 5 - Airfield DCT Limits Page 2 of 14
RADAN EG:
AD Departures/Arrivals DCT = 50nms
EGHL/LF/LK/NH/TD/TF/VO/WU Departures/Arrivals DCT = 0nms
EGTC Departures = 0nms
Arrivals = 50nms
EGKB Departures = 0nms
Arrivals = 50nms
EGVO = CPT/GWC(departures only), HAZEL (Departures. Arrivals only available for traffic via
Kathy) (EG**5505), PEPIS (arrivals only)
EGXJ = POL
EGXW = BANEM/BCN/BKY/CLN/DIKAS/JACKO/LAPRA/LND/NATEB/NUMPO/SONDO/TIPTA
EGWU = BNN LAM(arrivals only)
EGYD = BANEM (Arrivals only)/CLN
EGYM = NOT
Connecting points NOT ALLOWED for Departing traffic:
EGLL = WELIN
EGNS = BAGSO/LIFFY/NIMAT/NUMPI
EGPK = GOW
EGPH = DCS/GRICE/TLA/TRN
EGSS = EBOTO
EGGW = KENET/WELIN (Departures only)
RADAN EH:
The use of SID/STARs is mandatory, exemptions PPR SUP-Amsterdam ACC
SIDs/STARs shall be completely followed within EHAAFIR, leaving or joining at an intermediate point is not
permitted.
SIDs are compulsory for Dep. EHAM with RFL above FL065 (EH5503)
STARs are compulsory for Dest. EHAM with RFL above FL065, except Dep. Amsterdam Group, EBAW
(EH**5500)
Dest. EHBD/EH via REDFA/LAMSO/MOLIX/TOPPA shall file via HSD. (EH**5501)
Dest. EHRD via LAMSO/MOLIX/REDFA/TOPPA shall file via MASOS (EH**5502)
EHBK/GG Departures/Arrivals DCT = 0nms
Other AD’s: Departure/Arrivals DCT = 30nms (Except 1. where SID/STAR is available
2. RFL above FL065)
Connecting points for ARR. to airfields:
EHBK: GUL/NW (for local training flights only)
EHGG: SO/VZ (for local training flights only)
EHTW: ARNEM
Connecting points for DEP. from airfields:
EHBK: GUL/NW (for local training flights only)
EHGG: SO/VS (for local training flights only)
RADAN EI:
AD Departures/Arrivals DCT = 50NM
EICK/CM/DW/DL/KN/ME/NN/SG/WF/WT Departures/Arrivals DCT = 0NM
EIKY Departures DCT = 0NM
Arrivals DCT = 50NM
Connecting points for DEP/ARR from/to airfields:
EICK: CRK (Arr. below FL080)/GUNSO (Arr.)/OMOKO (Dep.)
EICM: CRN
EIDL: CFN/EGT
EIKN: CON
EIKY: KER
EIME: BAL
EISG: SLG
EIWF: WTD
EIWT: WST
| RADAN EK:
DCT No SID/STAR = 50nms
EKBI/KA/YT Departures = 100nms
EKBI/KA/YT Arrivals = 25nms
EKCH/RK Departures/Arrivals DCT = 0nms
EKBI - Departures for International flights shall be filed via one of the SID termination points (EK**5524)
EKCH – Departures shall be filed via one of the SID termination points except for destinations within the
Copenhagen Group, Malmo Group (EK**5525)
Updated on 28/07/11 RAD Airfield Connecting Points
Valid from 22/09/11 APPENDIX 5 - Airfield DCT Limits Page 5 of 14
Copenhagen Group (except EKCH), except Dest. Copenhagen Group, Malmo Group
ASTOS/BALOX/KEMAX/KOR/MADAG/NOVPO/SIMEG/SONAS/TNO
Compulsory for traffic with RFL below FL065 (EK**5528)
ASTOS/BALOX/BISTA/DOBEL/KEMAX/MAXEL/MIRGO/NOVPO/ROSKU/SIME
G/SORGA/TOBIS/SVD Compulsory for traffic between FL065-FL095 (EK**5529)
ASTOS/BALOX/BISTA/DOBEL/KEMAX/MAXEL/MIRGO/NOVPO/
ROSKU/SIMEG/SORGA/TOBIS, Compulsory for traffic with RFL above FL095
(EK**5530)
EKAH: AAL/ALS/GOTEX/KD/KULUD/LO/RAM/VES
EKCH: BETUD (Not available above FL075 until BETUD) (EK**5532)
MIKSI (Not available for traffic when MULTEX is active, traffic shall file via GOLGA) (EK**5533)
GOLGA (Not available for traffic when EKD352/3 are active, traffic shall file via MIKSI)
(EK**5534)
EKRK: ASTOS/DENEK/GAVBA/KEMAX/NOVPO
(RFL below FL065) BALOX/KOR/MADAG/SONAS/TNO/SIMEG/SVD (EK**5519)
(RFL between FL065-FL095) DOBEL/MIRGO/ROSKU/SORGA/SVD (EK**5521)
(RFL above FL095) DOBEL/MIRGO/ROSKU/SORGA (EK**5520)
EKTS: TESPI
Connecting points for ARR. to airfields:
EKAH: VADIN
EKCH: Arrivals shall be via one of the STAR starting points except for domestic traffic that may join the
STAR via CDA/KOR/TNO (EK**5531)
EKRK: ALM/KOR/ROBUS/SVD/TNO
RADAN EN:
DCT No SID/STAR = 200nms
ENBR/GM/ZV Departures/Arrivals DCT = 0nms
ENCN Departures/Arrivals DCT = 0nms (except local flights within Kjevik Group)
ENRY/TO Departures/Arrivals DCT = 0nms (except local flights within Farris Group)
For non-PRNAV equipped traffic below FL095, the following connecting points are available
ENCN: AMSEV/BEDIK/LANTI/OSVAL/RASVI/SUBUX/TIPSO
ENGM: ADOPI/BELGU/ESEBA/INREX/LUNIP/RIPAM
ENRY: BAMIX/ESOSI/REGMA/SKI/VATEX
ENTO: BAMIX/ESOSI/REPKU/SKI/VATEX
RADAN EP:
For AD’s where SID/STARs are published:
- the last RP of the SID shall be filed as the first RP of the route,
- the first RP of the STAR shall be filed as the last RP of the route.
SIDs/STARs shall be completely followed within EP**, leaving or joining at an intermediate point is not permitted.
| RADAN ES:
Departure/Arrival DCT = 100nms
ESGG/GP/MS/SA/SB Departure/Arrival DCT = 20nms
RADAN EV
The use of SID/STARs is mandatory where published
SIDs/STARs shall be completely followed within EVRRFIR, leaving or joining at an intermediate point is not
permitted
AD Departures/Arrivals DCT = 0nms
EVLA/RA/VA Departures/Arrivals DCT = 0nms (except local training flights with type of
flight “X” or “M”)
RADAN EY
AD Departures/Arrivals DCT = 50nms
RADAN LA:
For AD’s where SID/STARs are published:
- the last RP of the SID shall be filed as the first RP of the route
- the first RP of the STAR shall be filed as the last RP of the route
AD Departures/Arrivals DCT = 50nms
LATI Departures/Arrivals DCT = 0nms
RADAN LB:
For AD’s where SID/STARs are published:
- the last RP of the SID shall be filed as the first RP of the route
- the first RP of the STAR shall be filed as the last RP of the route
AD Departures/Arrivals DCT = 50nms
LBBG/PD/SF/WN Departures/Arrivals DCT = 0nms
LBGO Departures/Arrivals DCT = 24nms
RADAN LC:
AD Departures/Arrivals DCT = 20nms
RADAN LD:
DCT No SID/STAR = 50nms to/from point on airway
LDDU/SB/SP/ZA/ZD Dep./Arr. DCT = 0nms
RADAN LE:
Departures/Arrivals. DCT = 50nms
Dep./Dest. LEAS/BB/BL/DA/GE/IB/LC/LL/MD/MG/MH/PA/RS/ST/ZL DCT = 0nms
Dep./Dest. GC**, LETO DCT = 0nms
| RADAN LF:
For AD’s:
LFBO/JL/KF/KJ/LB/LC/LL/LP/LS/LU/LV/LY/MD/ML/MN/MP/MV/SB/ST/TH/TW/TZ
- The last RP of the SID shall be filed as the first RP of the route,
- The first RP of the STAR shall be filed as the last RP of the route.
For the following airfields (where SIDs and STARs are published)
LFBO/GA/JL/KB/KF/KJ/LB/LL/LP/LS/LU/LY/MD/ML/MN/MP/MV/SB/ST/TH/TW/TZ
Departures/Arrivals DCT = 0nms
Dep. LFRC DCT = 0nms
Dep./Arrivals LFLC/MC/TF DCT = 30nms
Dep./Arrivals LFPG/PO DCT = 50nms
AD Departures/Arrivals DCT = 50nms
For ADs: LFOB/PB/PC/PG/PN/PO/PT/PV – Dep. DCT BAXIR only available below FL195 (LF**5500)
LFPN/PO/PV – Dep. DCT NIPOR only available below FL115 (LF**5508)
Connecting points additional to the published SIDs/STARs for the above ADs:
DEPARTURES:
LGHI: KERMA
LGKV: IDILO
LGSA: SUD (Only for Dest. LGIR at FL090) (LG**5502)
ARRIVALS:
LGAL: ALX (Only for Dep. LGLM) (LG**5503)
LGHI: MES
LGIR: IRA (Only for Dep. LGSA) (LG**5504)
LGKF: KFN (Only for Dep. LGPZ/RX/ZA) (LG**5505)
LGKV: SUTIS (Only for Dep. LGAL) (LG**5501)
LGLM: ALX/LMO (Only for Dep. LGAL/KV) (LG**5506)/MES/NILVA/PEREN
LGMT: OLIDA
LGSA: BAVES (Only for Dep. LGIR) (LG**5509)
RADAN LH:
AD Departure/Arrival DCT = 50nms
Departure/Arrival LHPR DCT = 30nms
Departure/Arrival LHBP DCT = 25nms
RADAN LI:
The use of SID/STARs is mandatory where published.
SIDs/STARs shall be completely followed within Italian airspace, leaving or joining at an intermediate point is not
permitted
Updated on 28/07/11 RAD Airfield Connecting Points
Valid from 22/09/11 APPENDIX 5 - Airfield DCT Limits Page 11 of 14
• Exemptions for the above are city pairs LIMC-LIML, LIML-LIMC, LIMC-LIMF, LIMF-LIMC
Training flights departing/arriving from/to aerodromes where no SIDs/STARs are published (except RAD
Appendix 5 item A and B) shall file en-route DCTs (max 30 NM) to join the first/last RP of a STAR/SID to an
instrument aerodrome
Connecting points for DEP. from airfields for which no SIDs are published
LIBA: EKTOL/POLYP/TOPNO/UVOKA/VIE
LIBN: BRD/GEMVI/GRT/LATAN/TIGRA
LIBV: AME/BAR/BRD/CDC/EKTOL/GEMVI/LATAN/VEGAN/VIE
LICD: LPD (Only for traffic to ABRAM/BIRSA/NIGAT/RALAK/SUDIK) (LM**5500)
LICG: DEROG/DOBIX/MEGAN
LICZ: COBBA/ERNAM/LIBRO/NELDA/NOTRI/PAL/PIMOR/RCA/SIG
LIED: ALG/CAR/KOVAS/RAMEN/TABOT
LIRE: BOL/ELVIN/LAT/PEMAR/RIFFI
LIRG: PEMAR/SIPRO
LIRL: LAT/OST/PEMAR/PNZ/RIFFI/TEA
LIRM: LAT/PNZ/SOR/TEA
LIRS: MAREL (Only available for traffic Type MIL)(LI**5513)
RADAN LJ:
The use of SID/STAR is mandatory where published
SID/STAR shall be followed completely, leaving or joining at an intermediate point is not permitted
AD Departure/Arrival DCT = 50nms
LJLJ/MB/PZ Departure/Arrival DCT = 0nms
RADAN LK:
The use of SID/STARs is mandatory where published.
For AD’s where SID/STARs are published:
- the last RP of the SID shall be filed as the first RP of the route
- the first RP of the STAR shall be filed as the last RP of the route
SIDs/STARs shall be completely followed within LK**, leaving or joining at an intermediate point is not
permitted.
Arrivals
DCT LKCV = 0nms - One of the first reporting points of the STARs published in the MIL AIP shall be filed as
the last reporting point of the route: BEKVI/BODAL/ELPON/GOSEK/VLM
DCT LKKB = 0nms - One of the first reporting points of the STARs published in the MIL AIP shall be filed
as the last reporting point of the route: GOLOP/GOSEK/LOMKI/VLM
Departures
DCT LKCV = 0nms - One of the last reporting points of the SIDs published in the MIL AIP shall be filed as
the first reporting point of the route: BEKVI/BODAL/RAK/VOZ
RADAN LM:
DCT Departures/Arrivals LMML DCT = 0nms
SIDs shall be completely followed within LM**, leaving or joining at an intermediate point is not permitted.
RADAN LO:
The use of SID/STAR is mandatory where published
SID/STAR shall be followed completely, leaving or joining at an intermediate point is not permitted except for
landing at LOWI via KTI/RTT
AD Departures/Arrivals DCT =0nms
Updated on 28/07/11 RAD Airfield Connecting Points
Valid from 22/09/11 APPENDIX 5 - Airfield DCT Limits Page 13 of 14
RADAN LP:
AD Departures/Arrivals DCT =0nms (if published SID/STAR)
=25nms (if no published SID/STAR)
LPLA Departures/Arrivals DCT =50nms
RADAN LQ:
AD Departure/Arrival DCT =50nms
| RADAN LR:
AD Departure/Arrival DCT =50nms
Dep./Dest. LRTR DCT =35nms
Dep./Dest. LRBO/DS/FT/IC/TI =15nms
Dep./Dest. LRBS/OP =50nms
Dep./Dest. LRCK =0nms
Dep. LRCT =25nms
Dest. LRCT =20nms
RADAN LS:
AD Departures/Arrivals DCT = 0nms (if published SID/STAR is connected to route network)
Connecting points for DEP. from airfields for which no SIDs are published
LSMA: AGERI/GERSA/WIL
LSME: AGERI/ELMUR/FRI/GERSA/WIL
LSMD: ALBIX/DEGES/GERSA/VEBIT/WIL/ZUE
LSMM: AGERI/GERSA/WIL
LSMP: FRI/REVLI/SPR/SIROD/TELNO/VADAR/VADEM
LSMU/ZC: WIL
LSZL: LUGAN
Connecting points for ARR. to airfields for which no STARs are published
LSGS/MS: FRI/MOLUS/VADAR/VALOR (Compulsory followed by Y FPL)
LSMA: AGERI/BERSU/KELIP/WIL
LSME: AGERI/BERSU/KELIP/WIL
LSMD: BERSU/DOPIL/KESEX/NEGRA/RILAX/WIL/ZUE
LSMM: AGERI/BERSU/KELIP/WIL
LSMP: BENOT/FRI/SOSAL/ULMES
LSMU/ZC: AGERI/BERSU/KELIP/WIL
LSZG: WIL
LSZL: PINIK
RADAN LT: DCT only allowed within the confines of the TMAs
LTBJ Departure/Arrival DCT = 0nm
Updated on 28/07/11 RAD Airfield Connecting Points
Valid from 22/09/11 APPENDIX 5 - Airfield DCT Limits Page 14 of 14
RADAN LU:
The use of SID/STAR is mandatory where published
SID/STAR shall be followed completely within the LUUUFIR, leaving or joining at an intermediate point is not
permitted
RADAN LW:
SID/STAR shall be followed completely, leaving or joining at an intermediate point is not permitted
RADAN LY:
The use of SID/STAR is mandatory where published
SID/STAR shall be followed completely, leaving or joining at an intermediate point is not permitted
DCT for LYBE/BT/KV/NI/PG/TV/VR DCT = 0nms
For AD's LYBE/BT/KV/NI/PG/TV/VR
- The last RP of the SID shall be filed as the first RP of the route
- The first RP of the STAR shall be filed as the last RP of the route
RADAN LZ:
AD Departures/Arrivals DCT = 30nms
LZIB/PP Departures/Arrivals DCT = 0nms
Departures/Arrivals LZIB shall file via one of the following SID/STAR transition points:
SID - BERVA/NIT/NUBRA/TABIN/TOVKA/VAMOG.
STAR - ABLOM/BERVA/KUNET/NIT/TABIN/XOMBA.
Departures/Arrivals LZPP shall file via one of the following SID/STAR transition points:
SID - BERVA/NIT/OKR.
STAR - BERVA/JAN/NIT
Withdrawn:
Updated on 28/07/11 RAD – FLIGHT PROFILE RESTRICTIONS FPR Limits
Appendix 6 is purely operational data not published through AIS. It contains the vertical profile elements of the LoAs between adjacent ACCs.
These restrictions shall be S (Soft) checked, and the Flight Plan will not be REJected even when there is no reference to the corresponding
restriction in Field 15 however, in the future the output from IFPS will contain a WARNING message to the effect that the restriction has not
been actioned in the Flight Plan. In this case it is the option of the filer to either include or exclude the restriction in the FUEL PLAN. If there is
a requirement to “H” Hard check any restriction, then the corresponding restriction shall be transferred to the National RAD Annex.
RADAN EB
EDYY ACC
RADAN EH
RADAN EI
RADAN EK
RADAN LB
| RADAN LF
Dep. EDFH
Above FL355
Updated on 28/07/11 RAD – FLIGHT PROFILE RESTRICTIONS FPR Limits
RADAN LH
RADAN LJ
RADAN LK
RADAN LO
RADAN LS
RADAN LY
Withdrawn Items
RADAN LF
Not available for traffic To force traffic into the LFRRZS sector
LFEE8018A RAPOR UN857 DIRMO Dest. LFLC
Above 335
Not available for traffic To keep traffic out of the EDYYLXH sector
LFEE8016A MEDOX UN858 VALEK Dest. EDDK
Above FL325
Not available for traffic LFFFACC requirement to respect EBBUACC restriction at the
LFEE8015A SOMIL UN873 BELDI Dest. EBAW, EHBD/BK/WO boundary
Above FL275
Not available for traffic To force traffic into the LFRRZS sector
LFEE8019A KOVIN UY317 RESMI Dest. LFLC
Above FL335
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH BELGIUM & LUXEMBOURG - EB ANNEX EB
Valid from 22/09/11 Page No. 1 of 10
1. Eastbound:
a) KONAN-KOK-SPI-MATUG-POBIX/AMASI
b) KONAN-KOK-DIK-[SUTAL-GTQ]/[PITES-LIMGO-KRH weekend/night]
c) KONAN-KOK-REMBA-DIK-[SUTAL-GTQ]/[PITES-LIMGO-KRH weekend/night]
d) MEDOX-VALEK-LIMGO-BITBU-AMASI
e) MEDOX-VALEK-DIK-ARCKY
f) MEDOX-VALEK-DIK-BENAK-NOR
g) MEDOX-VALEK-LIMGO-PITES-AMASI (weekend/night)
h) ARDEN-NOR
2. Northbound
a) VEKIN-HELEN
b) SORAL-DIK-ARCKY-KENUM
c) SORAL-DIK-BENAK
d) EPL-ROUSY-DIK-ARCKY-KENUM
e) MEDOX-VALEK-DIK-BENAK
3. Southbound
a) NIK-DENOX-[CIV-MEDIL]/[DELOM-MOPIL]
b) NIK-[MOPIL]/[BUB-DIK-GTQ]
c) NIK-[MOPIL/MEDIL]/[BUB-DIK-GTQ]
d) BARTU-MEDIL/MOPIL
4. Westbound
a) NAVAK-SOGRI-BUB-[NIK-COA-SASKI]/[DENUT-RAPIX]
b) NAVAK/ULPEN/AGENI-LNO-[RAPOR]/[DINAN-XERAM]/[IDOSA-RAPOR]/[FAMEN (not below FL310)]/[NORPA-ROUSY-GTQ]
c) KENUM-LNO-[FAMEN(not below FL310)]/[DINAN-XERAM]
d) KENUM-GELSO-[IDOSA-RAPOR]/[DIK-SUTAL-GTQ]
e) TESGA-MAKOB-BATTY-BUB-[NIK-COA-SASKI]/[DENUT-RAPIX]/[DENUT-SASKI]
f) RUDOT-BITBU-DIK-RAPOR
g) LIRSU-BATTY-BUB-[NIK-COA-SASKI]/[DENUT-RAPIX]/[DENUT-SASKI]
h) NTM-RALAM-GOPAS-DINAN-XERAM
i) SORAL-DIK-BUB-[NIK-COA-SASKI]/[DENUT-RAPIX]/DENUT-SASKI]
j) SORAL-DIK-TERLA-LOPIK-SPY-LONAM
k) SORAL-DIK-NIK-TOLEN-SPY-LONAM/MIMVA/RAVLO/[SUPUR-GODOS]
l) EPL-DIK-BUB-[NIK-COA-SASKI]/[DENUT-RAPIX]/[DENUT-SASKI]
m) EPL-DIK-TERLA-LOPIK-SPY-[LONAM]/[ELDIN]/[UNIDO-TOPPA]
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH GERMANY - ED ANNEX ED
Valid from 22/09/11 Page 1 of 79
Note:
Note 1: Weekend: Summer: Friday 16.00 – Monday 06.00 UTC
Winter: Friday 17.00 – Monday 07.00 UTC
Note 2: FL250 is not available as cruising FL for traffic in the Hannover UIR (EDYY6000)
Note 3: FL250 is not available as cruising FL in the EDUUUAC (EDUU6000)
Withdrawn Restrictions
Not available for traffic To segregate departing traffic from overflying traffic
Dep. EDDM
L173 RIDAR - RIXED ED**2970
With Dest. EDDK
Week 08.00-10.00 (07.00-09.00)
Updated on 10/03/11 ROUTE RESTRICTIONS THROUGH ESTONIA - EE ANNEX EE
EE restrictions are valid 05.00 (0400)-22.00 (2200) except where otherwise specified
Valid from 05/05/11 Page No. 1 of 1
Times quoted are Winter times, Summer times are in Brackets ( )
Withdrawn restrictions
Not available for traffic To force traffic onto a more direct route
M/UM611 LOGNA - INTOR EE**2001
Via TLL
Not available for traffic To force traffic onto a more direct route
P/UP733 LATEG - SORPA EE**2004
Via TLL
Updated on 10/03/11 ROUTE RESTRICTIONS THROUGH FINLAND - EF ANNEX EF
Valid from 05/05/11 Page 1 of 1
Withdrawn restrictions
Updated On 28/07/11 ROUTE RESTRICTIONS THROUGH THE UNITED KINGDOM – EG ANNEX EG
Valid from 22/09/11 Where RFL is mentioned this applies only to EG** airspace Page 1 of 52
Withdrawn restrictions:
Only available for traffic Traffic segregation.
Dep./Overfly EH** Traffic limited to Dep/Overfly EH** so that
RIVOT - AKIVO EG**2419
EK** and EH** traffic is segregated. Traffic
from EK shall file via AKIVO via UP60.
UM85 Only available for traffic Traffic segregation.
Dest./Overfly EH** Traffic limited to Dest/Overfly EH** so that
AKIVO - RIVOT EG**2420 EK** and EH** traffic is segregated. Traffic
from AKIVO to EK** shall file via AKIVO via
UP60.
Updated On 28/07/11 ROUTE RESTRICTIONS THROUGH THE UNITED KINGDOM – EG ANNEX EG
Valid from 22/09/11 Where RFL is mentioned this applies only to EG** airspace Page 52 of 52
STANDARD ROUTES
Full details of standard routes within the UK can be found in the UK & Ireland Standard Route Document, available in Adobe PDF and database formats on the UK
Aeronautical Information Service CD-ROM or (in Adobe PDF format only) via the Eurocontrol AIS AGORA website. Enquiries concerning the UK SRD may be made
to the following:
Note 3: FL250 is not available for traffic overflying the Amsterdam FIR (EH**6000)
Withdrawn Restrictions:
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH THE NETHERLANDS - EH ANNEX EH
Valid from 28/07/11 All restrictions with ID EH** are only applicable below FL245 Page No. 8 of 9
2. Northbound
a) HELEN-SPY-GRONY-[BEDUM-JUIST/GREFI]/[EEL-DOBAK]
b) HELEN-SPY-[AMADA]/[LONAM]/[MIMVA]/[SUPUR-GODOS]
c) HELEN-[SOPIX-NIKIL]/[AGISU]/[TOLEN-MONIL]/[RAVLO]/[SUPUR-KOLAG/MIMVA/GODOS]
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH THE NETHERLANDS - EH ANNEX EH
Valid from 28/07/11 All restrictions with ID EH** are only applicable below FL245 Page No. 9 of 9
3. Southbound
a) AMADA-PAM-NIK
b) DOBAK-EEL-PAM-[GORLO-PEVAD/REFSO]/NIK
c) DOBAK-EEL-NIK
d) GREFI-EEL-NIK
e) JUIST-EEL-PAM-[GORLO-PEVAD/REFSO]/NIK
f) JUIST-EEL-SUPUR-KOLAG/MIMVA
g) JUIST-EEL-NIK
h) KUVEK-BARTU
i) LUGUM-EEL-SUPUR-GODOS/KOLAG/MIMVA
j) LUGUM-EEL-SPY-GORLO-PEVAD/REFSO
k) LUGUM-EEL-NIK
4. Westbound
a) DIBIR-LARAS-SUPUR-MIMVA/GODOS
b) DOBAK-EEL-SUPUR-GODOS/KOLAG/MIMVA
c) GOMIS-GORLO-PEVAD/REFSO
d) RKN-SPY-LONAM/[SUPUR-GODOS/MIMVA]/RAVLO
e) RKN-FLEVO-PAM-GORLO-PEVAD/REFSO
f) RKN-PAM-GORLO-PEVAD/REFSO
g) RKN-RENDI-GORLO-PEVAD/REFSO
h) TINIK-TORNU-BREDA-[KUDAD-RAVLO]/[HSD-REFSO]
i) XULET-GORLO-PEVAD/REFSO
Updated on 13/01/11 ROUTE RESTRICTIONS THROUGH IRELAND - EI ANNEX EI
Valid from 10/03/11 Page 1 of 4
Note1: Northern Oceanic Transition Area (NOTA) and Shannon Oceanic Transition Area (SOTA) as per EG AIP ENR 2-2-4-1
Withdrawn Restrictions:
Updated on 13/01/11 ROUTE RESTRICTIONS THROUGH DENMARK - EK ANNEX EK
Valid from 10/03/11 Where RFL is mentioned this applies only to EK** airspace Page 1 of 3
Note 1. (EK**6000) It is compulsory for traffic Dest. EKCH via MONAK/TESPI/TUDLO to file via one of the following options:
P729 TUDLO-LUGAS
T53 TUDLO-LUGAS
T54 TESPI-ROSBI
T55 TESPI-ROSBI
T56 TESBI-ROSBI
T57 MONAK-CDA
T296 MONAK-CDA
T299 MONAK-CDA
Withdrawn Restrictions:
Updated on 07/04/11 ROUTE RESTRICTIONS THROUGH NORWAY - EN ANNEX EN
Valid from 02/06/11 In ENORFIR/UIR BRNAV is mandatory above FL095 (EN**6000A) Page 1 of 1
Withdrawn restrictions:
Updated on 30/06/11 ROUTE RESTRICTIONS THROUGH POLAND - EP ANNEX EP
Valid from 25/08/11 Page 1 of 7
Withdrawn Restrictions:
Updated on 30/06/11 ROUTE RESTRICTIONS THROUGH SWEDEN - ES ANNEX ES
Valid from 25/08/11 ES Restrictions apply only to traffic above FL095 except where specified by Note 2 Page 1 of 11
Withdrawn restrictions:
Updated on 13/01/11 ROUTES RESTRICTIONS THROUGH Latvia – EV ANNEX EV
Valid from 10/03/11 Page 1 of 1
Withdrawn Restrictions:
Updated on 08/07/10 ROUTE RESTRICTIONS THROUGH ALBANIA - LA ANNEX LA
Valid from 26/08/10 LA** restrictions are valid between 0400-2200 UTC except where otherwise specified Page No. 1 of 1
Note 1: Weekend: Fri 12:00 -Mon 04:00, Bank Holiday 21:00 the day before until 04:00 the day after.
Withdrawn restrictions
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH BULGARIA - LB ANNEX LB
Valid from 22/09/11 Page 1 of 2
Withdrawn restrictions
1. Eastbound/Southbound
a) BULEN/DINRO-ODERO/RIXEN
b) ETIDA/NISVA/TIMUR-ADORU
c) NISVA/OSTOV/TIMUR-RODOP
2. Westbound/Northbound
a) MAKOL/UDROS-ARGES/KOMAN/REVDA
b) EVIVI-OKANA/LOMOS/SOMOV
c) VADEN-DOLAP/UTEKA/SOMOV
Updated on30/06/11 ROUTE RESTRICTIONS THROUGH CYPRUS - LC ANNEX LC
Valid from 25/08/11 Military Traffic is exempt from the restrictions below Page 1 of 1
Withdrawn restrictions
Updated on 05/05/11 ROUTE RESTRICTIONS THROUGH CROATIA - LD ANNEX LD
Valid from 30/06/11 | Traffic Dep./Dest. LD** (except LDDU) shall file with RFL Below FL365 within LD** airspace (LD**6000) Page 1 of 4
Withdrawn Restrictions:
A. South/Eastbound
a) BZO-PUL-SPL-DBK-TR
b) BZO-PUL-AIOSA-BRD
c) ABISO-ROKSA-DBK-TR
d) VEKEN-ILB-ZDA-TIBLA-AIOSA-BRD
e) KFT-PODET-ZAG-[DER]/[VBA-SMI]
f) CHI-PUL-KEB
B. North/Westbound
a) KOFER-VAKSU-UMSON-IXONA-PEVAL/ROTAR
b) AIOSA-IXONA-PEVAL-BABAG-NIVAS
c) SIVLA-VBA-OBUTI
Updated on 05/05/11 ROUTE RESTRICTIONS THROUGH CROATIA - LD ANNEX LD
Valid from 30/06/11 | Traffic Dep./Dest. LD** (except LDDU) shall file with RFL Below FL365 within LD** airspace (LD**6000) Page 4 of 4
C. Westbound
a) KOSIV-BOSNA-NAKIT-BABAG/ROTAR
b) BEO-TADAM-PEROT-VBA-ZAG-VANAX-GIMIX-ERKIR
c) SIVLA-VBA-ZAG-VANAX-GIMIX-ERKIR
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH SPAIN - LE ANNEX LE
LE restrictions are valid 05.00 (0400)-22.00 (2200) except where otherwise specified
Valid from 22/09/11 Page No. 1 of 16
Times quoted are Winter times, Summer times are in Brackets ( )
Winter: From the last Sunday of October until the Saturday before the last Sunday of March
Withdrawn restrictions
Not available for traffic To keep traffic out of the LECMDOM sector
BLV/SNR Dest. LEMD LE**2326
With RFL above FL345
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH FRANCE - LF ANNEX LF
Valid from 22/09/11 Page No. 1 of 59
Monday to Friday :
0001 to 0500 UTC (time over OBAKI) summer time
2300 to 0600 UTC (time over OBAKI) winter time
Weekend : Fri 1630 UTC to Mon 0600 UTC (time over
OBAKI) (+ 1 h in winter time)
+ Public holidays common UK and France
Not available for traffic Airspace design
ARBOS - PENDU Via DERAK LF**2967
This traffic shall file via UM982
Not available for traffic 1. Airspace design
UL47 1. Via LUVAL/RLP/LUL/LUPEN 2. Airspace design: Arrival organisation
2. Via EPL
PENDU - IXILU LF**2078
Weekday During weekdays EPL is a dead-end. During weekend, week
Except Dest. EDDR/RZ/FH, ELLX , LFJL/SF/SN/SO/SG nights, Public holidays EPL - DIK is open.
Traffic Dest. ELLX shall file via IXILU UL47 EPL GIVOR
Only available for traffic To force traffic onto a direct route, to avoid LFBBX sector
1. Dep. Bordeaux Group, LFBH/DN
SECHE - FJR LF**3068
2. Dep. LFRRFIR
3. Type MIL
Only available for traffic 1. To facilitate arrivals
FJR - ROVOT 1. Dest. Bastia Group, Nice Group, LFTH LF**2387 2. To force traffic via a specific point
| UL127 2. Via BTA To prevent turns
Not available for traffic To force traffic onto a dedicated route via
ROVOT - STP Dest. Nice Group, Toulon Group LF**3058 1. ABLAK Dest. Nice Group, LFTH
2. MTG Dest. LFMC/TF
Not available for traffic Maximum level requested by LIMMACC
TURIL - STP Dest. LIM*, LIP*, LIQS/RP/RQ, LSZA/ZL/ZS LFLI1041 To offload the LFMME2/3 sectors
Above FL305
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH FRANCE - LF ANNEX LF
Valid from 22/09/11 Page No. 14 of 59
Not available for traffic To organise arrival traffic in the Paris TMA
CNA - POI Dest. Orly Group LF**3008
This traffic shall file via CNA UT158 AMB
UT182
Only available for traffic Arrival restriction
POI - PEPAX Dest. LFPB/PG LF**2548 To avoid LFFOY sector
Except at FL260
Not available for traffic To force traffic on FIR route LMG-BALAN-POI
FOUCO - MANAK LF**2420
Dep. LFBL
Not available for traffic Traffic organisation
1. Via ANG/ARDOD 1. To prevent turning
MANAK - TIRAV LF**2304
2. Weekend 2. To force traffic on WE tracks
UT183 Via GARMI/KOTEM
Only available for traffic To prevent turns
LERGA - FOUCO LF**2962
Via FOUCO [UN460 CNA]/[UT183 MANAK]
Only available for traffic 1. To force traffic via a specific point and to prevent turns at
LERGA - OTROT 1. Via BTA LF**2963 ABN/ETREK/VAREK
2. Dest. Ajaccio Group, Bastia Group, LIEO 2. To join the Corsica distribution network.
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH FRANCE - LF ANNEX LF
Valid from 22/09/11 Page No. 50 of 59
Note:
1. 39ºN = OTARO, DOLIS, KAMER, REQIN, SALMA, CIRTA, MOUET, TABOT
Weekends : Summer: Friday 1500 - Monday 0700 UTC. (Busy Fridays 10.00)
Winter : Friday 1600 - Monday 0800 UTC.
Withdrawn restrictions
Only available for traffic 1. To facilitate arrivals.
FJR - ROVOT 1. Dest. Bastia Group, Nice Group, LFTH LF**2387 2. To force traffic via a specific point;
2. Via BTA To prevent turning.
Not available for traffic To force traffic onto the dedicated route via
ROVOT - STP Dest. Nice Group, Toulon Group LF**3058 3. ABLAK Dest. Nice Group, LFTH
4. MTG Dest. LFMC/TF
Not available for traffic Profile information
FJR - DEGOL Dest. Toulouse Group LF**2886
Above FL345
Not available for traffic Maximum level requested by Milano ACC at NOSTA :
Dest. LIM*, LIP*, LIQS/RP/RQ, LSZA/ZL/ZS Anticipation To offload LFMME2 and LFMME3 sectors
UT24 TURIL - STP LFLI1041
Via LFMME2/LFMME3 sectors LoA Marseille ACC and Milano ACC
Traffic shall file with RFL below FL305
Not available for traffic To offload the LFMMF2 sector. To avoid critical conflicting
STP - ADITA Dep. Bastia Group LF**3027 opposite levels over STP area
Above FL285
Not available for traffic To offload the LFMMF23/M23 sectors. To avoid opposite levels
STP - FJR Dep. LIRA/RF/RN LF**3060 over STP and FJR areas.
Above FL285
Only available for traffic To force traffic on a shorter route
LACOU - SECHE 1. Dest. Bordeaux Group, LFRRFIR LF**2766
2. Dep. Toulouse Group, Montpellier Group
Not available for traffic To force traffic on specific route (Y14.)
UY14 BORDI - PIGOS LF**2480
Dest. LFTZ
Not available for traffic To profile descending/arriving traffic
UZ185 ENOBA - BORDI Dest. Provence Group Toulon Group, LFMI/TW/TZ LFLI1038 LoA between Marseille and Milano ACC
Above FL255
i) MEBAK/RUSIT-LERGA-OLRAK-TBO-SOVAR-ZZA
j) MEBAK-TIS-LMG-FOUCO-CNA-RIVAK/LAPEX
k) MEBAK-TIS-LMG-FOUCO-MANAK-TIRAV-NTS
l) TERPO-TUPAR-CNA-AGN-TOU-LOMRA-ROCAN-PUMAL/GEANT
m) TERPO-TUPAR-CNA-AGN-ANETO
n) NTS-TUPAR-DIDRU-BEBIX-LERGA-KURIR/MTL
o) NTS-TUPAR-DIDRU-BEBIX-VALKU-TIS
p) OKABI-TOU-FISTO-PERIG-FOUCO-ADABI-BOKNO
q) RESMI-DEKOD-DISAK-DEPOM-DIRMO-ETAMO-VALKU-OLRAK-PPG-KANIG/ALBER (above FL285)
r) RESMI-DEKOD-DISAK-DEPOM-DIRMO-ETAMO-VALKU-OLRAK-BADAM-FJR (above FL285)
s) RESMI-KOTAP-KETEX-KUSEK-KOTIS-KUKOR-ADEKA-CFA-MEN-BADAM-NEKTA-PPG-KANIG/ALBER (below FL285)
t) RESMI-KOTAP-KETEX-KUSEK-KOTIS-KUKOR-ADEKA-CFA-MEN-BADAM-FJR (below FL285)
u) RESMI-KOTAP-KETEX-KUSEK-KOTIS-KUKOR-LERGA-LATAM-KOLON-DIVUL-BTA
v) RESMI-DEKOD-DISAK-DEPOM-DIRMO-ETAMO-GUERE-MAKOX-AGN-ANETO
w) RESMI-DEKOD-DISAK-DEPOM-DIRMO-ARTAX-BEBIX-LMG-SAU-BTZ-VRA
x) RESMI-DEKOD-DISAK-DEPOM-DIRMO-ARTAX-BEBIX-LMG-SAU- THUNE-NO
y) RESMI-DEKOD-DISAK-DEPOM-DIRMO-ETAMO-LOE (Dest LFBL)
z) LFPO-EDOXA-ERIXU-ERTOK-ETAMO-LOE (Dest LFBL)
aa) LAGOR-SAU-TBO-PERDU-MLA (week-end route)
bb) MILPA-GIRKU-BALSI-GIROL-MTG-DIVKO-MAMES
cc) VEVAR-BARSO-KOLON-ROKNO-OMARD-VAREK-ALG
dd) TALEP-SODRI-ABRON-ERPIN-BALEN-SORAS/RIXOT
ee) VAMTU-KOLON-GANGU-PADKO-DIVKO-MAMES
ff) FJR-DIVKO-NERAN-BALEN-39N
gg) TIS-MEBAK-GIPNO-BALSI-ROBEX-BLONA
hh) MILPA-MEBAK-LERGA-OLRAK
ii) LUMAS-TURIL-LUSOL-IRMAR-BLONA-KINES
jj) DIBER-SOSUR-MAXIR-LUSOL-IRMAR
kk) LUMAS-OBLAD-STP-PIGOS-ABN
ll) ISTER-LUNOR-NEGAT-OMEDA-TORTU
mm) AJO-PIGOS-BARSO-IRMAR-BLONA
nn) AJO/ELB-PIGOS-BARSO-GIPNO-BULOL-ARDOL
oo) ELB-PIGOS-ETREK-LERGA
pp) KINES-GIPNO-MEBAK-TIS
qq) MEN-LTP-GIPNO-MOLUS
rr) DIVUL-XAMAL-AGEVU (RFL above FL135)
ss) AGEVU-XAMAL-EBORA
tt) AMFOU-A3-MERLU (RFL below FL135)
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH GREECE - LG ANNEX LG
Military Traffic is exempt from the restrictions below
Valid from 28/07/11 Domestic Traffic NOT ABOVE FL305 Page No. 1 of 8
LG** restrictions are valid 04.00-22.00 UTC except where otherwise specified
Withdrawn restrictions:
1. Overflying South/Eastbound
a) RODOP-LMO-MES-LARKI-RDS-EVENO/ALKIS
b) RODOP-LMO-MES-KRC-KUMBI
c) FSK-MES-LARKI-RDS
d) FSK-LMO-RIKSO
e) MAKED-TSL-MES-RDS
f) TALAS-SKP-KEA-[SIT-PAXIS]/KUMBI
g) PINDO-ATV-KEA-[SIT-PAXIS]/TOSKA
h) PINDO-ATV-KEA-KUPIS-KUMBI/MAGIS
i) RUTOM/LATAN-KFN-TRL-MIL-MAGIS/RDS
j) RUTOM/LATAN-KFN-TRL-PLH
k) DINOB/LATAN-KRK-YNN
l) BELIX-PIDAS-SALUN/PLH
2. Overflying North/Westbound
a) EVENO/ALKIS/AGAPI-RDS-LARKI-MES-FSK
b) TOSKA/KAVOS-SIT-AMAXI-DIRMI-KOR
c) ANTAR-KRC-GIKAS-EVIVI/FSK
d) ANTAR-KRC-ASTIS-RIPLI-SKP-TSL-MAKED/TALAS
e) TANSA-AMAXI-DIRMI-MIL-KEA-ATV-SKP-TSL-MAKED/TALAS
f) TANSA-AMAXI-DIRMI-KOR-YNN/KRK
g) METRU-PLH-LORNO
h) METRU-PLH-TRL-KFN-LATAN/RUTOM
i) ABILO-KOR-YNN/KRK
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH GREECE - LG ANNEX LG
Military Traffic is exempt from the restrictions below
Valid from 28/07/11 Domestic Traffic NOT ABOVE FL305 Page No. 8 of 8
LG** restrictions are valid 04.00-22.00 UTC except where otherwise specified
3. DEPARTURES
a) KOR-KRK/YNN
b) NEVRA-KERES-PELAS-TSL-TALAS/MAKED/EVIVI (Dep. LGAV)
c) LARKI-MES (Dep. LGKO)
d) ASTIS-MIL-KOR/TRL
e) DIRMI- ALANI-TRL/KOR
f) ADESO-KOROS-GIKAS-FSK/EVIVI
g) OTREX-PLH-LORNO
4. ARRIVALS
Withdrawn Restrictions:
Not available for traffic To facilitate departing traffic
Except
Z/UZ21 SASAL - SOGMO LH**2042
1. Dep. LO**, LK**
2. Dest. LR**
Updated on 05/05/11 ROUTE RESTRICTIONS THROUGH HUNGARY - LH ANNEX LH
Valid from 30/06/11 Page 3 of 3
1. Eastbound:
a) DIMLO-BABIT.
b) GOTAR-SVR-MAVIR-TEGRI
c) GOTAR-BABIT
d) GOTAR-SVR-MAVIR-MOPUG
e) SASAL-SVR-MAVIR-MOPUG
f) STEIN-TEGRI
g) ALAMU-PUSTA-KEROP
h) ERGOM-DEGET
i) BALAP-NARKA
j) PITOK-BADOR
k) KEKED-KARIL
l) KOPRY-SVR-TPS-SAG-LONLA
2. Westbound:
a) BABIT-DIMLO
b) TONDO-SUBES-ABETI
c) TONDO-SUBES-ARSIN
d) TONDO-BEGLA
e) TONDO-SUNIS
f) PARAK-TPS-PATAK
g) PARAK-TPS-AMRAX
h) BUDOP-NORAH-PATAK
i) BUDOP-NORAH-AMRAX
j) BUDOP-DODAR-GYR-BEGLA
k) DEGET-SUBES-ARSIN
l) DEGET-SUBES-ABETI
m) KARIL-ABILU
n) NARKA-KEKED
o) KARIL-KENIN
p) LONLA-SAG-TPS-PUSTA-VEBAL
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH ITALY - LI ANNEX LI
LI** restrictions are valid 05.00-21.00 (Summer) 06.00-21.00 (Winter) except where otherwise specified
Valid from 22/09/11 Page 1 of 16
Where RFL is mentioned this applies only to LI** airspace
Note 1: Times quoted are Winter times. Summer times are in brackets (). Summer begins: 27/03/11. Winter begins 30/10/11
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH ITALY - LI ANNEX LI
LI** restrictions are valid 05.00-21.00 (Summer) 06.00-21.00 (Winter) except where otherwise specified
Valid from 22/09/11 Page 14 of 16
Where RFL is mentioned this applies only to LI** airspace
Withdrawn restrictions:
Not available for traffic To segregate departing traffic
CHI/ROKIB/VIC Dep. LIPZ LI**2241
Above FL325 at BRENO
Not available for traffic To force traffic via SID
MEDAL Dep. LIRF LI**2139
Except via Z/UZ806
Compulsory for traffic To avoid the LIRRUS sector
UL865 BOL - TAQ Dep. LIML LI**2026
With Dest. LICJ
Not available for traffic To segregate arriving traffic from overflying traffic
UM728 DOKAR - KISTO Dest. Rome Group LI**2118
This traffic shall file via BTA-UL146-ELB
Not available for traffic To force traffic onto a shorter route (flight efficiency)
UM730 VALEN - FRZ LI**2228
Dep. LIRQ
Not available for traffic To segregate departing traffic
M/UM859 ROSKA - BARPI Dep. LIPZ LI**2245
Above FL245 at ROSKA
Not available for traffic To force traffic onto a shorter route (flight efficiency)
UM872 VALEN - FRZ LI**2229
Dep. LIRQ
Only available and compulsory for traffic To segregate arriving traffic from departing traffic
Z/UZ254 BATOX - OKIDO Dest. LIEA LI**2236
Via ELB
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH ITALY - LI ANNEX LI
LI** restrictions are valid 05.00-21.00 (Summer) 06.00-21.00 (Winter) except where otherwise specified
Valid from 22/09/11 Page 15 of 16
Where RFL is mentioned this applies only to LI** airspace
1. GOKEL/PAPIZ-CONTE-LUMAR-LISKO-AKADO-VIC
2. SOPIR-TRP-QUENN-AJO
3. LORNO-CDC-PNZ-ELB-GEN
4. LATAN-PES-NORKI-URBAN
5. LATAN-PES-NORKI-VAPIX-VIC
6. TIGRA-BRD-LUXIL-TEA/SOR/AME
7. LORNO-TOMGI-EMILY-NORKI-URBAN/VAPIX
8. LORNO-TOMGI-SIRGI-SOR
9. OLGAT-ENOXA-VIE/GARGA/AIOSA
10. BRD-VIE-ANC-FRZ-GEN
11. ROTAR-AKADO-VIC-SUXAN
12. PEVAL-NIVAS-SOTOV
B. Northbound
1. MADIR-PAL-PNZ-LAT-PEMAR-VERUN-FER
2. OSMAR-CAR-BOLOT-AJO-TORTU-LUKIM-DESIP-ABESI
3. LORNO-TOMGI-EMILY-NORKI-VIC
4. TEA-PES-ANC
C. North-Eastbound
1. NOSTA-ABN-GEN-MONEB-GIBLO-NESTI-SUMIR-MALUG
2. NOSTA-ABN-GEN-LUPOS-BOA-CHI
3. NOSTA-ABN-GEN-MONEB-DESIP-ABESI/CANNE
D. South-Eastbound
1. BIBAN-SRN-ADOSA-CHI-ANC-VIE-BRD-NOSTO/TIGRA
2. DOKAR-KISTO-NERAR-BELIX
3. REKTO-ALG-SODIO-OSMAR
4. BZO-PEVAL
5. BZO-AKADO-GARGA-ENOXA-GOKEL/TIGRA/NOSTO
6. DETSA-CHI-ANC
7. NERAR-RCA-VENIM
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH ITALY - LI ANNEX LI
LI** restrictions are valid 05.00-21.00 (Summer) 06.00-21.00 (Winter) except where otherwise specified
Valid from 22/09/11 Page 16 of 16
Where RFL is mentioned this applies only to LI** airspace
E. Southbound
1. ODINA-SRN-KARPI-AMTEL-TAQ-RUTON-GIANO-TRP-SENSI
2. NATAG-BOA-VALEN-AMTEL-TAQ-RONAB-PININ-TUNEX
3. ODINA-EVANO-DORAV-IXITO-TALEP
4. ANC-PES-TEA
5. LIKDA-VIC-FER-VALEN-TAQ
6. DETSA-CHI-TAKUP-NIKMA
F. Eastbound/Westbound
1. LATAN-CRN-CDC-PAL-TRP-TUPAL
2. GOBIS-ALG-ROTUN-NERAR-CRN-RUTOM
3. DORAD-ALG-ROXAN-PNZ-SOR-BRD-GOKEL
4. TOP-GEN-FRZ-ANC-TORPO
5. ALG-BATOX-OST-PES-TUNAL
6. GOKEL-BRD-SOR-PNZ-ALG
7. KATTI-PES
8. GEN-BOA-CHI-DOL
9. RIFEN-PAR-LAGEN
G. South-Westbound/North-Eastbound
1. DINOB-MONIK-AMREX-LORED
2. XOLTA-SOR-GIANO-SUSIP
H. Westbound
1. ROTAR-AKADO-VIC-ORI-SRN-TERSI-AOSTA-MOLUS
2. DETSA-BZO-LUSIL-EVANO-VAMTU
I. Eastbound
1. CHI-LABIN
J. North-Westbound/South-Eastbound
1. ALG-SODIO-CAR-BULAR-MEGAN-SENSI
Updated on 10/03/11 ROUTES RESTRICTIONS THROUGH SLOVENIA - LJ ANNEX LJ
Valid from 05/05/11 All IFR Check Flights, Military Flights are exempt from Slovenian RAD Restrictions Page 1 of 2
Withdrawn Restrictions
Updated on 10/03/11 ROUTES RESTRICTIONS THROUGH SLOVENIA - LJ ANNEX LJ
Valid from 05/05/11 All IFR Check Flights, Military Flights are exempt from Slovenian RAD Restrictions Page 2 of 2
a) VEKEN-ILB-SPL
b) VEKEN-ABISO-NEMEK/EBITI-ROLBA
c) NIPEL-ABISO-ROLBA/NEMEK
d) KFT-ZAG
2. South/Westbound
a) GRZ-ARLON-DOL-ILB-BAXON
b) GRZ-ARLON-RIFEN
c) DIMLO-DOL-RIFEN
3. North/Westbound
a) GORPA-DOL-GIMIX
b) SABAD-EPODO-GIMIX
c) GISER-MAXUR-GRZ
d) ZAG-GRZ
4. North/Eastbound
a) NIKOL-ALIVO-VALLU-LAPNA-OSMOT/GOLVA
b) CHI-DOL-VALLU-LAPNA
Updated on 05/05/11 ROUTE RESTRICTIONS THROUGH CZECH REPUBLIC – LK ANNEX LK
Valid from 30/06/11 All RAD restrictions are MANDATORY for traffic Type MIL except where explicitly noted. Page 1 of 10
Withdrawn restrictions:
Updated on 16/12/10 ROUTE RESTRICTIONS THROUGH MALTA - LM ANNEX LM
Valid from 10/02/11 Page 1 of 3
Withdrawn restrictions:
Updated on 16/12/10 ROUTE RESTRICTIONS THROUGH MALTA - LM ANNEX LM
Valid from 10/02/11 Page 3 of 3
1. Eastbound:
a) SONAK-DOBIX-AMIBO-ARLOS
b) SONAK/BASMO-GZO-DEMAG
c) SONAK-GZO-BONAR
d) NIGAT-LPD-KUTOS-ARLOS
e) SONAK/NIGAT-SUDIK-ELIMO
f) SUBOK-DEMAG
g) SUBOK/ORTAP-AMIBO-ARLOS
h) OMENI-BONAR
2. Westbound:
a) ARLOS-AMIBO-DOBIX-SONAK
b) ARLOS-KUTOS-LPD-NIGAT
c) DEMAG-GZO-SONAK/BASMO
d) DEMAG-SUBOK
e) INDOT-SUDIK-SONAK/NIGAT
f) INDOT-LPD-NIGAT
g) ARLOS-AMIBO-ORTAP/SUBOK
3. Northbound:
a) SARKI-MABOX-ADEXI/LONDI
b) LUMED-SUDIK-GZO-LORED/NELDA/DILIN/DIGOS
c) SARKI-SUDIK-LORED
d) SARKI-LPD-SONAK
e) INDOT-MLT-GZO-ADEXI/DIGOS/DILIN
f) OLMAX-ASKOT
g) RALAK – ADEXI
h) LUMED-UPLIT-ADEXI
4. Southbound:
a) ADEXI/DIGOS/PAN-LPD-ABRAM
b) LORED-SUDIK-VARIG
c) SONAK-ABRAM
d) DIGOS/MARON-GZO-SUDIK-LOTIN
e) DIGOS-GZO-BONAR
f) SUBOK/TISAL/VENIM-BINKO-BONAR
g) ADEXI-RALAK
h) MARON-GZO-ELIMO
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH AUSTRIA - LO ANNEX LO
All IFR Check Flights, Austrian Military Flights and Sightseeing Flights are exempt from
Valid from 22/09/11 Page No. 1 of 10
Austrian RAD Restrictions
Withdrawn restrictions
Not available for traffic To segregate the Dep./Dest. track to/from LKTB
STO - MIKOV Dest. LKTB LO**2121
This traffic shall file via STO Z37 MIKOV
M984
Not available for traffic To force traffic onto the correct route
PUBEG - STO Above FL125 LO**2113
Except Type Austrian Mil
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH AUSTRIA - LO ANNEX LO
All IFR Check Flights, Austrian Military Flights and Sightseeing Flights are exempt from
Valid from 22/09/11 Page No. 10 of 10
Austrian RAD Restrictions
1. Eastbound
a) LIZUM- VEKEN-ROLBA/ILB
b) BIRGI-GRZ-BABIT
c) BIRGI-GRZ-GOTAR-SOGMO
d) BIRGI-GRZ-TEGRI
e) MIQ-VELOM-BUG
f) MIQ-VELOM-DIVAL-SVR
g) MUN- LOMRO-NIPEL-ILB/SABAD/NEMEK/ROLBA
h) UNKEN -KFT-ZAG
i) UNKEN -OBEDI-BABIT
j) UNKEN -OBEDI-GOTAR-TEGRI
k) UNKEN -OBEDI-GOTAR-SOGMO
l) OKF-SASAL-BABIT (for traffic Dep. LKAAFIR)
m) VIBUG-DETSA-CHI
2. Westbound
a) BUDOP-BEGLA-STO-VLM
b) BUDOP-BEGLA-STO-VOZ
c) BUDOP-LALIN
d) DEGET-LNZ-TALAL (for traffic Dest. EDDF/DN)
e) DEGET-SITNI-SBG
f) DEGET-SUBES-ALB
g) DIMLO-GRZ-ERKIR-KPT
h) ILB-GIMIX-KPT
i) SABAD-GIMIX-KPT
j) GORPA-GIMIX-KPT
k) VBA-DIPSA-NAPSA
l) VBA/ZAG-GRZ-LNZ
m) TONDO-FRE-ALB
n) TONDO-BEGLA-LALIN
o) TONDO-STO-VLM
p) TONDO-STO-VOZ
q) TONDO-SUBES-LNZ-TALAL (for traffic Dest. EDDF/DN)
r) TONDO-SUBES-SITNI-SBG
s) TONDO-SUNIS-SBG
Updated on 21/01/10 ROUTE RESTRICTIONS THROUGH PORTUGAL - LP ANNEX LP
LP restrictions are valid 05.00 (04.00)-22.00 (22.00) except where otherwise specified
Valid from 11/03/10 Page No. 1 of 2
Times quoted are Winter times, Summer times are in Brackets ()
Withdrawn restrictions
Dest. LPFR: Traffic entering Lisboa FIR from VES, waypoint MOSEN is recommended via BABEX DCT ALAGU
Dest. LPPT: Traffic entering Lisboa FIR via waypoint NARBO/RALUS/TURON is recommended via XAMAX
Traffic entering Lisboa FIR via waypoint MOSEN/NINOS/RIVRO is recommended via INBOM
Dep. LPPT: Whenever runway 21 is in use, traffic exiting Lisboa FIR via waypoint RAKOD is recommended via EXONA DCT PORLI
Other Suggestions:
Intermediate waypoint NARTA is recommended to avoid cross-border entry exit through Casablanca FIR/UIR
Updated on 16/12/10 ROUTES RESTRICTIONS THROUGH ROMANIA - LR ANNEX LR
Valid from 10/02/11 Page 1 of 1
Withdrawn Restrictions:
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH SWITZERLAND - LS ANNEX LS
Valid from 22/09/11 Page No. 1 of 31
Not available for traffic 1. To avoid LSAGN sector during the busy Ski Season
1. Dep. EB**, EG**, EH**, EI**, LFP* 2/3. To avoid creative flight planning
With Dest. LSGS/MS
UZ24 MOROK - BOLGI LSLF1063
Saturdays 0700-1800 (Note 1)
2. Dest. LSZB
3. Via LSAZUTA/CTA
Only available for traffic 1. A short cut for traffic heading southeast
Z50 GERSA - RESIA 1. Dep. Basle Group, Zurich Area, EDTD LS**2086 2. A shortcut for arriving traffic
2. Dest. LSZS
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH SWITZERLAND - LS ANNEX LS
Valid from 22/09/11 Page No. 28 of 31
Withdrawn restrictions:
1. Northeastbound:
a) BEGAR-TRA-DEGES-GAMSA-MADEB
b) KORED-BERSU-KUDES-ROMIR-LOKTA-TGO
c) KORED-BERSU-[DEGES-GAMSA-MADEB]/[KUDES-NUNRI]
d) KORED-BERSU-DITON-RIPUS-ODINA
e) ABESI-KUDES-[GAMSA-MADEB]/[ROMIR-LOKTA-TGO]
f) ABESI-ELMUR-[DITON-OLBEN-BENOT]/[HOC-LUL/MOROK]
g) SUXAN-ELMUR-HOC-LUL/MOROK
2. Southwestbound:
a) KPT-NEGRA-TRA-HOC-LUL/MOROK
b) KPT-NEGRA-TRA-[OLBEN-BENOT]/[ODINA]
c) NATOR-OLBEN-BENOT
d) NATOR-TRA-[ODINA]/[DEGES-GAMSA-MADEB]
f) MOPAN-OLBEN-BENOT
Updated on 28/07/11 ROUTE RESTRICTIONS THROUGH TURKEY - LT ANNEX LT
Valid from 22/09/11 Page 1 of 5
Note:
1. Domestic traffic (Dep./Dest. between Turkish airports) is not subject to the above restrictions.
2. Night = 17.30-02.30 (AIRAC April - AIRAC October inclusive) 17.00-04.30 (AIRAC November - AIRAC March inclusive)
3. Night = 17.30-02.30 (AIRAC April - AIRAC October inclusive)
Withdrawn restrictions
Updated on 24/12/09 ROUTE RESTRICTIONS THROUGH FYROM - LW ANNEX LW
Valid from 11/02/10 Page No. 1 of 1
Withdrawn Restrictions.
Not available for traffic To segregate overflying traffic
UL617 RAXAD - MAKED LW**2010
Dest. LGTS from arriving traffic
Only available for traffic To segregate arriving traffic from
T/UT389 NASKO - ERANA LW**2011
Dest. LGTS overflying traffic
1. South/Eastbound
a) RAXAD-SIN-RUGAS
b) RAXAD-MAKED
c) DOBAR-TALAS
d) MAVAR-TALAS
2. North/Westbound
a) RUGAS-SIN-RAXAD
b) MAKED-NEGOT-NASKO-RAXAD
c) TALAS-MAVAR
d) DISOR-NEGOT-MAVAR
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH SERBIA and MONTENEGRO - LY ANNEX LY
Valid from 28/07/11 Page No. 1 of 5
Note 1: Valid from the first AIRAC date in April until the last AIRAC date in October
Withdrawn Restrictions:
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH SERBIA and MONTENEGRO - LY ANNEX LY
Valid from 28/07/11 Page No. 4 of 5
1. South/Eastbound
2. North/Westbound
Withdrawn restrictions:
Updated on 02/06/11 ROUTE RESTRICTIONS THROUGH SLOVAK REPUBLIC - LZ ANNEX LZ
Valid from 28/07/11 Page 3 of 3
A. SouthEast
B. South
Withdrawn NERS
Updated on 10/02/11 North Atlantic European Route System (NERS) ANNEX NAT
Valid from 07/04/11 EASTBOUND NON-Common Portion + MIL Page No. 2 of 2
EASTBOUND NAT
ENTRY
FIR OR DEST GAT/OAT ROUTE
POINT
UN610 STN UN615 CALDA DCT DESIG UL603 DOLAS OAT DCT EA1
BILLY TR1 NAVPI
UN610 NATEB UL602 OTR UL90 DOLAS OAT DCT EA1 TR1 NAVPI
UN601 STN UN615 CALDA DCT DESIG UL603 DOLAS OAT DCT EA1
TR1 NAVPI
AKIVO
UN601 STN UN610 NATEB UL602 OTR UL90 DOLAS OAT DCT EA1 TR1
NAVPI
UN590 GOW UN615 CALDA DCT DESIG UL603 DOLAS OAT DCT EA1
TR1 NAVPI
NINEX
UP24 NEVIS UP58 FINDO UN610 NATEB UL602 OTR UL90 DOLAS OAT
DCT EA1 TR1 NAVPI
UP58 SUPIT UN590 GOW UN615 CALDA DCT DESIG UL603 DOLAS
OAT DCT EA1 TR1 NAVPI
ETSOM
UP58 FINDO UN610 NATEB UL602 OTR UL90 DOLAS OAT DCT EA1
TR1 NAVPI
UN572 TIR UN580 GOW UN615 CALDA DCT DESIG UL603 DOLAS OAT
DCT EA1 TR1 NAVPI
GINGA
UN572 TIR UN580 GOW UL602 OTR UL90 DOLAS OAT DCT EA1 TR1
NAVPI
DCT IBROD UP857 MAC UN57 DCT UN615 CALDA DCT DESIG UL603
OSBOX DOLAS OAT DCT EA1 TR1 NAVPI
| ED**, ET**
DCT MIMKU UP6 REMSI UL603 DOLAS OAT DCT EA1 TR1 NAVPI
SOVED DCT MIMKU UP6 REMSI UL603 DOLAS OAT DCT EA1 TR1 NAVPI
DCT NIBOG UN551 BEL UL10 WAL UM16 DOLAS OAT DCT EA1 TR1
NAVPI (Note: Not below FL285)
NETKI
DCT NIBOG UN551 NELBO UP6 REMSI UL603 DOLAS OAT DCT EA1
TR1 NAVPI
UL975 WAL UM16 DOLAS OAT DCT EA1 TR1 NAVP
(Note: Not below FL285)
LIFFY
UL975 DESIG UL603 DOLAS OAT DCT EA1 TR1 NAVPI
(Note: Only available between FL245-FL285)
UM140 EXMOR OAT DCT VLN TR1 NAVPI (Note: Not below FL245)
NORLA UM140 SAM UL620 MID UM185 BPK DCT UMBAG OAT DCT NAVPI
(Note: Not below FL245)
UL607 ABDUK UL180 DIKAS OAT DCT BZN TR1 NAVPI
EVRIN
(Note: Not below FL245)
UL180 DIKAS OAT DCT BZN TR1 NAVPI
LESLU UL180 MERLY UM140 EXMOR OAT DCT VLN TR1 NAVPI
(Note: Not below FL245)
UL620 LND OAT DCT MAM TR1 NAVPI (Note: Only available between
GAPLI FL245 – FL275)
UN20 GITUS OAT DCT MAM TR1 NAVPI (Note: Not below FL275)
Withdrawn MIL:
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 1 of 16
1
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 2 of 16
2
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 3 of 16
3
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 4 of 16
4
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 5 of 16
5
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 6 of 16
6
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 7 of 16
7
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 8 of 16
8
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 9 of 16
9
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 10 of 16
10
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 11 of 16
11
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 12 of 16
12
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 13 of 16
13
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 14 of 16
14
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 15 of 16
15
Updated on 07/04/11 North Atlantic European Routing System (NERS) ANNEX NAT
Valid from 02/06/11 EASTBOUND Common Portion Page No. 16 of 16
Withdrawn NERS
16
Updated on 10/06/10 NERS Annex NAT
Valid from 29/07/10 General Procedures Page 1 of 6
1. Introduction
This paper outlines the basic procedures for NERS and is intended as a guideline for
AOs, ANSPs, Operating Agencies and Computer Flight Plan Service Providers.
When applied, NERS are mandatory for Eastbound NAT OTS traffic, crossing W030º00
between the hours of 02.00-05.00 UTC, to the specified system airports(s).
NERS routes are published in the CFMU RAD Annex NAT in two sections; ‘Common
Portion’ and Non-Common Portion’
| System Airports
NERS IDENTIFIER
The NERS identifier shall only be used in the NAT OTS message, all other
communications shall use the full ATS route/fix identifiers
The ‘E’ is used to identify the route as a NERS route and to differentiate it from a NARS
(North American Routing System) route which commences with an ‘N.’
The numbering e.g. 1234 is the route number. All Eastbound NERS have ODD numbers
commencing with 0101 and continuing to 9999.
Exceptionally Z1100
The Z prefix identifies a NERS route which is normally not flight plannable due to RAD
restrictions and is made available only in unusual circumstances
In order to allow AOs to utilise more direct profiles and reduce fuel burn/emissions,
NTFSRs have been established for use during night hours. The NTFSRs are
promulgated as direct (DCT) routings from an Oceanic Landfall fix to specific fixes on the
UK Eastern boundary for flights above FL285. For traffic via Shannon’s airspace
(including NOTA/SOTA) the traffic shall plan via a designated fix on the EI/EG boundary.
NTFSRs are to be used in conjunction with the NERS and for ease of reference have
been included in the NERS Eastbound Common Portion route table. When transiting
from an Oceanic Landfall fix to the UK Eastern boundary fix between which an NTFSR
exists, it is mandatory to file the NTFSR during the promulgated times of availability, as
listed in the notes section of the Common Portion table. Unless otherwise specified in
the RAD, If no NTFSR exists between the chosen landfall/exit fix, a NERS route (for
system airport destinations) or RAD compliant route (non-system airport) should be
used.
NTFSRs can be used for destinations to both system and non-system airports (with
some exceptions, as noted in the NERS notes/RAD). Traffic to these excluded
Updated on 10/06/10 NERS Annex NAT
Valid from 29/07/10 General Procedures Page 2 of 6
destinations shall use either a NERS for a system airport or a RAD compliant route for a
non-system airport.
The NERS numbering convention is used for the NTFSRs, however the NTFSRs are
identified by the prefix “F” (e.g. F0009) to differentiate them from a NERS route. AOs
should be aware that no “alternative route” relationship exists between similarly-
numbered routes (e.g.E0009 and F0009).
The NERS Common Portion encompasses an area from ‘Coastal Fixes’ (which are either
‘Oceanic Exit Points’ (OEPs) or “Landfall Fixes” in UK, French and Irish airspace) to
‘Inland Navigational Fixes’ (INFs) which are normally on the UK Eastern/Southern UIR
boundary and on a longitudinal line through France.
The NERS Common Portion contains a list of routes (normally RAD compliant) which
shall be utilised for flight planning purposes at all times when operating to a ‘System
Airport.’
The Non-Common Portion routes are promulgated for flight planning from the INF to
System Airports. All routes contained within the Non-Common Portion are RAD
compliant and are available for flight planning purposes at all times. The Non-Common
Portion routes are optional, except when a NERS is mandated on the OTS message,
then they become mandatory.
When a NERS (or NTFSR) route identifier is published via the NAT Eastbound OTS
message from a specified OEP to a NERS system airport, AOs will reference the CFMU
RAD Annex NAT route tables for the NERS route identifier and corresponding flight plan
routeing. This route shall be filed via IFPS.
The NERS route identifier shall not be used by ATC or aircraft operating crew, with
all clearances being standard route/fix descriptions.
On the NAT Eastbound OTS message, NERS requirements will appear in the ‘EUR RTS
EAST’ line entry relevant to an OEP and will list an applicable system airport together
with NERS route identifiers. For example a line entry for OEP ATSIX with Frankfurt,
Heathrow and Paris CDG inbounds being “NERS managed” would appear as follows:
ATSIX…..EUR RTS EAST EDDF E127A EGLL E135A LFPG E137A. A sample signal is
at Appendix ‘A’.
Updated on 10/06/10 NERS Annex NAT
Valid from 29/07/10 General Procedures Page 3 of 6
If the daily NAT Eastbound OTS signal does not mandate any NERS routes for a system
airport destination through the individual OEPs/Landfalls, or flights operate outside of the
validity period as specified in Para 1, AOs shall then flight plan any suitable NER
connected to the OEP except in the case of RANDOM traffic (see para. below). This
ensures a strategic management arrangement is in place for flights destined to any of the
four system airports at all times and naturally deconflicts core traffic flows.
Any flights planning to Non-System airports shall file a NTFSR when available, or RAD
compliant route. The NERS Common Portion tables may be utilised as guidance for flight
planning route portions from the Oceanic Landfall fix to the INF and the Non-Common
Portions may also be utilised in a similar manner, breaking off at a suitable point to the
destination.
Traffic on Random Routes across the NAT shall file a NTFSR where available, or a RAD
compliant route in European Domestic airspace. If a NERS is mandated from an OEP,
then random traffic entering European Domestic airspace via the specified OEP shall
adhere to the appropriate NERS routing.
In order to generate daily NERS requirements, key ANSPs are required to review
available data and identify which system airport destinations will require specific NERS
being assigned.
Prior to the conference, Shanwick OACC shall obtain (from Gander) and fax a copy of the
proposed OTS to those units which require it, in order for them to assess any daily NERS
requirements for presentation at the tele-conference. UK FMP shall also obtain
notification of any Danger Area activation which will affect the availability of the NTFSRs.
Should a closure of any NTFSR be required, this shall be presented at the tele-
conference. In addition, a NOTAM shall be issued by NATS advising of the closure. The
CFMU shall be requested to make the affected route unavailable for flight planning
purposes. The result of the conference shall be recorded in the respective FMPs, and the
NMC will have the responsibility of ensuring that any NERS requirements are forwarded
via Shanwick to Gander OACCs for entry into the Daily NAT Eastbound OTS signal to be
published later that day.
If any unforeseen NERS requirements become apparent at the time of, or after the
generation of the NAT Eastbound OTS signal, Shanwick shall advise the London FMP
who will co-ordinate with adjacent units if necessary. ACCs should be aware of the
impact this may have on AO flight planners, and such changes should be avoided
wherever possible.
a. Re-routeings – Oceanic to Domestic (to join the NERS Common Portion routes)
Through the normal course of operation, the relevant OACC may elect to switch aircraft
between NAT tracks. In doing so, the relevant OEP for the flight will be amended and
Updated on 10/06/10 NERS Annex NAT
Valid from 29/07/10 General Procedures Page 4 of 6
therefore be subject to any NERS routeing requirement associated with the new OEP.
The ATC flight plan, through receipt of an ACH message from CFMU/IFPS will reflect the
amended route to be flown and will be CFMU RAD Annex NAT compliant.
In both cases above, the domestic airspace routing across the NERS Common Portion,
as passed by ATC on transfer from Shanwick, shall take this into account. The table at
Appendix B give examples of typical revision arrangements.
In all cases, any re-routeing information is to be passed using full ATS route/fix
identifiers; NERS route identifiers shall not be used at any time in FPLs or radio
communications.
On transfer from Shanwick OACC control, all flights will be expected to continue as per
their original flight planned route, or as amended by the relevant OACC, taking due
account of the NERS routeing requirements.
In the event that an aircraft subject to NERS requirements requests a re-route once
inside the NERS Common Portion (i.e. within the Shannon, Scottish, London or Brest
ACC areas of responsibility and under radar control), or the ACC itself is able to offer
beneficial re-routes, the handling ACC should not approve such a re-route without prior
consultation with those adjacent units expecting to handle the flight. Such co-ordination
is only required when the re-route results in:
i. a change of entry point into adjacent airspace resulting from tactical direct routeing
(e.g. an aircraft entering LACC airspace at LESLU in place of the planned entry via
LEDGO, but re-joining the NERS Common Portion route at point LND)
ii. a change of entry point into adjacent airspace which will also change the NERS
Common Portion exit point (e.g. Shannon ACC re-routes an aircraft entering LACC
airspace via SLANY which is planned to leave via XAMAB, to now enter via LEDGO
to leave via ANNET. Shannon co-ordinates with both LACC and Brest ACC, if Brest
agrees Shannon will inform LACC. Due to telephone connectivity, LACC will co-
ordinate when required with adjacent ACCs on behalf of Shannon with the exception
of Brest.
iii. a change of entry point into adjacent airspace which may or may not change the
NERS Common Portion exit point (e.g. Shannon ACC will not know if the Common
Portion exit point will be changed. LACC will assess if additional co-ordination with
neighbouring ACCs is required and carry it out on behalf of Shannon with the
exception of Brest)
Failure to effect such co-ordination could cause imbalances in demand and sector
throughput down route, thus negating any NERS principles and effects. The Table at
Appendix C gives examples of re-routing action for flights within the NERS Common
Portion
In all cases of co-ordinated re-routes, as well as passing any revised route clearance to
an aircraft it is the responsibility of the handling ACC effecting a re-route to generate an
ATC Flight plan Proposal (AFP) message to IFPS. This ensures that CFMU tactical
systems and route charging mechanisms are updated accordingly (CFMU IFPS
Handbook refers).
Tactical arrangements for re-routeings within the NERS Common Portion can be
established on a daily basis between the watch supervisory staff and FMPs of the
relevant ACCs.
Updated on 10/06/10 NERS Annex NAT
Valid from 29/07/10 General Procedures Page 5 of 6
APPENDIX A
APPENDIX B
Re-Routes - Oceanic to Domestic (to join the NERS Common Portion routes)
APPENDIX C