secure.metronaviation.com · web viewmulti-nodal atfm network common operating procedures (cop)2nd...

Distributed Multi-Nodal ATFM Network Common Operating Procedures

Multi-nodal atfm NeTWORK common operating procedures

(COP)

2nd Edition, 14th OCT 2016

This document provides an essential framework, details of procedures, rules and requirements applicable for Air Traffic Flow Management for Operational Trial.

Table of Content

Document Change Record..............................................................................................................................1

Document Administration..............................................................................................................................1

Reference Material.........................................................................................................................................3

1 Introduction............................................................................................................................................2

2 Distributed Multi-Nodal ATFM Network Concept Overview...................................................................4

3 Operational Trial: A Phased Approach with Tiered Participation............................................................5

4 Multi-Nodal Common Operating Procedures.........................................................................................7

General.......................................................................................................................................................7

Stakeholders’ Responsibilities....................................................................................................................7

Information on ATFM Measures...............................................................................................................10

Processes and Procedures for ATFM Measures........................................................................................10

Flight Plan and ATS Messages...................................................................................................................14

Exemption of Flights.................................................................................................................................14

Compliance management.........................................................................................................................14

Performance assessment..........................................................................................................................15

Failure of the ATFM system......................................................................................................................15

Safety Management System for ATFM Implementation and Operations.................................................15

CTOT Information Delivery.......................................................................................................................15

Post Operation Analysis............................................................................................................................16

Annex B.........................................................................................................................................................21

Annex C-1.....................................................................................................................................................22

Annex D-1.....................................................................................................................................................27

Annex E-1......................................................................................................................................................38


Document Change Record

The following table records the complete history of the successive editions of the present document.

Version Number Effective Date Reason for Change Pages Affected

1.0 12 July 2016 Original release version

All

2.0 14 Oct 2016 Amendments arising from MN11

All

Document Administration

This document has been co-authored by members of the Distributed Multi-Nodal Air Traffic Flow Management (ATFM) project. Comprising members from the participating Air Navigation Service Providers (ANSPs) and relevant stakeholders, this document aims to document provide a framework, details of procedures, rules and requirements applicable for ATFM operations based on the Distributed Multi-Nodal ATFM concept. This document will continue to evolve as the project matures from the operational trial stages to the eventual implementation of ATFM.


The following Air Navigation Service Providers (ANSPs) shall be jointly responsible for the administration and maintaining of this document. The administrative duties should be untaken by ANSPs on a quarterly rotational basis. Amendments to this manual will be issued on a quarterly basis unless circumstances dictate otherwise.

ANSPs Administrator Details

Aeronautical Radio of Thailand (AREOTHAI)

Tel: +66 2287-8024 / +66 2287-8025 / +66 8-1829-5256

Fax: +66 2287-8026 / +66 2287-8027

Email: [email protected]

ATFM Web Portal: Refer to email alerts for web link

AFTN Address: VTBBZDZX

Civil Aviation Administration of China (CAAC)

Tel: + 86 898 65751743

Fax: +86 898 65751741

Email: SANYAATFMU @GMAIL.COM / [email protected]

ATFM Web Portal: 59.50.76.99 (temporarily)

AFTN Address: ZJSYZRZX (temporarily)

Civil Aviation Authority of Singapore (CAAS)

Tel: +65 64227001

Fax: +65 65461790

Email: [email protected]

ATFM Web Portal: www.atfm.aero

AFTN Address: WSJCZQZX

Civil Aviation Department (CAD) of Hong Kong

Tel: +852 2910 6859

Fax: +852 2910 1655

Email: [email protected]. hk / [email protected]

ATFM Web Portal: Refer to email alerts for web link

AFTN Address: To be advised


mailto:[email protected]


http://www.atfm.aero/


http://59.50.76.99/


Reference Material

1. Chapter 3 paragraph 3.7.5 (Air Traffic Flow Management) of Annex 11 to the Chicago Convention — Air Traffic Services (13th edition — July 2001, incorporating amendment No 47)

2. Chapter 3 (ATS Capacity and Air Traffic Flow Management) of ICAO Doc 4444, Procedures for Air Navigation Services — Air Traffic Management (PANS-ATM) (15th edition — 2007)

3. ICAO Doc 9971 2nd Ed – Manual on Collaborative Air Traffic Flow management 4. ICAO Asia/Pacific Regional Air Traffic Flow Management Concept of Operations 5. ICAO Asia/Pacific Regional Framework for Collaborative Air Traffic Flow Management


DISTRIBUTED MULTI-NODAL ATFMCommon Operating Procedures (COP)

1 Introduction

1.1 The Asia Pacific region has experienced rapid increase in air traffic demand in the recent years with majority being cross-border flights within the region. While Air Navigation Service Providers (ANSPs) and airport operators are continuously exploring means to increase airspace and airport capacity to match the increasing demand, there is a need for a systematic method to balance demand and capacity in order to allow a sustainable growth in traffic demand in the near future.

1.2 Air Traffic Flow Management (ATFM) is a means to address demand and capacity imbalance. ATFM is a service established with the objective of contributing to a safe, orderly and expeditious flow of air traffic by ensuring that air traffic control capacity is utilized to the maximum extent possible, and that the traffic volume is compatible with the capacities declared by the ANSP.

1.3 Regulating air traffic flow through the application of ATFM measures such as Ground Delay Programs (GDP) is a known operational concept. This is typically carried out by a single entity within a region or independently applied within the domestic boundaries of an ANSP. However, there is an increasing need to apply ATFM measures to facilitate cross-border flight operations especially with the growth of international traffic movements. The concept of applying ATFM measures on cross-border traffic by different control authority can be achieved through the distributed multi-nodal ATFM concept.

1.4 Through a research collaboration led by Civil Aviation Authority of Singapore (CAAS) and Airbus ProSky, with participation from AEROTHAI, Air Traffic Management Bureau of Civil Aviation Administration of China, Department of Civil Aviation Malaysia and Hong Kong Civil Aviation Department, along with other relevant stakeholders, the effort has resulted in the Distributed Multi-Nodal ATFM Network concept. The concept relies on independent ATFM Nodes connected via information sharing network and operating on the same principle. The concept was adopted by ICAO Asia Pacific ATFM Steering Group as the foundation for cross-border ATFM in the Asia-Pacific Regional Framework for Collaborative ATFM document, which was developed to outline key performance enhancements needed for the region.

1.5 The distributed multi-nodal ATFM has since undergone several rounds of validation through the conduct of operational trials. The operational trial also includes the development and refinement of processes and procedures to enable cross-border ATFM service based on the provision of Calculated Take-Off Time (CTOT) for efficient pre-flight operations.

1.6 The progress made by the various ANSPs to operationalize the distributed multi-nodal ATFM concept would pave the way for the widespread implementation of ATFM throughout the Asia-Pacific region. Beyond the ANSPs that embark to carry out the operational trials, the ICAO Asia Pacific ATFM Steering Group (ATFM/SG) would be the suitable platform to propagate participation and implementation of ATFM. The ICAO ATFM/SG, recognizing the need and the challenges of implementing cross-border ATFM, has adopted the distributed multi-nodal ATFM concept and a viable option to address the imbalance and ensure smooth flow of air traffic across the region.

