The next duty starts in nine hours, the day’s rest has not exceeded two and a half hours, and the question is no longer whether you are tired: it is what you are going to write. A declaration of unfitness fits in a single line in a scheduling system. It costs a replacement, sometimes an extra hotel night for another crew, and it corrects strictly nothing if nobody can say what, in the way the pairing was built, produced that state. The report that accompanies it is the only thing capable of turning an individual withdrawal into usable information.
Two acts that everyday language confuses
Declaring yourself unfit is an operational act. It is unilateral, it takes effect immediately, and it requires no technical demonstration: the rule places the assessment of one’s own state with the person who is about to exercise the function, precisely because nobody else has that information. Writing a fatigue report is a documentary act. It removes nobody from duty, it produces no effect on the day itself, and its value depends entirely on what it contains.
The confusion comes from the fact that both often go through the same phone call. You notify crew control, explain in thirty seconds, and assume the message has got through. It has not: what remains in the system a few weeks later is an unavailability code, possibly with a free-text comment that nobody aggregates. Crew control has done its job — it found a replacement. Scheduling, for its part, received nothing.
A third object sometimes overlaps with the first two: the occurrence report under the European regulation. It follows a different logic, that of the mandatory reporting of facts liable to affect safety, with deadlines and transmission to the authority. A withdrawal decided before check-in generally does not fall under it. An episode of drowsiness in cruise, a checklist item forgotten, a descent begun on an incorrect altitude after a sleepless night: there, you enter the scope of the occurrence report, and the list of notifiable occurrences in the operations manual is authoritative, not the assessment of the moment.
| Object | Effect | Actual recipient | What it requires |
|---|---|---|---|
| Declaration of unfitness | Immediate: withdrawal from duty | Crew control, replacement crew | A personal judgement, not a justification |
| Fatigue report | Deferred: construction of rosters | Fatigue management, scheduling | Time-stamped facts and durations |
| Occurrence report | Regulatory: analysis and follow-up | Flight safety, authority | The fact, its circumstances, its consequences |
What scheduling can actually correct
A report is only as useful as what it feeds. The levers available to a scheduling department are finite in number: check-in time, the sequencing of sectors, the number of consecutive nights in a pairing, the positioning of rest relative to the local night, the use of reserve, the actual commute time between home and base, the quality of the rest location on layover. Each of these levers is driven by a specific type of fact. None is driven by the adjective « tired ».
The underlying mechanism is simple and rarely written into the forms: performance depends on three quantities that combine, the duration of continuous wakefulness since the last sleep, the debt accumulated over previous days, and the biological hour at which the duty falls. The first two are corrected by rest; the third cannot be corrected at all, it is worked around by moving the duty. A report that gives all three lets you choose the right lever. A report that gives none of them leaves the scheduler with a single option: change nothing.
Fatigue isn’t just about feeling tired—it’s about how long you’ve been awake, how much sleep you’ve missed, and what time of day it is. A good report helps schedulers fix the right problem, like adjusting rest times or shifting duties.
An Airbus A320 crew flying from Paris to Dubai with a 3-hour layover reports feeling unfit for the return. They note they slept only 4 hours in a noisy hotel, had a 1.5-hour commute to the airport, and their duty starts at 2 AM local time. This helps schedulers adjust future rotations by adding longer layovers or avoiding early morning departures.
That is why a declaration expressed in feeling — « exhaustion », « very hard rotation » — is rightly treated as an opinion. Not out of disregard for the person reporting, but because it attaches to no lever. Two crews can fly the same rotation, one with a long commute and a noisy hotel, the other with a few minutes’ drive and a quiet room: the rotation is identical, the exposure is not, and only a description of the conditions can show whether the problem lies in the pairing or in the logistics around it.
The anatomy of a report that is useful
A usable report does not tell a story: it lays down value-time pairs. The writing rule fits in one sentence: every line must be comparable to the same line from another crew on the same pairing. Anything that is not comparable is commentary.
| Fact reported | Lever it opens | What is lost without it |
|---|---|---|
| Time of last waking before check-in | Shifting the check-in time | Wakefulness duration at end of duty becomes uncalculable |
| Sleep obtained, duration and fragmentation | Lengthening or repositioning of rest | Rest offered gets confused with sleep actually taken |
| Number of consecutive nights already flown | Limiting night blocks within the pairing | Accumulated debt is attributed to the last duty alone |
| Actual home-base commute, both ways | Check-in time, positioning the night before | The duty looks short even though wakefulness is long |
| Conditions of the layover rest location | Changing hotel, room, or shuttle schedule | A logistics problem gets blamed on the rotation |
| Observed symptoms and their time | Classification of the episode, safety follow-up | The event dissolves into a general feeling |
The last line deserves a word. « Observed symptoms » does not mean confession. It refers to verifiable, time-stamped facts: an item re-read three times, a frequency read back incorrectly, heavy eyelids at a given point in the cruise, a drop in responsiveness noted by the other seat. These elements have particular value because they date the effect, whereas everything else only describes the exposure.
The right reflex. Note the times as you live through them, not when filling in the form. Wake-up time, time of falling asleep on layover, time of the first sign: three numbers entered on a phone as the duty unfolds are worth more than an honest reconstruction made several days later, which will invariably drift toward round numbers and averages.
The timing of the declaration, and what it costs
A declaration made during the window between the end of rest and check-in is settled with a phone call. Beyond that, every hour that passes multiplies the consequences: crew already in place, passengers boarded, aircraft to reposition, a replacement crew to bring in under its own rest regime. The important point is not the disruption caused — it is legitimate and expected — but the fact that the cost as perceived by the person reporting rises at the same time, and that this pressure pushes exactly the wrong way.

