The Master Guide to Aviation Occurrence Reporting

The Master Guide to Aviation Occurrence Reporting serves as an operational blueprint designed to translate complex regulatory frameworks into clear, real-world data pipelines. By standardizing technical triggers across flight, maintenance, and ground operations, this guide eliminates ambiguity regarding what constitutes a reportable event. Ultimately, it establishes a systematic methodology for capturing low-consequence hazards before they escalate into catastrophic accidents.

1. Core Definitions & International Standards

1.1 Taxonomy of Aviation Events

The classification of an aviation event determines its legal tracking, investigation depth, and the regulatory resources assigned to it. International aviation authorities standardize these definitions to ensure global data alignment.

According to ICAO Annex 13, the timeline for an operational event is defined by the temporal boundary: from the moment any person boards the aircraft with the intention of flight until all such persons have disembarked.

• Occurrence: Any safety-related event that endangers or which, if not corrected or addressed, could endanger an aircraft, its occupants, or any other person. This definition sets the baseline for what must be reported.
• Accident: An occurrence associated with the operation of an aircraft where a person is fatally or seriously injured, the aircraft sustains substantial structural damage or failure, or the aircraft is missing or completely inaccessible.
• Incident: An occurrence, other than an accident, associated with the operation of an aircraft which affects or could affect the safety of operation.
• Serious Incident: An incident involving circumstances indicating that there was a high probability of an accident. The difference between an accident and a serious incident lies solely in the result (e.g., a near-miss vs. an actual collision).

Authority-Specific Variations

While ICAO provides the baseline framework, regional national aviation authorities (NAAs) enforce specific statutory definitions:

1.2 Purpose and Objectives of Reporting

The primary objective of occurrence reporting is the prevention of accidents and incidents, not to attribute blame or liability. Data collected through these channels transitions through three processing methodologies defined in ICAO Doc 9859 (Safety Management Manual): Reactive, Proactive, and Predictive.

The SMS and State Safety Programme (SSP) Integration

Occurrence reporting drives the safety data pipeline at both the corporate and state levels:

1. Safety Risk Management (SRM): Hazard identification begins when an occurrence report is filed. The report serves as the initial data point that triggers formal hazard logging, risk analysis, and risk assessment.
2. Safety Assurance (SA): Aggregated occurrence data acts as a safety performance monitor. Organizations track the frequency and severity of specific occurrences to verify if active safety risk controls are working.
3. State-Level SSP Integration: Corporate occurrence data does not remain isolated. These metrics flow upward to the National Aviation Authority to populate the State Safety Programme (SSP). This data aggregate allows the State to continuously monitor its Acceptable Level of Safety Performance (ALoSP) across the entire national airspace ecosystem.

Separation of Safety and Discipline

To maintain data integrity, aviation legal frameworks establish a regulatory wall between safety tracking and punitive corporate actions. Under EASA Reg 376/2014 and FAA Part 193, information derived from voluntary and mandatory reporting systems cannot be used in disciplinary, civil, or administrative proceedings unless gross negligence or willful misconduct is proven.

2. Legislative & Regulatory Frameworks

2.1 Regional Regulatory Mandates

Aviation occurrence reporting is governed by a tiered legal architecture. ICAO provides global standards, while regional NAAs enact statutory laws to enforce data collection within their respective jurisdictions.

• ICAO Annex 19 (Safety Management): Establishes the global mandate for States to implement an SSP and require aviation service providers to execute a Safety Management System (SMS). It establishes the standard for both mandatory and voluntary safety data collection and processing systems (SDCPS).
• FAA (United States) – 14 CFR Part 193: Governs the protection of voluntarily submitted safety information, ensuring specific data cannot be used for enforcement actions.
• EASA (Europe) – Regulation (EU) No 376/2014 & 2015/1018: Regulation 376/2014 dictates the mandatory reporting, analysis, and systematic follow-up of civil aviation occurrences. It is paired directly with Implementing Regulation (EU) No 2015/1018, which provides the exhaustive, legally binding classification list of every operational and technical anomaly that triggers a mandatory report.
• DGCA (India) – Civil Aviation Requirements (CAR): Enforced via CAR Section 5, Series C, Part I (Notification of Incidents) and CAR Section 1, Series C, Part I (SMS implementation).

2.2 Scope of Mandated Reporters (Who Must File)

The obligation to report safety occurrences is explicitly listed across operational, technical, and ground domains (e.g., Article 4 of EASA Reg 376/2014):

