1.1. Introduction

This section sets the definition of terms and terminology used in the documentation explaining the functioning of the entire ECCAIRS 2 (from now on it can be referred to as E2) through the perspective of different roles. 

The E2 mission is to aid National and European transport entities in the collection, sharing and analysis of safety information in order to improve public transport safety. This section also briefly depicts what is E2, its goals and its legal support.

1.1.1. About ECCAIRS 2

ECCAIRS 2 (European Coordination Centre for Accident and Incident Reporting Systems) is the second version of an IT system designed to support a collaborative network of National Aviation Authorities (NAAs) and Safety Investigation Authorities (SIAs) from EU Member States, along with the European Union Aviation Safety Agency (EASA). Its core mission is to facilitate the collection, sharing, and analysis of safety-related information to enhance the safety of public transportation.

Key Objectives:

Integration of original reports from disparate, currently incompatible sources. Providing an occurrence reporting solution for Member States without an automated system.

E2 implements collection and dissemination requirements for:

Reports and Occurrences, as well as, Safety recommendations from the Safety Investigation Authorities,

Member States' safety data is consolidated in two central databases:

ECR-ECCAIRS – The European Central Repository for Occurrences (required by Regulation (EU) 376/2014), which aggregates national and European-level reports. ECR-SRIS – The European Central Repository for Safety Recommendations (required by Regulation (EU) 996/2010).

System Architecture & Functionality

ECCAIRS 2 is thean Europeanintegrated platformsystem designedsupported forby two distinct but interconnected taxonomies:

ECCAIRS Taxonomy (previously linked to ADREP) – Facilitates the efficientcollection and secure managementprocessing of original occurrence reportsreports. inSRIS Taxonomy – Enables the fieldrecording, tracking, and public dissemination of aviation.safety Theserecommendations, reportsincluding responses.

Occurrence Reporting Process

Based on the ECCAIRS Taxonomy, which standardizes definitions and classifications. Reports are submitted tovia the systemE2 Web Application, validated, and converted into confirmed occurrences. Data can be shared at the European level (ECR) or optionally with other authorized entities within the E2 system.

Safety Recommendations Process

Powered by reportersthe orSRIS organizations,Taxonomy suchto assupport airlines,Safety maintenanceInvestigation organisations,Authorities or(SIAs). otherEnables aviationthe stakeholders.recording, The collection, validation,tracking, and follow-uppublication of reportssafety arerecommendations, essentialalong taskswith thatresponse contributemonitoring, directly to the continuous improvement of operational safety.

The process is primarily managed by Occurrence Officers from aviation Authorities of each country. To reduce manual workload, the system also allows for the automation of repetitive or large-scale tasks through batch operations. Ason a result,dedicated thepublic systemportal.

requires prior configuration and ongoing maintenance, which are handled by National Security Administrator.

There are three types of reports in the process:

• Original Report (OR): It is a description of the safety event submitted by a Reporter.
• Validated Report (VR): It is a copy of the OR stored in the National Authority's E2 database. It is editable, allowing enrichment.
• Occurrence (OC): It is the main enriched report, representing the complete occurrence after integrating all related VRs. It consolidates all relevant information and can be shared with the European Central Repository (ECR) for further analysis and safety oversight.

In broad terms the workflow includes receiving an OR, validating it into VR, integrating the VR into an OC, and finally sharing the Occurrences with the European Central Repository (ECR):

In some cases, managing an occurrence can be more complex, as a single event (such as an accident or incident) may generate multiple OR from different reporters. Each OR is validated into a VR, and all VRs are eventually merged into a single OC to be shared with the ECR or forwarded to another authority. Furthermore, if changes are made to an OR or VR after processing has begun, they may conflict with existing data—therefore, the process includes mechanisms to identify and resolve such conflicts:

If an OR is sent to a non-competent authority, it may be transferred to the appropriate one.

The ECCAIRS2 Taxonomy is a standardized classification system that defines the structure and encoding of data fields in aviation occurrence reports. It serves as the official reference for ECCAIRS2, ensuring uniformity in occurrence reporting and coding. By providing a clear framework for data collection, the taxonomy enhances interoperability, supports safety analysis, and promotes regulatory compliance. Publicly available, it enables consistent and reliable reporting across the aviation industry.

The following sections describe all the functionalities and tasks that Occurrence Officers can perform using the E2 Web Application. They can only access information—such as reports, queries, and views—that is owned by their respective Authority.

Occurrence Officers can find essential information in the following sections:

• Safety Data – outlines all tools for managing reports.
• Data Management – includes Queries to filter and export reports (OR, VR, OC), plus Word Templates.
• Taxonomy Browser – helps locate entities and attributes with clear definitions.
• Other Features – offer additional support for workflow tasks.