First, let's finish the accident-reporting obligation — Page 492, Lesson 664

Let me walk you through the tail end of the accident-reporting rules, and then we move into a brand-new piece of legislation — EU Directive 2003/42, which is all about occurrence reporting. First, let's finish the accident-reporting obligation. The investigating body — that's the authority that carries out the official investigation into an accident — must make the final accident report public. And there's a time requirement attached to it: it must be published in the shortest possible time, and if possible within 12 months of the date of the accident. So the target is twelve months from the accident date, and the phrase "if possible" tells you it's a goal, not an absolute deadline — but the intent is clearly to get that report out promptly. Then there's a duty placed on the Member States themselves. They must take the necessary measures to ensure that the safety recommendations made by the investigating bodies — or entities — are duly taken into consideration and acted upon. So it's not enough for an investigation to produce recommendations; the State has a legal obligation to make sure those recommendations are actually considered and followed through. That closes the loop between finding out what went wrong and doing something about it. Now we shift to a completely different piece of law: EU Directive 2003/42. This one concerns itself with the reporting of occurrences. Let me define that term precisely, because it's the heart of the whole Directive. An "occurrence" means an operational interruption, defect, fault, or other irregular circumstance that has or may have influenced flight safety, and that has not resulted in an accident or serious incident. So break that down: it's something that went wrong or was abnormal during operations — an interruption, a defect, a fault, or any other irregular circumstance. It either has influenced flight safety, or may have influenced it. And crucially, it has not resulted in an accident or a serious incident. So an occurrence is, in effect, the safety event that sits just below the threshold of an accident or serious incident — it's the near-miss category, the thing that could have been worse. Now, what's the objective of this Directive? It is to contribute to the improvement of air safety by ensuring that relevant information on safety is reported, collected, stored, protected, and disseminated. Notice those five verbs — report, collect, store, protect, disseminate. That's the full lifecycle of the safety information. And here's the key philosophical point: the sole objective of occurrence reporting is the prevention of accidents and incidents, and not to attribute blame or liability. That's a critical principle for you as a professional. The whole system exists so we can learn and prevent, not so we can punish. That's why reports are protected — people need to feel safe coming forward with information. Then the Directive lays out obligations on the Member States, and the summary gives us four of them. First, Member States shall require that occurrences are reported to the competent authorities. So there's a mandatory reporting duty. Second, Member States shall designate one or more competent authorities to put in place a mechanism to collect, evaluate, process, and store reported occurrences. So not only must reports be made, but the State must set up a proper system — a mechanism — to handle them through those four steps: collect, evaluate, process, store. Third, Member States shall participate in an exchange of information by making all relevant safety-related information available to the competent authorities of the other Member States and the Commission. So this is a shared, cross-border system — information flows between States and up to the European Commission. And fourth, the Directive lists in detail examples of the occurrences that must be reported. So the law gives you a specific, detailed catalogue of what counts as a reportable occurrence. The big takeaway for you: occurrence reporting is a no-blame, prevention-focused system. The moment you see an operational interruption, defect, fault, or irregular circumstance that affected or could have affected flight safety — and it didn't result in an accident or serious incident — that's an occurrence, and it must be reported, collected, evaluated, processed, stored, and shared across the Member States.