FRA AIP publication and EAD data provision Asa STANDAR AIM Operations Expert ATM/RDS/IM 29 June 2015
Slide 2 Content Current guidelines for FRA publication Identified issues/ideas for further harmonisation on AIP publication Charting Data management in EAD Way Ahead
European guidelines for publication of Free Route Airspace EUROCONTROL guidelines for AIP publication in support of FRA concept exist in ERNIP since 2012 Developed in coordination with the RNDSG and the AI Operations Subgroup 6.5.2 FRA AIP Publication 6.5.3 FRA Charts Publication ENR 6 Guidelines include: AIP placeholders (sections/sub-sections) for FRA related information Instructions to support the publication Some options for publication, depending on implementation/ states choice European solutions (extensions) compared to ICAO provisions, to encompass the FRA specific information ENR charts, AD charts and FRA chart symbols 3
ERNIP guidance on AIP placeholders for FRA information GEN 2.2 Terminology/Abbreviations ENR 1.3 Instrument flight rules General FRA procedures 1.10 Flight planning 2.1 FIR, UIR, TMA and CTA 2.2 Other Regulated Airspace, incl. ATS delegation and cross-border application 4.4 FRA related significant points 5.1/5.2 Airspace reservations for FRA 6 FRA charts AD 2.24 Related terminal charts 4
Slide 5 Identified issues/ideas for further harmonisation on publication States started to publish FRA and also in cross-border/fab context Issues addressed within the Agency s Working Arrangements and stakeholders AIM working groups. Top 4 of issues identified by the AI Operations Sub-group 1) Enhancements to current publication guidance 2) Duplication of published information in involved states AIP What information is necessary to be published in all States AIP? Who will be the originator of common information? 3) EAD data management Data harmonisation objectives/operational rules Coordination requirements between several data providers 4) FRA conceptual proposals
Slide 6 Considerations on enhancements to current publication guidance - AIP Flight planning information General information in ENR 1.3 Detailed flight planning information in ENR 1.10 (instead of in ENR 1.3) Route Availability Document a candidate for relevant flight planning information (and not duplication in AIP) Description of FRA cross-border area in ENR 2.1 and 2.2 Include fictitious examples to accompany the guidance Expanded guidance on (required and not required) publication in adjacent states AIPs FRA relevance for significant points in ENR 4.4 table
Slide 7 Considerations on enhancements to current publication guidance - Charts ENR 6 charts Only the common FRA-border to be published, covering all involved States No other information included, such as transition routes or FRA significant points. This kind of detail only on individual States ENR charts Refer to other involved States AIP for details Could the common cross-border FRA boundary chart be an EUROCONTROL service/product? Ideas for complementing charts for flight planning (e.g. description of transition routes): ENR 1.10, to complement flight planning rules ENR 6, to complement en-route phase planning AD 2.22, as illustrations to flight procedures
Slide 8 Considerations linked to duplication of published information in involved States AIP Multiple publication of cross-border FRA information in each individual State s AIP in general not favoured Following comments raised: Duplication (x state) of publication effort for States Risk of non-coherence within AIPs EAD data management and coordination requirements between several data providers Currently optional in ERNIP
FRA evolution to be reflected in EAD EUROCONTROL FRA concept formalised in ERNIP (2012) Including the publication guidelines FRA implementation started on a baseline of one State FRA implementation is being extended to regional levels (FAB, multiple FAB s, Multi FIR s) Operated in one airspace volume (e.g. 2 FIRs in 1 FAB) Data maintenance under responsibility of several Data Providers Operational Hours Timesheets H-24, Night Only, WE/Holidays CBA issues (e.g. different vertical limits) Identification of FRA points and usage combinations REVIEW of data harmonisation rules launched with the AI Operations Sub-group 9
EAD data management EAD SDO Data Harmonization Objectives (DHO) Applied to ensure harmonized approach and rules for encoding Improve database consistency and overall quality Enhance interoperability To overcome technical constraints in current data model, to cover new concepts DHO-7 Free Route Airspace Developed in 2009 (before ERNIP) to support States in uploading data in SDO Based on AIXM 4.5 data model Published as part of the EAD Operational User Handbook Data Provider 10
DHO-7 objectives to meet user needs What is the purpose of DHO-7 in EAD SDO? I. EAD Data Users can Identify the FRA Airspace Volume: Lateral and Vertical (AIP ENR 2.1 and 2.2.) Identify the FRA Airspace Volume availability (working hours) II. EAD Data Users can Identify the FRA Points and their usage (in accordance with AIP ENR 4.4 publication) III. I and II are required to link in AIXM the FRA Airspace Volume with FRA Relevance 11
FRA encoding in EAD Static Operations (SDO) Current situation - FRA data is uploaded in SDO: Per FIR However AIRSPACE CODE_TYPE= RAS (Regulated Airspace) AIRSPACE CODE_ID e.g. LBSFRA Not all Data Providers adhere fully to DHO-7 The linkage for the FRA points between the Airspace and the related Significant Point in airspaces is not made Consequences of current situation Data Users have difficulty to identify the FRA Points (Usage) and the related FRA Airspace Relational data base quality is affected Operational usage impacted 12
DHO-7 review challenges Overcome/ mitigate technical constraints, though still provide FRA data to the EAD data users Develop further operational rules for encoding in AIXM thus enhance the FRA relational database consistency and quality between: FRA Airspace volume and FRA Point Usage (Relevance) Enhance operational usability in SDO 13
Current state of DHO-7 update AI Operations SG-12 (17-18 June 2015) Agreed on proposed updated DHO operational rules on Entity/Attribute level (AIXM 4.5): Airspace Type - [RAS] Coded Identifiers to cover different FRA scenarios, such as; When FRA stays within one FIR when FRA goes beyond the national FIR Other scenarios Link the FRA points (as published in ENR4.4) through AIXM Significant-Point-in-Airspace [SPA] attribute 14
EAD next steps Network Manager FRA Workshop 29-30 June 2015 EAD Data Harmonisation Objectives approval process Consecutive approval by the EAD Service Steering Group will be sought DHO operational implementation and adherence monitoring EAD in the transition phase from AIXM 4.5 to AIXM 5.1 AIXM 5.1 offers a more flexible approach to encode FRA airspace type supported by a harmonised list of values Requires to develop consistent Data Mapping from 4.5 to 5.1 and alignment with EAD release planning 15
Slide 16 Way ahead The AI Operations Sub-group continues to: Collecting States further requirements on FRA AIP publication and charting based on current ERNIP guidance including ENR 4.4 table layout Proposing enhancements to harmonised FRA AIP publication & data harmonisation and relevant FRA conceptual aspects Enhancement proposals channelled to the RNDSG for processing towards ERNIP inclusion/updates