1.7 This document aims to outline key principles and requirements for all stakeholders to involve in the distributed multi-nodal ATFM concept. The document aims to establish the common operating


2

procedures for stakeholders to have a reference and guidance to establish their local process and procedures to implement multi-nodal ATFM. This document also aims to provide the individual ANSPs the basis for publishing their respective AIP Supplement which would contain the specific details and procedures for multi-nodal ATFM operations in their area of service. It is foreseeable that the procedures established in this document will be used as a foundation to harmonize cross-border ATFM process and procedures for the wider aviation community in the Asia-Pacific region.

1.1


3

2 Distributed Multi-Nodal ATFM Network Concept Overview

2.1 Asia-Pacific airspace is characterized by several FIRs and low transit times for flights. Independent local ATFM measures implemented in isolation within one FIR tend to have knock-on effect on downstream FIRs. Existing ATFM frameworks operated fundamentally on centralized management of air traffic flow, which adequately addressed domestic ATFM needs. However, a distributed solution for cross-border ATFM was essential to meet the needs of Asia-Pacific. CAAS and Airbus ProSky, with inputs from other industry partners developed a Distributed Multi-Nodal ATFM Network concept as an alternative solution to implement cross-border ATFM in this region.

2.2 The concept involves each ANSP leading and operating an independent, ATFM/CDM node supported by interconnected information sharing framework. The flow of air traffic will be managed based on a common set of agreed principles among participating stakeholders. An ATFM Node comprising ANSP and associated airports manages demand and capacity through adjustments in aircraft Calculated Landing Time (CLDT) which in turn determines the Calculated Take-Off Time (CTOT) distributed to aircrafts prior to departures from the airports of origin. By using CTOT as a basis for traffic management in the region, ANSPs can avoid imposing excessive unpredictable ground delays through application of measures such as Minutes-in-Trail, Miles-in-Trail or Minimum Border-Crossing Intervals. This could also further reduce the potential airborne delay and carbon emission that would otherwise be incurred when approaching the destination airport.

2.3 Airspace Users play a fundamental role in Collaborative Decision Making (CDM) by specifying delay absorption intent and additional information regarding the flights indicating the capability of compliance to CTOTs. Additionally, being involved in the ATFM operations, Airspace Users will be able to receive advance CTOT information, which will in turn allow for improved flight operations and optimization of available resources.

2.4 Airport Operators, contribute to CDM by providing accurate and updated airport capacity and maximum allowable gate delay based on the airport’s operational demand and capability to manage it. The maximum gate delay component could be considered in the appropriate issuance of CTOTs during ATFM implementation.

2.5 In summary, common core principle, efficient interconnected information sharing platform, and effective CDM chain with comprehensive stakeholder participation form the basis of Distributed Multi-Nodal ATFM Network concept. The concept in turn forms the most viable ATFM solution that can better manage the cross-border flow of traffic in Asia-Pacific region.


4


5

3 Operational Trial: A Phased Approach with Tiered Participation

3.1 The Operational Trial aims to validate the Distributed Multi-Nodal ATFM Network concept leading toward implementation. To enable timely commencement and to provide room for continuous development and expansion, the Operational Trial would first focus on addressing Demand-Capacity Balancing (DCB) at individual airports through regulating arriving flights using CTOT and GDP at ports of origin. Subsequently the project would focus on DCB within sectors and airspace managed by participating ANSPs as well as looking into flow management of long-haul inter-regional flights.3.2 To methodically work toward the goal of the Operational Trial, the project adopts a multi-stage, multi-phase approach as follows:

Phase 1 – DCB for Constrained Arrival AirportsStage 1 Stage 2 Stage 3

Communication Linkage and Protocols

Information Dissemination

Demand Prediction Validation

Local Table-Top Exercises Cross-Border ATFM

Procedure Development and Validation through Demonstration Flights

Limited-Scope Operational Service: Providing ATFM service for planned and ad-hoc events; introduction of Combined ATFM Measure

Phase 2 – DCB for Constrained AirspaceTBD

3.3 Participating stakeholders form individual ATFM Nodes for each respective FIR comprising the ANSP as the Node leader and local Airspace Users (AUs) and Airport operators (AOs) as members. As an example, a typical Singapore ATFM Node would consist of the Civil Aviation Authority of Singapore (CAAS) as the Node Leader, Changi Airport Group (CAG) and local AUs as members. This approach provides a coherent linkage among individual stakeholders within the same FIR and ensures harmonized capability development across the industry.

3.4 In order to encourage more participation from regional states, the Operational Trial adopts a tiered participation level approach to provide the opportunity for stakeholders to participate based on their readiness and capability. The different participation levels also aims to provide an avenue for ATFM Nodes to upgrade to a higher level as members become more ready and capable. The participation levels and their associated capabilities are as follows:

Tiered Participation Level

Expected Capabilities

Level 3 ATFM Nodes Capable to generate, deliver, receive, and comply with CTOT

Level 2 ATFM Nodes Capable to receive and comply with CTOT

Level 1 ATFM Nodes Observe and participate in the Trial Progress


6

3.5 With the rapid and sustained increase in air traffic in the region, it is palpable that ATFM nodes endeavor to be at Level 3 to implement ATFM for constraint airports when required. Recognizing the importance of ATFM nodes to make appropriate preparations to upgrade their participation level, a Readiness Checklist has been developed as a guideline for the required personnel, procedures, support system and stakeholder awareness, with the view that Node Leaders will ensure stakeholders readiness appropriately. The checklist can be found in Annex A.


7

4 Multi-Nodal Common Operating Procedures

General

4.1 To achieve effective DCB through cross-border ATFM measures, it is important that ATFM Stakeholders adhere to the Multi-Nodal Common Operating Procedures (COP) to ensure a common understanding of process, procedures and outcomes. For the COP, “common” is intended to address the high level process flow (e.g. demand prediction, slot allocation, slot dissemination, and slot management) and not details with respect to individual ANSP’s ATFM operational concepts (e.g. CTOT generation algorithms, slot substitution workflow). The autonomy of ANSPs to determine appropriate operational concepts within the common high level process flow is understood and accepted under this COP. In line with the provision of Annex 15, ANSP should publish AIP Supplement with regards to ATFM operations/activities in a timely manner. It is the responsibility of the AUs and AOs to keep current with the latest AIP Supplement before conducting their operations.

4.2 The planning, coordination and execution of the ATFM measures by the parties referred to below in para 4.3 shall comply with the ICAO provisions specified in the Annex 11.

4.3 This document lays down the common requirements in order to optimise the available airports and airspace capacity of the ATFM Nodes for:

(a) airspace users;(b) airport operators;(c) air traffic services (ATS) units;(d) other flow management positions (FMPs);(e) ATFM units;(f) slot coordinators of coordinated airports; and(g) all other organisations and individuals that have a stake in ATFM.

