Thursday evening, the end of a three-day rotation for an on-demand charter operator. Friday morning, a second operator, with whom the same crew member is qualified and works under a services contract, offers a there-and-back trip. Taken separately, the two rosters are beyond reproach. That leaves the one question that decides whether Friday’s flight is legal: which of the two operators has the total for the last seven days in front of them? Neither. This is the blind spot of multi-employer work, and no software corrects it.
The limit attaches to the crew member, not to the contract
A flight time limitation is not a clause in an employment contract: it is a limit carried by a person. Cumulative windows are counted on an individual and add up every task performed on behalf of an operator, whichever it may be. Changing client resets no counter, any more than changing home base or status does. The rule superbly ignores the contractual boundary that nevertheless structures the whole working life of a freelance.
For a salaried crew member with a single employer, this obvious fact has no practical consequence. The operator holds the roster, its tool holds every duty performed, and the limit check is automatic. As soon as a second operator enters the picture, the data ceases to exist anywhere: it lives only in the crew member’s head and in the records he chooses, or does not choose, to consolidate.
In a multi-operator configuration, the legality of a flight depends on information that the person taking the decision does not hold. The regulatory framework draws two symmetrical consequences from this: the crew member must provide each operator with the elements needed to build its roster, and each operator must keep records of flight time, duty time and rest that also cover the activities carried out for the others.
Flight time limits follow the crew member, not the employer. If you work for two operators, their rosters don’t automatically add up. You must track all your duties yourself to stay legal.
A pilot flies 3 days for Operator A (Mon-Wed) and 2 days for Operator B (Fri-Sat). Each operator’s system only sees its own flights. The pilot must manually add them to check the 7-day duty limit (e.g., 60 hours). If the total exceeds 60 hours, the Friday flight is illegal.
A diligent operator is not the one that assumes: it is the one that asks, dates the answer and keeps it. A diligent crew member is not the one who answered once when signing the framework agreement: it is the one who re-declares at every request, because an answer three weeks old says nothing about the current window.
Rolling windows never reset to zero
The word rolling is the one that costs. A window of twenty-eight consecutive days is not a month: it is recalculated every day and releases the oldest duty at the other end. An assignment accepted today therefore weighs on every calculation for up to twenty-seven days afterwards, and on the annual counter until 31 December. There is no moment at which the slate is clean.

