Occurrence Reports: What Each System Actually Protects

Main glissant un papier plié dans une boîte à fente

Twenty seconds below the minimum sector altitude, an immediate go-around, and the question that always follows: if you file a report, what is actually protected — your job, your licence, criminal proceedings? The two major reporting systems answer differently, because they are not buying the same thing at the same price.

Two systems that do not buy the same thing

In Europe, occurrence reporting is an obligation: operators, maintenance organisations, air navigation service providers and aerodromes operate a mandatory reporting system paired with a voluntary channel. The reporter negotiates nothing; a report must be filed, and quickly: the European regulation sets a short deadline, on the order of seventy-two hours after becoming aware of the occurrence. The protection is the counterpart of a constraint: it covers what can happen to a person because they filed a report.

In the United States, individual filing with the national voluntary reporting system cannot be compelled: the authority cannot impose it on a certificate holder — it buys it, at the price of a waiver of enforcement action announced in advance and subject to verifiable conditions. It does not touch the employment relationship, over which the federal authority has no hold, but exactly what it could itself decide: a civil penalty, certificate suspension. Everything else follows from this difference in origin — who keeps the account, what is done with it, where the shelter stops.

What the European system protects

The first mechanism is material: de-identification. Reports are stripped of personal data before feeding national databases and the European central repository, where the search is for trends, not names. The analyst receives an occurrence, not a crew.

The second targets the employer: an employee who has filed a report must suffer no detriment based on the information they provided. The exception is narrow — wilful misconduct, or a manifest, serious and grave disregard of an obvious risk combined with a profound failure of professional responsibility. This is European just culture: neither impunity nor punishment for ordinary error.

The third targets the State: authorities refrain from prosecuting unpremeditated or inadvertent infringements that come to their knowledge solely through a report. Those three words decide everything. The fourth is procedural: every organisation must adopt written internal rules describing how just culture is guaranteed, and each State designates a body before which an employee can report a breach of those rules. An operator without this document has a statement of intent, not a just culture.

Finally, the regulation organises the encounter with the judiciary instead of denying it: arrangements are agreed in advance between safety authorities and judicial authorities. Criminal law remains a national competence, and no safety text suspends it.

In Europe, filing a report protects you from being punished by your employer or the state for making a mistake, as long as it wasn’t a deliberate or reckless act. The system is strict but fair, with clear rules to follow.

What the American system protects

The mechanism rests on an architectural trick rather than a promise: the voluntary report goes not to the civil aviation authority, but to a third-party agency, outside the world of the certificate, which receives it, time-stamps it, detaches the identification strip and returns it to the reporter. The authority obtains only a de-identified analysis: it cannot trace back to a name, for the simple reason it never had one. The returned strip is the sole proof of filing.

The waiver of sanction is conditional and cumulative. The deviation must be inadvertent and not deliberate; the matter must involve neither a criminal offence nor an accident, nor call into question the holder’s competence; the holder must not have been the subject of a finding of violation during a reference period of several years; the filing must have occurred very soon after the deviation, within a deadline on the order of ten days set by the advisory circular, which must be read in its version currently in force. If a single condition fails, the shelter disappears entirely. What is lifted is the sanction, not the finding: the violation can be established and remain without punitive consequence.

The second tier is contractual. Safety action programmes, concluded between an operator, the authority and the professional group, rest on a signed protocol and a tripartite review committee ruling by consensus. An accepted report leads to a corrective action — an amended procedure, an operations notice, a placard — rather than to enforcement action, and the grounds for exclusion are listed there, not inferred.

The third tier covers flight data: under an approved programme, de-identified data does not form the basis for enforcement action, except in cases of deliberate or criminal acts. Added to this is protection against public disclosure of voluntarily provided information — a central concern on the American side, where the perceived risk comes as much from the press and civil litigation as from the authority.

In the U.S., filing a report protects you from fines or license suspension, but only if you meet strict conditions. The system is more rigid, with clear rules that must be followed exactly to get protection.

A Boeing 737 crew in the U.S. files a report within 10 days after an unstabilized approach at 300 feet below the glidepath. The report is sent to a third-party agency, which removes their names before forwarding it to the FAA. Because the crew had no prior violations and the error was unintentional, they receive protection from penalties. However, if the same crew had missed the 10-day deadline, they would lose that protection.

Three arenas, one single sheet

