Operational Instruction

Size: px

Start display at page:

Download "Operational Instruction"

Maude Robertson
5 years ago
Views:

1 From 1 Introduction In certain situations we may need to prevent flights from entering an airspace ATFCM solutions are used to control access to this airspace Affected flight operators need to take action to indicate to the NMOC their intention to operate or not Currently, NMOC usually suspend such flights (flights receive a FLS) and the aircraft operators have to confirm (send a FCM) to operate The objectives of this ATFCM process were to: 1 Inform aircraft operators of the closure 2 Give aircraft operators the possibility to confirm/cancel the flight Improve predictability and free capacity The current process does not fully satisfy the initial objectives The limitations of the current process are: 1 No delay information is included in the suspension message 2 Flights lose the initial slot at suspension time The new sequence is based on the confirmation time stamp instead of initial ETO The current process leads to a high percentage of flights being initially confirmed that are finally cancelled/not operated This deteriorates predictability and wastes capacity 2 Objectives The objective of the new Delay Threshold Mechanism is to give to the aircraft operators delay information and time to react before being fully suspended An additional benefit is that the flights do not lose the initial sequence based on the ETO, as the slot is kept booked for a period of 20 minutes A new delay threshold value can be set as a parameter in the regulation editor The Delay Threshold Mechanism reflects which delay is considered significant to evaluate different alternatives This threshold value will be set in the regulation editor Progressive Application of the Procedure The Delay Threshold Mechanism is in operations since the 27 th October 2015 The Phase application of Delay Threshold Mechanism is NOT applicable until further notice The Delay Threshold Mechanism is in operations in trial mode since 27 th October when applying Rerouting and Level Capping Scenarios (See section 5 Summary of Regulation ) Any scenario transmitted by NMC in the Daily Plan of the 26 th October (on D-1) from PREDICT was transferred with the Delay Confirmation The Delay Threshold Regulations in pretactical Phase have to be managed as described on the specific note for pretactical in section 5 Summary of Regulation ) After a satisfactory trial period of one month, the Delay Threshold Mechanism will be used for other operational situations such as Unavailability (See section 5 Summary of Regulation ) Page 1 of 6

2 From 1 Phase 1 (applicable until the end of the trial) See Phase 1 Cases Scenarios Whenever a Delay Threshold Mechanism is applied an AIM shall be sent to inform the aircraft operators and the ARO offices (see AIM in section 7 AIM text to be used for regulations with Delay Threshold Mechanism) 2 Phase 2 (** UNTIL FURTHER NOTICE**) See Phase 2 Cases Non-Availability (Weather, accident, etc rate 0) Phase (** UNTIL FURTHER NOTICE**) See Phase Cases High delay situations (Industrial Actions, Capacity Shortfall, etc regardless of the rate) Use cases Rate Delay threshold / Value (Set by NM) XCD RVR FCM mandatory Shift Phase Zero rate Scenario No No No No 1 Unavailability (no matter the duration) (Delay Threshold NOT to be used for unavailability) 2 High delay RVR (Delay Threshold NOT to be used for High Delay Zero rate for strike nor RVR nor Zero Rate for Strike) * Even exempted flights shall be captured ** Phase 2: Use Delay Threshold for any availability period The suspensions will be managed with the threshold value 4 New Delay Threshold Mechanism Procedure for FM and NMC staff It is recommended to use the Delay Threshold functionality whenever the delay is such that aircraft operators should consider alternative options for the flights: canceling FPL or route changes (update EOBT, rerouting, etc) Whenever a Delay Threshold Mechanism is applied, the value shall be introduced in the Delay Confirmation Threshold field in the regulation editor The Delay Threshold value will be automatically added by the ETFMS in the Anm Tfv description field as follows: DELAY THRESHOLD (X) MIN In the event of unexpected behavior of the Delay Threshold Mechanism, the regulation type shall be changed back to an existing regulation type (eg FCM) Whenever a Delay Threshold Mechanism is applied for a regulation, an AIM shall be published (see section 7 AIM text to be used for regulations with Delay Threshold Mechanism) 41 System Behavior Flights affected by regulations with a delay threshold value selected will be treated as follows: a) Before SIT1 a If the delay is lower than the threshold value, the provisional delay for the flight will be indicated in the flight lists and slot lists in the Delay column Page 2 of 6

3 From b If the delay is higher than the threshold value, the provisional delay for the flight will be indicated in the flight lists and slot lists in the Delay column A D in the Most Penalizing regulation will indicate that the flight has a delay above the threshold and can be potentially suspended at SIT1 Alternatively, a d is shown if there is another regulation acting as the most penalizing Close follow up of those flights can be done using CHMI/NOP by aircraft users Flight lists show the expected delays and the corresponding D b) At SIT1 (EOBT - 2 hours) or later a If the delay of the flight is higher than the delay confirmation threshold time specified in the editor, a slot for that flight will be booked An FLS will be sent containing a Proposal Take-Off Time (PTOT) and a time for response by (20 minutes) The aircraft operator shows their acceptance of the PTOT by sending a Flight Confirmation Message (FCM) message within the time for response by time Upon the reception of a FCM a SAM/SRM is sent and the PTOT becomes the CTOT If the aircraft operator fails to respond within the response by time, the booking is lost and the flight remains suspended During the Response by period, the flight is suspended but will continue to be visible in flight lists and Load Display as proposal flight (orange colour) Note that proposal button is located in the top left corner of the menu bar in ETFMS When choosing PROPOSAL, the counts, loads, flight lists, etc take into consideration all proposals sent (SIP, RRP, and FLS) like if they were positively replied b If the delay is lower than the threshold, the flight will get a SAM/SRM When the new Delay Threshold Mechanism is selected, it applies to the whole regulation period irrespective of any defined sub-periods 42 Interactions with FCM and RVR The Delay Threshold Mechanism, given its advantages over the FCM (better info to the operators, sequence kept ), shall be used instead of FCM and not in combination with FCM The Delay Threshold Mechanism is not expected to create any problem when it is used in combination with any other functionality likely to trigger a FLS (RVR) The order of priority is the following: FCM has priority over RVR The FCM mechanism suspends all flights regardless of RVR conditions RVR suspension has priority over the Delay Threshold Mechanism The RVR mechanism and cannot be overwritten by the Delay Threshold Mechanism 5 Summary of Regulation settings The operational situations where application of the new mechanism applies are presented below: Page of 6

