Mandatory or voluntary report: choosing the route according to what actually happened

A flight crew and operations manager in a cockpit at dusk, reviewing an in-flight alert on a digital log.

A resolution advisory in cruise, followed immediately, no visible trace from the ground: at the debrief, the question always comes back in the same order, “shall we file it as voluntary?”. It is the wrong question. The dividing line between the two regimes turns neither on severity, nor on the outcome, nor on the view one takes of one’s own part in the affair: it is read off a list and off the role one was performing that day. The rest — the sense of having had a close call, the certainty of having nothing to reproach oneself with — belongs to another conversation.

The switching criterion rests on two conditions

The mandatory regime opens when two conditions are met at the same time, and it closes as soon as one of them is missing. The first concerns the person: the European regulation on occurrence reporting in civil aviation designates roles — flight crew, cabin crew in the cases provided for, staff responsible for maintenance and release to service, staff who sign continuing airworthiness documents, air traffic controllers, aerodrome and ground handling staff, staff who install or modify equipment. The second concerns the fact: the occurrence must match an entry in the list annexed to the implementing regulation that classifies the occurrences to be reported.

Neither of them mentions the outcome. This is the point that most offends the practitioner’s intuition: an alert triggered and then dealt with in a few seconds may fall under the mandatory regime, whereas a situation that left the crew silent all the way to the gate — schedule pressure, a briefing that did not land, a division of tasks that came apart — matches no entry and remains voluntary. That does not make it minor. It says only that no entry knows how to name it, and that is information in itself.

The design is deliberate. The person who has just lived through the occurrence is the least well placed to weigh its severity: they know the outcome but not the population of similar occurrences, and most often have no idea how many times the same configuration arose elsewhere within the month. A criterion based on significant risk alone would produce a filter of variable geometry and data that could not be compared from one operator to another. The list therefore moves the severity judgement downstream, where the rest of the picture is available, and leaves the reporter with nothing but an act of recognition.

The mandatory or voluntary choice depends on two things: your role and whether the event matches a predefined list. The outcome (how serious it was) doesn’t matter. The system is designed this way to ensure consistent reporting across all airlines, not to rely on individual judgement.

A flight crew member notices a TCAS resolution advisory during cruise, but no conflict occurs. This must be reported mandatorily because it matches an entry in the list. Meanwhile, a cabin crew member observes a miscommunication during boarding that could have delayed the flight but didn’t. Since this doesn’t match any list entry, it’s a voluntary report.

What decides the regime: the list, not the outcomeA two-way matrix. The columns show the outcome of the occurrence, innocuous on the left and striking on the right. The rows show membership of the list, present at the top and absent at the bottom. The two top cells call for a mandatory report whatever the column; the two bottom cells fall under the voluntary route, including where the outcome was striking. No column moves a cell from one row to the other.benign outcomestriking outcomeon the listoff the listmandatorythe outcome changes nothingmandatoryand often much morevoluntaryweak signalvoluntaryfear does not create the rulethe row decides the regime, the column decides the attention
The regime is read along the row, never down the column. The two highlighted cells are the ones that offend intuition: an alert with no sequel remains mandatory, a fright that no entry names remains voluntary.

The list names facts, not damage

The implementing regulation arranges the entries by domain: aircraft operations, technical and systems matters, maintenance and continuing airworthiness, air navigation services and aerodromes, with separate treatment for other-than-complex motor-powered aircraft. Within each domain, the drafting always follows the same grammar: the entry describes an observable fact — an alert that went off, a limit exceeded, a configuration that was not the one intended, a defect found on opening a panel, a quantity announced that does not match the one on board — and never the damage that followed or failed to follow.

The practical consequence is immediate. You do not apply the list by asking whether the occurrence “was worth” a report, but by looking for whether it bears the name of an entry. The question is not “is it serious?”, it is “what is it called?”. An experienced practitioner answers the first badly and the second very well, which is exactly the intended effect.

A second mechanism, less well known and yet decisive: the operator may lengthen the list, it may not shorten it. The operations manual, the maintenance organisation exposition or the internal reporting procedure almost always add in-house entries — deviations from a company-specific procedure, ground handling occurrences, service conditions that concern only this fleet, thresholds deliberately lowered at a sensitive point of the network. The list you must apply is therefore your operator’s, and it is longer than the one in the regulation. The absence of an entry from the European text never settles the question on its own.