4.4 All flights intended to operate in accordance with the instrument flight rules (IFR) within the airspace and that is subject to ATFM.

4.5 ATFM measures should:

(a) prevent excessive air traffic demand compared with declared air traffic control (ATC) capacity of sectors and airports;

(b) use airspace capacity to the maximum extent possible in order to optimise the efficiency of the airspace and minimise adverse effects on operators;

(c) optimise the airspace capacity made available through the development and application of capacity enhancing measures by ATS units; and

(d) support the management of critical events;

4.6 The allocation of ATFM departure slots shall give priority to flights according to the order of their expected entry into the location at which the ATFM measure will apply.


8

Stakeholders’ Responsibilities

4.7 ANSP stakeholder plays a key role as Node Leaders in the Operational Trial. Accurate traffic demand prediction and airspace outlook, effective issuance of ATFM measures (CTOT information), and coordination of CDM web/teleconference are important elements provided by ATFMU and Tower ATC Units within each ANSP. The following tables outline responsibilities on the part of Level 2 and 3 ANSPs.

Level 3 ANSPs

Responsibilities Descriptions

Demand prediction and monitoring

Predict traffic demand at airports within the node through a range of data sources including AU schedules, Airport slots, and ATS messages (FPLs) and assess demand-capacity imbalance; monitor effectiveness of the demand.

ATFM Measures Ensure the effective implementation of ATFM measures in conjunction with local FMP/ATS units, moreover providing information on ATFM in a timely manner to relevant stakeholder in accordance to the cross-border procedures developed.

Host local CDM conference

Host scheduled CDM conference with local stakeholders to prepare ATFM measures

Host / Participate in cross-border CDM conference

Host or participate in cross-border CDM conference with other node leaders

Generate and distribute ATFM Daily Plan (ADP)

Generate ADP to outline the air traffic situation for the day

Generate and distribute CTOT

Generate CTOTs and distribute via appropriate channels preferably no less than 2 hours before Estimated Off-Block Time (EOBT) to support stakeholder’s advance planning

slot substitution Provide platform for slot substitution management/request to be process

ATFM Measure Effectiveness

Monitor CTOT effectiveness and lead post-ops analysis effort

Adhere to CTOT in departure management

Manage departure traffic in adherence to CTOT within the CTOT tolerance of -5/+10 minutesWhere a flight is subject to an ATFM departure slot, that slot is included as part of the air traffic control clearanceMake every effort to enable departing flights to comply with CTOT.


9

Level 2 ANSPs


Participate in cross-border CDM conference

Participate in cross-border CDM conference with other node leaders

Adhere to CTOT in departure management

Manage departure traffic in adherence to CTOT within the CTOT tolerance of -5/+10 minutesWhere a flight is subject to an ATFM departure slot, that slot is included as part of the air traffic control clearanceMake every effort to enable departing flights to comply with CTOT.

4.8 Other stakeholders’ participation is crucial to the success of the project and of an ATFM system. Timely sharing of information, operational planning, and participation in the CDM chain are all important elements provided by Airport Operators and Airspace Users. The following tables outline responsibilities on the part of these stakeholders.

Airport Operators


Provide flight schedules Provide updated flight schedule to ATFMU for accurate demand prediction

Update airport capacity constraints Notify ATFMU of events that may impact capacity

Participate in CDM conference Actively participate in local CDM conference to provide input on ATFM measures

Ensure capability in receiving CTOT info

Participate in CTOT communication flow

Participate in post-ops analysis Provide feedback on ATFM operations

Airspace Users


Flight Plan (FPL) Management Ensure updated FPLs are filed at least 3 hours prior to EOBT

DLA/CHG Message Submit DLA or CHG messages via AFTN for delay of more than 15 minutes. *Do not update EOBT as a result of CTOT*

Participate in CDM conference Actively participate in CDM conference to provide input on ATFM measures

Monitor alerts and receive CTOT Receive CTOT for departure via website and/or email and monitor ATFM alerts via email for changes

Raise critical operations concerns Highlight significant operations concerns during CDM conference


10

Participate in post-ops analysis Provide feedback on ATFM operations

Information on ATFM Measures

4.9 Information on ATFM will be distributed by the node leaders. This information includes ADPs, alerts/notifications on ATFM measures, CDM web conference/ helpdesk and CTOT dissemination.

(a) The ATFM Daily Plan (ADP) The ADP will provide a summary of planned ATFM measures for the 24 hours period. ADP will be released at 0100UTC. When necessary, a revised ADP will be released. Sample of ADP can be found in Annex B.

(b) Alerts/notifications on ATFM measures

Alerts and notification on ATFM measures will be disseminated through the various means of communications established by the Operational Trial such as email, web portal, AFTN, direct line, instant message applications, etc. Examples on alerts/notifications of ATFM measures can be found in Annex C.

(c) Collaborative Decision-Making Web Conferences Collaborative decision-making (CDM) will allow all members of the ATM community to participate in the ATM decision-making that affects them. Node leaders will arrange and lead the CDM web conferences, where the ADP will be presented and discussed to provide further information on identified constraints. This platform will also provide opportunities for all stakeholders to participate in the decisions marking process which may have a potential impact on their operations.

Processes and Procedures for ATFM Measures

4.10 The effectiveness of ATFM measures to address demand – capacity imbalance requires the cooperation of stakeholders to fulfil their roles and responsibilities in accordance to the agreed common processes and procedures. When ATFM measures are in place, stakeholders shall adhere to the following processes and procedures:

(a) CTOT Dissemination and Publication

4.11 The process of CTOT dissemination and publication would be triggered by the Arrival ATFMU. The Arrival ATFMU shall communicate the intention of putting in place ATFM measures by disseminating the ADP to the following stakeholders. Subsequently, CDM conference shall be conducted to provide clarification and more detailed information on the planned ATFM measures. The CDM conference also provides the Arrival ATFMU a better understanding on the other constraints that stakeholders may have in complying with the ATFM measures. See Annex D-1 for details of the process.


11

4.12 After the CDM conference is completed, the Arrival ATFMU shall publish the CTOT at least 2 hours before the flight’s initial planned EOBT. To cater for the different ATFM support system and processing criteria, distribution of CTOT information could be done in batches according to arrival time or point of departure etc., it could also be delivered singularly to individual flight. Stakeholders, on receipt of CTOT shall trigger the follow up actions accordingly.

I. The Arrival Airport having noted that arriving flight(s) that have CTOT would have a landing and in-block time that would be different from the scheduled time. As such, the necessary adjustments would need to be made if required to the gate allocation for the arriving flight(s).

II. The Departure ATFMU shall inform ATC at the departure airport accordingly. To ensure that all the affected flights are aware of the CTOT, the Departure ATFMU shall collate the acknowledgments from the stakeholders for the affected departures under the purview of the Departure ATFMU. The collated acknowledgement shall then be conveyed to the Arrival ATFMU to complete the information dissemination confirmation.

III. The Departure Airport having noted the CTOT shall adjust their gate planning accordingly to take into consideration the affected departures with CTOT may delay their start-up and off-block times. The Departure Airport shall also notify the Departure ATMFU the acknowledgment of the ATFM measures.

