Regulations

EASA FTL rules (ORO.FTL): the complete crew planning guide

SkAI Tech · Published on 31 August 2026

EASA flight time limitations (Part-ORO, Subpart FTL) cap how much commercial air transport crews in Europe may fly, work and how little they may rest: no more than 900 flight hours per calendar year, a basic flight duty period of at most 13 hours, and minimum rest of 10 to 12 hours. Every compliant roster is built inside those boundaries.

If you build rosters for a living, ORO.FTL defines the shape of your solution space. This guide walks through the limits one by one, as a planner meets them in practice.

What is ORO.FTL?

ORO.FTL is the Flight Time Limitations subpart of Part-ORO in the EU Air Operations Regulation (Regulation (EU) No 965/2012, amended by Regulation (EU) No 83/2014). In force since 18 February 2016, it applies to EU-certified commercial air transport (CAT) aeroplane operators and replaced the older EU-OPS "Subpart Q".

Three scope points that matter in practice:

• Air taxi, emergency medical service (EMS) and single-pilot CAT operations are carved out: they remain under national rules until EASA adopts specific requirements. A business jet operator may therefore sit under a different regime than a scheduled carrier; always confirm against the AOC and the competent authority.
• ORO.FTL is implemented through each operator's individual flight time specification scheme, approved by its authority. Two compliant operators can run different internal rules.
• FTL sets a regulatory floor. Collective agreements and company rules almost always sit on top, and the roster has to satisfy both layers at once.

What are the cumulative flight and duty limits?

The ORO.FTL.210 ceilings every planner should know cold:

Note that all of these except the calendar-year cap are rolling windows. An assignment that is legal today can silently make a pilot unavailable next week, because it pushes a 28-day counter over the line at that point. Rolling windows are precisely what spreadsheets are worst at: every new assignment changes the arithmetic of the whole window, in both directions.

What is a flight duty period (FDP) and how is it capped?

The flight duty period runs from report time until the aircraft finally comes to rest after the last sector. It includes briefing, turnarounds and ground time, not just block hours.

The basic maximum daily FDP is read from a table with two inputs:

1. Report time (in the time zone the crew member is acclimatised to): up to 13:00 for a favourable daytime start, stepping down to 11:00 for the most penalising night starts.
2. Number of sectors: minus 30 minutes per sector from the third sector onwards, with a floor of 9:00.

Two concepts drive that table:

• The Window of Circadian Low (WOCL), 02:00-05:59: the body-clock trough. FDPs that infringe it are reduced, which is what punishes early starts and late-night finishes.
• Acclimatisation: after enough time-zone crossings, a crew member is no longer "on local time", and different (usually stricter) values apply.

Can the maximum FDP be exceeded?

Yes, through three separate mechanisms, each with its own logic:

• Planned extension without in-flight rest: up to 1 extra hour, at most twice in any 7 consecutive days. It is paid for in rest — either 2 extra hours on both the preceding and the following rest period, or 4 extra hours on the following one — and it is capped by sectors: 5 sectors where the WOCL is not infringed, 4 where it is infringed by 2 hours or less, 2 beyond that. Extensions are a planning tool to be used deliberately; a roster that needs them routinely to cover the programme is simply under-crewed.
• In-flight rest with an augmented crew: with additional flight crew and an onboard rest facility, CS FTL.1.205 raises the maximum FDP to 16:00, 15:00 or 14:00 with one additional flight crew member (rest facility class 1, 2 or 3), and 17:00, 16:00 or 15:00 with two. This is the long-haul regime, and the class of the rest facility is worth as much as an extra body.
• Commander's discretion: for unforeseen circumstances arising at or after report time, the commander may extend the FDP by up to 2 hours (3 hours with an augmented crew). It is a real-time safety valve, reported to the authority, never a planning parameter. A roster that only works if commanders keep using discretion is not compliant.

What are the rest requirements?

