The Agency adopts and implements this proactive and evidence-based approach with an Internal Occurrence Reporting System (IORS), for the traceability of reported occurrences and of individual follow-up decisions and corrective actions, where applicable.
Rachel Daeschler, Head of Safety Intelligence and Performance Department at EASA, explains how this system works.
What does IORS mean in practice? How does the IORS database work?
IORS is the set of tools and procedures through which the Agency manages information coming from aviation safety occurrences which are reported to it.
The IORS database is the repository where you will find all occurrence data reported to EASA, including information on follow-up actions, such as risk assessment, corrective action related information, reference to published EASA safety publication (Airworthiness Directive, Safety Information Bulletin). The IORS database started in February 2012.
How did it work before? What are the differences with the previous system?
Before IORS, each Project Certification Manager (PCM) received directly from the relevant Design Approval Holder (of an aircraft, engine, propeller, equipment etc.) occurrence data of interest to that particular PCM. In addition, the Agency also received voluntary occurrence reports from a wide range of entities (i.e., airlines, national aviation authorities) as well as further mandatory reports from non-EU maintenance organisations that have to report to EASA under their EASA Part-145 approval.
The data was not centralised. Its storage in the Agency was dependent upon individual filing solutions. At that time, we were the only aviation authority in Europe who did not yet have an established occurrence reporting system with a centralised database.
What does EASA expect from this mechanism?
IORS is necessary to ensure proper traceability of incoming occurrence data and also proper traceability of the decisions that were taken by the Agency in response to this safety-relevant information. Furthermore, as time goes on, the IORS database becomes an increasingly interesting source of information for safety analysis purposes, especially when looking for global safety issues related to design or technical issues. In this area, we still need to further progress to allow the data to be used to its full potential.
Who has to report an occurrence to EASA? And how?
In principle, those organisations for which EASA is the competent authority will have to report safety-related occurrences to us. This includes all European design approval holders (aircraft, engine, propeller type certificate holders, equipment design approval holders, Supplemental Type Certificate holders), production organisations, foreign maintenance or production organisations having a EU approval (unless covered under bilateral agreement).
Furthermore, in Europe there are principles for the exchange of safety information between national aviation authorities (NAAs)and EASA. This leads NAAs to report occasionally to EASA, especially on design-related issues, for which NAAs believe there might an (unattended) potential unsafe condition.
What are the next steps concerning this reporting mechanism?
The next steps particularly include the implementation of EU Regulation 376/2014 on the reporting of occurrences, their follow-up and analysis. We are already compliant with this regulation to a large extent. But we will have to refine some of our processes and tools, to implement a systematic risk classification scheme, and we will have to transfer regularly IORS data to the European Central Repository of occurrences, in the same way as all other NAAs already do.
But the most significant next steps lie in the internal improvements that we need to bring to IORS: collective review of occurrences for which we decide no follow-up is needed (“screening”), providing better feedback to the reporters, starting to perform safety analysis of larger amounts of occurrence data, i.e. going beyond the processing of individual occurrence data. After more than 3 years of accumulation of data, such an extension of our analysis work can be envisaged.
More information under: http://easa.europa.eu/easa-and-you/aviation-domain/safety-management/occurrence-reporting/iors-internal-occurrence-reporting-system