IV. The Airspace Users on receiving the CTOT shall notify the Departure ATFMU the acknowledgment of the ATFM measure. The Airspace Users shall then inform the pilots of the affected flights of the CTOT.

4.13 The Arrival ATFMU shall also notify the ATC supporting the Arrival Airport of the ATFM measure. This would allow close coordination between the Arrival ATFMU and ATC supporting the Arrival Airport to take place effectively to support the ATFM measures. See Annex D-2 for details.

(b) CTOT Management and Lead Time Requirement

4.14 Upon the acknowledgement of receipt of CTOTs by AUs and AOs. Arrival ATFMU will maintain CDM web conference line to provide helpdesk support for AUs and AOs on enquires and request for CTOT management, when a flight has been determined that it is unable to meeting the initial CTOT restriction due to operational or technical reason.

4.15 When the crew of a flight deemed they are unable to comply with the CTOT restriction, the crew shall inform their Flight Ops of the reason for the predicted non-compliance to the CTOT and request for a revised CTOT. On receipt of the request by Flight Ops, it should trigger a series of coordination necessary for the issuance of a revised CTOT;

I. Flight Ops shall monitor and use CTOT information published on the web portal, to determine whether it is possible for either a slot substitution between company traffic or a slot substitution into an open ATFM slot. A request will then be put forth to the Arrival ATFMU to be assess and process. Upon receipt of a revised CTOT, Flights Ops shall inform their flight crew of the revised CTOT time.


12

II. The Arrival ATFMU shall assess the latest development in demand prediction and best facilitate Flight Ops on the slot substitution request. They shall update the web portal with the latest CTOT information after the substitution had been made and inform the Departure ATFMU and AU through email of the revised CTOT for the flight(s) concerned. The Arrival ATFMU shall informed their local stakeholders, ATC and Airport etc. in the change of arrival timing for the flight(s) concerned for their gate and resource planning.

III. The Departure ATFMU on receipt of the revised CTOT, shall acknowledge the change through email and inform ATCs and Airport stakeholders of the change in departure time for the flight(s) concerned for their gate and resource planning. ATC shall facilitate departure of the flight(s) based on the revised CTOT. See Annex D-4 and D-5 for details.

4.16 The requirement to request for a revised CTOT should also take into consideration the operational restrictions that AO and AU can be subjected to. To mitigate the constraints of insufficient reaction time for the processing of revision in CTOT, the table below specifies the lead time required should the request for a revised CTOT originates from the respective user.

Changes Initiated by Lead Time Requirement

Obtaining an EARLIER ATFM Slot

Obtaining a LATER ATFM slot

Airspace User CTOT – [max STT*+ Buffer]Now: CTOT – 30 minutes

N/A

Arrival ATFMU Now: CTOT – 45 minutes

*Max STT refers to maximum standard taxi-out time used in CTOT calculation among the airports in the network: for current operations, the maximum STT is 20 minutes

(c) Revision and cancellation of ATFM measure

4.17 When the Arrival ATFMU determined that the current ATFM measure is insufficient to balance demand and capacity or the projected capacity allows for a relaxation of ATFM measures at the constraint airport or airspace, the Arrival ATFMU shall issue a revision of the ATFM measure. The Arrival ATFMU shall determine the revised AAR and constraint period. This information shall be disseminated, with the appropriate intention stated in the revised ADP via email to the Departure ATFMU, Arrival and Departure airport and AU. The Arrival ATFMU shall then publish the revised CTOTs on the web portal and inform all the stakeholders involved to note the revision in CTOTs. On receipt of the email notification, stakeholders trigger the follow up action accordingly as depicted in para 4.12, with regards to CTOT dissemination and publication in the context of revision in CTOT.

4.18 The Arrival ATFMU shall also notify the ATC supporting the Arrival Airport of the ATFM measure. This would allow close coordination between the Arrival ATFMU and ATC supporting the Arrival Airport to take place effectively to support the ATFM measures. See Annex D-10 and D11 for details

4.19 Upon assessment that an ATFM measures is no longer required for the regulation of air traffic flow. The Arrival ATFMU shall inform the Departure ATFMU and AUs of the cancellation of the ATFM measures. Upon receipt of the confirmation of cancellation of the ATFM measures;


13

I. The Departure ATFMU shall acknowledge the cancellation and inform the Departure ATC and Airport of the cancellation of ATFM measures. The Departure ATC and airport shall then collaboratively facilitate departures based on normal operations, ensuring full utilization of ATC and airport capacity.

II. AUs shall acknowledge the cancellation and inform the flights previously affected by the CTOTs on the cancellation of ATFM measures. The flight crew shall then plan their departure based on normal operation and work in collaboration with the Departure ATC for their clearance.

4.20 The Arrival ATFMU shall inform their local ATC and Airport of the cancellation of ATFM measure to allow reassessment of ground resources and gate allocation planning. See Annex D-6 for details.

(d) Re-time of flights

4.21 When a flight is expected to deviate from its initial flight plan, AUs shall disseminate the appropriate information to the Arrival ATFMU as the accuracy of demand prediction is dependent on the timely submission of flights plans and AFTN messages. The Arrival ATFMU on receipt of the FPL and AFTN messages of change, delay or cancel nature shall monitor changes in the demand prediction and if necessary, to publish a revised ATFM measure that best regulate traffic flow while maximizing capacity. See Annex D-8 and D-9 for details.

(e) Over-riding constraints/restrictions

4.22 An Individual flight should be subjected only to one flow control measure throughout its course of a flight to ensure that a flight is not subjected to potentially unreasonable cumulative delay. If such scenario does occur, AUs should relay this information to the Departure ATFMU or the Arrival ATFMU and seek exemption from the least constraining flow controls measures.

I. The Departure ATFMU upon receipt of such information either from the Departure ATC, Departure Airport or AUs shall inform the Arrival ATFMU and request for exemption from the ATFM flow measures.

II. The Arrival ATFMU upon receipt of a legitimate exemption request, shall exclude the particular flight from the flow program and not subject the flight to a conflicting flow control restriction. If the request is received after the publishing of CTOT, it might not be efficient to re-model the GDP with the exclusion of the particular flight. As such, the Arrival ATFMU should inform the Arrival ATC of the scenario and manage the flight at the tactical level.

4.23 AUs shall inform the flight crew of the exemption from the least constraining flow control measures and flight crew shall coordinate with the departure ATC to take-off at a time that is compliant with the other restriction that is impacted on the flight. See Annex D-7 for detail.

Flight Plan and ATS Messages


14

4.24 In order to ensure that ATFM can balance demand and capacity effectively, up-to-date flight information is required to anticipate the traffic demand. Air traffic demand can be determined from sources such as airport flight schedules/slots, flight plans submitted by operators, and ATS messages through the Aeronautical Fixed Telecommunication Network (AFTN).

4.25 The submission of timely flight plans together with ATS messages such as DLA, CNL, CHG and DEP helps ensure accuracy in demand prediction. This also allows ATFM units to derive an effective ATFM measure when required. The transmission of DEP messages provides ATFM operations with accurate updates of the predicted demand and facilitates the verification of CTOT adherence for the arrival ATFM unit, as well as allowing statistical analysis for post operations review.

