---
title: "ANNEX I — LIST OF REQUIREMENTS APPLICABLE TO THE MANDATORY AND VOLUNTARY OCCURRENCE REPORTING SCHEMES — Regulation (EU) No 376/2014, Occurrence Reporting · Avioverse"
description: "Note: The data fields must be completed with the information requested."
url: "https://avioverse.aero/regulations/easa/occurrence-reporting/regulation-eu-no-376-2014/annexes/annex-i-list-of-requirements-applicable-to-the-mandatory-and-voluntary"
---

# ANNEX I — LIST OF REQUIREMENTS APPLICABLE TO THE MANDATORY AND VOLUNTARY OCCURRENCE REPORTING SCHEMES

Regulation (EU) No 376/2014 · Regulation (EU) No 376/2014 · EAR revision 27 Sep 2023

IR Implementing rule

## ANNEX I — LIST OF REQUIREMENTS APPLICABLE TO THE MANDATORY AND VOLUNTARY OCCURRENCE REPORTING SCHEMES

Note: The data fields must be completed with the information requested. If it is not possible for the competent authorities of the Member States or the Agency to include that information because it has not been provided by the [organisation](https://avioverse.aero/glossary/easa/organisation) or the [reporter](https://avioverse.aero/glossary/easa/reporter), the data field may be completed with the value ‘unknown’. However, with a view to ensuring that the appropriate information is transmitted, use of that ‘unknown’ value should, to the best extent possible, be avoided, and the report should, where possible, be completed with the information later.

1\. COMMON MANDATORY DATA FIELDS

When entering, in their respective databases, information on every [occurrence](https://avioverse.aero/glossary/easa/occurrence) mandatorily reported and, to the best extent possible, every occurrence voluntarily reported, organisations, Member States and the Agency must ensure that occurrence reports recorded in their databases contain at least the following information:

(1) Headline

Headline

(2) Filing Information

Responsible Entity

File Number

Occurrence Status

(3) When

UTC Date

(4) Where

State/Area of Occurrence

Location of Occurrence

(5) Classification

Occurrence Class

Occurrence Category

(6) Narrative

Narrative Language

Narrative

(7) Events

Event Type

(8) Risk classification

2\. SPECIFIC MANDATORY DATA FIELDS

2.1. [Aircraft](https://avioverse.aero/glossary/easa/aircraft)-related data fields

When entering, in their respective databases, information on every occurrence mandatorily reported and, to the best extent possible, every occurrence voluntarily reported, organisations, Member States and the Agency must ensure that occurrence reports recorded in their databases contain at least the following information:

(1) Aircraft Identification

State of Registry

Make/Model/Series

Aircraft serial number

Aircraft Registration

Call sign

(2) Aircraft Operation

Operator

Type of operation

(3) Aircraft Description

Aircraft Category

Propulsion Type

Mass Group

(4) History of Flight

Last Departure Point

Planned Destination

Flight Phase

(5) Weather

Weather relevant

2.2. Data fields relating to air navigation services

When entering, in their respective databases, information on every occurrence mandatorily reported and, to the best extent possible, every occurrence voluntarily reported, organisations, Member States and the Agency must ensure that occurrence reports recorded in their databases contain at least the following information:

(1) [ATM](https://avioverse.aero/glossary/easa/atm) relation

ATM contribution

Service affected (effect on ATM service)

(2) ATS Unit Name

2.2.1. Separation Minima Infringement/Loss of Separation and Airspace Infringementrelated data fields When entering, in their respective databases, information on every occurrence mandatorily reported and, to the best extent possible, every occurrence voluntarily reported, organisations, Member States and the Agency must ensure that occurrence reports recorded in their databases contain at least the following information:

(1) Airspace

Airspace type

Airspace class

FIR/UIR name

2.3. Aerodrome-related data fields

When entering, in their respective databases, information on every occurrence mandatorily reported and, to the best extent possible, every occurrence voluntarily reported, organisations, Member States and the Agency must ensure that occurrence reports recorded in their databases contain at least the following information:

(1) Location Indicator (ICAO indicator of the airport)

(2) Location on the aerodrome

2.4. Aircraft damage or personal injury-related data fields

When entering, in their respective databases, information on every occurrence mandatorily reported and, to the best extent possible, every occurrence voluntarily reported, organisations, Member States and the Agency must ensure that occurrence reports recorded in their databases contain at least the following information:

(1) Severity

Highest Damage

Injury Level

(2) Injuries to persons

Number of injuries on ground (fatal, serious, minor)

Number of injuries on aircraft (fatal, serious, minor)

IR — Regulation (EU) No 376/2014 · Occurrence Reporting Easy Access Rules · EAR revision 27 Sep 2023

[All rules in ANNEXES](https://avioverse.aero/regulations/easa/occurrence-reporting/regulation-eu-no-376-2014/annexes)

Consolidated from the EASA Easy Access Rules (revision 27 Sep 2023, extracted 13 Oct 2026) for convenience. Not the official publication — verify against the Official Journal of the European Union and the EASA publications before operational use.