Whistleblowing and safety reporting: two systems that are often confused

A technician and supervisor in a control room reviewing an occurrence report under dim lighting

A member of certifying staff is instructed to defer an overdue task to the next station and to sign the release to service anyway. He files an occurrence report, ticks the confidential-handling box, and considers himself covered. He is, for the technical deviation he has just described. He is not, for what will happen to him over the following months, because the protection he has just obtained does not bear on that — and because he has filed nothing in the system that would have provided for it.

Two systems, two objects that do not overlap

The occurrence report bears on a fact: something happened, or nearly happened, that affects or could affect safety. It is mandatory for a list of occurrences defined by the European regulation, voluntary for everything else, and it asks its author neither to characterise a fault nor to name a person responsible. Its purpose is statistical and corrective: to feed the organisation’s safety management system, then a European repository where data from many operators, workshops and providers cross-check one another to reveal what none of them sees alone.

The whistleblowing report bears on a breach: a violation of the law, a threat or harm to the public interest, of which the reporter became aware in the course of their professional activities. It presupposes a characterisation, however summary — this should not have been done — and it seeks individual handling, not a trend. The occurrence report feeds a database; the whistleblowing report opens a case file.

The confusion arises because both begin with the same sentence: “I have to report this.” What follows has nothing in common, and it diverges from the very first line of the form. A reporting system that receives “I was told not to declare it” does not know what to do with it: the taxonomy at its disposal describes occurrences, flight phases, systems and consequences, not intentions. At best, the analyst will classify it as an organisational factor and raise it at a review meeting — without anyone in that chain having a mandate to investigate an accusation or the power to draw any consequence from it against anyone.

Decision matrix between occurrence report and whistleblowing reportTwo-way table. In columns, the nature of what is reported: a safety fact on the left, the conduct of the organisation on the right. In rows, the character of the act: unintentional at the bottom, deliberate at the top. Three cells fall under the occurrence report alone, with or without source protection; the highlighted top-right cell calls for both systems at once.safety factconduct of the organisationdeliberateunintentionaloccurrence reportprotection not securedoccurrence reportsource protectionboth channelstwo documents, two filingsoccurrence reportvoluntarythe column sets the channel, the row decides the protection
It is not severity that separates the two systems, it is the nature of what is being described. One and the same incident may occupy the left-hand column through its technical fact and the right-hand one through the instruction that produced it: the top-right cell is the only one that requires writing twice.

The occurrence report is about safety facts, while the whistleblowing report is about illegal or harmful actions. One is for data collection, the other is for investigating wrongdoing. They serve different purposes and protect different things.

A mechanic notices that an A320’s landing gear was released without completing a required inspection. They file an occurrence report for the safety issue. But if their supervisor told them to sign off on it anyway, they should also file a whistleblowing report about the supervisor’s instruction. The first protects the safety data; the second protects the mechanic from retaliation for reporting the supervisor.

What each protection actually covers

The just culture principle, as the European reporting regulation establishes it, comes down to two statements. First, information from occurrence reports is not used to attribute blame or liability; it serves only to maintain or improve safety. Second, the employer does not subject the person who reported to any detriment on account of what they reported, save for gross negligence or wilful misconduct. That is powerful, and it is narrow: the protected object is the act described in the occurrence report.

Whistleblower protection has the opposite object. It takes no interest in the nature of the act reported and targets the measures taken against the reporter: termination or non-renewal, transfer, removal from a role, exclusion from an instructor pool, reassignment to less desirable routes, refusal of training, an appraisal suddenly downgraded. In most national transpositions it carries effects that just culture does not have: nullity of retaliatory measures, a shifted burden of proof before the court, protection extended to facilitators and relatives, and immunity for producing documents lawfully accessed in the exercise of one’s duties.

The practical consequence reads in a single sentence: an operator can respect its just culture charter to the letter — never sanctioning a reported deviation — while at the same time ceasing to roster on the requested pairings the person who put a finger on the organisation. Nothing in the first system gives any hold on the second behaviour, because nothing in the first system concerns it.