• Operational Personnel: Flight crews, cabin crews, and Air Traffic Controllers (ATCOs) identifying flight-path deviations, system failures, emergency evacuations, or separation infringements.
• Technical & Airworthiness Personnel: Licensed Aircraft Maintenance Engineers (AMEs/Part 145) signing a Certificate of Release to Service (CRS), and Continuing Airworthiness Managers (CAMO) tracking fleet defects.
• Ground & Design Personnel: Aerodrome operators, Ground Handling Agents (GHAs) managing fueling or weight/balance, and Design/Production representatives (Part 21/CAR 21).

2.3 Regulatory Reporting Timelines & Portals

Global tracking mechanisms require distinct submission windows based on severity and reporting program types:

Submissions utilize specific authority nodes: EASA via the European Corporate Portal (aviationreporting.eu), FAA via the Service Difficulty Reporting System (SDRS) or Web-Based Analytical Technology (WBAT), and DGCA via the eGCA portal.

3. Reporting Mechanics & System Typologies

3.1 Mandatory Occurrence Reporting (MOR) Manual Integration

To ensure seamless cross-departmental coordination, regulatory reporting workflows must be explicitly formalized across three core operational manuals:

• Flight Safety Manual: Defines flight crew reporting thresholds and cockpit data protocols.
• SMS Manual: Outlines internal triage, risk-scoring, and hazard-logging managed by the safety/quality department.
• Airport Emergency Plan: Coordinates ground-handling, aerodrome-service, and emergency response criteria.

3.2 Technical & Operational Triggers (Exhaustive Checklist)

The following events constitute mandatory reportable occurrences across their respective technical and operational domains:

Aircraft Technical & Structural Thresholds

• Structural Integrity: Damage to a Principal Structural Element (PSE) not qualified as damage-tolerant (life-limited elements); structural defects exceeding allowable limits that reduce structural stiffness or compromise aeroelastic characteristics; structural defects risking the liberation of items of mass or jeopardizing systems; any in-flight structural detachment.
• System Controllability & Redundancy: Loss or significant malfunction of any system/sub-system when Standard Operating Procedures (SOPs) cannot be accomplished; uncommanded actions or complete loss of system control; failure of associated protection devices/emergency systems; total loss of system redundancy.
• Air Conditioning & Pressurization: Complete loss of avionics cooling hardware; cabin depressurization events.
• Auto-Flight Systems: Failure of the auto-flight system to execute intended operations while engaged; control difficulties linked to auto-flight functioning; failure of any auto-flight disconnect device; uncommanded mode changes.
• Communications: Passenger address system failure resulting in total loss or inaudible cabin transmission; total loss of communication in flight.
• Electrical Systems: Loss of one electrical distribution system (AC/DC); total loss or loss of more than one electrical generation system; failure of backup or emergency electrical generating hardware.
• Cockpit, Cabin, & Cargo: Pilot seat control mechanism loss during flight; failure of emergency systems (evacuation signaling, exit doors, emergency lighting); loss of cargo loading system retention capability.
• Fire Protection: Any fire or smoke warning (excluding immediate false positives); undetected failure or defect of detection/protection systems; absence of warning during an actual fire or smoke event.
• Flight Controls: Asymmetry of high-lift devices (flaps, slats, spoilers); movement limitation, stiffness, or delayed response in primary flight controls; control surface runaway or vibration; mechanical disconnection or failure.
• Fuel Systems: Fuel Quantity Indicating System (FQIS) malfunction causing total loss or erroneous onboard fuel indications; fuel leakage causing significant loss, fire hazards, or contamination; fuel jettison system malfunctions; inability to transfer or utilize total usable fuel.
• Hydraulics: Complete loss of a hydraulic system; significant fluid leakage; loss of more than one hydraulic circuit; backup system failure; inadvertent Ram Air Turbine (RAT) extension.
• Ice Detection & Protection: Undetected loss or reduced performance of anti-ice/de-ice systems; loss of more than one probe heating system; inability to obtain symmetrical wing de-icing; abnormal ice accumulation degrading performance; crew vision significantly obstructed.
• Indicating & Recording Systems: System malfunctions presenting misleading indications; loss or malfunction of more than one display unit or display/warning computer function within a glass cockpit environment.
• Landing Gear, Wheels, & Brakes: Brake fire events; significant loss of braking action; unsymmetrical braking; failure of the landing gear free-fall extension system; unwanted gear or door extension/retraction; tyre burst events.
• Oxygen Systems: Total loss of cockpit oxygen supply in pressurized aircraft; loss of oxygen supply to more than 10% of passengers.
• Bleed Air Systems: Hot bleed air leaks causing fire warnings or structural damage; loss of all bleed air systems; failure of leak detection loops.

