Occurrence reporting in the UK and the rest of Europe is
governed by European
It requires the reporting, analysis and follow up of occurrences
in civil aviation and delivers a European Just Culture Declaration.
An occurrence means any safety-related event
which endangers or which, if not corrected or addressed, could endanger an
aircraft, its occupants or any other person.
The purpose of occurrence
reporting is to improve aviation safety by ensuring that relevant safety
information relating to civil aviation is reported, collected, stored,
protected, exchanged, disseminated and analysed. It is not to attribute blame
This delivers a European Just Culture Declaration.
Regulation (EU) 376/2014 on Occurrence Reporting Analysis and Follow-up of occurrences in civil aviation repeals Directive 2003/42/EC and regulations 1321/2007 and 1330/2007.
Commission Implementing Regulation (EU) 2015/1018 lays down a list classifying occurrences in civil aviation to be mandatorily reported.
This paper aims to explain the intended purpose of Regulation 376/2014 provisions and its implementing regulations, in accordance with the spirit of the agreement found between colegislators. It proposes, where relevant, possible means of compliance and examples of good practice, to contribute to a consistent implementation of Regulation 376/2014 and its implementing rules across the EU.
Access the Guidance Material.
For Annex II aircraft, reporting remains voluntary under the new regulations, although this may be reviewed in the future.
Under the new regulation, occurrence information can only be used to maintain or improve aviation safety. This means that we can't release occurrence information to the general public or to the media, including in response to Freedom of Information Act (FOIA).
If you need occurrence information for aviation safety you need to:
For anything more detailed please compete form SRG1605.
Occurrence Reports are treated confidentially to maintain full and free reporting from the aviation community and to protect the identity of the individual in accordance with EU legislation.
The list of reportable occurrences are published in Commission Implementing Regulation 2015/1018.
This is divided into the following disciplines:
We have produced some additional guidance to help you interpret the disciplines listed above.
The MORs Code
When you submit your report, you need it to be in an ECCAIRS/ADREP compatible format.
This format is an XML / XSD specification containing the mandatory data fields and their associated value lists. This specification is published on the European Commission Joint Research Centre’s website, you will need to request an account to access the schema. The schema is a subset of attributes and values selected from the whole taxonomy, called the Reduced Interface Taxonomy (RIT).
To make sure your report is in a compatible format either:
If your reporting software isn't compatible and you're unable to upgrade it to give the correct output, or you don't have any reporting software, the EU Reporting Portal is the best option.
provides initial guidance on the development, validation and submission of a
direct compliant output.
Reporting Portal is subject to continuous development and it is recognised that
it is not the final product but it does meet the requirement of reporting in a
We are currently looking for an experienced airworthiness surveyor to join our team in Gatwick https://t.co/zKFSP3VXZE
5 days ago
Our Aircraft Registration Dept currently has a vacancy based in Central London https://t.co/OGgRziRUK7
7 days ago
"Most airports rated very good or good for assistance to disabled passengers – all should in future" https://t.co/8KchjkEsKA #AccessToAir
9 days ago
Read all @UK_CAA
CAA statement on Government drone consultation response
24 July, 2017
CAA statement on sky's the limit campaign
2 December, 2016
CAA sets out expectations to Heathrow Airport for delivering a new runway
25 October, 2016
Read all News
International women in engineering day
22 June, 2017
How we're changing the CAA
15 April, 2016
Read All Blogs