What just culture covers, what reporter protection coversA horizontal axis runs from unintentional error to deliberate act. The upper band, representing the protection attached to the occurrence report, stops at a dashed vertical: beyond it, nothing. The lower band, representing whistleblower protection, spans the whole width, because its object is not the act reported but the measures taken against the person who spoke.the axis describes the act reported, not the fact of having spokenjust culture — object: the act reportedsanction ruled outgross negligence: nothingreporter protection — object: the measures taken against themretaliation prohibited, whatever the actunintentional errordeliberate act
The two protections do not overlap; they do not even bear on the same object. One neutralises the act you have just described and stops dead before the deliberate; the other ignores the nature of the act and targets what the organisation will do with you afterwards.

The channels never cross

The occurrence report enters the internal system, held by the safety function. It is analysed, coded, cross-checked against the others, then transmitted to the national supervisory authority within a short and framed deadline, before joining the European repository in disidentified form. The person who handles it has neither the mandate nor the means to investigate an accusation: this is not organisational timidity, it is the very condition for reports to keep coming in.

The whistleblowing report enters through a separate channel — designated officer, ethics officer, sometimes an external provider — reporting to compliance or to the legal department. It may, depending on the case and without any obligation to go through the internal route under recent regimes, be brought directly before a designated external authority, the civil aviation authority generally being among them. Public disclosure comes only at the end of the chain, under strict conditions, including grave and imminent danger.

Going to the wrong desk does not only cost time. The reporting deadline runs from the moment one became aware of the occurrence, not from the answer of an internal whistleblowing channel. A report filed on Monday with the ethics officer, whose outcome one patiently awaits, leaves the occurrence reporting obligation unpaid in the meantime — and that obligation weighs on the individual too, not only on the organisation.

The two channels of a reportFrom a single reporter, two independent chains set out. The upper chain, that of the occurrence report, passes through the internal reporting system, then the national supervisory authority, then a European repository where the data are disidentified. The lower chain, that of the whistleblowing report, passes through a dedicated internal channel, then a designated external authority, and opens public disclosure only under conditions.reporteroccurrence reportinternal reportingsystemnational supervisoryauthorityEuropean repositorydisidentified datawhistleblowing reportinternal channeldesignated officerexternal authoritydesignatedpublic disclosureunder conditions
The two chains start from the same desk and never meet again. One descends towards a shared database that will no longer know anyone; the other rises towards a decision that does name someone.

Two regimes compared point by point

The table below is not there to pick a side but to locate, line by line, the exact point at which a report tips from one regime into the other. Three lines deserve a slow reading: the handling of identity, the persons covered, and what each system produces as an output.

What each system takes on, and what it leaves to the other
Point of comparison Occurrence report Whistleblowing report
What is reported A fact: an occurrence that happened or was avoided, a deviation observed, a hazardous condition A breach: violation of a rule, threat or harm to the public interest
Characterisation asked of the reporter None; describing is enough, and an opinion on the causes is optional One, at least summary: to state what should not have been done, and by whom
First recipient The organisation’s reporting system, held by the safety function The dedicated internal channel, held by compliance, ethics or a mandated third party
Rest of the chain National supervisory authority, then shared European repository Designated external authority, then public disclosure under strict conditions
Handling of identity Known on entry, erased before any wider sharing Known and kept; it is its disclosure that is prohibited and sanctioned
Protection granted No detriment on account of the report; the data are not used to attribute blame Prohibition of retaliatory measures, with effects before the employment court
What defeats it Gross negligence, wilful misconduct, deliberate harm A report made in bad faith or outside the scope defined by the text
Persons covered Those who report in the system of the organisation to which they are accountable A wider circle: former employee, job applicant, contractor, subcontractor’s staff, facilitator
What the system produces An aggregated data point, a trend, a safety action An investigation, a decision, possibly a sanction against a named person
Tempo A short deadline, counted from the moment one became aware of the occurrence Prompt acknowledgement of receipt, feedback on handling within months

The line on persons covered is the one that changes the most for anyone working outside a classic employment contract. The occurrence report follows the function performed: you report because you are crew, certifying staff, a ramp agent or a controller, whatever the contractual link. Reporter protection, for its part, follows a circle far wider than salaried employment alone — former employee, job applicant, co-contractor, a subcontractor’s staff. For a self-employed worker on an assignment contract, retaliation never takes the form of a disciplinary sanction: it takes the form of an assignment that is not renewed, and that is precisely what the first system does not see.

When a single finding falls under both at once

Let us return to the release to service signed on instruction. It contains two distinct objects that cannot be melted into a single document. The first is a fact: an aircraft was returned to operation with a task not carried out, outside the framework provided by the approved documentation. That is a reportable occurrence, and the obligation to report it is personal as much as organisational. The second is a breach: the instruction given not to record it, and the corruption of traceability that follows. No occurrence code covers that.