ORO.FTL.235 sets the minimum rest before an FDP:

• At home base: at least 12 hours, or as long as the preceding duty if that is longer.
• Away from base: at least 10 hours, or as long as the preceding duty if longer, and it must allow an 8-hour sleep opportunity once travel and physiological needs are accounted for.

On top of this sits the recurrent extended recovery rest: at least 36 consecutive hours including 2 local nights, with never more than 168 hours between the end of one and the start of the next, and twice a month that rest extends to 2 local days. In practice this rolling "weekend" is the skeleton of any monthly roster: you place it before you place a single flight.

Standby has its own crediting rules towards FDP and duty. That topic deserves its own article, and it is a particularly live one for charter and medevac operators.

Why is FTL compliance so hard to keep by hand?

Every single assignment touches, at once: the FDP table (report time × sectors), the WOCL, acclimatisation state, three rolling flight-time counters, three rolling duty counters, pre-duty rest, the 168-hour recovery-rest clock, extension budgets, and whatever the collective agreement adds. Across even a modest fleet and a few dozen crew members, the combinatorics outgrow what a spreadsheet can verify reliably, and every disruption (a delay, an AOG, a sick call) invalidates part of the checking already done.

December 2025 showed what happens when planning falls behind the rule. IndiGo, which carries roughly 65% of India's domestic market, cancelled more than 4,500 flights in ten days after failing to adapt its rosters to India's revised flight duty time limitations (FDTL), introduced back in January 2024 (Kumar, 2025, IJFMR). The airline put the financial impact of those disruptions at ₹577.2 crore (~USD 65m) for the quarter, and its quarterly net profit fell 78%, a fall to which the disruptions contributed without being the only cause (ThePrint, 2026). A different regulatory regime, but the same mechanics: when planning cannot keep up with the rule, the whole programme breaks.

This is exactly the problem a constraint-based optimisation engine solves: generate a roster in which every assignment is checked against all the rules (ORO.FTL, regional rules and the operator's own) in minutes rather than days. That is SkAI Tech's approach, as an add-on to the operations system you already run, with an observed average generation time of 12 minutes.

FAQ

Does ORO.FTL apply to business aviation?

To CAT aeroplane operations, yes. Air taxi, EMS and single-pilot operations are exempted, though, and remain under national rules. Many European business aviation operators therefore fly under a national regime that resembles, but is not, ORO.FTL. What applies depends on the AOC; confirm with the authority.

Flight time, duty, FDP: what's the difference?

Flight (block) time runs off-blocks to on-blocks. The FDP runs from report to the end of the last sector. Duty covers any task performed for the operator, flying or not: simulator, training, positioning. Each has its own ceilings, and a roster must respect all three.

Is an FTL-compliant roster a safe roster?

Not automatically. FTL draws a legal boundary and does not model fatigue: a pairing can be legal and still exhausting. That gap is what Fatigue Risk Management Systems and biomathematical fatigue models address; we cover them in a dedicated article.

What happens if a limit is breached?

Outside properly reported commander's discretion, a breach is a non-compliance: it must be reported and analysed, and it surfaces in audits. One more argument for rosters that are verified at generation time instead of patched after the fact.

Sources

• Regulation (EU) No 965/2012 and Regulation (EU) No 83/2014, laying down the air operations requirements and Subpart FTL.
• EASA, Easy Access Rules for Air Operations — Part-ORO Subpart FTL and CS FTL.1, the consolidated reference for every value quoted above.
• National authority material (in France, the DGAC) for the air taxi, EMS and single-pilot regimes left outside ORO.FTL.
• Kumar, S. (2025), IndiGo Airlines Crisis 2025 — A Critical Analysis of India's Largest Aviation Disruption, IJFMR 7(6).
• ThePrint / PTI (2026), IndiGo Q3 profit plunges 78 pc to Rs 549 cr; ops disruptions cause Rs 577 cr financial impact.

All resources