RAD Evolution Workshop Network approach to the RAD

RAD Evolution Workshop Network approach to the RAD - DP/3 The Vision RAD WS 12 - 13 DEC 2018, Brussels, Belgium Boris Radovanovic NM/NSD/PCI 12 DEC 2018

General issues Photo © Lewis Clarke (cc-by-sa/2. 0) Document Confidentiality Classification: Green

Need for the Network RAD restrictions The first principle envisaged by the EC Regulation No 677/2011 of 7 July 2011: The establishment and configuration of airspace structures shall be based on: § operational requirements, § irrespective of national or functional airspace block borders or FIR boundaries, § that shall not necessarily be bound by the division level between upper and lower airspace. Document Confidentiality Classification: Green

RAD restrictions creation, structure and introduction § Operational goal? § How many flights? Seasonal? Daily? § Clear definition § One interpretation Adequate utilisation § Compulsory for? Impact on Flight planning flexibility / predictability Document Confidentiality Classification: Green OLD RAD restrictions

Last Minutes Changes § § § not only the simple “technical” modification not always related to the proven safety issue non-compliance with cut-off dates late provision of any RAD change inappropriate internal State coordination mistakes in CACD § to allow Operational Stakeholders time to react Document Confidentiality Classification: Green Exceptional circumstances? Significant impact on operations / safety?

RAD restrictions amount § RAD restrictions introduced to suppress certain flight planning outputs (in the RAD usually defined as creative or funny flight plans). § To support the “Shortest Option” § Instead of defining, revising and adapting RAD restrictions contributing to the generation of not desirable profiles, new RAD restrictions are introduced. § The number of RAD restrictions makes their effective evaluation and RAD restriction database maintenance very difficult. § Some of the restrictions that are currently existing are obsolete and are not used (considered) by flight planning systems. § E. g. LF 3286 - > how many flights? Document Confidentiality Classification: Green

RAD versus ATC M 1 - FPL Data M 3 - Actual SAAM - RAD ON SAAM - RAD OFF Document Confidentiality Classification: Green

Why Network RAD? § RAD restrictions should never be considered as alone-standing entities. § They are often influenced by other RAD restrictions that can even completely suppress (annul) or double the effect of another one. § Difficult to recognize this correlation. § When considering RAD restriction utilization examples, a recent case where need for defining operational requirements irrespective of national or functional airspace block borders or FIR boundaries was expressed within NM/4 ACC + 11 initiative. Document Confidentiality Classification: Green

Network RAD restriction § Set of measures defined in cooperation with NM to adequately reflect combined States / FABs / ANSPs Operational Goals with controlled distribution of traffic flows in a way that will have the smallest impact on the AOs flight planning and operations. § Network RAD restriction shall be created by the NM on States / FABs / ANSPs request and combined Operational Goals in cooperation with other States / FABs / ANSPs concerned. § The Operational Goals provided by the States / FABs / ANSPs shall clearly explain the problem to be resolved while the request for network RAD restriction shall not propose the solution how to resolve that problem. § Network RAD restriction might be followed by adaptation of existing airspace structures. Document Confidentiality Classification: Green

Network RAD restriction Network (RAD restrictions) Operational goal State (RAD restrictions) Document Confidentiality Classification: Green

Recommendation The participants at the RAD Evolution Workshop are invited to: § Consider the content of this paper; § Support the idea for the need for the Network RAD restrictions. Document Confidentiality Classification: Green