---
title: "ATM/ANS.OR.A.070 Contingency plans — Part-ATM/ANS.OR · Avioverse"
description: "A service provider shall have in place contingency plans for all the services it provides in the case of events which result in significant degradation…"
url: "https://avioverse.aero/regulations/easa/atm-ans/annex-iii-common-requirements-for-service/subpart-a/atm-ans-or-a-070"
---

# ATM/ANS.OR.A.070 Contingency plans

ANNEX III COMMON REQUIREMENTS FOR SERVICE PROVIDERS (Part-ATM/ANS.OR) · Regulation (EU) 2017/373 · EAR revision 12 Mar 2025

IR Implementing rule

## ATM/ANS.OR.A.070 Contingency plans

A service provider shall have in place contingency plans for all the services it provides in the case of events which result in significant degradation or interruption of its operations.

IR · ATM/ANS.OR.A.070 — Regulation (EU) 2017/373 · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

AMC Acceptable means of compliance

## AMC1 ATM/ANS.OR.A.070 Contingency plans

[MODE S INTERROGATOR](https://avioverse.aero/glossary/easa/mode-s-interrogator) CODES

(a) An air traffic service provider should assess the possible impact on air traffic services of interrogator code conflicts, and the corresponding potential loss of Mode S target surveillance data from the impacted Mode S interrogators, taking into account their operational requirements and available redundancy.

(b) Unless the potential loss of Mode S target surveillance data has been assessed to have no safety significance, the surveillance provider should:

(1) implement monitoring means to detect interrogator code conflicts caused by other Mode S interrogators impacting eligible Mode S interrogators that they operate on any operational interrogator code;

(2) ensure that the interrogator code conflict detection provided by the implemented monitoring means is achieved in a timely manner and within a coverage that satisfy their safety requirements;

(3) identify and implement as appropriate, a fallback mode of operation to mitigate the possible interrogator code conflict hazards on any operational code, identified in the assessment referred to in point (1);

(4) ensure that the implemented fallback mode of operation does not create any interrogator code conflict with other Mode S interrogators referred to in the [interrogator code allocation plan](https://avioverse.aero/glossary/easa/interrogator-code-allocation-plan).

AMC · AMC1 ATM/ANS.OR.A.070 — Regulation (EU) 2017/373 · ED Decision 2023/018/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GM Guidance material

## GM1 ATM/ANS.OR.A.070 Contingency plans

GENERAL

The contingency plan may include the definition of the measures, the coordination with other actors (i.e. the State, the competent authorities, possibly the other service providers, the insurance companies, aerodrome operators, as applicable) and alternative services needed in case of degradation or interruption of the services, while the applicability of emergency response planning may be attributable to or affected by an aviation safety occurrence.

GM · GM1 ATM/ANS.OR.A.070 — Regulation (EU) 2017/373 · ED Decision 2017/001/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

[All rules in SUBPART A — GENERAL REQUIREMENTS (ATM/ANS.OR.A)](https://avioverse.aero/regulations/easa/atm-ans/annex-iii-common-requirements-for-service/subpart-a)

Consolidated from the EASA Easy Access Rules (revision 12 Mar 2025, extracted 13 Oct 2026) for convenience. Not the official publication — verify against the Official Journal of the European Union and the EASA publications before operational use.