Three nested frames: regulation, operator, everything elseThree nested frames. The outer frame stands for all safety occurrences. The intermediate frame, dashed, stands for the operator’s internal list. The inner frame, solid, stands for the regulatory list, identical for everyone. The operator may only widen the list outwards, never remove an entry from it. Whatever remains outside the intermediate frame falls under voluntary reporting.all safety occurrencesoperator’s internal listregulatory listidentical for everyoneinternaladditionsno removal possibleeverything else: voluntarythe applicable list is the operator’s, never shorter
The list you apply is longer than the one in the regulation. The operator adds its own entries and has no power to remove any: the absence of an entry from the European text therefore never settles the question on its own.

What the voluntary route actually serves

The voluntary report is not a lighter version of the other. It has a purpose of its own: to collect what the mandatory system cannot capture — a hazard that has not yet produced any occurrence, a condition that is slowly degrading, an observation, a near miss that no entry names. It is open to everyone, including those who perform no designated role, and it knows no enforceable deadline.

Nor is it a private channel, and that is where a second misunderstanding lodges itself. The operator that collects it must analyse it like the rest and pass up to the authority whatever reveals an actual or potential risk to safety. In other words, a voluntary report may perfectly well end up in the same repository as the mandatory ones, de-identified in the same way. What distinguishes the two routes is therefore not their destination, it is the moment at which they speak.

For an entry names an occurrence, and a hazard is not yet an occurrence. As long as the dangerous configuration has met none of the situations described by the list, the mandatory system sees nothing: by design, not by neglect. The voluntary route is the only instrument that speaks beforehand, and that is what it is judged on — its lead time, not its volume.

The voluntary route speaks first, the mandatory one counts afterwardsTwo schematic curves, with no figures, on a horizontal axis of time since a hazard appeared and a vertical axis of report volume. The solid curve, that of voluntary reports, rises early and then levels off. The dashed curve, that of mandatory reports, stays flat as long as no entry is met, then rises from the moment marked by a dashed vertical. The gap between the two starting points is the lead time the voluntary route provides.volume of reports filedvoluntary reportsfirst entry encounteredmandatory reportshazard appearedtime
An entry names an occurrence, yet a hazard is not an occurrence yet. The shapes are what count, not the values: the mandatory system sees nothing before the dashed vertical, not through neglect but by design.

The two regimes compared point by point

The table below does not compare two levels of severity but two mechanisms. Two rows deserve careful reading: the one on protections, strictly identical, and the one on silence, which is not identical at all.

What really changes from one regime to the other, and what does not
Point of comparison Mandatory report Voluntary report
Trigger An entry of the applicable list is met, whatever the outcome may have been Any hazard, condition or observation that no entry names
Who is bound Persons performing a designated role, each for their own part No one is bound; anyone may file
Deadline Short regulatory time limit, counted from becoming aware No enforceable deadline, but a signal that quickly loses its value
What becomes of the written report Analysis, follow-up, then transfer to the national and European repository Analysis, then transfer as soon as an actual or potential risk appears
Protection of the reporter Just culture, within the same limits Just culture, within the same limits
Handling of identity De-identification before dissemination, identifying part kept apart De-identification before dissemination, identifying part kept apart
If nothing is filed A free-standing breach, distinct from the occurrence itself No breach: simply a signal lost
What is expected of it Comparability: counting the same thing from one operator to another Earliness: seeing what no entry yet names coming

The clock starts from becoming aware

The European regulation sets a time limit of seventy-two hours, and the most frequent error concerns not its length but its starting point: it is not the flight, it is the moment when the person bound became aware of the occurrence. A defect found weeks later on opening a panel, an anomaly revealed by the analysis of a recording, a piece of information reported long afterwards by a third party: in every one of these cases the clock starts at the discovery, and it starts full.

Each link then counts its own time limit from its own moment of becoming aware. The reporter’s filing opens the operator’s, which must in turn pass the report to the competent authority. That is why a report filed on the last day is not a neutral act: it does not merely consume your own window, it eats into the room for manoeuvre of the next link, which will sometimes have to complete, verify and classify the report within the day.

The consequence is counter-intuitive for anyone used to polished writing: an incomplete report filed within the window and completed afterwards is better than an impeccable text filed on the fifth day. The system knows how to add a piece to an open file; it does not know how to reopen a deadline that has passed. The exceptional circumstances that allow an overrun are construed narrowly — a hospital admission, a physical impossibility of reaching the system — and a heavy pairing is not one of them.

