RAD Evolution Workshop RAD Purpose and evolutions to-date - IP/1

1. RAD Evolution WorkshopRAD Purpose and evolutions to-date - IP/1 Beginning, Evolution, Management, Control Tihomir Todorov Head of Section Airspace Design 12 DEC 2018 RAD WS 12 - 13 DEC 2018, Brussels, Belgium

2. before 1996 - mid 2012

3. Structural Airspace Restrictive Measures • The initial aim was to communicate to AOs the ATC / ATFM and structural airspace restrictive measures imposed by States • Before 1996 … Traffic Orientation Scheme (TOS) … • Before 1996 … Contingency Routing Scheme…: • 1999 - 2001 …. Standard Routing Scheme (SRS) (Contained tables with some ATS routes restrictions and routing suggestions for main traffic flows via States) • Due to several non-operational crises in Europe the SRS was converted into Avoidance Routing Scheme (ARS)

4. History of the RAD The Beginning • Route Availability Document (RAD) as from 2001 • Discussions on RAD started somewhere in 1997 at CRS / TOS Meeting that originally defined the SRS • Proposal tabled by AO organisation - tell us what you don’t want • Austria - First to agree the concept followed by Germany • Germany - First to adopt full RAD principle - SRS plus AIP route flow restrictions • Two parts: Part 1 - State by State, Part 2 - Pan European • February 2001 - Scandinavia added • Proposals out to: UK, France for Paris, Reims and Brest (1 Annex) and Bordeaux, Turkey • Transition starting 19th April 2001 and SRS was withdrawn • End transition 5th October 2001 - All States compliant

5. History of the RAD Benefits and dis-benefits Benefits • Computer readable • Electronic download into external computer systems • Sole source data • Single publication • Single document versus AIPs • All AIP route flow restrictions included (many currently checked) • Pan European • Automatic AO compliant routes • Reduction/elimination of MANual queues • No requirement by AO’s for route catalogue • Review of AIP restrictions • Route continuity check • Publication discipline Dis-Benefits • Interim complexity • Interim management • Route characteristics remain in AIP • Expansion of the SRS area

6. History of the RAD Requirements From States • Remove Route Flow restrictions from AIP • Determine publication method • Direct enquirers to EUROCONTROL website for RAD • Maintain Annex together with EUROCONTROL • Ensure timely updates (42 day AIRAC requirement) • Review restrictions regularly for currency • Facilitate cross-border compatibility of routing From EUROCONTROL • Maintain RAD • Ensure timely publication (42 days) • Ensure smooth transition meets target dates • Develop tools to validate RAD • Review allocation of Annexes (post summer 2001) and renumber in alphabetical order • Publish Part 2 of RAD - Winter 2001 (post transition) • Ensure external users participate in development

7. RAD Structure - 2001 RAD Part 1 • 3 (three) Appendices: • Appendix 1 - Introduction; • Appendix 2 - Area Definition; • Appendix 3 - City Pair Level Capping. • 32 (thirty two) Annexes: • Annex 1 - 30: States; • Annex 31: NAT; • Annex 32: Military Routes. RAD Part 2 • Includes Annex 1 - 30 structured on ATS route alphabetical order

8. RAD Restrictions Structure • 2 main types of restrictions, the inclusive and the exclusive. • In inclusive restriction, traffic must meet ALL of the conditions to be subject to the restriction. • In Exclusive restriction traffic only needs to meet ONE of the conditions to be subject to the restriction • Each RAD Annex comprises a list of ADVISORY routeings for Major Traffic Flows to assist with Flight Planning, until the process is fully automated.

9. RAD Structure Evolution 2001 - 2012 • RAD0312 - 27 NOV 2003 - Annexes renamed as National Annexes, Annex MIL and Annex NAT • RAD0401 - 20 JAN 2004 - New Appendix 4 DCT Limits • RAD0411 - 28 OCT 2004 - New Appendix 5 - SID/STAR • RAD1003 - 11 MAR 2010 - New Appendix 6 - Inter ACC • RAD1007 - 01 JUL 2010 - Annex MIL withdrawn and restrictions included in National Annexes • RAD1206 - 31 MAY 2012 - New Annex Special Event - created for the purpose of EURO2012.

10. Beyond mid 2012

11. ERNIP RAD • PART 1 - The European Airspace Design Methodology Guidelines - General Principles and Technical Specification for Airspace Design • Chapter 8 Route Network and Free Route Airspace utilisation rules and availability • PART 4 - Route Availability Document (RAD) User Manual The 4th meeting of the Network Management Board (NMB) on 7th June 2012 approved the full ERNIP (5 documents) and the actions required to enhance airspace utilisation.

