Free Route Airspace ASM Dimension. Giuseppe Acampora

Transcription

1 Free Route Airspace ASM Dimension Giuseppe Acampora Head of DNM/NOM/OPL/PRO section 29/06/2015

2 GOALS Highlight those activities related to ASM in FRA Provide information on the latest ASM developments supporting FRA operations Highlight some issues to be addressed for further developments

3 WHY ASM? Average AIRAC cycle IFPS flights per AIRAC cycle on average interested flights on CDR1s 7426 effectively planning at least one CDR1 segment 2254 interested flights on CDR2s 1413 effectively planning at least one CDR2 segment Figure 1 ECAC map of published CDR, CDR2,CDR1/2, CDR1/3 and CDR2/3 for the last AIRAC (1413) of the year 2014 enter your presentation title 3

4 ASM and AFUA Primary Objectives Improve Network performance through better utilisation of existing ASM processes; Enhance performance driven ASM/ATFCM processes (including those ATS processes that are linked to the ASM/ATFCM processes); Introduce more dynamic and flexible ASM/ATFCM/ATS processes; Provide for safe, efficient and accurate information/data flows.

5 ASM and AFUA Phases The first phase ( up to 2015) is focused on the consolidation of recent improvements and the finalisation of objectives under discussion. The second phase (up to 2017) will be focus on the introduction of improvements aiming to support an effective airspace management in a free route environment, including the initial management of real time airspace data and dynamic airspace configuration. The third phase (up to 2020) will be dedicated to the exploitation of a full rolling ASM/ATFCM/ATC process (no more snapshots), supported by an automatic share of information among the different stakeholders (B2B), for the management of suitable dynamic airspace configuration offering the best ATM performance to satisfy airspace users requests.

6 ASM ASM Management and Advance FUA NSP Work Plan Work Area 0 Project management Work Area 1 ASM Solutions Work Area 2 Airspace Configuration & CDM Work Area 3 Rolling ASM/ATFCM process and ATC response Work Area 4 ASM in FRA Environment Work Areas 5 : ASM System Support and Data Management Work Areas 6: ASM POST OPS & Performance Monitoring Work Areas 7: Support to other ASM related activities (e.g. SESAR, SES, support to states, etc.)

7 ASM activities vs FRA ASM notification process in FRA WA Description Target time WA4 Initial implementation EAW in FRA 2015 WA4 Improve notification in FRA 2015 WA4 Full implementation of EAW in FRA 2016 WA4 Improve notification in FRA 2016 WA5 System changes for EAW in FRA 2016 WA5 System changes for notification in FRA 2015/2016

8 ASM activities vs FRA Initial CDM for Network Impact Assessment in FRA WA Description Target time WA4 Review procedures to support network impact assessment in FRA 2016 WA4 Perform Validation activities 2016 WA4 Amend ASM Handbook 2016 WA5 WA5 Define operational requirements for NM system supporting initial network impact assessment in FRA Implement NM systems improvements initial network impact assessment in selected FRA environment NM 22.0

9 ASM activities vs FRA Full CDM for Network Impact Assessment in FRA WA Description Target time WA4 Fine tuning procedures to support network impact assessment in FRA 2018 WA4 Perform Validation activities 2018 WA4 Amend ASM Handbook 2019 WA5 WA5 Define operational requirements for NM system supporting full CDM for network impact assessment in FRA Implement NM systems improvements full CDM for network impact assessment at ECAC level NM 24.0

10 First set of improvements Revision of ASM Handbook (2013) Alignment to ERNIP Part 1; Stress the management of airspace volume in alternative to CDR through the AUP/UUP process; Revision of FUA Indicators; Introduction of a new Indicator: RoAA= rate of Areas Availability; Similar to RoCA; Not yet measured due to the lack of areas information by some States. 10

11 Second set of improvements new AUP Template - Background AOs strongly require a single source of information to process all airspace status information; AOs support the usage of AUP because processed automatically via B2B; Additional information needs to be process via AUP in order to support operations in FRA environment; Additional information requested by AOs. 11