4 From Use cases Rate Delay threshold / Value (Set by NM) XCD RVR FCM mandatory Shift Phase Zero rate Scenario No No No No 1 Unavailability (no matter the duration) (Delay Threshold NOT to be used for unavailability) 2 High delay RVR (Delay Threshold NOT to be used for High Delay Zero rate for strike nor RVR nor Zero Rate for Strike) * Even exempted flights shall be captured ** Phase 2: Use Delay Threshold for any availability period The suspensions will be managed with the threshold value Note 1: The use of the Delay Confirmation Threshold does not interfere with the XCD/ RVR option Note 2: The Delay Confirmation Threshold value should reflect which delay is considered significant enough to ask aircraft operators for confirmation Refer to the values of the table above for each case Note : Delay Confirmation Threshold option replaces XCD/FCM option Note 4 (pretact): Delay Threshold Regulations in PREDICT have to be managed as follows: 1 Select Delay Threshold and type the corresponding value 2 Select XCD/FCM Before transferring the Daily Plan to ETFMS unselect XCD/FCM/Shift options in case of Zero Rate scenario Use the Group To do so, use the group edit XCD attributes of regulations in the Scenario Display Before transferring the Daily Plan to ETFMS unselect FCM option in case of Unavailability XCD/Shift options shall remain To do so, use the group edit XCD attributes of regulations in the Scenario Display Page 4 of 6

5 From 6 New Messages Classification: Flight Messages (Outgoing) Kind : FLS Subject : Aircraft AFR8788 Period : 11-06:10 to 11-06:11 Matching entries : 1 Last Updated: 11-08:21 DD-HH:MM Subject Correspondent :10 AFR Message : Sent to: Message description:-title FLS -ARCID AFR8788 -IFPLID AA ADEP LFPO -ADES GMMN -EOBD EOBT PTOT 1000 (NEW) -RESPBY 060 -REGUL DTS9811 COMMENT SUSPENDED DUE TO DELAY EXCEEDING THRESHOLD VALUE SEND FCM BEFORE RESPBY TO SECURE PTOT ALTERNATIVELY, REROUTE, OR UPDAT EOBT WITH A DLA MSG, OR CNL -TAXITIME REGCAUSE CE 81 7 AIM text to be used for regulations with Delay Threshold Mechanism TACT/CASA MESSAGE : SCENARIO HAVE BEEN APPLIED WITH DELAY THRESHOLD VALUE SCENARIO:FL1BR2(REGID:FL1BR2) DEPARTURES:ALL DESTINATIONS:LFPO NOT ALLOWED VIA SECTOR (OR ABOVE): LFBB R2 FILE BELOW FL295 BY : LULUT OR FISTO REF NON-AVAILABILITY OF DUE TO: REG ID: DELAY THRESHOLD VALUE: Page 5 of 6

6 From VALID : WEF: UNTIL: UTC REMARKS : PROVISIONAL DELAY CAN BE MONITORED BEFORE EOBT -2 VIA NOP/CHMI FLIGHTS WITH DELAY HIGHER THAN THRESHOLD VALUE WILL BE SUSPENDED AT EOBT-2 AND THE SLOT WILL BE BOOKED FOR 20 MIN SUSPENDED FLIGHTS INTENDING TO OPERATE MUST SEND FCM BEFORE RESPBY TO SECURE PTOT ALTERNATIVELY, REROUTE, OR UPDATE EOBT WITH A DLA MSG FLIGHTS DIVERTING AND NOT YET DEPARTED MUST CNL THE FPL AND RE-FILE TO ALTERNATE AERODROME FLIGHTS NOT INTENDING TO OPERATE MUST CNL THEIR FPL BY SENDING A CNL MESSAGE NMOC - BRUSSELS Note: AIM to be published only on tactical operations For pre-tactical scenarios, the delay threshold information will be indicated in the Network News at D-1, but not a separate AIM 8 Feedback Feedback on the procedure shall be reported to the Post-Operations Manager 9 Appendix ATFCM operations manual updates The relevant sections of the ATFCM Manual will be updated accordingly after the trial period Operations Manager Page 6 of 6

EUROCONTROL Advanced ATC TWR Implementation Guide

EUROCONTROL Advanced ATC TWR Implementation Guide Advanced ATC TWR Implementation Guide Edition No. : 1.400 Edition Issue Date : 01 Aug 2017 Authors : Hans Koolen Reference : Copy No. : stamp here Document Control Copyright Notice 2017 European Organisation