4.26 In view of the above, stakeholders should adhere to the following:

(a) Except where necessary for operational or technical reasons, FPL should be submitted not less than 3 hours before EOBT;

(b) DLA message should be originated when the departure of an aircraft, for which basic flight plan data (FPL or RPL) has been sent, is delayed by 15 minutes of more after the EOBT contained in the basic flight plan;

(c) CHG and CNL message are promptly originated in accordance with the provision of ICAO Doc 4444 Procedures for Air Navigation Services (PANS-ATM) 11.4.2.2; and

(d) DEP message to be transmitted in accordance with the provision of ICAO Doc 4444 Procedures for Air Navigation Services (PANS-ATM) 11.4.2.2.

Exemption of Flights

4.27 States may choose to prioritize or exempt certain classes of flight from ATFM measures. Examples of such flights include but are not limited to:

(a) flights experiencing an emergency, including aircraft subjected to unlawful interference; (b) flights on search and rescue or firefighting missions;(c) urgent medical evacuation flights specifically declared by medical authorities;(d) flights with “Head of State” status; and(e) other flights specifically identified by State authorities

4.28 Additionally, aircraft, which are already airborne prior to coming into ATFM area, will be exempted from CTOT requirements. Airborne and long haul flow control will be explored in the later phase of the Operational Trial.

Compliance management

4.29 It is a shared responsibility between Airspace User (AU) and departure ATS unit to ensure a flight’s adherence to CTOT. AU should plan their flight to be ready for take-off at the CTOT (at the holding point). The CTOT adherence window is defined as –5 to +10 minutes for the Operational Trial; to cater for operational variance in aerodrome ground conditions and ATC capabilities. ANSP are encourage to develop and implement local procedures to facilitate and ensure adherence to CTOT at an airport of departure.


15

4.30 Departure nodes shall provide relevant information of non-compliance and the actions taken to ensure adherence to ATFM departure slots.


16

Performance assessment

4.31 Level 3 node ANSPs shall ensure that post analysis reports are produced indicating the quality of ATFM and shall include details of:

(a) causes of ATFM measures;(b) impact of ATFM measures; (c) adherence to ATFM measures; and(d) ATFM Measure effectiveness.

Failure of the ATFM system

4.32 In the event of an ATFM system failure during the Operational Trial period, the node leader will advise on the cancellation of CTOT restrictions and airspace users are to depart according to their EOBTs unless alternate or other flow measures are in place.

Safety Management System for ATFM Implementation and Operations

4.33 The introduction of ATFM may induce changes to existing procedures for Stakeholder. ANSPs should evaluate the need to apply safety management system processes when implementing ATFM in line with existing provisions in PANS-ATM, which includes identification of hazards during ATFM operations. Hazards identified by stakeholders during the ATFM operations should be raised to the ATFMU concerned for follow up actions in accordance to the safety management policies of the respective ATFMUs.

CTOT Information Delivery

4.34 In line with the distributed cross border ATFM concept of operation where member states operates different ATFM system and interface but collaborate and collectively share information necessary for the success of cross border ATFM operations. Member state may select the desired/appropriate method of delivering CTOT information to other stakeholders, while keeping in mind of the compatibility and capability at the receiver’s end. The table below provides a description of how CTOT information originating from the different Arrival ATFMU are disseminated to the relevant stakeholders. Notwithstanding this, member state may wish to explore other information delivery/exchange method.

Delivery Method China Hong Kong Singapore ThailandWeb Portal (User Management and Helpdesk ) Email (+CTOT List) + +Excel format on the Internet AFTN (SAM, SRM, SRC)

*AFTN messages template are included in Annex E


17

Annex A-1Readiness Checklist

LEVEL 3 ANSP

Checklist Item RationaleOperationsCapacity Assessment Procedure

To ensure that the ANSP is able to accurately assess airport capacity under various situations, and thus able to put appropriate Airport Acceptance Rate (AAR) and ATFM program in place

Internal Communication Procedure

To ensure ADP, ATFM Measures and CTOT information can be communicated in a timely manner among ATFMU and operational ATS units

ATFMU Staffing To ensure that the ATFMU is operational and staffed with appropriate personnel, able to initiate ATFM program when needed regardless of time-of-day

Staff Training – ATCs To ensure that ATCs understand the ATFM concept of operations and are able to facilitate departures for flights regulated by CTOTs. This also includes training on CTOT confirmation through clearance delivery.

Staff Training – ATFMU Managers and FMPs

To ensure ATFMU staffs are appropriately trained and capable of facilitating ATFM program effectively. This includes demand-capacity balance assessment, initiation and administering of ATFM Measure, and provision of assistance to stakeholders through Help Desk facility.

System SupportATFM Support System To ensure that the ATFM Support System that is able to (1) accurately

predict demand against capacity, (2) generate and disseminate CTOT information, and (3) allow user to interact with CTOT by changing, adding, canceling, and swapping slots.

Capacity Assessment Tool (if needed)

To aid ATFMU personnel in assess resource (airport / airspace) capacity accurately.

CTOT Distribution Channels To ensure ATFMU can disseminate CTOT information to relevant stakeholders in a timely manner through channels discussed (Web Portal, E-Mail, AFTN)

Web Conference and Help Desk Facility

To ensure the ATFMU can host online web conference for the CDM process and also provide Help Desk for stakeholders to coordinate and/or request assistance during the ATFM program

Awareness / OutreachEngagement with Local Stakeholders (Airlines and Airport Operators)

To exchange knowledge on ATFM concept of operations and procedures between ANSP and Aircraft Operators / Airport Operators and ensure understanding among all stakeholders

Awareness Documents / AIP Supplement / NOTAM

To ensure information regarding the Operational Trial gets distributed to relevant stakeholders and can affect changes in their operations to support the progress

Regulator Engagement To ensure that regulator is up to date with the progress of the Operational Trial, and can assist in any regulatory administration necessary


18


LEVEL 2 ANSP

Checklist Item RationaleOperationsInternal Communication Procedure

To ensure ADP and CTOT information can be communicated in a timely manner among ATFM Point of Contact and operational ATS units

ATFM Point of Contact To ensure that there is an established Point of Contact for ATFM operational information and that the Point of Contact can disseminate information to relevant units as appropriate

Staff Training – ATCs To ensure that ATCs understand the ATFM concept of operations and are able to facilitate departures for flights regulated by CTOTs. This also includes training on CTOT confirmation through clearance delivery.

System SupportATFM Communication Linkage To ensure that there is an established communication linkage to

receive ADP and CTOT information through channels discussed (Web Portal, E-Mail, AFTN)

Awareness / OutreachEngagement with Local Stakeholders (Airlines and Airport Operators)

To exchange knowledge on ATFM concept of operations and procedures between ANSP and Airlines / Airport Operators and ensure understanding among all stakeholders


19


AIRLINES / AIRSPACE USERS


