Airport Operations Plan (AOP) means a single, common and collaboratively agreed rolling plan used by all involved airport stakeholders whose purpose is to provide common situational awareness and to form the basis upon which airport stakeholder decisions relating to process optimization for operations can be made.

The AOP shall make all the information that is relevant for the network available to the NOP in real time.
The AOP is the principal source of information used and shared by all involved airport stakeholders. It requires individual stakeholders to make changes within their own sphere of operations. These changes must be synchronised in order to be consistent and provide common situational awareness.

The AOP supports operations at airports with an increased scope and sharing of data between the airport and the Network Manager, building upon the airport collaborative decision making (A-CDM) supporting systems.
The AOP is a rolling plan comprising different phases including Planning, Execution and Monitoring and Post-operations, that interacts with a number of services, systems and stakeholders gathering information from several systems.

Main stakeholders are Airport Operators. Stakeholders also impacted are all the other involved airports stakeholders such as but not limited to:

• Aircraft operators;
• Ground handlers;
• De-icing handlers;
• ANSPs;
• Network Manager;
• MET services providers;
• Support services (police, customs and immigration, etc.).

The AOP can be implemented in two steps: Initial AOP (iAOP) and Extended AOP.

The initial AOP (iAOP) focuses on the short-term planning phase and the execution phase. The iAOP comprises the basic elements to exchange the data elements with the NOP and paves the way to Extended AOP.

The following data are part of the initial AOP:

• Flight trajectory data: Information sharing related to Flight Progress Information Elements of an Inbound/Outbound/Airport transit Trajectory to/from/at Airport.
• Airport Resources data: resources such as but not limited to runway capacity and configuration, or parking stands.
• Local weather data: Information sharing related to MET Information Elements of the airport.

The iAOP shares flight trajectory data and some airport resources data with the NOP via Arrival Planning Information (API) and Departure Planning Information (DPI) messages.

System requirements:

To support the Initial AOP implementation, the following elements shall be taken into account:

• A-CDM (a pre-requisite for iAOP);
• Arrival planning information and extended departure planning information (in addition to A-CDM DPI messages) for iAOP/NOP exchange;
• MET-data: to allow the outcome of weather impact assessment;
• Airport Operations Plan management tool containing the rolling plan of the airport operations and capabilities for short-term time frame;
• The AOP shall be connected to the NOP via SWIM service(s) when available and shall make available to the network all the network-relevant data.

NOTE FOR MILITARY AUTHORITIES: It is the responsibility of each military authority to review this Objective IN ITS ENTIRETY and address each of the SLoAs that the military authority considers RELEVANT for itself. This has to be done on top and above of the review of "MIL" SLoAs which identify actions EXCLUSIVE to military authorities.

NOTE: The SLoAs listed in this document should be addressed to air navigation service providers as well as to airport operators. This is due to the fact that some airports operate their own ground control units for specific areas of responsibility at the airport. Airport operators providing air traffic control services qualify as ANSPs and are therefore covered by the ASP SLoAs. It is up to each implementer to check and select what is relevant to them, depending on local areas of responsibility.

Edition

2022

Stakeholders

Air Navigation Service Provider / Airport Operator

Type

CP1

Scope

Airport

Status

Active