Hence the most widespread error among freelance crew members: reasoning by calendar week and by contract. The reasoning two days with A this week, so there is margin is wrong twice over. The window of seven consecutive days does not begin on Monday, and the margin is not calculated on one operator’s share but on the total. The two errors add up exactly in the configuration described here: the assignment that tips the balance almost always straddles two contracts and two calendar weeks.
| Quantity | Window | Order of magnitude of the limit | What the second operator cannot calculate without the crew member |
|---|---|---|---|
| Duty time | 7 consecutive days | 60 hours | The duty hours of the previous six days, standby included |
| Duty time | 14 consecutive days | 110 hours | The detail of the duties, not the number of days worked |
| Duty time | 28 consecutive days | 190 hours | The positioning and training days assigned elsewhere |
| Flight time | 28 consecutive days | 100 hours | The actual flight hours, block to block, not the planned hours |
| Flight time | Calendar year | 900 hours | The running total since 1 January, all operators combined |
| Flight time | 12 consecutive months | 1,000 hours | A rolling total that no operator’s tool keeps |
| Minimum rest | From one duty to the next | At least the length of the preceding duty, with a floor at home base | The actual end time of the last duty, with the other operator |
| Extended recovery | Maximum interval of 168 hours | 36 hours including two local nights | The dates of the last block genuinely free of duty and standby |
These orders of magnitude are those of the baseline scheme applicable to commercial air transport by aeroplane. An approved scheme, a variation or a collective agreement may be more restrictive, and the schemes for cabin crew or for other operations differ. What does not vary is the mechanism: the window rolls, and it counts everything.
The calculation that matters is forward-looking. At the moment the Friday assignment is accepted, the total of the window that will end on Friday evening has to be projected, including the duties already rostered with the other operator when the window encompasses them. Noting after the event that a limit has been exceeded does not cancel the exceedance: it documents it.
Rest cannot be shared
A rest period is defined by what it excludes: an uninterrupted period during which the crew member is free from all duty and all standby. The decisive word is all. A day off granted by the first operator is not rest if the second places a standby in it, even one never called out, even at home. It becomes at best two fragments, neither of which reaches the required length.
This mechanism is more constraining than the hourly limits, and it is almost always the one that bites first. The minimum rest before a duty is calculated from the preceding duty, whoever assigned it, with a floor at home base and at least the length of that preceding duty. The recurrent extended recovery rest period, for its part, requires under the baseline scheme a block of the order of thirty-six hours including two local nights, with a maximum interval typically set at one hundred and sixty-eight hours between the end of one and the start of the next; an approved scheme may be more demanding.
This two-night block is exactly what dual activity nibbles away. The freelance crew member fills his empty days: that is the very principle of his business model, and that is what gives value to a direct connection with operators. The result is a calendar in which each party sees an airy roster, while in reality not a single clean thirty-six-hour window is left. No one cheated; no one looked at the same calendar.
The trap: the once-and-for-all declaration. Many services contracts contain a line by which the crew member declares that he does not work for another operator, or undertakes to report it. Signed at the outset, it is true that day and out of date the following week. It protects the operator on paper and protects no one’s flight: what is needed is a declaration attached to every request, carrying the projected totals, and not a box ticked in a contractor registration file.
Two home bases, two sets of local nights
Each operator assigns the crew member a home base, and only one. Nothing prevents the two bases from differing, including by several time zones. Yet the base determines the local night, the reference time and the acclimatisation state, and therefore the maximum flight duty period admissible for a given duty start time. Two operators can thus apply, on the same day and to the same crew member, two different tables, each one correctly.
The journey between the two bases adds a grey area. If it is not assigned as positioning, it is not duty; nor is it useful rest, since it is spent in a station, in a car or in a cabin. Formally it consumes no counter; physiologically it consumes the very resource that rest is supposed to restore. A crew member who strings together a night on a train between two bases is compliant and tired, and that is exactly the situation the personal fitness declaration is designed to stop.
The right reflex: keep a single consolidated log, by days and not by contracts. One line per duty period, whoever assigned it, with the start time, the end time and the base of attachment; the totals for the four windows can then be read at a glance, and the answer to the second operator is given in writing before accepting. This log is also the only document that covers both operators at once: each of them will only ever keep its own share.
Who answers when the limit is exceeded
Responsibility is shared, but it is not shared equally depending on the nature of the breach. The operator answers for its rostering and its records: compliant rosters, keeping of flight, duty and rest times, and the ability to show that it collected the information relating to activities carried out elsewhere. The crew member answers for what he declares and for what he accepts: providing each operator with the necessary data, and refusing a duty that would cross a limit or that he does not know himself fit to perform.
In the event of an exceedance, the question asked by the oversight authority is therefore not only who was at fault, but at which link the information stopped. If the operator never asked, the shortcoming lies in its management system and is dealt with at certificate level. If it asked, dated and kept an inaccurate answer, the shortcoming lies with the crew member, and it touches a licence, not a contract. It is this asymmetry that makes the matter sensitive for a freelance: a contract comes to an end, whereas a measure recorded on a licence is recounted for years in interviews.
The economic imbalance aggravates this risk. The employee who refuses a duty is applying a company rule; the freelance who refuses forgoes revenue and risks not being called again. The regulatory framework does not compensate for this imbalance, and that is why it places the written, dated declaration at the centre of the arrangement: it is the only object over which the crew member keeps complete control, and the only one that, after an event, will say what he knew and what he passed on.
What to check in your own documentation
Three checks are worth making before the next request. The first: which limitation scheme each operator actually applies, and which of the two is the more restrictive. The counters are shared, but the thresholds applied may differ, and it is the stricter one that governs the assignment with that operator. The second: the exact form each operator gives to the declaration of outside activity, who keeps it and for how long. The third: what each of them counts as duty.
This last point is the most underestimated. A simulator session is not a flight, but it is work; a day of instruction for a third-party training organisation, an assigned positioning or a standby at home do not weigh the same way depending on the scheme, and above all depending on the entity that assigns them. For anyone preparing a type rating while maintaining line activity, the course calendar has to be laid over the same diary as the assignments, before committing: a compact course and a maintained freelance activity mechanically produce a run of weeks with no compliant recovery period. The type rating courses make no provision for a slot for parallel activity: it is up to the candidate to build one.
One grey area remains. An aeronautical activity carried out outside an operator holding an approval — aerial work, instruction at a flying club, private flying — does not fall within the definition of duty performed on behalf of an operator. No counter is troubled by it. Yet it takes up the time that rest assumes to be available, and it is invisible to both operators and to the duty log alike. This is where declared fitness stops being a formality and becomes again what it is: the last check, and the only one that sees the whole.
These reference points have explanatory value only. The applicable regulation, the limitation scheme approved for each operator and that operator’s approved documentation prevail over this article in the event of divergence: for a given assignment, it is the operations manual of the operator that assigns it that governs.
Questions fréquentes
Do the counters go back to zero when you change operator?
No. Cumulative windows bear on the person, not on the contract: they add up every duty performed on behalf of an operator, whichever it may be. An assignment flown for the first operator weighs on the seven-, fourteen- and twenty-eight-consecutive-day totals that will be applied by the second. No change of client, of home base or of aircraft type opens a clean slate.
Who has to declare what when you fly for two operators?
The crew member must provide each operator with the data needed to build a compliant roster, and each operator must keep records that also cover the activities carried out elsewhere. In practice, the operator asks for and keeps a dated answer; the crew member re-declares at every request, and not once only when the framework agreement is signed. An old declaration says nothing about the current window.
Does a standby with the second operator that is never called out break the rest granted by the first?
Yes. A rest period is an uninterrupted period free from all duty and all standby. A standby placed in the middle of a free day splits it into two fragments, neither of which generally reaches the required length. This is the mechanism that bites earliest in a multi-operator configuration, well before the cumulative hourly limits.
Can you have two home bases?
Each operator assigns one base and one only, but nothing prevents the two bases from differing, including by several time zones. Each then calculates the local night, the reference time and the acclimatisation state from its own base, and may apply a different maximum duty table to the same crew member on the same day. The journey between the two bases is generally neither duty nor useful rest.
Does a simulator session or a day of instruction count?
It is not flight time, but it is work, and depending on the applicable scheme and on the entity that assigns it, it falls under duty time. A day spent at the training centre is in any case not a rest day and cannot be used to make up an extended recovery rest period. A rating course run alongside line activity must therefore be laid over the same diary as the assignments.
What happens if the second operator asks nothing?
The absence of a question exempts no one from anything. In the event of an exceedance, the shortcoming is read first in the operator’s management system, which must collect and record that information; but the crew member remains bound to refuse a duty that would cross a limit. The two responsibilities coexist, and the crew member’s bears on his licence, not only on a contract.

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