The time limit runs from becoming aware, not from the flightTwo horizontal bands above a time axis. The upper band describes an occurrence known during the flight: the reporter’s window starts at the flight, the operator’s follows on at once, then transmission goes to the authority. The lower band describes the same time limit for an occurrence discovered weeks later: both windows shift by as much, without ever getting shorter. Each link counts from its own moment of becoming aware.awareness: the flightreporter · 72 hoperator · sameauthorityawareness: the discoveryreporter · 72 hoperator · samethe flightthe discovery, weeks latertimeeach link counts its own time limit
The window does not get shorter when it starts late: it shifts. A defect found weeks after the flight opens a full time limit, and the reporter’s filing opens the operator’s, which still has to pass it on.

The channel counts as much as the text. An email to the sector manager, a line in the aircraft technical log, a call to the internal helpline or a message in the crew app file no occurrence report at all: they inform someone, which is not the same thing. Only the operator’s reporting system opens the regulatory circuit and stops the clock. The converse is equally true: an occurrence report does not replace the entry in the technical log, which alone drives the handling of the fault.

Protection does not depend on the route chosen

The idea that the voluntary route protects better is widespread and false. Confidentiality, de-identification before dissemination and the just culture principle apply to both regimes in the same way, and the shelter stops at the same place in both cases: wilful misconduct and manifest disregard of an obvious risk, that is, a characterised failure to meet professional responsibilities. Filing under the mandatory route amounts to no admission; filing under the voluntary one redeems nothing. The channel does not change the nature of what is written.

What enjoys no protection at all, on the other hand, is the report that was not filed. The shelter covers what has been written; it does not cover a silence. And the omission of a mandatory report constitutes a free-standing breach, separate from the occurrence itself: one can be beyond reproach on the fact and in default on the report, the two assessments not offsetting each other. This is the only point where the choice of route carries a direct personal consequence, and it always works in the same direction.

Why doubt is always settled on the same side

Doubt is the normal situation, not the exception: an entry is rarely recognised at first glance when you do not have the list in front of you, and end-of-pairing fatigue does not help. What settles the matter is therefore not a certainty, it is an asymmetry of costs.

An occurrence wrongly classified as mandatory costs one more line in the repository and a downgrade by the person designated to handle reports. It is a routine act, it leaves no trace against anyone, and it is part of that role’s work: classifying is precisely its job. An occurrence wrongly classified as voluntary costs a missed deadline that cannot be made up, since the clock had been running from the moment of becoming aware. And the reclassification, when it finally comes, comes in an altogether different light: on the occasion of an audit, of a second similar occurrence, or of a request for the file from outside.

Hence an order of questions that fits into three steps, best asked in the cold light of day rather than in the crew rest area.

Three doors, and only two channelsA horizontal line runs from the occurrence and crosses three decision points. The first asks whether the role performed is a designated one: a negative answer goes down to the lower band, that of the voluntary report. The second asks whether the occurrence bears the name of an entry: a positive answer goes up to the upper band, that of the mandatory report. The third asks whether any doubt remains: yes leads to the same upper band, no carries on to the lower band.mandatory reportvoluntary reportoccurrencedesignated role?entry on the list?any doubt left?noyesyesnothe three doors are crossed in this order
Two of the three doors lead to the same channel. Doubt is not an exit door towards the voluntary route: it leads exactly where the entry leads, because downgrading belongs to the designated person and not to the reporter.

Three questions, in this order, before choosing the channel. Were you performing a designated role at the time of the fact? Does the occurrence bear the name of an entry in your operator’s list, the outcome set aside? Does any doubt remain about the entry? A positive answer to the second or the third leads to the same place: the mandatory report, filed within the window, with a sentence stating in so many words that the classification remains to be confirmed. Downgrading belongs to the person designated to handle reports, not to the reporter.

The circuit traps that cost the most

Beyond the channel itself, four confusions come back with disarming regularity.

  • The forgotten cascade. One and the same occurrence opens as many obligations as there are roles concerned: flight crew, cabin crew, certifying staff, ground handling. The filing by one does not release the others, and this is not administrative red tape — cross-checking several points of view on the same fact is precisely what gives the analysis its value.
  • The third route. Accidents and serious incidents fall under a distinct circuit, that of notification to the safety investigation authority, which is to be confused neither with the occurrence report nor with informing the oversight authority. These circuits add up, they do not replace one another.
  • Security is not safety. A threat, a security breach, an act of unlawful interference follow their own chain, with their own recipients. Hybrid occurrences — a disturbance on board with an operational consequence — open two of them, and one does not dispense with the other.
  • The occurrence outside the usual framework. On a wet-leased aircraft, at a foreign station, or where staff come under a certificate different from the one under which the flight is conducted, the circuit is determined by the person’s status and by the applicable certificate. This is a question to settle upstream, in the documentation, not at three in the morning on a parking stand.
