EASA ORO.FTL.205 Explained — A Pilot's Working Guide

EASA ORO.FTL.205 is the clause that defines your maximum Flight Duty Period — the longest stretch of time you may legally be on duty for the purpose of operating a flight. It looks simple on paper. In practice it has more moving parts than the average modern airliner's FCOM.

This article is a working guide. We won't reprint the regulation verbatim — your authority publishes it for free — but we will walk through the parts that actually decide whether you can fly the trip in front of you.

What ORO.FTL.205 actually says

In one sentence: your maximum FDP depends on your reporting time and the number of sectors you'll fly. Everything else — extensions, encroachment, split-duty, in-flight rest — is a modifier on top of that base value.

The base table runs across two axes:

• Reporting time — when you sign on, in local base time. The table spans roughly 06:00 to 04:59 in 30-minute or one-hour bands.
• Sectors — 1, 2, 3, 4, 5, 6, 7, 8+. Each sector knocks 30 minutes off the maximum.

A long-haul captain reporting at 09:00 for a single sector gets the most generous slot in the table — 13 hours of FDP. A short-haul first officer reporting at 04:30 for six sectors gets one of the tightest — under 10. Both of you may be perfectly legal, but the math behind your day is structurally different.

WOCL — the regulator's bedtime

The Window of Circadian Low (WOCL) is the band 02:00 to 05:59 base time. It exists because human alertness collapses there, regardless of how rested you think you feel. ORO.FTL.205 penalises duty that encroaches the WOCL — meaning your duty starts before, during, or finishes inside it.

Encroachment shortens the maximum. The most generous slots in the table sit comfortably outside WOCL. The tightest are the ones where the regulation is explicitly trying to discourage you from flying.

"The numbers in the FDP table aren't recommendations. They're upper bounds. Your operator's manual may apply company limits below them — and your fatigue reporting culture should sit lower still."

Reporting time vs. block-off time

An easy trap. Reporting time is when your duty starts — typically 60 to 90 minutes before scheduled departure for line operations. The FDP clock starts at reporting and stops at on-blocks of the final sector. Block-off time is irrelevant to FDP calculation; it's the reporting time that goes into the table.

Extensions — when the legal max stretches

ORO.FTL.205 allows the basic maximum to be extended by up to 1 hour, but only under tight conditions:

1. The extension cannot be planned. It has to be a response to operational disruption — slot delay, ATC re-routing, technical issue.
2. It cannot be used twice in seven consecutive days.
3. The commander must declare the extension and document it.
4. Some operators apply additional contractual limits — your agreement may restrict extensions further.

The extension is not a tool your roster department can dispatch you with. If a roster shows you an FDP that already exceeds the base table by 45 minutes, what they're publishing is illegal — even if "an extension is available" in their planning software.

Split-duty — splitting one duty in two

Split-duty is the regulation's way of acknowledging that some operations — particularly cargo and long-haul positioning — naturally fall into two flying segments separated by a meaningful break.

Under ORO.FTL.225, if you receive a rest break of at least 3 hours during a duty period (with a horizontal sleeping surface and protection from noise/light), the maximum FDP can be extended by a portion of that rest. The math is roughly:

• Rest of 3:00 to 6:00 hours: extension equals rest minus 2:00, capped
• Rest of 6:00 hours or more: full split-duty applies, extension can reach the full 4 hours
• The rest must be entirely between two flying duty segments
• The accommodation requirements are non-negotiable — a crew lounge with a couch may not qualify

What pilots get wrong about split-duty

Two common mistakes:

One — "the rest counts even if I'm in transit." No. Time spent positioning, in transit, or otherwise not at a designated rest facility does not count toward split-duty rest.

Two — "I can take the rest at any point in the duty period." Also no. The rest has to be a meaningful pause between two genuine flying segments. Two short legs followed by a 4-hour break followed by a single positioning sector probably doesn't qualify, depending on your operator's interpretation.

Cumulative limits — the long view

FDP per duty is one constraint. ORO.FTL.210 layers cumulative limits on top:

These are block hours, not duty hours. A duty period can include 90 minutes of pre-flight, taxi, deicing — none of which counts toward the cumulative numbers. The numbers above are wheels-off to wheels-on, accumulated.

This is the limit that actually catches most line pilots out. A heavy roster in November pushed by a heavy roster in December puts you against the 28-day cap right when you want to be flying for double-time.

How operators apply the rule

EASA publishes the regulation. Member state authorities (CAA, BFU, DGAC, SHGM, ENAC, etc.) implement and supervise it. Your operator publishes a Flight Time Specification Scheme (FTSS) that describes how it interprets the rule for its operation. Three things to remember:

• The FTSS cannot be more permissive than ORO.FTL.
• It can be more restrictive — and most are, in specific areas.
• Approved variations exist (different rules for ULR, helicopter HEMS, fire-fighting). If you fly one of these specialties, ORO.FTL.205 is the starting point, not the finish line.

Practical takeaways

1. Know your base FDP for your typical duty pattern. A short-haul European FO probably operates with maximum FDPs between 11:00 and 13:30. A long-haul ULR captain works in a different table entirely (ORO.FTL.220).
2. Don't rely on extensions. If a roster bumps against the limit, plan as if no extension exists. The extension is for when the day breaks down, not for when the day is built.
3. Track cumulative early. The 28-day cap will catch you if you only check it at month-end. Watch the 7-day rolling number.
4. Understand WOCL on your roster. A 04:30 reporting time is a different animal from 06:30 even though they're on the same airport on the same date.
5. Document. If you exercise commander's discretion, write it down. If you took an extension, write it down. Your logbook is your defence.

Where Flight Log fits

We built Flight Log so the FDP gauge in your hand is the same one your operator's planning system sees. When you start a duty, the app reads your reporting time and number of planned sectors and shows you exactly how many minutes are left in your maximum. Notifications fire one hour before, and again at the limit — even when the phone is on Do Not Disturb. Cumulative 7-, 28- and 365-day windows update automatically.

It's not advice. It's not a substitute for your operator's calculation. It's a parallel reading — the same one the regulation expects every commander to be able to make on demand.

If you fly under EASA, the app is built around your rule set first. FAA Part 117 is included for the cross-jurisdictional pilots, but the EASA implementation is the older, more refined codebase.

Further reading

The primary text — Commission Regulation (EU) No 965/2012, Annex III, Subpart FTL — is published by the EASA on its official website. Read the rule. Read your operator's FTSS. Cross-check both against the company OM.

Then read it again every two years, because it changes in places you don't expect.