To ensure ADP and CTOT information can be communicated in a timely manner between Flight Dispatchers and Pilots and other relevant operational units


Staff Training – Pilots and Dispatchers

To ensure that Pilots and Flight Dispatchers understand the ATFM concept of operations and are able to appropriately plan departures for flights regulated by CTOTs or coordinate with ATFMU to manage CTOTs if needed



Awareness / OutreachEngagement with Ground Handlers

To exchange knowledge on ATFM concept of operations and procedures with relevant Ground Handlers and ensure understanding as Ground Handlers can sometimes be vital to aircraft turnaround process for flights regulated by CTOTs


20


AIRPORT OPERATORS


To ensure ADP and CTOT information can be communicated in a timely manner between relevant units for operations


Staff Training – Airside Operations / Gate Planning

To ensure that Airside Operations / Gate Planning Personnel understand the ATFM concept of operations and are able to appropriately plan gate usage for flights regulated by CTOTs or coordinate with ATFMU to manage CTOTs if needed




21

Annex BATFM Daily Plan (ADP) TEMPLATE

ATFM DAILY PLAN SINGAPORE [ANSP]DATE / TIME OF ISSUE 17 NOVEMBER 15, 0100UTCSTATUS / REFERENCE NEW / WSSS171115

CONSTRAINTS AND IMPACT

LOCATION APPLICABLEPERIOD (UTC) REMARK

EXPECTED ARRIVAL DELAY

(AVERAGE)WSSS 17 NOV 15 0500 0700 THUNDERSTORM 20 MINS

ATFM MEASURE

LOCATION ATFM MEASUREPERIOD (UTC) ATFM MEASURE CAPACITY IMPACT

WSSS 17 NOV 15 0430 0600 CTOT DEST WSSS AAR - 19WSSS 17 NOV 15 0600 0800 CTOT DEST WSSS AAR - 28

OTHER INFORMATIONWeather Condition – SIGMET, AD, TAF, METAR, Met charts, etc)ANY CHANGES TO FLIGHTS, PLEASE CONTACT SINGAPORE ATFMU VIA PHONE OR HELP DESKHELPDESK NUMBER / WEB CONFERENCE ADDRESSAdditional Remarks


22

Annex C-1Alerts/notifications on ATFM Messages Template

1. ADP dissemination + CDM Web Conference

Subject: MULTI-NODAL ATFM OPS TRIAL – [Title of Operation] [Node] – ADP and CDM Web ConferenceDear All,Please refer to the attached for:

1. ADP - Information on the declared AAR and proposed ATFM Measure2. Meteorological Information

Due to thunderstorm with rain expected from [start time] to [end time], there is a high potential for ATFM Measure to be initiated for arrivals into [ICAO designator for airport] on [date] from [start time] to [end time] Action required:

ATFMUs (Level 2 & 3) please join the CROSS BORDER web conference conducted by [Node] ATFMU at [time] UTC. URL : [ web conference address]

Airlines and Airport Operators participation in the cross border CDM web conference are OPTIONAL

No acknowledgement on the receipt of this email is required. If you encounter any issues participating in the web conference, please email [Node] ATFMU at [Node’s ATFMU email address]


23


2. CTOTs Publication and Slot management Web Conference

Subject: ATFM OPS TRIAL MULTI-NODAL [Title of Operation] [Node] – CTOTs Publication and Slot Management Web Conference Dear All,ATFM Measure will be initiated for arrivals into [ICAO designator for airport] on [date] from [start time] UTC to [end time] UTC.

Calculated Take Off Time (CTOT) Information Please refer to the following website: [ATFM CTOT information website] to view CTOT information.

Slot Management (If required)1. Identify the flight(s) and slot you wish to swop. Example:

Slot Swop: Flight A and Flight B Open Slot: Flight C and Slot “xx/xxxx”

2. Join the Slot management web conference conducted by [Node] ATFMU to request for slot change. URL :[Web conference address]

Action required: Login to web portal using User ID and Password which was provided to the key POCs in your

organization (please check with your respective POCs) View CTOT information Acknowledge the receipt of this email through your ATFM Node leader If required, join Slot Management web conference


24


3. Slot Management

Subject: ATFM OPS TRIAL MULTI-NODAL [Title of Operation] [Node] – Slot Management Dear all,Please note that the following request for Slot Management is successful. Slot Swop

Flight A: Updated CTOT XXXX UTC Flight B: Updated CTOT XXXX UTC

Open Slot Flight C: Updated CTOT XXXX UTC

Please refer to the following website: [ATFM CTOT information website] to view the updated Calculated Take Off Time (CTOT) information.


25


4. ADP Revision Dissemination

Subject: ATFM OPS TRIAL MULTI-NODAL [Title of Operation] [Node] – ADP Revision DisseminationDear All,ATFM Measure implemented for arrivals into [ICAO designator for airport] on [date] from [start time] UTC to [End Time] UTC will be REVISED.Due to change in weather conditions, the duration of the ATFM Measure will be extended till [End Time] UTC. With a further reduced AAR of xx between [start time] UTC to [End Time] UTC Please refer to the following website: [ATFM CTOT information website] to view the revised Calculated Take Off Time (CTOT) information.


organization (please check with your respective POCs) View revised CTOT information


26


5. CTOT Publication (Revision) + Slot Management Web Conference

Subject: ATFM OPS TRIAL MULTI-NODAL [Title of Operation] [Node] – CTOT Publication (Revision) + Slot Management Web ConferenceDear All,ATFM Measure for arrivals into [ICAO designator for airport] on [date] has been REVISED from [start time] UTC to [End Time] UTC

Revised Calculated Take Off Time (CTOT) Information Please refer to the following website: [ATFM CTOT information website] to view CTOT information.

Slot Management (If required)3. Identify the flight(s) and slot you wish to swop. Example:

Slot Swop: Flight A and Flight B Open Slot: Flight C and Slot “xx/xxxx”

4. Join the Slot management web conference conducted by [Node] ATFMU to request for slot change. URL : [Web conference address]


organization (please check with your respective POCs) View REVISED CTOT information Acknowledge the receipt of this email through your ATFM Node leader If required, join Slot Management web conference


Annex D-1CTOT Dissemination and Publication (1/2)


Departure Airport

No action requiredNo action requiredNo action required

Departure ATC PilotsArrival ATC

Arrival ATFMU Departure ATFMU Airspace Users

Publish CTOTs on web portal

Model and implement ATFM measure with reduced AAR

Join web conference (optional)

Receive ADP email

Join web conference (optional)

Join web conference Conduct cross-border CDM

web conference Join web

conference (optional)

Receive ADP emailReceive ADP emailReceive ADP email

and prepare for web conferenceDisseminate ADP through

email indicating time and attach web link for CDM web

conference

Assessment of demand prediction and weather

conditions

Arrival Airport

28

Annex D-2CTOT Dissemination and Publication (2/2)


29

Annex D-3CTOT Compliance


Departure Airport

Inform affected flights of CTOTs

Acknowledge implementation of

ATFM measure through email to respective

local ATFMUs

Receive email and access web portal to

