Almost every dispute about flight time limitations turns out, on inspection, to be a dispute about a single instant: the moment the flight duty period is deemed to have begun. Move that instant by twenty minutes and the maximum permitted duty can fall by far more than twenty minutes, a rest period already taken can become insufficient, and an extension that looked available can cease to exist. The start point is not an observation of when the crew happened to arrive. It is a value the operator fixes, and every other number in the scheme is computed from it.
Report time is a decision, not an observation
Report time is the critical anchor for flight duty calculations. Both major limitation schemes anchor the flight duty period to reporting. In the European rules, the flight duty period begins when a crew member is required to report for a duty that includes a sector, and ends at on-blocks of the last sector flown. The United States rule is built the same way: the flight duty period begins when a flightcrew member is required to report for duty with the intention of conducting a flight, a series of flights, or a positioning or ferry flight, and ends when the aeroplane is parked after the last flight, with no further movement intended by the same crew member.
The load-bearing words are required to report. Nothing in either text says the clock starts when the crew walks through the door. Reporting times are specified by the operator in its operations manual, and they are supposed to be realistic: long enough for briefing, flight preparation, meteorological and notice review, security screening, the walk-around and boarding. A reporting time set for rostering convenience rather than for the work that actually has to be done is a defect that never appears in any of the numbers, because the numbers all start after it.
Two practical consequences follow immediately. A crew that arrives forty minutes early out of habit does not start its own flight duty period early. And a crew instructed by operations control to be at the aeroplane earlier has been given a new reporting time, whether or not anyone uses that phrase, with every downstream consequence attached.
The report instant starts four clocks, and they do not stop together
The single most common source of error is treating duty, flight duty period, flight time and rest as one quantity measured on one scale. They are four distinct objects with different triggers, and only the first three start at or after the report. Rest is the one that has to be verified backwards.
| Clock | Starts | Stops | What it limits |
|---|---|---|---|
| Duty period | At the report time for any assigned task, flying or not | When the crew member is free of all duties, post-flight tasks included | Cumulative duty over rolling windows of days, and the days-off pattern |
| Flight duty period | At the report time for a duty that includes at least one sector | At on-blocks of the final sector | The daily maximum read from the table, and the availability of extensions |
| Flight time | When the aeroplane first moves for the purpose of taking off | When it comes to rest at the parking position and the engines are shut down | Cumulative flight time over rolling windows and the calendar year |
| Rest period | Only once the preceding duty period has genuinely ended | At the report time of the next duty | Whether the next duty may legally be commenced at all |
Note the asymmetry in the second and fourth rows. The flight duty period ends at on-blocks, but the duty period does not: post-flight paperwork, debriefing, technical log entries and transport arrangements continue to count, and the rest period only begins when those have finished. A crew that computes its rest from on-blocks rather than from the true end of duty will overstate it, systematically, by the same amount every day.
The report time starts multiple clocks, but they don’t all stop at the same time. Flight duty ends when the plane parks, but actual work duties (like paperwork) can extend it, affecting rest periods. Ignoring this can make rest periods seem longer than they really are.
An Airbus A320 crew reports at 05:00 for a 06:00 departure. After landing at 18:00, they spend 30 minutes on paperwork. Their rest period starts at 18:30, not 18:00, even though the flight duty period ended at 18:00. If their next report is at 05:00 the next day, they only get 10.5 hours of rest instead of the required 12.
The table has bands, and bands have edges
The daily maximum flight duty period is not a single figure. It is read from a table indexed by the reporting time expressed in the reference time zone to which the crew is acclimatised, and by the number of sectors to be flown. The start-time axis exists because a duty commencing in the early hours cuts into sleep and may touch the window of circadian low; the bands covering the middle of the day are the most generous, and the maxima fall away on either side of them.
Because the axis is banded rather than continuous, it has edges. A reporting time near a band boundary and one a few minutes on the other side of it sit in different rows, and the difference between adjacent rows is a fixed step of the table rather than a proportional adjustment. A report advanced far enough to cross several bands loses several steps at once, and the total loss can exceed the size of the change that caused it. This produces the counter-intuitive result that matters most in daily operations: pulling a report time earlier does not simply make the day longer. It can simultaneously make the permitted day shorter. Both quantities move in the wrong direction at once, and the margin between them can close far faster than the change to the schedule suggests.
The trap. A schedule change that advances report by a quarter of an hour looks harmless because it is compared against the wrong baseline. The correct comparison is not « fifteen minutes more duty » but « fifteen minutes more duty against a maximum that may have dropped a whole row. » Check the row before checking the clock.
Everything that happens before the first take-off
The report instant is rarely the moment the crew reaches the aeroplane it will fly. Positioning, standby and ground duties all sit between the two, and each is treated differently. The European scheme is explicit that positioning — travelling as a passenger at the operator’s behest, the journey between home and the designated reporting place excepted — counts as duty, and that positioning immediately preceding an operating duty falls inside the flight duty period without adding a sector. That combination is punishing: a long road transfer to another aerodrome consumes the flight duty period at full rate while attracting none of the table’s compensation, because the table only compensates for sectors.
| Event | Counts as duty | Inside the flight duty period | Adds a sector |
|---|---|---|---|
| Positioning by road or rail immediately before operating | Yes, in full | Yes | No |
| Positioning by air immediately before operating | Yes, in full | Yes | No |
| Airport standby followed by an assignment | Yes, in full | Normally counted from the report for standby | No |
| Standby away from the aerodrome, then called out | Partly, at a proportion fixed in the certification specifications | From the report for the assigned duty, with the maximum reduced once the standby has run long enough | No |
| Ground duty on the same day before flying, such as training or a simulator detail | Yes, in full | Depends on the operations manual; assume yes unless it says otherwise | No |
The standby rows are where the largest surprises live. Airport standby is normally counted from the report time for the standby itself, so an assignment arriving several hours into it begins with a flight duty period that is already several hours old. Standby elsewhere is counted at a proportion, and beyond a threshold it starts to erode the maximum for whatever flying follows. The proportions and thresholds are set in the certification specifications and may be tightened in the operator’s own manual, so the figure that applies is the one in Part A, never a remembered number from a previous employer.
Rest is measured backwards from the report, and cannot be repaired afterwards
Minimum rest before a duty is a function of the preceding duty and of whether the crew is at home base or away from it. The period must be free of all duties and, critically, it is bounded at one end by the true end of the previous duty and at the other by the report time of the next. It is therefore the only quantity in the scheme that a change to the report can invalidate retrospectively.
The mechanism is worth stating plainly. If the report is advanced, the rest that has already been taken shrinks by exactly that amount. If it falls below the minimum, the following duty is not legal — not because it is long, but because the rest that preceded it was short. This check has to be made at the moment the change is offered, not after the crew has reported, because by then the only remaining options are disruptive ones.
The right reflex. Before accepting any change to a report time, answer two questions in order. Does the preceding rest still meet the minimum when measured to the new report? And does the new report still fall in the same band of the table? Only then look at whether the day fits.
One moved report time, and everything that follows it
The cascade is easier to see laid out than described. Each row below is a separate check, and an operation that only performs the first one is not verifying legality; it is verifying arithmetic.
| What moves | Immediate effect | Second-order effect |
|---|---|---|
| Preceding rest | Shortened by the same amount | May fall below the minimum, making the whole duty unlawful before it starts |
| Row of the daily table | May cross into one or more earlier start bands | Maximum flight duty period reduced by one step of the table for each band crossed |
| Classification of the duty | May become an early start or a disruptive schedule | Triggers separate limits on consecutive occurrences and on the rest that must follow |
| End of the flight duty period | Earlier on-blocks if the schedule moves with it, unchanged if only the report moves | If only the report moves, the day is longer against a shorter maximum |
| Cumulative counters | Duty hours added in the rolling windows | Can breach a weekly or monthly ceiling several days later, invisibly |
| Extension availability | Baseline maximum changes | An extension believed to be in hand may no longer bring the duty inside the limit |
Extensions and commander’s discretion both measure from the baseline
The European scheme permits a limited extension of the basic maximum flight duty period: a fixed increment, usable only a small number of times within a rolling seven-day window, not combinable with split duty or with in-flight rest, and accompanied by an increase in the rest that precedes or follows it. It is a planning instrument, applied before the day begins. Commander’s discretion is something else entirely — a power exercised in response to circumstances that could not have been foreseen, subject to consultation with the crew and to a report to the operator and, past a threshold, to the authority.
Both are expressed as a quantity above a maximum, which means both are meaningless if the maximum was computed from the wrong start point. A discretion report that states an overrun of thirty minutes, when the underlying maximum was an hour lower than the one used, describes an event that did not happen and conceals one that did. This is the mechanism by which a rostering error becomes a reporting error, and then a data quality problem in the operator’s own fatigue analysis.
The two systems also diverge here, and the divergence is worth knowing before quoting either as universal. The United States rule draws its line at take-off: unforeseen operational circumstances arising before take-off open a bounded extension of the flight duty period, while those arising once the aeroplane is airborne are handled under a separate provision, with a duty to report beyond a set threshold in either case. The European scheme frames its planned extension and its in-flight discretion as separate instruments with separate conditions. Operators of both certificate types exist inside the same alliances, and crews move between them; the vocabulary is similar enough to be misleading.
Records: the operator proves it, the crew reconstructs it
Operators are required to keep records of duty periods, flight time and rest for a defined period and to make them available on request. Those records are built from the instants that were applied, which is precisely what is in dispute whenever something goes wrong. A crew member’s own record is the only independent account of the same events, and it is worth very little unless it captures the right fields.

Four entries do almost all the work: the report time actually applied and, if it differs from the published one, who changed it and when; the start and end of any positioning; the moment a standby call-out was received; and on-blocks of the final sector, distinguished from the moment duty genuinely ended. With those four, any duty can be reconstructed against the table months later. Without them, a crew arguing about legality is arguing from memory against a database, which is not an argument. Practical comparisons of how different operators publish and change report times are discussed at forums.fl330.com.
The general principle is unglamorous and holds everywhere. A limitation scheme is a function, and the report instant is its first argument. Every table lookup, every rest check, every cumulative counter and every extension is downstream of it. Getting the rest of the calculation right while guessing at the start point is not compliance; it is a well-presented result to the wrong question.

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