A report can be used against you in three forums with distinct rules of evidence and timelines: internal discipline, the authority’s action on the certificate, criminal proceedings. Each system covers them unevenly, and as a mirror image of the other.

Protection matrix: three arenas, two systemsTwo rows, three columns. Europe: full protection against the employer, limited against the authority and the criminal judge. United States: full protection against the certificate authority, subject to a protocol against the employer, none in criminal matters.employerlicencecriminalEuropeUnited Statesfulllimitedlimitedby agreementfullnonethe scope is written into each cell
The two systems protect as mirror images. Europe covers the employment relationship first and remains cautious before the judge; America secures the certificate through a published rule and leaves employment to the protocol.

Europe is strong where America is silent, and cautious where America is clear-cut: it promises neither criminal immunity nor an end to oversight. Symmetrically, without a signed protocol, or after it has expired, all that remains on the American side is protection against disclosure.

What each system does with the report
Mechanism European system American system
Nature of the filing Short-deadline individual obligation, plus a voluntary channel Voluntary filing; the notification duty falls mainly on the operator
Holder of the account The organisation, then the authority, identifiers removed A third-party agency, which returns the identification strip
What is lifted Detriment from the employer; prosecution for inadvertent infringement The administrative sanction: civil penalty, certificate suspension
What is not National criminal law; the authority’s oversight The finding of violation; any action by the employer
Exclusion criterion A general standard: wilful misconduct, manifest disregard of an obvious risk A closed list, plus formal conditions
Who assesses The employer, a designated national body, then the judge The authority alone, or a tripartite committee by consensus
Role of the deadline It creates the obligation; missing it is a deviation It creates the protection; missing it removes it
Proof of filing The registration number held by the operator The time-stamped strip, kept by the reporter

What is never protected, anywhere

The two systems converge on a hard core: deliberate act, falsification, substances, criminal activity. They diverge on how they get there, and that difference decides predictability: you know in advance whether you tick a box on a list, never how a “manifest disregard” will be characterised.

Two ways to extinguish protectionProtection granted according to the degree of deviation, from inadvertent error to deliberate act. The solid line, European, decreases progressively. The dashed line, American, stays at maximum then drops abruptly once a listed exclusion is crossed.United StatesEuropeprotectioninadvertent deviationdeliberate act
A slope versus a cliff. On the left, the ordinary error; on the right, the intended act. The solid line describes a standard assessed case by case; the dashed line, a list: as long as no box is ticked, protection is intact, the moment one is, it drops all at once.

Two exclusions go more unnoticed. The accident first: the occurrence shifts into the investigation regime and changes text, purpose and actors — the safety investigation aims at prevention, but it exists alongside a judicial procedure that, for its part, seeks those responsible. Competence next: no report repairs a missing qualification, an expired medical certificate, a check not held.

Above all, protection covers the use of the report, never the existence of the occurrence: this is the concept of the single source. A level deviation lives on in radar recordings, an unstabilised approach in the recorded flight data parameter, a deferred defect in the logbook. As soon as another source establishes the fact, the report no longer proves anything beyond the fact that it was reported first — which remains the best possible position.

The single-window trap. Believing that one filing covers everything. A report addressed to the safety department satisfies the regulatory obligation, but it does not trigger the sanction waiver of a third-party programme, does not survive an expired protocol, does not withstand a committee that rejects the case. By the time the rejection arrives, the deadline for the independent channel has already run out: nothing can be reopened after the fact.

Writing a report that holds up

A useful report is one that an analyst can work with without knowing you: chronology, configuration, flight regime, workload, state of the documentation, what was seen and what triggered detection. These elements produce a corrective action; these alone.

Three categories of writing add nothing to the analysis and a great deal to a case file. The legal characterisation of one’s own act: writing that you “breached” a procedure is not reporting a fact, it is stating a conclusion, and it is not for the reporter to state it. Implicating a third party: naming a controller, a mechanic, a colleague creates a statement about someone else in a document you no longer control. Speculating about intent: describing what you did and why it seemed right at the time is a contribution; judging yourself is not.

The test to run a report throughThree questions in sequence: deliberate act, gross negligence, other source. A positive answer leads down to the box where protection does not apply; three negatives lead to full protection.deliberate act?negligencegross?other source?protectionfullnononoyesyesyesprotection does not apply
Three questions, in this order. The first two extinguish protection; the third deprives it of its object: the fact is already established elsewhere.

