2.1 Occurrence Reporting under Regulation (EU) No 376/2014

2.1 Occurrence Reporting under Regulation (EU) No 376/2014

Core Principle: The sole objective of occurrence reporting under European Union law is the prevention of accidents and incidents, without the attribution of blame or liability. Safety analysis relies on an uninhibited, confidential flow of operational and technical data from frontline technicians to civil aviation authorities.

Civil aviation safety has achieved its historic reliability by systematically learning from precursors, incidents, and maintenance anomalies before they manifest as catastrophic accidents. Within the European regulatory domain, this proactive approach is codified under Regulation (EU) No 376/2014 of the European Parliament and of the Council. For licensed aircraft maintenance engineers (Part-66), understanding occurrence reporting is not merely an administrative exercise—it is a personal, statutory duty with direct airworthiness and legal implications.

---

Legislative Framework and Purpose of Regulation (EU) No 376/2014

Regulation (EU) No 376/2014 governs the reporting, analysis, and follow-up of occurrences in civil aviation. It repealed earlier fragmented legislation (Directive 2003/42/EC and Commission Regulations (EC) No 1321/2007 and (EC) No 1330/2007) to establish a uniform, pan-European occurrence reporting regime. It operates directly alongside the EASA Basic Regulation (EU) 2018/1139, which sets the overarching airworthiness standards for all European aviation activities.

Primary Objectives of the Regulation

1. Accident Prevention: Ensure that safety-critical occurrences are collected, evaluated, and analyzed to detect emerging hazards across the European fleet.
2. Non-Punitive Safety Culture: Guarantee statutory protection to reporters through "Just Culture" principles, preventing reports from being weaponized in disciplinary or judicial proceedings.
3. Fleet-Wide Information Sharing: Centralize safety records into a common database—the European Central Repository (ECR)—accessible by National Aviation Authorities (NAAs) and the European Union Aviation Safety Agency (EASA).
4. Closing the Safety Loop: Mandate that organisations and Member States do not merely collect data, but actively implement corrective actions within defined statutory deadlines.

To ensure consistent implementation across all Member States, the European Commission enacted Commission Implementing Regulation (EU) 2015/1018, which provides an exhaustive, standardized classification of occurrences that must be mandatorily reported across various aviation domains.

---

Mandatory Occurrence Reporting (MOR) vs. Voluntary Occurrence Reporting (VOR)

Regulation (EU) No 376/2014 establishes two complementary reporting streams: Mandatory Occurrence Reporting (MOR) and Voluntary Occurrence Reporting (VOR).

+-----------------------------------------------------------------------------+
|                   REGULATION (EU) No 376/2014 FRAMEWORK                     |
+---------------------------------------+-------------------------------------+
|   Mandatory Occurrence Reporting (MOR) |  Voluntary Occurrence Reporting (VOR)|
|             (Article 4)               |             (Article 5)             |
+---------------------------------------+-------------------------------------+
| • Legally required events             | • Events perceived as safety hazards |
| • Listed in Reg (EU) 2015/1018        | • Latent conditions & near-misses   |
| • Strict 72-hour reporting window     | • No formal statutory classification|
| • Defined list of mandated reporters  | • Open to all aviation personnel    |
| • Statutory investigation & follow-up | • Equal Just Culture protections    |
+---------------------------------------+-------------------------------------+

Mandatory Occurrence Reporting (Article 4)

MOR applies to events that pose a significant risk to aviation safety. Article 4(6) lists the specific categories of natural persons mandated to report, which explicitly includes:

• The pilot-in-command or commander of an aircraft;
• Any person involved in the design, manufacture, continuing airworthiness management, or maintenance of an aircraft, its equipment, or parts;
• Any person who signs an airworthiness review certificate (ARC) or a certificate of release to service (CRS) for an aircraft or component;
• Air traffic controllers and flight information service officers;
• Aerodrome managers and ground-handling service personnel.

For certifying staff (Part-66 B1, B2, B3, C, and L licence holders), signing a CRS while ignoring a reportable technical defect constitutes a severe regulatory violation under both Part-145 (145.A.60) and Regulation 376/2014.

Voluntary Occurrence Reporting (Article 5)

VOR systems capture safety-related anomalies, hazards, or near-misses that fall outside the mandatory criteria of Regulation (EU) 2015/1018, but are perceived by the reporter as an actual or potential hazard. Examples include:

• Awkward ergonomic access leading to difficulty verifying split-pin installation;
• Ambiguous or poorly phrased instructions in an Aircraft Maintenance Manual (AMM);
• Hangar lighting deficiencies that increase the risk of foreign object debris (FOD) oversight;
• Near-miss tool misplacement identified and corrected prior to aircraft departure.

Crucially, Article 5 mandates that every organisation and competent authority establish a VOR scheme, and that voluntary reports receive the exact same confidentiality and Just Culture legal protections as mandatory reports.