12. RAD Official legal establishment • The RAD was created based on EC Regulations No 255/2010 of 25 March 2010 and No 677/2011 of 7 July 2011. • 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. • 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.

13. RAD Basic Principles • The objective of the RAD is to facilitate flight planning. • The RAD enables States/FABs/ANSPs to maximise capacity and reduce complexity. • The RAD should also assist the Network Manager in identifying and providing rerouting options • The content of the RAD shall be agreed between the Network Manager and the Operational Stakeholders through an appropriate Cooperative Decision Making (CDM) process. • The RAD is subject to continuous review by the Network Manager and the Operational Stakeholders to ensure that the requirements are still. • The RAD is updated each AIRAC cycle following a structured standard. • The RAD is only applicable to the IFR part of the Flight Plan. • The NM is responsible for preparing of a common RAD reference document, collating, coordinating, validating and publishing it.

14. RAD Restriction Eligibility • A restriction normally shall not qualify for inclusion in the RAD unless it has a FLOW ELEMENT and/or TIME AVAILABILITY / RESTRICTION APPLICABILITY attached to it. • A FLOW ELEMENT is defined as affecting either: • Departures from an Airfield / Group / Area; • Arrivals to an Airfield / Group / Area; • Traffic flying between Airfield / Group / Area; • Overflying traffic.

15. RAD Restriction Structure • Each restriction is hierarchical and specific and has been arranged to facilitate parsing of the information into computer systems. • 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: • Not available for … Flight planning via restricted object is forbidden for described flow(s). • Only available for … Flight planning via restricted object is allowed exclusively for described flow(s). • Compulsory for … Flight planning via restricted object is the only valid option for described flow(s). • For the combination of elements that define the flow of traffic, there are 2 (two) types of restrictions - inclusive and exclusive: • 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. • 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.

16. RAD Period of Validity • 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. • 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.

17. RAD Temporary Changes • 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 routings will be activated where possible following co-ordination with the relevant FMPs and AOs. • Temporary changes will be published by AIM giving details of the traffic affected, the period of activation and the corresponding routings.

18. RAD Tactical Operations • 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. • 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.

19. RAD Structure - 2018 • 7 (seven) Appendices: • Appendix 1 - General Description; • 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 (as from RAD1404 - 3 APR 2014). • Network wide Pan-European Annex • Annex for special events, if necessary (restrictions of temporary nature for European Sport Events, World Sport Events, Olympic Games, Large scale Military exercises, Economic forums, etc.

20. RAD Management

21. RAD Management - RMG • The RMG is a co-ordination forum for European RAD and confines its discussions to RAD related issues. The members of the RMG are experts in ATFCM and/or Airspace Design fromEUROCONTROL, the ECAC member States and their ANS providers, airspace users internationalorganisations, flight planner organisations and other relevant international organisations. • Despite that, the RAD was established since 2001 the first meeting of the RMG (RMG/1) was held in EUROCONTROL on 22 MAY 2005. • Until then thirty two meeting was convened and the last RMG/32 was held on 13 NOV 2018.

22. RAD The NM RAD Team • Until mid-2012, EUROCONTROL Operations performed the RAD process and dedicated team was not established officially. • The need to establish improved links between the processes of Airspace Design and Airspace Utilisation in coordination with the Operational Stakeholders is one of the top priorities for the Network Manager.  • As from 7 JUN 2012 in order to fulfil this requirement, a multidisciplinary NM RAD Team had been established in support of Operational Stakeholders dealing with all aspects of the RAD from policy to implementation and review. • The NM RAD Team, in close coordination with all the Operational Stakeholders, is responsible for preparing of a common RAD, collating, coordinating, validating and publishing it. • The NM RAD Team is responsible for preparing of a common RAD, collating, coordinating, validating and publication through liaison with the National RAD Coordinators (NRCs) on an AIRAC cycle basis. The final content of any amendment to the RAD is positively agreed between the NM RAD Team and relevant NRC.  • Additionally to all other responsibilities the NM RAD Team is entitled to refuse and/or remove any RAD requirement, if not properly co-ordinated until the coordination process is completed.

23. RAD Publication Coordination • The NM RAD Team creates RAD in accordance with ICAO publication procedures and publish it 28 days prior to the relevant AIRAC cycle. • “Last minute” changes are changes required due to exceptional circumstances and/or only when they have a significant impact on operational requirements. They are promulgated on the NM NOP portal via the “Increment File”. • The RAD including the “Increment File” are published via EUROCONTROL NM NOP website as xls files and via B2B.

24. Recommendation The participants at the RAD Evolution Workshop are invited to: • Consider the content of this paper; • Note the purpose of the establishment of the RAD, its history and RAD evolutions to-date.