Good practice is therefore to produce two documents on the same day, in two channels, with two contents that do not resemble each other. The occurrence report sticks to the fact: what, when, which aircraft, what actual or potential effect on safety, what was done next, in what state the aircraft departed. No names, no imputed intent, no legal characterisation. This is not caution: it is the format. Disidentification applies to the fields provided for it, not to the free narrative slipped into the comments box, and that narrative will travel into the sharing chain.

What becomes of the reporter’s identity through the handling processTwo traces on an axis running from filing to retention. The solid trace, that of the occurrence report, starts from a named filing and falls to a near-zero level after the disidentification step: the source is erased before sharing. The dashed trace, that of the whistleblowing report, stays at the top from one end to the other, because identity is known at every step and it is its disclosure that is prohibited.identitynamedanonymousfilinginternal analysistransmissionretentiondisidentificationwhistleblowing: identity known, disclosure prohibitedoccurrence report: source erased
The occurrence report loses its author along the way; the whistleblowing report keeps them and owes them secrecy. That is why a name written into an occurrence report travels: disidentification bears on the designated fields, not on the narrative slipped inside.

The whistleblowing report carries exactly what the occurrence report must not carry: who asked for what, when, in front of whom, on what medium, with which supporting documents, and the reference of the occurrence report already filed. The cross-reference works in that direction and never the other: citing the occurrence report number in the whistleblowing report is useful and has no adverse effect; citing the whistleblowing report in the occurrence report amounts to pouring a named accusation into a file designed to be shared, including outside the company.

The trap. Believing that the occurrence report opens up whistleblower protection. It opens up source protection, which is not the same thing: it prevents what you described from being used to sanction you, it prevents nothing of what the organisation will later decide about you on other stated grounds. The day a non-renewal or a removal from the programme comes along, you must be able to show an earlier report filed in the channel that triggers the shifted burden of proof. A disidentified occurrence report, by construction, does not make that proof: it was emptied of its author along the way.

The routing mistakes that cost the most

The four most common mistakes are:

  • Waiting for the whistleblowing channel to respond before filing the occurrence report, which causes the reporter to miss the short deadline for the safety report.
  • Reporting issues to a manager or in informal notes, which triggers no legal protection and may not be found later.
  • Filing an anonymous report, which weakens the occurrence report (since the author can’t clarify details) or may not be valid for whistleblowing (since protection requires a known identity).
  • Putting accusations or names in the occurrence report, which forces the safety team to handle a disciplinary matter they’re not equipped for, often leading to the report being removed from the safety system entirely.
The two clocks of a single findingA qualitative time scale runs from the immediate to months. On the upper track, that of the occurrence report, filing and then transmission to the authority play out in days and the lessons come back much later. On the lower track, that of the whistleblowing report, only the acknowledgement of receipt is quick: feedback on handling is counted in months, and escalation to the outside comes later still. Waiting for the second clock makes you miss the first.qualitative scale, no duration is to scaleoccurrencereportwhistleblowingreportfilingtransmission to the authoritylessons disseminatedacknowledgement of receiptfeedback on handlingexternal escalationimmediatedaysweeksmonths
The first clock is short and counted; the second is not. They do not start from the same triggering event, and that is why one cannot be suspended while waiting for the other.

The right reflex. Before writing, ask a single question: is what is about to be described a state of the world, or someone’s conduct? If it is both, two documents go out the same day, and one keeps outside the employer’s systems a dated personal record: the reference of the occurrence report, the acknowledgement of receipt from the whistleblowing channel, and the facts on one page. It is these three items, and not the technical content, that make the difference if an adverse measure arises later.

What the safety function must know how to route

On the organisation’s side, the symmetry of the problem is rarely addressed. The person nominated for safety regularly receives, in their reporting system, material that belongs to whistleblowing: pressure to depart, hours not recorded, training signed off without having been delivered, a signature obtained from an unqualified third party. They can neither investigate it, nor keep it, nor pass it to the reporter’s line management without destroying the trust that keeps their system alive. The only clean way out is written in advance in the manual: a routing procedure that provides for going back to the reporter, pointing them to the whistleblowing channel and leaving the filing in their hands, while keeping in the safety chain only the factual part of their report.