Two actions remain that no one will take on your behalf. Keeping proof of filing — registration number, acknowledgement, time-stamped strip — and its date: in the American system, this proof is the very condition for the shelter. And filing where it is useful: when an independent channel exists, the internal report and the voluntary filing complement each other.

The right reflex. Write it twice. A free version, for yourself, where everything goes, including the anger and the doubt; a second, filed version, containing only what an analyst needs to know to prevent a repeat. The interval between the two — an hour, a night — separates a usable report from a self-written piece of evidence.

De-identification is not anonymity

A de-identified report often remains identifiable. On a fleet reduced to a few aircraft, a date, a route and a type of occurrence are often enough to narrow the number of possible crews down to one; free-text fields finish the job. De-identification protects the database, not the person within their own hangar.

Second blind spot: the committee that knows you. In an operator programme, review takes place openly; protection there comes not from anonymity but from the signed agreement, and it ends with it. Third: geography. An occurrence abroad falls first under the law of the State where it happened, and the protections of origin do not cross the border with the crew.

The last is temporal, and the most insidious. The “gross” nature of a negligence is assessed after the fact, by someone who knows the outcome. No text cancels out hindsight bias: the same decision, made in the same fog, reads differently depending on whether it produced a caught deviation or a wreck. Good internal rules require the decision to be assessed with the information the crew had at the moment they made it.

What to check in your own documentation

Four points can be checked in half an hour and change everything on the day it matters.

Two men in uniform review a document in a cockpit at night.
System checks ensure flight safety through meticulous documentation.
  • The internal just culture rules: do they exist in writing, where, signed by whom, and what do they say about the point at which safety analysis stops and a disciplinary procedure can begin?
  • The circuit: is the form you fill in the regulatory channel, an internal tool, or both? Who reads the free-text field? How long is the identified version retained?
  • The designated national body before which a breach of these rules can be brought: this route has value only if you know it exists before the incident.
  • Under a North American programme: is the protocol in force, renewed without interruption, and which categories of occurrence are excluded from it?

For anyone preparing an upgrade to command, an instructor rating or a designated post-holder position, the question becomes one of the file. Knowing what goes into it, what does not, and in what form, is part of the preparation just as much as the technical oral — and practices vary enough from one operator to another that exchanges between practitioners are worth more than a manual on this point.

This article describes mechanisms, not your situation. The applicable text, the operator’s approved documentation and, where relevant, the signed protocol of your reporting programme prevail over everything above: in the event of a discrepancy, it is your manual that governs.

Questions fréquentes

Can my employer use a report filed in Europe against me?

The regulation prohibits an employer from causing detriment to an employee on the basis of information they provided in a report. The exception covers wilful misconduct and a manifest, serious disregard of an obvious risk, assessed according to the written internal just culture rules the organisation must have. If these rules do not exist or are not followed, a designated national body can be asked to examine the breach.

Does filing in the American voluntary system also protect my employment?

No. The sanction waiver covers what the federal authority can decide, namely a civil penalty or action against the certificate. The employment relationship falls under contract and, where applicable, the tripartite protocol of the operator’s safety action programme. Without a protocol in force, nothing constrains the employer’s reaction.

What happens if the occurrence is already known through recordings?

Protection covers the use of the report, not the existence of the fact. As soon as another source — radar, flight data, logbook, witness — establishes the occurrence, the single-source question disappears and the facts can be used normally. The report still carries a different but real value: it shows that the reporting came from the crew before any external discovery.

Does de-identification guarantee anonymity at a small airline?

No, and that is a costly confusion. On a small fleet, the date, route and nature of the occurrence are often enough to identify the crew, and free-text fields add further clues. De-identification protects the national databases and the European repository; inside the organisation, it is the internal just culture rule that protects, not anonymity.

Should you report a deviation that was caught with no consequence at all?

Yes, and that is precisely the raw material of the system. Deviations detected and corrected reveal which defences are working and which nearly failed — something no completed event can show. In Europe, the reporting obligation does not depend on the severity of the outcome but on whether the occurrence falls within the categories to be reported, and the voluntary channel collects the rest.

Do my protections follow me on a flight abroad?

Not automatically. An occurrence taking place on the territory of another State falls first under that State’s law, including for judicial procedure and access to recordings. The protections of the system of origin apply to how the report is handled by the operator and its authority, not to the acts of a foreign authority. You therefore need to check what the operator’s documentation provides for occurrences taking place outside the home jurisdiction.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

FL330, c’est toute l’aviation professionnelle — explorez nos autres espaces.