12 AUP - Agreed changes BRAVO field List of DCT closed DELTA field List of NAM ECHO field List of special event/ ad hoc area FOXTROT field List of SIDs/STARs Fifth column FUA/EU restriction CHARLIE/DELTA fields FBZ areas NM Release

13 FUA Restriction NM Release 19.0 FUA Restriction Route Network Route Network + DCTs DCTs FRA 13

14 FUA RESTRICTIONS FUA restrictions are Hard Traffic Flow restrictions implemented in CACD (same as RAD restrictions). FPL s violating a FUA restriction will become invalid and the IFPO or FPL originator must correct the error. FUA restriction are used for daily allocation of areas FUA restrictions are only implemented in CACD after a request/ coordination with involved State(s)/ANSP(s). More FUA restrictions can be defined for each area

15 Publication FUA RESTRICTIONS & exemptions RAD document

16 Appendix 7 Fictitious example Change record RSA Restriction ID Number Operational Goal Affected ATS route/s / DCT/s L_R24 Not available for traffic during the times and within the vertical limits allocated at EAUP/EUUP L_R24R Traffic is not allowed to flight plan across active military area. AAA L1 BBBBB CCCCC M1 DDDDD DCT EEE - FFFFF E_TRA51 During the times and within the vertical limits allocated at EAUP/EUUP Only available for traffic 1. DEP/ARR E _ 2. Military GAT 3. Via AAAAA N3 BBBBB 4. Via CCCCC N3 DDDDD E_TRA51R Traffic is not allowed to flight plan across active military area except specified flows. AAA L1 BBBBB CCCCC M1 DDDDD GGGGG N1 HHHHH DCT RRRRR - TTTTT DCT NNNNN - LLLLL

17 FUA RESTRICTIONS Manual Intervention for CDR/ATS routes management (CIAM) FUA restriction Strategic exemptions Non - activated Activated Manual selection of CDR/ATS routes to be open/closed Expansion function Wrong selection of CDR/ATS routes to be open NO effect ONLY AREAS Information

18 FUA RESTRICTIONS Notification to Airspace Users FUA restriction Without expansion function With expansion function NO CDR/ATS routes Closed or Open in EAUP Manual selection of CDR/ATS routes to be opened or closed, including nearby Wrong selection of CDR/ATS routes visible in EAUP but no effect on FPL (REJ or FLS)

19 NEW NEW 19

20 NEW NEW 20

21 FBZ - Definition The FPL Buffer Zone (FBZ) is the associated airspace which may be applied to a reserved/restricted area. The FBZ defines the lateral and vertical limits for the purpose of submitting a valid IFR FPL when such areas are active or planned to be active.

22 Today s situation IFPS Procedures E Exit Point D F Design + Local procedures C Way Point B Entry Point A H

23 New procedure FBZ Application E Exit Point Local Procedures for Tactical Coordination D F C FBZ Way Point B Entry Point A H

24 Full FBZ

25 FBZ State decision; Published in AIP; Notified via EAUP/EUUP;

26 FBZ PUBLICATION FBZ area is published in a similar format as any other area (ASM Handbook, ) Identification, Name and Lateral Limits AABBCC N E N E N E N E N E N E. AABBCCZ N E N E N E N E N E N E. Upper Limit Lower Limit 6500 FT MSL GND 7500 FT MSL GND Remarks

27 RSA L2 Publication in CIAM Not Using CIAM Allocated in CIAM Not allocated in CIAM Not published in AIP

