Skip to content

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

DAT.OR.200 Reporting requirements

SPECIFIC REQUIREMENTS FOR PROVIDERS OF DATA SERVICES · Regulation (EU) 2017/373 · EAR revision 12 Mar 2025

IRImplementing rule

DAT.OR.200Reporting requirements

(a)The DAT provider shall:

(1)report to the customer and, where applicable, the equipment design approval holder all the cases where aeronautical databases have been released by the DAT provider and have been subsequently identified to have deficiencies and/or errors, thus not meeting the applicable data requirements.;

(2)report to the competent authority the deficiencies and/or errors identified according to point (1), which could lead to an unsafe condition. Such reports shall be made in a form and manner acceptable to the competent authority;

(3)where the certified DAT provider is acting as a supplier to another DAT provider, report also to that other organisation all the cases where it has released aeronautical databases to that organisation and have been subsequently identified to have errors;

(4)report to the aeronautical data source provider instances of erroneous, inconsistent or missing data in the aeronautical source.

(b)The DAT provider shall establish and maintain an internal reporting system in the interest of safety to enable the collection and assessment of reports in order to identify adverse trends or to address deficiencies, and to extract reportable events and actions. This internal reporting system may be integrated into the management system as required in point ATM/ANS.OR.B.005.

IR · DAT.OR.200 — Regulation (EU) 2017/373 · ED Decision 2017/001/R · ATM/ANS Easy Access Rules · EAR revision 12 Mar 2025

GMGuidance material

GM1 DAT.OR.200Reporting requirements

Show the text

GENERAL The DAT provider should notify the competent authority of the following by using the occurrence reporting form:

(a)errors/deficiencies affecting safe operations in an airspace segment/block;

(b)errors/deficiencies with negative impact on safety stemming from a source in a Member State or a functional airspace block (FAB); and

(c)errors/deficiencies with negative impact on safety stemming from erroneous processing of the data or information within the intended aircraft application/equipment.

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

GMGuidance material

GM1 DAT.OR.200(b)Reporting requirements

Show the text

UNSAFE CONDITION ‘Unsafe condition’ may be considered as a situation where due to a data error there will be, but is not limited to: aircraft deviation from the published procedure; erroneous warning (red colour) in the cockpit (e.g. PULL UP, TERRAIN, RWY TOO SHORT); pilot workload increase due to presentation of misleading or conflicting data in the primary flight display; and malfunction or defect of an indication system at a critical phase of the flight, etc.

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

All rules in SUBPART A — ADDITIONAL ORGANISATION REQUIREMENTS FOR PROVIDERS OF DATA SERVICES (DAT.OR)

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 DAT.OR.200 →

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