view CTOTs

Receive CTOTsReceive CTOTsNote ATFM

measures for arrivals

Inform Arrival ATFMU on the receipt of CTOTs by all local

node

Acknowledge implementation of

ATFM measure through email to respective local

ATFMUs

Collate acknowledgements of

CTOTs from all local node members

Note CTOT information for gates

planning

Inform ATC of CTOTs


view CTOTs


view CTOTs

Receive email and access web portal

to view CTOTs

Note the changes in arrival timing for

gate planning

Inform ATC of ATFM Measures

Send email alerts to stakeholders informing them of

the implementation of ATFM measure, publish of CTOTs on

web portal and slot management web conference

link

CTOTs Publication


Arrival ATFMU Departure ATFMU Airspace UsersArrival Airport

30

Annex D-4CTOT Management – Slot Swop between 2 Flights


Note CTOT information for gate planning

Departure Airport

Depart in compliance with

CTOTsRefer to CTOTs to facilitate departures

Tactical management of arrivals with due considerations to compliance flights

Note changes in arrival timing for gate

planningNo action requiredNo action

required

Assess effectiveness of existing ATFM measure and

revise/cancel ATFM measure, if required

Monitor changes in demand prediction and the amount of

pop-up flights

After CTOT dissemination



31

Annex D-5CTOT Management – Slot Swop into Open Slot


Departure Airport

Note revised CTOTs information for gates

planning

Facilitate departures based on revised CTOTs

Departure ATC

Arrival AirportRequest for slot swop between Flight A and B from

Arrival ATFMU

Determine which flight (Flight B) to perform a slot

swop with Flight A based on web portal information

Flight A inform Flight Ops unable to comply CTOT due

technical

Receive Revised CTOTs

Note the changes in arrival timing for gate

planning

Departure ATFMU

Inform ATCs and Airports of slot swop information

Acknowledge slot swop information from Arrival

ATFMU through email

Inform Arrival Airport, Departure ATFMUs and

Airspace Users of revised CTOTs through email

Assist Flight Ops in slot swop through web portal

Maintain web conference line to serve as a “Help

Desk” for CTOT management

Pilots Arrival ATFMU

Airspace Users

Flight C inform Flight Ops unable to comply CTOT due Inform ATCs and Airports

of slot swop information


Departure ATFMU


Pilots Arrival ATFMU

32

Annex D-6Cancellation of ATFM Measures


Flight C inform Flight Ops unable to comply CTOT due Inform ATCs and Airports

of slot swop information



Note the cancellation of

ATFM measures for arrivals into

constraint airport or airspace

Departure Airport

Acknowledge cancellation of ATFM measure and depart

based on normal operations

Note the cancellation of ATFM measures and facilitate departures

based on normal operations

Note the cancellation of ATFM measures for

arrivals

Note the cancellation of ATFM measures for

arrivals

Note the cancellation of ATFM measures

for arrivals and inform affected

flights

Note the cancellation of

ATFM measures and inform

Departure Airport and ATC

Send email alerts to stakeholders informing the

cancellation of ATFM measure

ATFM measures is no longer required, Arrival ATFMU

decides to cancel/purge the ATFM measures

Assessment of ATFM measures based on Demand Capacity

Balancing



33

Annex D-7Over-riding Flow Constraints/Restrictions on ATFM Measures


When applicable (AUs to coordinate directly with Arrival ATFMU)

or

Tactical management of arrivals for unknown restrictions and evaluate at post

event

Manually exclude the particular arrivals with another known restriction prior to

issue of CTOTs

Arrival ATFMU

Inform Departure ATFMU if there is an over-riding

constraint

Departure Airport


constraint

Departure ATC


constraint

Airspace Users

Inform Arrival ATFMU if there is an over-riding

constraint

Departure ATFMU

34

Annex D-8Re-timing of Flights into Contraint Period


Monitor changes in demand prediction and the

amount of pop-up flights

Cancel and re-file FPL or send Delay

or Change messages

Revise ATFM measure if required

Note cancelled/ new FPL/ Delay/ Change messages

sent by airline

Arrival ATFMUAirspace Users

35

Annex D-9Re-timing of Flights out of Contraint Period


Cancel and re-file FPL or send Delay

or Change messages

Note cancelled/ new FPL/ Delay/

Change messages sent by airline

Arrival ATFMUAirspace Users

36

Annex D-10Revision of ATFM Measures


Further reduce AAR and extend duration of ATFM

measure

No action requiredNo action requiredNo action required


Arrival ATFMU Departure ATFMU Airspace Users

Publish CTOTs on web portal

Model and implement ATFM measure with reduced AAR

Receive revised ADP email




Disseminate ADP revision through email indicating intention to revise ATFM measure (reduce AAR)

Assessment of constraint and determine if revision of ATFM

measure is required

Arrival Airport Departure Airport

37

Annex D-11CTOT Publication (Revision)


Departure Airport

Inform affected flights of revised CTOTs

Acknowledge revision of ATFM measure through

email to respective local ATFMUs

Receive email and access web portal to view revised CTOTs

Depart in compliance to revised CTOTs

Facilitate departures based on revised CTOTs

Note the revision of ATFM

measures for arrivals

Inform Arrival ATFMU on the receipt of CTOTs by all local node members

Acknowledge revision of ATFM measure through

email to respective local ATFMUs

Collate acknowledgements of

CTOTs from all local node members

Note revised CTOT information for gates

planning

Inform ATC of revision in CTOTs



Receive email and access web portal

to view revised CTOTs

Note the changes in arrival timing for

gate planning

Inform ATC of ATFM Measures

Send email alerts to stakeholders informing them of the

implementation of revision of ATFM measure

CTOTs Publication (Revision)

Departure ATC Pilots

Arrival ATC


Annex E-1ATS Data Exchange Presentation (ADEXP) Messages

1. ADEXP provides a format for use in on-line, computer to computer message exchange and for message exchange over switched messaging networks. The ADEXP specification defines the principles and syntax rules of the ADEXP format. It provides this definition in terms of a comprehensive definition of the ADEXP fields. ADEXP messaging is optional during the trial.

2. ATFM ADEXP messages issued by ATFM Nodes are: SAM, SRM, SLC, FLS, DES, see Annex E for examples.

3. Slot Allocation Message (SAM)

4. The SAM is used to inform AOs & ATS of the Calculated Take-Off Time (CTOT) computed by the ATFM system for an individual flight, to which AOs/ATC must adhere. This message is usually sent to AOs/ATS 2 hours before the last received EOBT.

—TITLE SAM —ARCID SIA123 —ADEP WSSS —ADES VTBS—EOBD 160701 —EOBT 0100 —CTOT 0115 —REGUL VTBS — TAXITIME 0015 —REGCAUSE WA 84

Figure 4-1 Composition of Slot Allocation Message (SAM)

The SAM is used to inform AO’s and ATS of the Calculated Take-Off Time (CTOT) for an individual flight.

Normal response of AO’s/ATS to a SAM message

AO’s must comply with the CTOT. A slot is issued as a Calculated Take-Off Time (CTOT). The CTOT is defined as a time at which the aircraft shall take-off.

