eATM Portal

AOP12.1 — Airport Safety Nets

Airport safety nets refers to the Airport Safety Support Service as defined in the EUROCONTROL Specification for Advanced-Surface Movement, Guidance and Control System (A-SMGCS) Services Edition: 2.0 dated: 22 April 2020 and EUROCAE Standard ED87-D: Minimum Aviation System Performance Specification (MASPS) for A-SMGCS, June 2019.

The scope of this Objective covers the Aerodrome Movement Area as defined by the ICAO documents (ICAO Annex 14 Aerodrome Design and Operations, Volume I, Edition 7, 2016).
The A-SMGCS Airport Safety Support Service contributes to airside operations as a safety improvement, enabling Controllers to prevent hazards/incidents/accidents resulting from Controller, Flight Crew or Vehicle Driver operational errors or deviations. This Service depends on the Surveillance Service being in operation.

The Airport Safety Support Service supports Controllers by:

• Anticipating potential conflicts (e.g. hazardous situations between aircraft or aircraft and vehicles).
• Detecting conflicts and incursions.
• Detecting mobiles that are not following given Clearances.
• Providing alerts.

The Airport Safety Support Service is designed on the basis of one or more of the following three functions. These functions may be partially introduced depending on local requirements e.g. not all CATC or CMAC alerts may be suitable depending on the aerodrome layout:

• Runway Monitoring and Conflict Alerting (RMCA)
• Conflicting ATC Clearances (CATC).
• Conformance Monitoring Alerts for Controllers (CMAC).

The RMCA function acts as a short-term alerting tool, whereas the CATC and CMAC serve to be more predictive tools that aim at preventing situations where an RMCA alert may be triggered.
For the CATC and CMAC alerts to function correctly it is important that the system receives the Controller’s Clearances, therefore, the Controller shall be provided with an Electronic Clearance Input (ECI) means e.g. Electronic Flight Strips (EFS).
Some of the CMAC alerts work on the assumption that every mobile entering the Runway Protected Area (RPA) or Restricted Area shall have received a Clearance from the Controller.
The clearances to be addressed by the Air Traffic Controllers in the context of the Airport Safety Nets service, are described in the EUROCONTROL A-SMGCS Specification Ed. 2.0. This EUROCONTROL reference document also covers the issues linked to potential local limitations that may arise.

Depending on the local implementation strategy, this Objective could also affect other stakeholders subject to using vehicles on the movement area, such as but not limited to Handling Companies, De-Icing Agents, often operating under the coordination of the airport operator that is responsible for the safeguard of all the stakeholders involved.

System requirements:

The detection of Conflicting ATC Clearances (CATC), the Conformance Monitoring of Alerts for Controllers (CMAC) shall be performed by the ATC system based on the knowledge of:

• Data related to the aircraft or vehicle e.g. identity, type, flight plan, SSR code, stand, Clearances, planned route, cleared route, assigned runway, timing information, de-icing information, aircraft status (e.g. assumed, pending, transferred),
• Airport Operations data e.g. aerodrome maps, reference points (runway thresholds, holding points, stop bars etc…), operational use of runways, ATC procedures, activation/de-activation of LVP etc…

The detection of CMAC alerts requires in some cases the ATC system to know the aircraft route e.g. Route deviation.
The air traffic controller shall input all clearances given to mobiles into the ATC system using an Electronic Clearance Input (ECI) means.
The Airport Safety Support Service may be partially introduced depending on local limitations due to airport specificities, e.g. not all CATC or CMAC alerts may be suitable depending on the aerodrome layout. In these cases, some systems requirements contained in the two documents referred to above (the EUROCONTROL Specification and the EUROCAE document) may have to be adapted to meet the local needs.

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 responsibilities.

Air Navigation Service Provider / Airport Operator


Related Elements

Applicability Area(s) and Timescales

Applicability Area 1:
See list of airports in MP Level 3 Implementation Plan - Annexes
Applicability Area 2 (non-CP1 Airports):
See list of airports in MP Level 3 Implementation Plan - Annexes
Timescales From By Applicable to
Initial Operational Capability 01-01-2021 Applicability Area 1 + Applicability Area 2 (non-CP1 Airports)
Full Operational Capability / Target Date 31-12-2025 Applicability Area 1 + Applicability Area 2 (non-CP1 Airports)

Links to SESAR Solutions

Links to PCP ATM Sub-Functionalities

ICAO Block Modules: No associated data


Applicable legislation
Regulation (EU) No 2021/116 on the establishment of the Common Project One
Applicable ICAO Annexes and other references
Deployment Programme 2022
Family 2.3.1 - Airport Safety Nets
Operating Environments

Expected Performance Benefits

Improved safety in airport operations.
Increased situational awareness.
Operational efficiency
Increased situational awareness.
Cost efficiency
Increased situational awareness.
  Code Title From By Related Enablers
ASP01 Supporting RMCA systems implemented
  • 01-01-2021
  • 31-12-2025
ASP02 Supporting CATC and CMAC systems implemented
  • 01-01-2021
  • 31-12-2025
ASP03 Operational procedures developed
  • 01-01-2021
  • 31-12-2025
ASP04 Safety Assessment
  • 01-01-2021
  • 31-12-2025
ASP05 Training
  • 01-01-2021
  • 31-12-2025
ASP06 Operational use
  • 01-01-2021
  • 31-12-2025
APO01 Supporting RMCA systems implemented
  • 01-01-2021
  • 31-05-2025
APO02 Supporting CATC and CMAC systems implemented
  • 01-01-2021
  • 31-12-2025
APO03 Develop operational procedures
  • 01-01-2021
  • 31-12-2025
APO04 Safety assessment
  • 01-01-2021
  • 31-12-2025
APO05 Training
  • 01-01-2021
  • 31-12-2025
APO06 Operational use
  • 01-01-2021
  • 31-12-2025
Code Dates
1999 99
2000 00
2001 01
2002 02
2003 03
2004 04
2005 05
2006 06
2007 07
2008 08
2009 09
2010 10
2011 11
2012 12
2013 13
2014 14
2015 15
2016 16
2017 17
2018 18
2019 19
2020 20
2021 21
2022 22
2023 23
2024 24
2025 25

Supporting Material

Title Related SLoAs

SDM - Standardisation and Regulation support to CP1 deployment 2021, Deliverable D1.1.1 07/2021

APO01, APO02, APO03, APO04, APO05, ASP01, ASP02, ASP03, ASP04, ASP05

Consultation & Approval

Working Arrangement in charge
Outline description approved in
Latest objective review at expert level
Commitment Decision Body
Objective approved/endorsed in
Latest change to objective approved/endorsed in