---

Reportable Maintenance Occurrences: Regulation (EU) 2015/1018 Annex II

Annex II of Commission Implementing Regulation (EU) 2015/1018 establishes the exhaustive list of reportable occurrences related to technical conditions, maintenance, and continuing airworthiness. Licensed aircraft maintenance personnel must be thoroughly familiar with these categories:

1. Structural and Airframe Integrity

• Cracking, permanent deformation, or structural failure exceeding allowable limits defined in the Structural Repair Manual (SRM);
• Severe corrosion penetrating primary structure or exceeding allowable structural rework limits;
• Failure, disconnection, or severe degradation of primary structural joints, fittings, or engine pylon attachments.

2. Flight Controls and Primary Systems

• Disconnection, reversal, binding, severe friction, or runaway of primary and secondary flight control systems (elevators, ailerons, rudders, stabilizer trim, flaps, slats, spoilers);
• Complete loss of multiple independent hydraulic circuits or electrical generation buses;
• Total failure of primary flight instruments or pitot-static systems.

3. Propulsion and Powerplant Systems

• Uncontained engine failure (turbine rotor burst, blade shedding through the casing);
• In-flight shut-down (IFSD) of any turbine engine, or uncommanded thrust variation / engine runaway;
• Inability to feather a propeller or control engine thrust reverser deployment;
• Loss of fuel system cross-feed capability, major fuel leaks posing fire hazards, or severe fuel contamination (water, biological fungal growth, particulate, or incorrect fuel grade).

4. Maintenance Process Errors and Unapproved Parts

• False Release to Service: The issuance of a Certificate of Release to Service (CRS) for an aircraft or component known or suspected to be non-airworthy, or where mandatory maintenance tasks were not completed;
• Critical maintenance tasks performed incorrectly without required independent dual inspection;
• Installation of Suspected Unapproved Parts (SUP), counterfeit hardware, or parts lacking valid documentation (such as a forged or missing EASA Form 1);
• Structural assembly errors resulting in system fouling, chafing, or control surface binding.

5. Electrical Wiring Interconnect Systems (EWIS)

• Significant chafing, arcing, overheating, or insulation degradation in electrical wiring harnesses, particularly in high-risk zones (fuel tank vapor areas, landing gear wells, or engine nacelles).

---

Statutory Reporting Timelines: The 72-Hour Rule

Regulation (EU) No 376/2014 imposes strict, harmonized statutory timelines to ensure that technical safety threats are communicated without delay.

+-----------------------------------------------------------------------------+
|                     72-HOUR STATUTORY REPORTING TIMELINE                    |
+-----------------------------------------------------------------------------+

   T = 0                      T <= 72 HOURS                     30 DAYS / 3 MONTHS
   Awareness of Event         Initial Occurrence Notification   Prelim / Final Analysis
   ------------------         -------------------------------   -------------
   • Defect discovered        • Reporter -> Internal / Org     • Causal analysis
   • Incident occurs          • Organisation -> NAA            • Root causes
   • Unairworthy status       • Organisation -> TC / STC       • Corrective plan
     identified                 Holder                           submitted to NAA
+-----------------------------------------------------------------------------+

The Initial 72-Hour Notification (Article 4(6) and 4(7))

• Individual Reporter to Organisation: The natural person must report the occurrence to their employer or approved organisation within 72 hours of becoming aware of it.
• Organisation to Authorities: The approved maintenance organisation (Part-145, Part-CAO) must submit the occurrence report to the competent National Aviation Authority (NAA) within 72 hours of becoming aware of the event.
• Mandatory OEM Notification: The organisation must simultaneously report the technical defect to the organisation responsible for the design of the aircraft or component—typically the Type Certificate (TC) holder or Supplemental Type Certificate (STC) holder—within 72 hours.

The 90-Day Analysis and Follow-Up (Article 13)

Occurrence reporting does not end with initial notification. Under Article 13 of Regulation 376/2014:

• The approved organisation must carry out an internal investigation into the causes of the occurrence;
• Within 30 days of the date the occurrence was notified by the reporter, the organisation must transmit to the competent authority the preliminary results of its analysis and any action it intends to take;
• The final results of the analysis must follow as soon as they are available and, in principle, no later than 3 months from the date of notification of the occurrence.

---

Information Flow: From Maintenance Floor to the European Central Repository (ECR)

Data collected under Regulation (EU) No 376/2014 follows a tightly regulated hierarchy designed to maintain data integrity, reporter confidentiality, and international compatibility.

