Skip to content

A gradual release of Avioverse begins in October 2026. Request early access →

ORA.GEN.160 Occurrence reporting

ANNEX VII (Part-ORA) · Regulation (EU) No 1178/2011 · EAR revision 25 Nov 2025

IRImplementing rule

ORA.GEN.160Occurrence reporting

(a)As part of its management system, the organisation shall establish and maintain an occurrencereporting system, including mandatory and voluntary reporting. For organisations having their principal place of business in a Member State, that system shall meet the requirements of Regulation (EU) No 376/2014 and Regulation (EU) 2018/1139 as well as the delegated and implementing acts adopted on the basis of those Regulations.

(b)The organisation shall report to the competent authority and, in case of aircraft not registered in a Member State, the State of Registry any safety-related event or condition that endangers or, if not corrected or addressed, could endanger an aircraft, its occupants or any other person, and in particular any accident or serious incident.

(c)Without prejudice to point (b), the organisation shall report to the competent authority and the design approval holder of the aircraft any incident, malfunction, technical defect, exceeding of technical limitations, occurrence that would highlight inaccurate, incomplete or ambiguous information, contained in data established in accordance with Regulation (EU) No 748/2012, or other irregular circumstance that has or may have endangered an aircraft, its occupants or any other person and has not resulted in an accident or serious incident.

(d)Without prejudice to Regulation (EU) No 376/2014 and the delegated and implementing acts adopted on the basis thereof, reports in accordance with point (c) shall:

(1)be made as soon as practicable, but in any case no later than 72 hours after the organisation has identified the event or condition to which the report relates unless exceptional circumstances prevent this;

(2)be made in a form and manner established by the competent authority, as defined in point ORA.GEN.105;

(3)contain all pertinent information about the condition known to the organisation.

(e)For organisations not having their principal place of business in a Member State:

(1)initial mandatory reports shall:

(i)appropriately safeguard the confidentiality of the identity of the reporter and of the persons mentioned in the report;

(ii)be made as soon as practicable, but in any case, no later than 72 hours after the organisation has become aware of the occurrence unless exceptional circumstances prevent this;

(iii)be made in a form and manner established by the Agency;

(iv)contain all pertinent information about the condition known to the organisation;

(2)where relevant, a follow-up report providing details of actions the organisation intends to take to prevent similar occurrences in the future shall be made as soon as those actions have been identified; those follow-up reports shall:

(i)be sent to relevant entities initially reported to in accordance with points (b) and (c);

(ii)be made in a form and manner established by the Agency.

IR · ORA.GEN.160 — Regulation (EU) No 1178/2011 · Regulation (EU) 2020/2193 · Aircrew Easy Access Rules · EAR revision 25 Nov 2025

AMCAcceptable means of compliance

AMC1 ORA.GEN.160Occurrence reporting system

Show the text

GENERAL In addition to occurrence reporting in accordance with Regulation (EU) No 376/2014 the organization should report all occurrences defined in AMC 20-8.

AMC · AMC1 ORA.GEN.160 — Regulation (EU) No 1178/2011 · ED Decision 2025/002/R · Aircrew Easy Access Rules · EAR revision 25 Nov 2025

All rules in SUBPART GEN – GENERAL REQUIREMENTS

Consolidated from the EASA Easy Access Rules (revision 25 Nov 2025, extracted 17 Aug 2026) for convenience. Not the official publication — verify against the Official Journal of the European Union and the EASA publications before operational use.

Ask Metis about ORA.GEN.160 →

Metis opens with Avioverse in October 2026 · request early access.