End-of-Month Carry-Forward: The Rule That Stops the Calendar Drifting

A pilot in a cockpit at dusk, reviewing a crew record on a tablet, with runway lights visible outside.

A validity date looks like the simplest thing in a crew file: a check was flown, it counts for a number of months, and here is when it runs out. It is not simple, because two separate conventions are at work — one that rounds deadlines to the end of a month, and one that counts backwards from the expiry rather than forwards from the check. Together they stop the training calendar sliding earlier year after year. Applied to the wrong item, or read in the wrong direction, they produce a flight nobody notices is non-compliant until an audit finds it.

Two clocks in the same file

Open any crew record and you will find deadlines that behave in fundamentally different ways. Some are expressed in calendar months and expire at the end of a month regardless of the day the event took place. Others are rolling windows counted in days, which move continuously and never round to anything. A licence proficiency check, an operator proficiency check, a line check, recurrent safety equipment training and dangerous goods training belong to the first family. Recent experience — the takeoffs and landings a pilot must have accomplished in the preceding period — belongs firmly to the second.

The two are handled by the same planning system, printed on the same page and, very often, reasoned about with the same mental model. That is where the errors start. A rolling window has no end-of-month generosity and no look-back window; it is either satisfied at the moment of the flight or it is not.

The two families of deadline and how each is counted
Family Typical items How it is counted Rounding Look-back window
Calendar-month validity Licence and operator proficiency checks, line checks, recurrent and emergency equipment training, rating validity A number of calendar months from a reference date Expires at the end of the month Yes, in the rules that provide one
Rolling window in days Recent experience for takeoffs and landings, and other currency requirements expressed in days A fixed number of days counted backwards from the moment of the intended flight None None — the concept does not apply
Programme cycles Multi-year training programmes covering a syllabus over several cycles Elements distributed across the cycle Depends on the programme approval Governed by the approved programme, not by the item’s own validity
Medical certification Class of medical certificate held A period fixed by the certificate, varying with age and class None; the certificate states its own expiry date A look-back window exists in the European rules, expressed in days rather than months

What « calendar month » actually buys you

When a rule says a check is valid for a number of calendar months, the count does not run from the day of the check to its anniversary. It runs to the end of the month in which the anniversary falls. A twelve-calendar-month item completed on 3 March is valid until 31 March of the following year, not until 3 March. The holder gains the remainder of the month, up to almost a full extra month, for free.

This is not a loophole; it is a planning device. It converts a date into a month, and a month is the unit rosters are actually built in. It also means that the correct question in crew planning is never « on what day does this expire » but « in what month is this due » — and that a check flown on the 1st and a check flown on the 28th of the due month produce exactly the same result.

The look-back window is an anti-drift device, not a bonus

Now the second convention, and the one that is genuinely misread. Rules that carry a validity period generally allow the item to be re-accomplished some time before it expires, and when that is done inside a defined window preceding the expiry, the new validity period is counted from the original expiry date — not from the date of the check. In Part-FCL, the revalidation of a class or type rating uses the three months immediately preceding the expiry date in exactly this way; the operator training and checking rules are built on the same construction, with the window set by the applicable requirement.

Understand what this is for. Without it, every check flown a few weeks early would permanently move the deadline earlier, and the following year’s check would move it earlier again. Over a career the whole cycle would creep backwards through the calendar, and a twelve-month item would end up being flown more often than once a year. The look-back window freezes the anchor month. It is a correction applied to protect the planning system from its own operational reality — because a check can rarely be flown on the exact day it is due.

Three properties follow, and each one is where somebody goes wrong.

  • It looks backwards from the expiry, never forwards from the check. The question is always « is the check inside the window that precedes this expiry », not « how long ago was the last one ».
  • It never extends the current validity. Flying the check early does not buy extra time now; it only protects the future anchor. The item still expires on its original date if nothing else happens.
  • It does not chain. The window restores the original month and stops there. It cannot be used twice to push one deadline progressively further out, and it never carries a second item forward with it.

The look-back window is a safety net that keeps your training deadlines from slipping earlier in the year. If you do your check early (but within the window), it doesn’t give you extra time now—it just makes sure next year’s check is still due in the same month. If you do it too early, you lose time and mess up the schedule.

A pilot’s type rating expires on 31 March 2024. The look-back window is 3 months. If they do the check on 15 February 2024 (inside the window), the new validity runs from 31 March 2024 to 31 March 2025. If they do it on 10 December 2023 (outside the window), the new validity runs from 10 December 2023 to 31 December 2024—losing 3 months of validity.

The arithmetic, done four ways

The mechanism is easier to trust once the numbers are on the table. Take an item with a twelve calendar-month validity and a three-month look-back window — the common shape, though the applicable rule for each specific item is what governs. The last check was flown on 14 March of Year 1, so the item is valid to 31 March of Year 2, and the window that precedes that expiry covers January, February and March of Year 2.

One item, four ways of re-accomplishing it
When the new check is flown Inside the window? New period counted from New expiry Net effect
20 March, Year 2 Yes 31 March, Year 2 31 March, Year 3 Anchor month preserved
5 February, Year 2 Yes 31 March, Year 2 31 March, Year 3 Nearly two months early and nothing is lost
10 December, Year 1 No — before the window opens The date of the check 31 December, Year 2 Three months of validity permanently given up, and the anchor month has moved
5 April, Year 2 No — the item has already expired The date of the check 30 April, Year 3 Not a revalidation at all; the privilege was unavailable between 1 and 5 April