28 Areas AUP Publication vs NOTAM ASM Handbook doesn t contain any requirement for publication of NOTAM in case of AMA activation For NAM activation existing in CACD; NAM information is reported according to AIP information; Change or activation of NAM areas notified via NOTAM are also published in AUP/UUP The ASM Handbook guidelines doesn t exclude the possibility for States to publish NOTAM as well in case of AMA activation via AUP; These NOTAMs plus any other NOTAM, unless specifically asked by States and or impacting traffic (FUA/EU restriction), are not processed by CADF staff; If NOTAM published and information notified via AUP/UUP needs of consistency (Buffer Time). Solution to overcome proliferation of NOTAM and answering AOs requirements of national source: Report in AIP or AIP supplement/notam for temporary manageable areas that activation will be notified via AUP/UUP 28

29 29

30

31 FRA ASM Operations Tactical Management - Improvements Quite Flexible but risks of increasing predictability Promote FPL process Extensive use of AUP/UUP; Therefore validity time for any UUP change. promote management of volume closure (force airspace users to refile). Improve accuracy airspace booking; Enhance usage procedure 3. Promote coordination of tactical management at FAB level Ensure maximum extension at FAB and not State level Coordination of areas allocation to minimise impact on traffic flows To ensure synchronisation Achieve a better re-routing from entry to exit points at FAB level ATCOs procedures

32 FRA ASM Operations PCA Prior Coordination Airspace (PCA) is a portion of airspace of defined dimensions within which individual GAT is permitted to fly "off-route" only after prior coordination initiated by controllers of GAT flights with controllers of OAT flights. enter your presentation title 32

33 FRA ASM Operations RCA Reduced Coordination Airspace (RCA) is a portion of airspace of defined dimensions within which GAT is permitted to fly "off-route" without requiring controllers of GAT flights to initiate coordination with controllers of OAT flights. enter your presentation title 33

34 FRA ASM Operations Tactical Management for OAT crossing controlled airspace (ATS route, CDR, CTA) ASM Handbook, Section 5 When bilaterally agreed, the controller responsible for GAT should be provided with the plan of action of the controller responsible for OAT intending to cross a specific portion of controlled airspace under his/her responsibility. Accordingly, a notification of intention is sent by controller responsible for OAT to the controller responsible for GAT. The display to the GAT controller of all relevant OAT flight data allows the controller to be aware of the foreseen crossing conditions and to initiate coordination, if required. Division of the responsibility or the provision of separation between OAT and GAT is subject to detailed description in relevant LoAs. When the crossing requires prior coordination, the OAT controller sends, by means of a silent coordination message, a request for the crossing of controlled airspace (ATS route, CDR, and CTA). This request is responded to by the GAT controller by means of a silent coordination message. The answer contains either an acceptance of crossing parameters or, if not acceptable, an alternative proposal, including revised crossing data (heading, FL, etc.). Verbal coordination is used if the alternative proposal is not acceptable.

35 Airspace Crossing Dialogue Function OLDI Specification The Airspace Crossing Request Message (XRQ) Airspace Crossing Acceptance Message (ACP) Airspace Crossing Counter-Proposal Message (XAP) Airspace Crossing Reject Message (RJC) enter your presentation title 35

36 Airspace Crossing Request Content OLDI-XRQ-10-M The XRQ message shall contain the following items of data: Message Type; Message Number; Message Reference (if modifying an earlier agreed crossing); Aircraft Identification; SSR Mode and Code; Number and Type of Aircraft; Route; Sector Identifier. Note: The Sector Identifier item contains the identifier of the sector responsible for the flight. OLDI-XRQ-30-M The Route element shall contain a description of the crossing route including at least two points. 36

37 Airspace Crossing Request XRQ Example -TITLE XRQ -REFDATA -SENDER -FAC EBSZZXZQ -RECVR -FAC EBBUZXZQ -SEQNUM 012 -ARCID DEUCE22 -SSRCODE A1240 -ARCTYP F111 -NBARC 3 -SECTOR SOUTH -BEGIN RTEPTS -PT -PTID GEO01 -TO FL F250 -PT -PTID GEO02 -TO FL F250 END RTEPTS -GEO -GEOID GEO01 -LATTD N -LONGTD E -GEO -GEOID GEO02 -LATTD N -LONGTD E -ADEP EBBE -ADES EGUN 37

38