Propulsion & Powerplant Anomalies

• Engine Operations: In-flight flameout, shutdown, or speed control malfunction; overspeed or inability to control any high-speed rotating component; non-containment of debris; uncontrolled internal/external fire; thrust vectors deviating from pilot demand.
• Thrust & Power Control: Thrust reversing systems failing to operate or operating inadvertently; inability to control power, thrust, or RPM; engine mount structure failure; partial or complete powerplant separation; dense visible fumes or toxic products causing crew/passenger incapacitation; inability to execute a normal engine shutdown or restart.
• Life-Limited Components: Any technical defect in a life-controlled part forcing its operational retirement before completing its certified full lifecycle; engine parameter exceedances; Foreign Object Debris (FOD) ingestion causing structural or internal damage.
• Propellers & Assemblies: Propeller overspeed or excessive drag generation; thrust in the opposite direction to pilot command; release of a propeller or major portion; severe balance failures; unintended blade movement below minimum in-flight low-pitch limits; inability to feather or command a pitch change.
• Rotary-Wing Specifications: Damage or defect of the main rotor gearbox/attachment resulting in in-flight separation or control malfunctions; damage to tail rotor, transmission, and equivalent drive systems.
• Auxiliary Power Units (APUs): Shutdown or failure when the APU is required by operational regulations (e.g., ETOPS); inability to execute an APU shutdown; APU overspeed or start failure when operationally required.

The Pushback Boundary Condition: Technical anomalies occurring during pushback (before taxiing under own power) are excluded from mandatory regulatory reporting and managed via internal MEL dispatch logic—unless the defect introduces an immediate safety hazard (e.g., brake failure or uncontained fire)

Aircraft Flight Operations & Air Navigation

• Operational Control: Risk of collision with aircraft, terrain, or obstacles where avoidance maneuvers are required; take-off/landing incidents (under-shooting, overrunning, running off side); landings or rejections on closed, occupied, or incorrect runways; runway incursions.
• Flight Envelope Violations: Inability to achieve predicted performance during take-off/climb; critically low fuel or fuel imbalance exceedances; partial or temporary loss of control ($LOC-I$); occurrences close to or above $V_1$ forcing a rejected take-off ($RTO$), tail strike, or power loss.
• Navigation & Guidance: Unintentional significant deviations from airspeed, track, or altitude; descent below decision height/altitude without required visual references; loss of situational or position awareness; incorrect receipt/interpretation of radiotelephony ($RT$) messages.
• System Interactions: Breakdown in communication between flight crew, cabin crew, ATC, or engineering; abnormal runway contact or unpaved surface departures; ground collisions; inadvertent or incorrect control operations; configuration failures; abnormal vibration profiles; primary warning activations (stall/stick-shaker, configuration, overspeed); GPWS/EGPWS warnings; ACAS/TCAS Resolution Advisories ($RAs$); jet or prop blast causing damage or serious injury.
• Incapacitation: Medical incapacitation of any flight crew member, or cabin crew member rendering them unable to execute essential emergency duties.
• Meteorological Events: Lightning or hail strikes causing aircraft damage or loss of essential services; severe turbulence causing occupant injury or requiring a technical turbulence check; windshear encounters; icing encounters causing handling difficulties.

Maintenance, Repair, & Ground Support

• Maintenance Execution: Incorrect assembly of components discovered during inspection or test; use of misleading, incorrect, or insufficient maintenance data/procedures.
• Structural Deterioration: Fractures, cracks, corrosion, delamination, or disbonding requiring major repairs or component replacement within primary structures/PSEs; secondary structural damage endangers the aircraft.
• Material Integrity: Introduction of products, parts, appliances, or materials of unknown or suspect origin (Unapproved Parts / SUPs).
• Air Navigation Services ($ANS$): Provision of incorrect, inadequate, or misleading ground info (ATC, ATIS, databases, charts); provision of less than prescribed terrain clearance; incorrect pressure reference data ($QNH$ altimeter settings); separation minima infringements; unauthorized airspace penetration; unlawful radio communication transmissions; significant CNS facility degradation.
• Aerodrome Operations: Movement areas obstructed by aircraft, vehicles, animals, or FOD causing hazardous conditions; airfield marking errors; airfield lighting system failures or unavailability.
• Ground Handling Services: Significant fuel spillage during servicing; loading incorrect fuel quantities affecting endurance/balance; unsatisfactory ground de-icing/anti-icing application; loading contaminated or incorrect fuel/fluid types (including oxygen and potable water); ground equipment defects causing hazardous aircraft servicing conditions; baggage/cargo mass/balance loading errors; incorrect or inadequate cargo/container stowage impeding emergency evacuations; dangerous goods incidents.

