70 likes | 82 Views
Addressing limitations in NMOC system handling RAD issues, proposing solutions for vertical dependent applicability, connecting point restrictions, new point groups, point usage, and RAD analyses tool. Seeking feedback for refining NMOC and RAD structure.
E N D
RAD Evolution WorkshopCurrent RAD status - DP/2 NMOC and RAD Issues Proposals On behalf of NATS UK - Tihomir Todorov Head of Section Airspace Design 12 DEC 2018 RAD WS 12 - 13 DEC 2018, Brussels, Belgium
RAD Issues “Vertical” Dependent Applicability • Proposal:The NMOC systems to cope with Level Sensitive Dependent Applicability where the referencing are multiple danger areas which are activated to different interim levels in a single RAD restriction e.g. EG2533 • The above RAD will capture traffic correctly if EGD323B/C/D/E/F/G are all activated to the same level e.g. all active to FL315. However if the danger area segments are activated to different levels e.g. EGD323 B/C/D activated to FL285 and EGD323 E/F/G activated to FL335, then the system cannot currently handle this, resulting in miss-capture. • In order to accommodate FUA and FRA adequately, UK requires the NMOC systems to be updated to handle level sensitive dependent applicability based on multiple level activations.
RAD Issues Restrictions on intermediate SID/STAR connecting point • Proposal: Ability to restrict intermediate connecting points on SIDs/STARs to certain flights only e.g. in Appendix 5 General Conditions it is stated: EGNX: When using a EGNX STAR the use of the STAR initial waypoint is mandatory except for: Traffic via AVANT DCT VELAG, which may join the PIGOT1J STAR at VELAG • VELAG is part of the STAR definition and is added as an additional connecting point on the PIGOT1J STAR in CACD, however there is currently no way of encoding this connecting point to be only available for the traffic routeing AVANT DCT VELAG. So it is currently available to all and consequently creates the potential for other FPLs to be erroneously filed.
RAD Issues Group of Points • Proposal: “Group of points” concept, similar to the way in which group of airfields is done in Appendix 2 e.g. EG2247 • In the above RAD restriction, the reference to the nine waypoints in point 1 might be simplified if they could all be classified into a single group e.g. the GOMUP_GROUP (ADODO, AMLAD, BALIX, ERAKA, ETILO, GOMUP, IBROD, MIMKU, ORTAV).
RAD Issues Point Usage (non-FRA) • Proposal: Ability to automatically encode points dependent upon their usage. • For example if a waypoint exists only within a SID and State does not want it to be used for anything other than departures on that SID, currently it is required to create RAD to prohibit this. Otherwise, the waypoint could be filed within an en-route DCT portion.
RAD Issues RAD Analyses Tool • Proposal: Analysis of RAD restrictions - to have a means of gauging the ‘hit rate’ of various RAD restrictions to assess whether they are still required (it may be this is already possible).
Recommendation The participants at the RAD Evolution Workshop are invited to: • Consider the content of this paper; • Express the vision on all presented issues in order to define the appropriate way forward on possible improvements in NMOC system and RAD restriction structure.