This procedure has a corollary too often forgotten: the safety manager must not become, in practice, the whistleblowing officer. Combining the two roles amounts to bringing an investigative function into the safety system, and spontaneous reports dry up within a few months as soon as crews understand that the same office handles both. Separating the desks is not a refinement of the organisation chart, it is what keeps the flow of the first one going.

What to check before you need it

Three checks are done cold, and can no longer be done on the day. The first: open your operator’s or your organisation’s just culture charter and read what it names exactly as the limit. The wording used locally to designate wilful misconduct varies, and it is that wording which will be invoked; knowing whether a joint committee decides such cases, and within what deadline, is better than finding out while personally concerned. The second: identify the whistleblowing channel, its named recipient, the form of filing and the acknowledgement deadline. In many medium-sized aviation structures this channel has existed on paper since transposition and has never been used; that is the moment when you discover that the address no longer works.

A man in a mechanic's uniform fills out a maintenance report while another gestures in an aircraft hangar.
Maintenance reports are critical for safety and compliance.

The third concerns self-employed and seconded personnel, a situation that has become common in flight operations as in maintenance. The whistleblowing channel to approach is not necessarily that of the entity that pays: in principle it is that of the organisation in which the facts were observed. A pilot on an assignment contract who files with their agency a report aimed at the operator has filed in the wrong place, and the agency has neither the mandate nor the interest to carry it any further.

One grey area remains that nobody has closed: the interface with the safety investigation conducted by the independent investigation authority after an accident or a serious incident. That investigation is haunted by the same precaution as the occurrence report — its elements are not used to establish liability — but it coexists with judicial proceedings which do establish it. A witness may find themselves speaking in turn to three interlocutors, only one of whom owes them secrecy as to their identity. Knowing which one, before opening one’s mouth, is part of the job just like the rest.

These markers describe a general mechanism; in case of divergence, the applicable texts, the just culture charter and the approved procedures of the operator or of the organisation prevail over what is written here.

Questions fréquentes

Is an occurrence report enough to protect me if I name a person responsible in it?

No, and it even produces the opposite effect. The protection attached to the occurrence report prevents what you describe from being used to attribute a fault to you; it does not protect you against measures taken against you on another stated ground. Naming someone in an occurrence report also places a named accusation in a chain designed for sharing, which exposes the reporter as much as the person named. To target a course of conduct, it is the whistleblowing channel that must be used.

Must one necessarily go through the internal channel before approaching an external authority?

Under the regimes derived from the European directive on the protection of whistleblowers, going through the internal route is no longer an imposed precondition: the reporter may approach a designated external authority directly. That choice still has to be weighed, because the internal channel is often faster on a verifiable fact and leaves you in control of what follows. The occurrence reporting obligation, by contrast, knows no such alternative and follows its own chain in every case.

I am a self-employed pilot on an assignment contract: am I covered by these protections?

For the occurrence report, the obligation and source protection follow the function performed and the system of the organisation to which you report, regardless of the contractual link. For whistleblowing, the circle of protected persons expressly includes co-contractors, service providers and subcontractors’ staff, which covers your situation directly. The point to watch is the desk: the report is in principle filed in the organisation where the facts were observed, not with the agency that pays you.

What happens if my occurrence report reveals my own error?

That is exactly the case just culture is made to cover: an unintentional deviation, reported by its author, must not give rise to a sanction on account of that report. The limit is gross negligence or wilful misconduct, whose exact wording appears in your operator’s charter and is to be read before you need it. In practice, the question that arises is almost never one of principle but that of knowing who characterises the deviation, and under what procedure.

Is an anonymous whistleblowing report a good idea?

It carries a high cost: protection against retaliation attaches to an identified person, and with no identity known to the channel there is neither a prior filing to rely on nor any status to invoke later. The protective regime rests on the confidentiality of the identity, whose disclosure is prohibited and sanctioned, rather than on anonymity. A named filing in a channel bound to secrecy is generally more protective than an anonymous one.

How can I show that a non-renewal is linked to my report?

That is precisely where the whistleblowing regime brings what the occurrence report does not: a shifted burden of proof, the employer having to establish that its decision rests on grounds unrelated to the report. You still have to be able to date the report and prove that it was received, hence the importance of the acknowledgement of receipt and of a copy kept outside the employer’s systems. A disidentified occurrence report does not fulfil that function.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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