3.3 Voluntary & Confidential Reporting Systems

Voluntary Occurrence Reporting (VOR) captures lower-consequence hazards, human slips, and latent conditions (procedural errors, ergonomics, or fatigue) not caught by mandatory frameworks. Third-party systems—such as NASA’s Aviation Safety Reporting System (ASRS) under FAA AC 00-46—ensure safety data collection by striping personal identifiers and providing administrative immunity from civil penalties or certificate actions, provided submissions occur within the strict 10-day window following an inadvertent violation.

4. Data Standards, Taxonomies, & Software

4.1 Standardized Safety Data Coding

To execute global risk analysis, raw narratives from frontline reports are coded using standardized data taxonomies:

• ICAO ADREP Taxonomy: Establishes the structural hierarchy of Attributes and Descriptors ensuring global database interoperability.
• CICTT Categories: Maintained by the CAST/ICAO Common Taxonomy Team, these codes standardize occurrence labels:
  • LOC-I: Loss of Control – Inflight (unintentional aerodynamic or flight path deviations).
  • RE: Runway Excursion (veering off or overrunning a runway surface).
  • RI: Runway Incursion (incorrect presence of an asset on a active runway).
  • RAMP: Ground Handling anomalies (servicing, loading, or towing incidents).
  • CFIT: Controlled Flight Into Terrain (collision with terrain while under crew control).

4.2 ECCAIRS 2 Ecosystem

The European Coordination Centre for Accident and Incident Reporting Systems (ECCAIRS 2) is the digital platform implemented to meet EASA Regulation (EU) No 376/2014 requirements. It aggregates regional metrics into the European Central Repository (ECR). The platform enforces a mandatory minimum data set before a file can be indexed: Temporal metadata (UTC), Spatial coordinates, Environmental parameters (VMC/IMC, light states), Operational profiles (flight phases, commercial types), and Aircraft Metrology (MTOM limits, engine cycles).

5. Risk Classification & Analytical Processing

5.1 Risk Scoring Methodologies

The Industry Shift from Subjective Probability to Objective Barrier Math

Historically, aviation safety relied on legacy $5 \times 5$ matrices (as defined in ICAO Doc 9859) to cross-reference Safety Risk Probability against Safety Risk Severity. However, estimating the qualitative probability of a rare, complex systemic failure introduces high levels of analyst subjectivity. To eliminate this variation, the modern aviation infrastructure is shifting toward objective, barrier-state mathematical models. Rather than guessing how often an event might occur, these advanced frameworks measure the exact performance status of defense barriers remaining during the event.

The European Risk Classification Scheme (ERCS) Architecture

For EASA member states, Regulation (EU) No 376/2014 mandated the creation of the ERCS. The precise scoring parameters and logical flow of this framework are formally established by Commission Delegated Regulation (EU) 2020/2034 and executed via Commission Implementing Regulation (EU) 2021/2082.

The scheme calculates risk through a strict two-axis grid:

1. Axis 1 (Worst Likely Accident Outcome): Scores the ultimate severity of the potential accident scenario had all remaining defenses failed, categorized strictly by aircraft mass, passenger capacity, and potential loss of life.
2. Axis 2 (Probability of the Potential Outcome / Maturity of Barriers): Evaluates the remaining system safety defenses. Barriers are graded mathematically as Effective (performed as designed), Degraded (reduced performance margin), Failed (failed to protect), or Not Present.

The intersection of Axis 1 and Axis 2 outputs a standardized two-digit alphanumeric code (e.g., A3, E1) directly into the European Central Repository (ECR) to prioritize automated regulatory indexing.

5.2 Root Cause Analysis (RCA) Frameworks

