Skip to content

A gradual release of Avioverse begins in October 2026. Request early access →

ATM/ANS.OR.A.085 Aeronautical data quality management

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

IRImplementing rule

ATM/ANS.OR.A.085Aeronautical data quality management

When originating, processing or transmitting data to the AIS provider, the service provider shall:

(a)ensure that aeronautical data referred to in Appendix 1 conform to the specifications of the aeronautical data catalogue;

(b)ensure that the following data quality requirements are met:

(1)the accuracy of aeronautical data is as specified in the aeronautical data catalogue;

(2)the integrity of aeronautical data is maintained;

(3)based on the integrity classification specified in the aeronautical data catalogue, procedures are put in place so that:

(i)for routine data, corruption is avoided throughout the processing of the data;

(ii)for essential data, corruption does not occur at any stage of the entire process and additional processes are included, as needed, to address potential risks in the overall system architecture to further assure data integrity at this level;

(iii)for critical data, corruption does not occur at any stage of the entire process and additional integrity assurance processes are included to fully mitigate the effects of faults identified as potential data integrity risks by thorough analysis of the overall system architecture;

(4)the resolution of aeronautical data is commensurate with the actual data accuracy;

(5)the traceability of aeronautical data is ensured;

(6)the timeliness of the aeronautical data is ensured, including any limits on the effective period of the data;

(7)the completeness of the aeronautical data is ensured;

(8)the delivered data meet the specified format requirements;

(c)with regard to data origination, establish specific formal arrangements with the party originating data that contain instructions for data creation, modification or deletion, which include as a minimum:

(1)an unambiguous description of the aeronautical data to be created, modified or deleted;

(2)the entity to which the aeronautical data is to be provided;

(3)the date and time by which the aeronautical data is to be provided;

(4)the format of the data origination report to be used;

(5)the format of the aeronautical data to be transmitted;

(6)the requirement to identify any limitation on the use of the data;

(d)ensure that data validation and verification techniques are employed to ensure that the aeronautical data meets the associated data quality requirements and in addition:

(1)the verification shall ensure that aeronautical data is received without corruption and that corruption does not occur at any stage of the entire aeronautical data process;

(2)aeronautical data and aeronautical information entered manually shall be subject to independent verification to detect any errors that may have been introduced;

(3)when using aeronautical data to derive or calculate new aeronautical data, the initial data shall be verified and validated, except when provided by an authoritative source;

(e)transmit aeronautical data by electronic means;

(f)establish formal arrangements with:

(1)all parties transmitting data to them;

(2)other service providers or aerodrome operators when exchanging aeronautical data and aeronautical information;

(g)ensure that the information listed in point AIS.TR.505(a) is provided in due time to the AIS provider;

(h)collect and transmit metadata which include as a minimum:

(1)the identification of the organisations or entities performing any action of originating, transmitting or manipulating the aeronautical data;

(2)the action performed;

(3)the date and time the action was performed;

(i)ensure that tools and software used to support or automate aeronautical data and aeronautical information processes perform their functions without adversely impacting the quality of aeronautical data and aeronautical information;

(j)ensure that digital data error detection techniques are used during the transmission or storage of aeronautical data, or both, in order to support the applicable data integrity levels;

(k)ensure that the transfer of aeronautical data is subject to a suitable authentication process such that recipients are able to confirm that the data has been transmitted by an authorised source;

(l)ensure that errors identified during data origination and after data delivery are addressed, corrected or resolved and that priority is given to managing errors in critical and essential aeronautical data.

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

GMGuidance material

GM1 ATM/ANS.OR.A.085(a)Aeronautical data quality management

Show the text

AERONAUTICAL DATA CATALOGUE The aeronautical data catalogue presents the scope of data that can be collected and maintained by the AIS providers and provides a common terminology that can be used by data originators and service providers.

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

GMGuidance material

GM1 ATM/ANS.OR.A.085(b)Aeronautical data quality management

Show the text

GENERAL Minimum requirements for the processing of aeronautical data may be found in EUROCAE ED-76A, ‘Standards for Processing Aeronautical Data’, June 2015, which aims to assist aeronautical data chain actors.

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

GMGuidance material

GM1 ATM/ANS.OR.A.085(b)(4)Aeronautical data quality management

Show the text

RESOLUTION