The third line is the expensive one, and it is entirely self-inflicted. A check flown a few days too early — outside the window rather than inside it — costs a full slice of validity that can never be recovered, and it shifts the anchor month for every subsequent cycle. This is why the date the window opens matters as much in crew planning as the expiry date, and receives a fraction of the attention.

The right habit. Plan against the date the window opens, not against the date the item expires. Once the window is open, any day inside it produces an identical result, which gives the planners weeks of latitude at zero cost. One day before it opens, the same check destroys months of validity. Only two dates in the cycle turn on a single day: this one and the expiry itself.

Rolling windows do not round and do not carry forward

Recent experience is the item most often contaminated by calendar-month thinking. Where a rule requires a number of takeoffs and landings within a preceding number of days, that period is counted in days backwards from the intended flight. There is no end-of-month extension, no look-back window, and no notion of a due month. A pilot whose qualifying landings fall out of the window at 23:59 is not current at 00:01, whatever the roster’s monthly view suggests.

The practical consequence for planning is that these two families need different treatment in the same system. Calendar-month items are planned by month and tolerate being brought forward inside the window. Rolling-day items must be checked against the actual date of the flight being planned, every time, and they cannot be satisfied in advance in any meaningful sense — accomplishing landings early simply moves the window, and the window keeps moving.

The trap. A roster tool configured to count every deadline from the date of the event rather than from the expiry. It never produces a visibly illegal plan, so nobody investigates it — but it quietly shortens every validity in the company, drags the anchor months backwards year after year, and generates checks that should not have been needed. The mirror-image configuration, counting from the expiry when the check was flown outside the window, is the dangerous one: it shows a validity the rule does not grant, and the flight built on it is non-compliant.

Once the date has passed, it is a different procedure

An expired item is not a late item. The distinction has a name in the licensing rules: revalidation is what happens while the privilege is still alive, renewal is what is required once it has lapsed, and they are not interchangeable. Revalidation restores the period. Renewal generally requires refresher training whose content and volume are determined by an approved training organisation, sometimes in agreement with the authority, and scaled to how long the lapse has lasted and what the holder has been doing meanwhile.

The same logic applies to operator recurrent items, though the mechanism is different: the crew member simply may not exercise the privilege until the item has been re-accomplished, and the operator’s approved programme sets out what has to be done after various lengths of absence. In both cases the new validity is counted from the date of the new check — the anchor month is lost, and it will stay lost until somebody deliberately plans a cycle to bring it back, which is a decision to give up validity on purpose.

Where the operations manual is stricter than the rule

The regulatory deadline is a floor, not a target. Operators routinely impose internal validities shorter than the regulatory ones, or narrower windows, for reasons that are entirely legitimate: a fleet with limited simulator access, a training footprint that has to be smoothed across the year, a customer requirement, or an insurer’s condition. Where the operations manual is stricter, the operations manual is what governs the crew member’s ability to operate, even though the licence remains regulatorily valid.

Two people in an aircraft cockpit use a tablet showing a calendar with a green arrow.
Calendars align precisely to prevent timekeeping errors.

The reverse never applies. No internal arrangement, no roster tool configuration and no manager’s decision can extend a validity beyond what the applicable rule allows. Where an extension genuinely exists it comes from the authority, under conditions written in the rule, and it is documented — not assumed because the aircraft was somewhere else on the due date.

Frequent misreadings and what actually happens
What is believed What the mechanism does
« I flew it early, so I gained time now » Nothing is gained now. The current period ends on its original date; only the next anchor is protected
« I flew it early, so I lost time » Only if the check was outside the window. Inside it, early costs nothing at all
« The check is due on the anniversary of the last one » Calendar-month items are due at the end of the anniversary month, not on the day
« The window can be used again to push the date further » It restores the original month and stops. It cannot be chained, and it never moves two deadlines at once
« A combined check revalidates everything to the same date » Each item keeps its own period and its own anchor. One combined event can leave one item anchored and another reset
« Recency works like the other deadlines » Rolling windows in days have no month rounding and no look-back. They are evaluated against the date of the flight
« Planning has it under control » The privilege is held by the individual. A planning error does not transfer the consequence

Who carries the consequence

Responsibility here is genuinely shared, and shared does not mean halved. The operator must keep records demonstrating that every crew member was qualified for every flight operated, and a discrepancy is an operator finding. But the privilege belongs to the licence holder, who is required to satisfy themselves that they may exercise it. When a flight turns out to have been operated with a lapsed item, both are exposed: the operator through its certificate and its records, the individual through their licence.

What follows a discovery is worth knowing in advance rather than improvising. The flight was operated outside the approved conditions, which the operator has to handle as an occurrence and report where the applicable rules require it; the item has to be re-accomplished under the renewal path rather than the revalidation one; and the root cause is almost always systemic — a tool configured wrongly, a window misread, or a combined event assumed to have covered more than it did. Crews comparing how different operators configure these cycles will find the practical detail discussed in training circles and on formations.fl330.com.

Building a cycle that does not drift

Everything above reduces to four working rules. Know which family each deadline belongs to, because the two are counted by incompatible methods. Plan against the opening of the window rather than the expiry, since that is the only date where a day matters. Treat the anchor month as an asset worth protecting, because losing it is permanent and quiet. And check the assumption your planning tool is actually making, since a system that counts from the wrong end of the period will either waste validity for years or produce a flight that should never have departed — and only one of those two failures announces itself.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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