The calculation of take-off times takes into account the off-block times and an average taxiing time for the runway in use at the airfield concerned.

5. Slot Revision Message (SRM)

After the ATFM system has issued an initial SAM, subsequent updates may be notified via the Slot Revision Message – (SRM). This message may be used to indicate a delay increase or decrease. The SRM notifies a change of slot. It is issued after the SAM, if applicable. AOs/ATC must comply with the NEWCTOT.

Sending of a SRM

A SRM is sent to notify all concerned of either a significant change (>5’) to the original CTOT. Such changes are due to circumstances unrelated to the flight e.g. The introduction of a new restriction or a change to the parameters of an existing restriction.

When AO modifies slot on the web portal or through the Nodes and the new slot is within a TMI then a SRM will be sent.

To notify all concerned of a routine improvement/deterioration of the CTOT.


39

—TITLE SRM —ARCID ABC101 —ADEP VTBS —ADES VHHH—EOBD 160701 —EOBT 0125 —NEWCTOT 0150 —REGUL VHHH — COMMENT CLDT 160701 0350— TAXITIME 0010 —REGCAUSE WA 84

Annex E-2

Figure 4-2 Composition of a Slot Revision Message (SRM)

Response of AOs/ATS to SRMComply with the NEWCTOT.

6. Flight Suspense Message (FLS)

Indicates that a specific flight has been suspended in the system and is considered as not taking off. The flight data is kept in the database, but suspended (closure of an aerodrome for a long period, for example).

AOs may suspend their flights on Web portal and later de-suspend their flights into open slots. This is used when an AO is experiencing technical difficulties and needs to temporarily suspend their flight. AOs are still required to send a CHG or DLA to modify the FPL.The system will cancel the original CTOT, issue the suspension with a Flight Suspension (FLS) message and await the response of the AO.

—TITLE FLS —ARCID ABC101—ADEP VHHH —ADES VTBS —EOBD 160701 —EOBT 0945 —TAXITIME 0015

Figure 4-3 Composition of Flight Suspense Message (FLS)

7. Slot Requirement Cancellation Message (SLC)

Sent to AOs/ATS to advise that a flight is no longer subject to ATFM measures and may depart without delay or as per EOBT.

An SLC is sent to AOs/ATS to advise that a flight which has received a CTOT is no longer subject to an ATFM restriction. It may be due to the change in parameters of an existing restriction or its cancellation, or to the reception of a message from AOs such as DLA, and CHG.

—TITLE SLC —ARCID ABC101 —ADEP VHHH —ADES VTBS —EOBD 160701 —EOBT 0945 —TAXITIME 0015

Figure 4-4 Composition of Slot Requirement Cancellation Message (SLC)

Response of AOs/ATS to a SLCA flight may normally depart without an ATFM restriction.

8. De-Suspension Message (DES)

Annex E-3


40

This message indicates that a flight, which was previously suspended, is now de-suspended and active in the system. No further action is expected after the reception of a DES by the AO.

The ATFM system sends a DES when a flight not subject to ATFM restrictions is de-suspended. The original suspension could have been due to e.g. receipt of an SAM, the effect of exceptional conditions, closure of aerodrome, termination of the activation monitoring.

—TITLE DES —ARCID ABC101 —ADEP VTBS—ADES WSSS —EOBD160701—EOBT 0945—COMMENT CLDT 160701 1055 —TAXITIME 0015

Figure 4-5 Composition of a De-Suspension Message (DES)

The required action by the AO/ATC is to amend the EOBT by more than 15 minutes later than the EOBT given in the flight plan by sending a DLA message.


41

Annex E-4ATFM ADEXP ATFM Messaging

Each ATFM message comprises a number of fields some of which are mandatory and some optional. Their number varies according to the message type. The fields used ATFM messages are summarized as follows.


FIELDS DEFINITION ADEP ICAO indicator of aerodrome of departure ADES ICAO indicator of aerodrome of destination CTOT Calculated Take-Off Time EOBD Estimated Off-Block Day. EOBT Estimated Off-Block Time NEWCTOT Revised CTOT NEWEOBT Revised EOBT REGUL Identifier for the restriction imposed (may include more than one) COMMENT Commentary TAXITIME Taxi Time REGCAUSE Regulation Cause TITLE Title of the message

42

Annex E-5ATFM ADEXP Messages List (Optional)

ATFM Messages issued by ATFM Nodes: SAM, SRM, SLC, FLS, DES ATFM Messages Examples The following tables give examples of all ATFM messages currently in use. The tables include a brief description of each message and subsequent actions.

Message Originator and Description Action - TITLE SAM- ARCID ABC123- ADEP VTBS- ADES WSSS- EOBD 100303- EOBT 0925- CTOT 1037- REGUL WSSS- COMMENT CLDT 160701 1237 - TAXITIME 0010- REGCAUSE TBA

SAM: Slot Allocation Message

Sent to AU/ATC 2 Hours before last received EOBT.

Web-portal shows CTOT.

The SAM is used to inform AUs & ATS of the Calculated Take-Off Time (CTOT) computed by ATFM system for an individual flight, to which AUs/ATC must adhere.

Sent to AUs/ATS 2 hours before the last received EOBT. AUs/ATC must comply with the CTOT.

- TITLE SRM- ARCID ABC123- ADEP VTBS- ADES WSSS- EOBD 100303- EOBT 0925- NEWCTOT 1037- REGUL WSSS- COMMENT CLDT 160701 1237 - TAXITIME 0010- REGCAUSE TBA

SRM : Slot Revision Message

Sent to AU/ATC to pass or confirm any revision to a CTOT following the issue of the initial SAM.

This message may be used to indicate a delay increase or decrease.

The SRM notifies a significant change of slot. AUs/A TC must comply with the NEWCTOT.

- TITLE SLC- ARCID ABC123 - ADEP VTBS- ADES WSSS- EOBD 100303- EOBT 0925- TAXITIME 0010

SLC : Slot Requirement Cancellation Message

Sent to AU/ATC to advise that a flight, which has received a CTOT, is no longer subject to a restriction.

Flight may depart without restriction unless a new message is received later.


43

Annex E-6ATFM ADEXP Messages List (Optional)

Message Originator and Description Action - TITLE FLS- ARCID ABC123 - ADEP VTBS- ADES WSSS- EOBD 100303- EOBT 0815- TAXITIME 0010

FLS : Flight Suspension Message

Sent to AO/ATC at or after Slot Issue Time to suspend a flight due to exceptional conditions or adverse weather conditions or AO delays flight will enter suspension mode on Web-portal

Flight must be de-suspended to become active again via the Web-portal.

- TITLE DES- ARCID ABC123- ADEP VTBS- ADES WSSS- EOBD 100303- EOBT 0815-COMMENT CLDT 160701 1015 -TAXITIME 0010

DES : Flight De-suspension Message

Sent to AU/ATC to de-suspend a SAM will be sent as well.

No action is normally required of AOs/ATS and the flight if subjected to ATFM regulation will be issued with a CTOT.