(a)Stating that resolution needs to be commensurate with the actual accuracy means that digital data needs to have sufficient resolution to maintain accuracy. Typically, if an accuracy of .1 unit is needed, then a resolution of 0.01 or .001 units would enable a data chain to preserve the accuracy without issue. A finer resolution could be misleading as one could assume that it supports a finer accuracy. This factor range of 10 to 100 between accuracy and resolution is applicable regardless of the units of measurements used.

(b)The resolution should be enough to capture the accuracy of the data.

GM · GM1 ATM/ANS.OR.A.085(b)(4) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 ATM/ANS.OR.A.085(b)(5)Aeronautical data quality management

Show the text

TRACEABILITY Traceability is supported by maintaining the metadata.

GM · GM1 ATM/ANS.OR.A.085(b)(5) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

AMCAcceptable means of compliance

AMC1 ATM/ANS.OR.A.085(b)(8)Aeronautical data quality management

Show the text

FORMAT The format requirements should be specified in the formal arrangements.

AMC · AMC1 ATM/ANS.OR.A.085(b)(8) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

AMCAcceptable means of compliance

AMC1 ATM/ANS.OR.A.085(d)Aeronautical data quality management

Show the text

VALIDATION AND VERIFICATION

(a)The processes implemented to carry out validation and verification should define the means used to:

(a)verify received data and confirm that the data has been received without corruption;

(b)preserve data quality and ensure that stored data is protected from corruption; and

(c)confirm that originated data has not been corrupted prior to being stored.

(b)Those processes should define the:

(1)actions to be taken when data fails a verification or validation check; and

(2)tools required for the verification and validation process.

AMC · AMC1 ATM/ANS.OR.A.085(d) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 ATM/ANS.OR.A.085(d)Aeronautical data quality management

Show the text

VALIDATION AND VERIFICATION — GENERAL

(a)Validation

(1)Validation is the activity where a data element is checked as having a value that is fully applicable to the identity ascribed to the data element, or where a set of data elements are checked as being acceptable for their intended use.

(2)The application of validation techniques considers the entire aeronautical data chain. This includes the validation performed by prior data chain participants and any requirements levied on the data supplier.

(3)Examples of validation techniques

(i)Validation by application One method of validation is to apply data under test conditions. In certain cases, this may not be practical. Validation by application is considered to be the most effective form of validation. For example, flight inspection of final approach segment data prior to publication can be used to ensure that the published data is acceptable.

(ii)Logical consistency Logical consistency validates by comparing two different data sets or elements and identifying inconsistencies between values based on operative rules (e.g. business rules).

(iii)Semantic consistency Semantic consistency validates by comparing data to an expected value or range of values for the data characteristics.

(iv)Validation by sampling Validation by sampling evaluates a representative sample of data and applies statistical analysis to determine the confidence in the data quality.

(b)Verification

(1)Verification is a process for checking the integrity of a data element whereby the data element is compared to another source, either from a different process or from a different point in the same process. While verification cannot ensure that the data is correct, it can be effective to ensure that the data has not been corrupted by the data process.

(2)The application of verification techniques considers only the portion of the aeronautical data chain controlled by the organisation. Yet, verification techniques may be applied at multiple phases of the data processing chain.

(3)Examples of verification techniques

(i)Feedback Feedback testing is the comparison between the output and input state of a data set.

(ii)Independent redundancy Independent redundancy testing involves processing the same data through two or more independent processes and comparing the data output of each process.

(iii)Update comparison Updated data can be compared to its previous version. This comparison can identify all data elements that have changed. The list of changed elements can then be compared to a similar list generated by the supplier. A problem can be detected if an element is identified as changed on one list and not on the other.

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

GMGuidance material

GM2 ATM/ANS.OR.A.085(d)Aeronautical data quality management

Show the text

VALIDATION AND VERIFICATION TECHNIQUES Validation and verification techniques are employed throughout the data processing chain to ensure that the data meets the associated DQRs. More explanatory material may be found in Appendix C (Guidance on compliance with data processing requirements) to EUROCAE ED-76A ‘Standards for Processing Aeronautical Data’.

GM · GM2 ATM/ANS.OR.A.085(d) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 ATM/ANS.OR.A.085(e)Aeronautical data quality management

Show the text

ELECTRONIC MEANS The transmission of aeronautical data and aeronautical information may be done by various electronic means.

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

AMCAcceptable means of compliance

AMC1 ATM/ANS.OR.A.085(f)Aeronautical data quality management

Show the text

FORMAL ARRANGEMENTS Formal arrangements should include the following minimum content:

(a)the aeronautical data to be provided;

(b)the data quality requirements (DQRs) for each data item supplied according to the aeronautical data catalogue;

(c)the method(s) for demonstrating that the data provided conforms with the specified requirements;

(d)the action to be taken in the event of discovery of a data error or inconsistency in any data provided;

(e)the following minimum criteria for notification of data changes:

(1)criteria for determining the timeliness of data provision based on the operational or safety significance of the change;

(2)any prior notice of expected changes; and

(3)the means to be adopted for notification;

(f)the party responsible for documenting data changes;

(g)data exchange details such as format or format change processes;

(h)any limitations on the use of data;

(i)requirements for the production of data origination quality reports;

(j)metadata to be provided; and

(k)contingency requirements concerning the continuity of data provision

AMC · AMC1 ATM/ANS.OR.A.085(f) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 ATM/ANS.OR.A.085(f)Aeronautical data quality management

Show the text

FORMAL ARRAGNEMENTS ATM/ANS providers may use the predetermined template ‘Data Provision Agreement’ developed by EUROCONTROL (ADQ Formal Arrangement Template, version 1.1. issued on 22 February 2016.)

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

GMGuidance material

GM1 ATM/ANS.OR.A.085(i)Aeronautical data quality management

Show the text

SOFTWARE

(a)A means by which the requirement in ATM/ANS.OR.A.085(i) can be met, is through the verification of software applied to a known executable version of the software in its target operating environment.

(b)The verification of software is a process of ensuring that the software meets the requirements for the specified application or intended use of the aeronautical data and aeronautical information.

(c)The verification of software is an evaluation of the output of an aeronautical data and/or aeronautical information software development process to ensure correctness and consistency with respect to the inputs and applicable software standards, rules and conventions used in that process.

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

GMGuidance material

GM2 ATM/ANS.OR.A.085(i)Aeronautical data quality management

Show the text

TOOLS Tools can be qualified meeting point 2.4.5 Aeronautical Data Tool Qualification of EUROCAE ED-76A/RTCA DO-200B ‘Standards for Processing Aeronautical Data’, dated June 2015.

GM · GM2 ATM/ANS.OR.A.085(i) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 ATM/ANS.OR.A.085(j)Aeronautical data quality management

Show the text

DATA ERROR DETECTION TECHNIQUES

(a)Digital error detection techniques can be used to detect errors during the transmission or storage of data. An example of a digital error detection technique is the use of cyclic redundancy checks (CRCs). Coding techniques can be effective regardless of the transmission media (e.g. computer disks, modem communication, or internet).

(b)Transmission of data via electronic/digital means (e.g. file transfer protocol (FTP) sites, web downloads, or email) may be subject to malicious attack that can corrupt the integrity of data for its intended use. Provision of means to mitigate the intentional corruption of digitally transmitted data may already exist within the organisational construct and operating procedures of participating entities.

(c)The objective of data security is to ensure that data is received from a known source and that there is no intentional corruption during processing and exchange of data.

(d)Records should be maintained to show what data security provisions have been implemented.

(e)Provisions supporting this objective may include:

(1)implementation of technical data security measures to provide authentication and prevent intentional corruption during exchange of data (e.g. secure hashes, secure transmissions, digital signatures); and

(2)implementation of organisational data security measures to protect processing resources and prevent intentional corruption during processing of data.

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

GMGuidance material

GM2 ATM/ANS.OR.A.085(j)Aeronautical data quality management

Show the text

DATA ERROR PROCESSING More explanation and guidance may be found in Appendix C (Guidance on compliance with data processing requirements) to EUROCAE ED-76A.

GM · GM2 ATM/ANS.OR.A.085(j) — Regulation (EU) 2017/373 · ED Decision 2020/008/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 ATM/ANS.OR.A.085(l)Aeronautical data quality management

Show the text

ERROR HANDLING

(a)The term ‘error’ is understood as being defective, degraded, lost, misplaced or corrupted data elements, or data elements not meeting stated DQRs.

(b)Guidance on how to detect, identify, report and address/resolve aeronautical data errors may be found in Appendix C (Guidance on compliance with data processing requirements) to EUROCAE ED-76A ‘Standards for Processing Aeronautical Data’.

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

All rules in SUBPART A — GENERAL REQUIREMENTS (ATM/ANS.OR.A)

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

Ask Metis about ATM/ANS.OR.A.085 →

Metis opens with Avioverse in October 2026 · request early access.