1. Maintenance Floor: A certifying engineer discovers an unapproved bolt sheared inside an elevator control quadrant during a scheduled C-check. The engineer files an internal occurrence report.
2. Organisation Safety Review Board: The organisation's safety department assesses the event against Regulation (EU) 2015/1018. Confirming it as a mandatory reportable defect, they notify the NAA (e.g., LBA in Germany, DGAC in France, ENAC in Italy, or Austro Control in Austria) and the airframe TC holder within 72 hours.
3. National Aviation Authority Validation: The NAA reviews, validates, and classifies the occurrence using the standardized ECCAIRS (European Coordination Centre for Accident and Incident Reporting Systems) software platform and ICAO ADREP (Accident/Incident Data Reporting) taxonomy.
4. European Central Repository (ECR): Member States are legally required under Article 8 to upload all validated occurrence records to the ECR within 30 days of registration.
5. EASA Safety Analysis: The ECR is managed by the European Commission in close collaboration with EASA. EASA aggregates pan-European data to identify systemic fleet defects, update the European Plan for Aviation Safety (EPAS), or issue mandatory Airworthiness Directives (ADs).

---

Reporter Dis-identification and Statutory Confidentiality

Under Articles 6, 15, and 16 of Regulation (EU) No 376/2014, occurrence reporting systems are protected by strict statutory confidentiality rules designed to encourage reporting without fear of exposure:

• Dis-identification of Data: When an organisation forwards an occurrence report to the competent authority or TC holder, personal details (names, contact numbers, home addresses) of the reporter and any individuals mentioned must be removed.
• Central Repository Anonymity: Personal information must never be recorded in the European Central Repository (ECR). Only technical, operational, and environmental parameters necessary for safety analysis are retained.
• Exemption from Public Freedom of Information: Occurrence reports held by NAAs, EASA, and the European Commission are legally exempt from public freedom of information requests and cannot be made accessible to the press or general public.
• Protection Against Inappropriate Use: Regulators and judicial authorities are prohibited from using occurrence reports to attribute blame or liability, ensuring that the reporting system remains purely focused on safety improvement.

---

Comparison: MOR vs. VOR in an Approved Maintenance Organisation

---

Practical Maintenance Scenarios

Scenario 1: Wing Spar Exfoliation Corrosion

During a heavy maintenance C-check on an Airbus A320, a B1 certifying technician notices severe intergranular exfoliation corrosion on the lower wing spar fitting that exceeds the allowable rework limits of the Structural Repair Manual (SRM). Due to an imminent flight schedule, line management requests the technician to "blend it out and release the aircraft, then document the defect at the next A-check."

Regulatory Assessment:

1. Illegal Action: Releasing the aircraft under these conditions constitutes a false release to service under Part-145 (145.A.50) and a major safety violation.
2. Statutory Duty: The technician must refuse to sign the CRS until an approved engineering repair scheme is issued by the TC holder (Airbus) or an approved Part-21 Design Organisation (DOA).
3. Mandatory Reporting: Because the corrosion exceeds SRM allowable limits, it constitutes an MOR under Regulation (EU) 2015/1018 Annex II. The organisation must notify the competent NAA and Airbus within 72 hours.
4. Protection: The technician's refusal to issue a false CRS and their submission of an internal occurrence report are protected by law under Article 16 of Regulation 376/2014 against employer retaliation.

Scenario 2: Counterfeit Hydraulic Actuator Seal

During scheduled seal replacement on a Boeing 737 elevator PCU (Power Control Unit), a technician notices that the replacement O-rings from a newly received batch exhibit uneven flash ridges, lack proper batch cure-date packaging, and have an illegible EASA Form 1.

Regulatory Assessment:

1. Suspected Unapproved Part (SUP): The technician must immediately quarantine the component batch and submit an occurrence report.
2. Mandatory Reporting: Under Regulation (EU) 2015/1018 Annex II, the presence or installation of unapproved parts is a mandatory reportable occurrence.
3. Notification Pathway: The maintenance organisation must notify the competent NAA, the aircraft TC holder, and EASA within 72 hours so that an Airworthiness Directive or Safety Information Bulletin (SIB) can be evaluated to alert other operators.

---

EASA Part-66 Examination Tips & Regulatory Summary

• The 72-Hour Rule: Questions frequently test the reporting window. Remember that both the individual reporter and the approved organisation have 72 hours from the moment they become aware of the occurrence.
• Dual External Notification: Maintenance organisations must report mandatory technical defects to both the competent National Aviation Authority (NAA) and the organisation responsible for design (TC/STC holder).
• The 30-Day Rule: Member States have 30 days from initial registration to upload validated reports into the European Central Repository (ECR).
• The 30-Day / 3-Month Rule (Article 13(4)): Preliminary analysis results and intended actions go to the NAA within 30 days of notification; the final results follow in principle within 3 months.
• Exhaustive List: Remember that Regulation (EU) 2015/1018 contains the specific lists classifying occurrences—Annex II is dedicated to technical conditions and maintenance.