• HFACS (Human Factors Analysis and Classification System): Maps human error across four operational layers: Unsafe Acts (direct pilot/engineer errors), Preconditions for Unsafe Acts (environmental/fatigue factors), Unsafe Supervision (scheduling or oversight failures), and Organizational Influences (corporate policies or manual design defects).
• The Bow-Tie Model: Places the central safety event (e.g., an uncommanded inflight thrust loss) between its proactive causes/preventative barriers (such as maintenance borescope checks) and its reactive mitigation barriers/consequences (such as auto-feathering systems and emergency checklist executions).

6. Just Culture & Legal Safeguards

6.1 Objective Just Culture Assessment

A Just Culture framework establishes an objective process to distinguish acceptable human error from unacceptable behavior. Under international guidelines, it explicitly separates protected errors (slips, lapses, honest cognitive overloads) from unprotected actions (willful sabotage, gross negligence, substance abuse). Organizations utilize James Reason’s Substitution Test (“Would a peer with identical training and experience make the same decision under the same latent conditions?”) to isolate systemic defects from individual culpability.

The Source Protection Framework: EASA Article 16

While standard literature often confuses data access with source protections, the statutory firewall between safety reporting and judicial prosecutorial discovery within EASA member states is explicitly mandated by Article 16 of Regulation (EU) No 376/2014 (Protection of the information source).

Article 16 establishes that the identities of the reporter and any persons mentioned in the occurrence log are strictly confidential and legally protected. National aviation authorities are prohibited from releasing these data records to judicial bodies for criminal or civil liability proceedings unless an exceptional threshold is met under Article 16(10)—specifically, when an independent investigation proves an intentional, reckless, or criminally negligent disregard for safety.

6.2 Data Cleansing Mechanics

Before safety data can be shared externally, it undergoes rigorous de-identification to strip away personal identifiers via automated and manual workflows:

• Identity Stripping: Complete removal of human identifiers (names, license digits, crew codes).
• Asset Masking: Swapping tail registration tracking values (e.g., N101AA) with broad metadata classifications (Boeing 737-800).
• Spatial/Temporal Blurring: Generalizing exact timestamps and locations into block hours and flight phases.
• Narrative Sanitization: Processing free-text entries through natural language processing (NLP) algorithms to erase contextual naming variables.

This ensures that technical lessons—such as flap asymmetries or hydraulic leaks—are retained for industry analysis without exposing individual professionals to liability.

7. Closing the Safety Loop & Predictive Modeling

7.1 Safety Performance Indicators (SPIs)

Organizations aggregate individual occurrence reports to establish baseline safety metrics, transforming raw metrics into Safety Performance Indicators (SPIs) and Safety Performance Targets (SPTs) normalized against an operational denominator (e.g., flight hours or cycles). Closing the safety loop requires dispersing analyzed data back to frontline operators via Safety Flashes, Maintenance Memo revisions, or FCOM/AMM updates.

7.2 Data Fusion and Macro Safety Analytics

To validate subjective human reports, safety departments utilize Data Fusion, cross-referencing narrative databases with automated operational programs: Flight Data Monitoring (FDM/FOQA) and Line Operations Safety Audits (LOSA).

The Global Safety Data Pipeline: IATA IDX

While state-level platforms capture mandatory regulatory data, the primary mechanism for international airline benchmarking is IATA’s Incident Data Exchange (IDX). IDX operates as a massive, multi-carrier safety data pipeline. Participating airlines contribute their cleaned, de-identified voluntary and mandatory occurrence reports into this global repository. This enables safety analysts to perform macro-level trend forecasting and benchmark internal fleet performance against global operational baselines.

The Safety Action Loop: ADs and Alert Service Bulletins

When aggregated occurrence reporting networks expose a critical, recurring technical risk, the safety workflow escalates from data monitoring to mandatory mechanical rectification:

1. Alert Service Bulletins (ASBs): The Original Equipment Manufacturer (OEM) tracks technical occurrence reports. If a specific structural or system threshold is breached, the OEM issues an ASB detailing immediate inspection, limitation, or modification procedures.
2. Airworthiness Directives (ADs): If the defect compromises the aircraft’s type certification or represents an immediate safety-of-flight hazard, the State of Design regulatory authority (e.g., the FAA for Boeing, EASA for Airbus) issues an Emergency Airworthiness Directive (EAD) or standard AD. This legal mandate makes the execution of the ASB compulsory; failure to comply grounds the aircraft.

Data fusion ensures that a minor telemetry anomaly flagged by an FDM algorithm automatically cross-references human input before a systemic component failure triggers an emergency airworthiness directive.

8. Technical Appendix: Statutory References