The trap. The intermediate layover. You know, on waking, that your condition will not allow you to fly the return sector properly, but the crew is already far from base, the declaration would block everyone, and you tell yourself you’ll « hold on until landing ». The declaration is then made after the flight, when it no longer has any protective effect and exposes you to the reproach of having flown knowingly. A condition found before check-in is declared before check-in, including on layover, including when the logistics of the return look unsolvable: solving them is crew control’s job, not yours.
Two dimensions therefore intersect, and they do not buy the same thing. Earliness buys the replacement under bearable conditions. Precision buys the lasting correction. An early, vague declaration protects the day’s flight and leaves the cause intact; a late, documented declaration explains a month later what could have been avoided on the day itself.
Just culture: what the declaration covers, and what it does not
The principle of just culture does not say that everything is excused; it says that a sanction cannot fall on the fact of having reported, and that it remains possible for deliberate wrongdoing or conscious, unacceptable risk-taking. Applied to unfitness for fatigue, the dividing line is clear in principle and blurred in practice. What is protected is withdrawing from a duty because you judge your condition insufficient, even if that assessment turns out to be debatable in hindsight, even if it is repeated, even if it falls on a day of heavy workload. What is not protected is checking in knowing you will not be able to perform the duty, then producing a fatigue report afterwards to cover an error made in flight.
There remains an area that manuals rarely address: mixed causation. A sleepless night shared between a sick child and a badly built pairing cannot be split into percentages. The reasonable practice is to declare the condition without haggling over its origin, then to describe in the report what falls under professional exposure — schedule, sectors, rest offered — and to mention the existence of a personal factor without going into detail. The operator needs to know whether the line should count in the pairing’s statistics; it needs no health information for that, and must not ask for it.
From isolated case to signal: what becomes of your entry
An isolated report has almost no demonstrative power, and that is what discourages most the crews who take the trouble to write one. The mechanism of a fatigue management system is statistical: the number of declarations is set against the number of times the pairing was flown, similarly structured pairings are compared, and what stands out from the background noise is sought. A pairing that produces only a very occasional declaration stays within individual variability. The same pairing, if it produces one on almost every crew rotation, carries a construction defect, and the only way to show it is for the declarations to exist.
This arithmetic also explains the most destructive bias in the system: selective under-reporting. Those who report least are rarely the least exposed; they are often the ones who fear how their entry will be read, or who concluded, after two reports left without a response, that the exercise was pointless. The denominator stays correct, the numerator collapses, and the defective pairing disappears from the radar. That is why feedback to the person reporting is not a courtesy but a component of the mechanism: without it, the source dries up and the analysis loses its material.
What should be checked before the next rotation
Four points should be checked in advance, not at the moment you hesitate to pick up the phone. The first: where exactly is the fatigue report form located, and does it remain accessible from a hotel room without a company network? A form that exists only on the base intranet will never be filled in on layover, which is precisely where the information is fresh. The second: who reads it, within what timeframe, and in what form does the reporter receive a response? The third: is the report nominative on receipt and de-identified at the analysis stage, and who has access to what in between? The fourth: what exactly does the operations manual say about a declaration made away from base, and about repatriating someone who has declared themselves unfit on layover?
A grey area persists, and it is better to name it than to pretend it has been resolved: the personal threshold. No text provides a measured state beyond which you must withdraw, and no onboard instrument will do it for you. What is measurable are the conditions that lead to it, and that is precisely what your report documents. For anyone preparing a type rating or changing operator, the question to ask at interview is, incidentally, not « can you declare yourself unfit? » — the answer is always yes — but « how many fatigue reports changed a pairing last year? ». The answer, or its absence, says more about the system than any chapter of a manual.
The applicable regulations, the operator’s approved documentation and the procedures in its operations manual prevail over this article, whose sole purpose is to explain a mechanism.
Questions fréquentes
Does a declaration of unfitness for fatigue need to be medically justified?
No. The declaration concerns your condition at the time and your ability to perform the duty, not a diagnosis. The operator may ask for facts that help it correct scheduling — hours, sleep obtained, rest conditions — but unfitness declared for fatigue does not follow the same mechanism as a suspension of medical fitness, which goes through the examining physician.
Does a declaration of unfitness count as a fatigue report?
No, and that is the most frequent confusion. The declaration produces an unavailability code in the scheduling system, nothing more. The report is a separate document, often optional in form, that feeds the fatigue analysis. Without it, the withdrawal costs a replacement without correcting anything in how rosters are built.
What should you do when you feel unfit on layover, far from base?
Declare it before check-in, just as you would at base. Sorting out the return of the aircraft, the passengers and the crew is crew control’s job, not the reporter’s. A declaration held back until after the flight loses all protective effect and exposes you to the reproach of having flown knowingly.
What facts should be noted for a report to actually be useful?
Value-time pairs that are comparable from one crew to another: time of last waking, duration and fragmentation of sleep actually obtained, number of consecutive nights already flown, actual commute between home and base, conditions of the rest location, and the time of any observed symptoms. An adjective like “exhausted” attaches to no scheduling lever.
Does just culture protect every declaration?
It protects the act of declaring, including when the assessment turns out to be debatable in hindsight or falls on a day of heavy workload. It does not cover deliberate wrongdoing: checking in knowing you will not be able to perform the duty, then producing a fatigue report afterwards to cover an error, remains outside the scope of the protection.
Why does an isolated declaration change nothing?
Because the analysis is statistical: it sets the number of declarations against the number of times the pairing was flown, then compares similarly structured pairings. An isolated case blends into individual variability; it is repetition on the same pairing that reveals a construction defect and triggers its review.

Leave a Reply
You must be logged in to post a comment.