Dates are worked out in your browser from the rule text below. Nothing is sent or stored. Check your own procedure and your authority's page: some authorities word the clocks differently, and the tool shows the stricter reading where we know of one.
The three clocks in Regulation (EU) 376/2014
| Clock | What is due | Rule |
|---|---|---|
| 72 hours | Each person who must report (pilot in command, maintenance and airworthiness staff, ATCOs and others) reports within 72 hours of becoming aware. The organisation reports to its competent authority "as soon as possible, and in any event no later than 72 hours after becoming aware of the occurrence". | Art 4(6), (7), (8) |
| 30 days | Where the organisation's analysis identifies an actual or potential aviation safety risk: the preliminary results and any action to be taken, "within 30 days from the date of notification of the occurrence". | Art 13(4) |
| 3 months | The final results "as soon as they are available and, in principle, no later than three months from the date of notification of the occurrence". | Art 13(4) |
When does "aware" start? EASA's FAQ: when "someone in the organisation identifies the occurrence as falling into the category of a mandatory occurrence report". For automated data such as flight data monitoring, when the person analysing the data detects it. Voluntary reports have no 72-hour clock.
Accidents and serious incidents are a separate, faster flow: notify the safety investigation authority of the state of occurrence "without delay" Reg (EU) 996/2010 Art 9(1), and still file the 376/2014 report.
Information security (Part-IS). For incidents or vulnerabilities that may be a significant risk to aviation safety: a notification as soon as known, a report within 72 hours, and a follow-up report once the recovery and prevention actions are identified IS.I.OR.230(c). See the Part-IS starter kit.
Sources: Regulation (EU) 376/2014, EASA occurrence reporting FAQ, Regulation (EU) 996/2010, EASA Easy Access Rules for Information Security.
What changed with Regulation (EU) 2026/1821
The list of occurrences you must report sits in Implementing Regulation (EU) 2015/1018. Regulation (EU) 2026/1821 rewrote it:
- Adopted 27 July 2026, published 28 July 2026. It enters into force on the twentieth day after publication Art 2, which we count as 17 August 2026. We found no later application date.
- Annexes I to V are replaced (air operations, technical, air navigation, aerodromes and ground services, and non-complex aircraft), and a new Annex VI covers unmanned aircraft systems.
- Information security items are added to the lists, in line with Part-IS. In Annex V (non-complex aircraft) there is a new section 1.6 Information Security.
- U-space and UAS items are added across the annexes, and "RPAS, model aircraft" wording is replaced by UAS.
- Some aviation security items leave the list. "Bomb threat or hijack" stays only until 31 December 2027.
The new lists item by item, with an example for each non-complex aircraft item: what must be reported.
Sources: EASA page for Regulation (EU) 2026/1821, EUR-Lex text, ENAC notice.
ECCAIRS 2 and E5X: how reports get in, country by country
Most authorities now take reports through ECCAIRS 2. How a file from your own system gets in differs. Read in October 2026 from each authority's public page; check at the source before you rely on it.
| Authority | Main route | E5X file or machine link | Worth knowing |
|---|---|---|---|
| Portugal, ANAC | ECCAIRS 2 web form on aviationreporting.eu | E5X upload on the EU portal; a machine link ANAC describes as designed for large organisations | Accidents and serious incidents go direct to GPIAAF, and ANAC is also notified. Source |
| Norway, Luftfartstilsynet | ECCAIRS 2 since June 2023 (replaced Altinn) | Organisations with their own system can use the API; a test environment is ordered first | The main page counts 72 hours from the event itself. The calculator uses that stricter reading. Source |
| Finland, Traficom | ECCAIRS 2 since 27 May 2024, for all organisation reports | Not stated on the pages read | Final results are worded "within 3 months of the event". The calculator uses the earlier date. Source |
| Ireland, IAA | EU portal, "ideal for use by small organisations or individuals" | E5X files by email to AVREP@iaa.ie for approved organisations with an SMS | Your surveillance inspector moves you to the E5X route. Source |
| Sweden, Transportstyrelsen | ECCAIRS 2 portal with the Swedish web form | Own-system integration possible; agree the technical solution first | National rules in TSFS 2017:75. Source |
| Denmark, Trafikstyrelsen | ECCAIRS 2 with 15 Danish report forms | No E5X route stated | Grey fields in the form are for authority staff. Source |
| Germany, LBA | EU portal, which forwards to the LBA | Machine link (API) for registered organisations, with an organisation account and an IP allow-list; E5X by SFTP no longer processed since 1 January 2023 | ATM events go to the BAF. Source |
| France, DGAC / DSAC | ECCAIRS 2 portal | Upload up to 50 files and 600 MB at once, after DSAC has validated your software's E5X output | Vendors may build automatic sending. Source (PDF) |
| Spain, AESA | Email to sucesos.aesa@seguridadaerea.es within 72 hours | .e5x or .e5f files by email | Source |
| United Kingdom, CAA | UK ECCAIRS 2 portal at eccairs.icao.int. UK 376/2014 retained | E5X only after the CAA has approved your software's output in writing | A UK organisation that also holds an EASA approval reports to both. Source |
E5X is a zip of occurrence data in XML, on the ECCAIRS taxonomy. The schema and data bridge files are published at aviationreporting.eu. Free text should not contain personal information.