Borderline situations: what the chosen route opens, and what it does not dispense you from doing
Situation What the step opens What remains due besides
Fault found in flight and entered in the aircraft technical log The maintenance circuit and the handling of the fault The occurrence report, if an entry is met
Occurrence meeting the definition of a serious incident Immediate notification to the investigation authority The occurrence report, which adds to it and does not replace it
Schedule pressure felt, with no deviation observed The voluntary report Nothing else, but silence is never made up for
Fact calling into question the conduct of the organisation The occurrence report on the technical fact The whistleblowing channel, if there is conduct to be denounced
Threat or act of unlawful interference The security chain, distinct from the safety chain The occurrence report if operations were affected
Deviation noted at a station by another role The report by the person who observed it The own obligation of each of the other roles concerned

What to check in your own documentation

Five points can be checked in a few minutes, and they are usefully checked only before you need them.

Three men in an office reviewing documents and a tablet, discussing operational procedures.
Incident reporting must reflect actual events, not assumptions.
  • Where the applicable list lives, and whether it is reproduced or merely cited. A list that is merely cited forces you to go and find the text, which is not conveniently done from a hotel room on a Sunday evening.
  • Which internal entries the operator has added, and for which roles they apply.
  • Who the person designated to collect and handle reports is, and through which channel they are reached outside office hours.
  • What becomes of the identifying part: who has access to it, at what moment it is separated from the rest, how long it is kept.
  • Whether feedback is provided for, in what form and within what time. A system that gives nothing back stops being fed, and that shows in the filing figures long before it shows in the occurrences.

Two grey areas remain that documentation rarely settles, and that are better put to your safety department than to an investigator: the case of facts observed off duty, and that of facts observed by a person who was not at the time performing the designated role that binds them. The exchanges between practitioners show that the answers vary from one operator to another, which is indication enough to go and ask the question at home. Lastly, for anyone preparing a rating or a management role, the examiner never asks you to recite the list: he asks for the switching criterion, the starting point of the time limit and what doubt changes — three answers of one sentence each, which the FL330 training paths work through in that order.

The applicable regulation, the list annexed to the implementing regulation and the operator’s approved documentation prevail over this article; in the event of divergence, they are what count, and a doubtful entry is settled with the person designated to handle reports, never against them.

Questions fréquentes

Can a voluntary report become mandatory after the fact?

The regime is determined by the entry that was met, not by the channel used. If the analysis shows that the occurrence falls under the list, the designated person reclassifies it and the operator transfers it to the repository. The time limit, for its part, had been running from the initial moment of becoming aware and cannot be made up: that is exactly the gap avoided by filing under the mandatory route as soon as doubt arises.

Are you less protected when you file a mandatory report?

Protection does not vary with the channel used. Confidentiality, de-identification before dissemination and the just culture principle apply in the same way to both regimes, and the shelter stops at the same place: wilful misconduct and manifest disregard of an obvious risk. What is protected nowhere is the report that was not filed, and the omission of a mandatory report is assessed separately from the fact itself.

What should you do when you do not know whether the occurrence is on the list?

File under the mandatory route within the time window, and write in so many words that the classification remains to be confirmed. Downgrading to voluntary is a routine act for the designated person and leaves no trace against the reporter. The reverse move, on the other hand, always happens out of time.

Does the flight crew’s report release the cabin crew or the mechanic?

One person’s filing releases none of the others. The obligation attaches to each designated role and accumulates: several people may have to report the same fact, each for what they saw. This is not administrative redundancy, because cross-checking several points of view on the same occurrence is precisely what makes the analysis usable. In practice, the crew sees the effect in flight, the certifying staff sees the state of the equipment, and neither account contains the other.

Does the time limit run from the flight or from the moment you learn of the occurrence?

It runs from the moment the person bound to report becomes aware. A defect found weeks after the flight opens a full time limit from the discovery. Each subsequent link then counts its own from its own moment of becoming aware, which is why a late filing weighs on the operator as well.

Does an occurrence with no consequence whatsoever justify a mandatory report?

Yes, as soon as an entry names it. The lists are written on the observable fact and not on the damage, precisely so that the reporter does not have to weigh a severity they are not in a position to assess. The absence of consequence is in fact useful information for the analysis, not a reason to keep quiet.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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