Flight Time Limitations: the legal ceilings on duty, block hours and rest, and
the reports that show where you stand against them.
Where: Admin → Crew → FTL setting · Permission: adminFtlSetting
This screen is read-only. It shows the rules in force; it cannot change
them. Adjusting a limit is done by your provider, not from here.
The header shows the active AOC, a search box, and Total / Overridden
counts. Rules are grouped into cards:
| Group | Typical contents |
|---|---|
| Duty & FDP offsets | Reporting time before the first sector, post-sector time |
| Cumulative duty | Rolling 7 / 14 / 28-day duty ceilings, separately for cockpit and cabin |
| Block hours | 28-day and calendar-year block limits |
| Rest requirements | Home-base and down-route rest, weekly rest, rest after consecutive night duties, days off, local nights |
| Training | Whether simulator counts as duty |
| Positioning | Whether positioning counts as duty |
| Short break | FDP extension rules |
| Maximum daily FDP | The FDP matrix |
Each row shows Parameter, Overwrite (AOC override or default),
Value and Description.
Values in minutes are displayed as
hh:mm, so a 3600-minute limit reads
60:00— that is sixty hours, not sixty minutes. Parameter names are shown in
their raw form and many descriptions are empty.
Where: REPORTS → Crew → FTL sheet
Required: a date range and a crew member. The report stays blank
until you pick a person — this is the most common reason for an empty screen.
Also available: timezone (UTC / THR), aircraft types and position types.
Aircraft type and position type only narrow the crew dropdown. They do not
filter the report itself.
Columns cover date, duty type, aircraft, duty start and end, rest before duty
(actual and minimum), block hours, sectors, duty time, FDP (actual and maximum),
and the limit groups. A bold summary row is pinned at the bottom. Exports:
Excel and CSV.
Where: REPORTS → Crew → FTL violation
Shows only failures, grouped per crew member — a blank report means no
violations in the period, which is the good outcome.
Each check is a simple pass or fail: red ✗ failed, green ✓ passed. There is no
severity ranking and no rule-name column.
The status chart counts only the FDP check, so it understates the total when
other checks have failed. Read the table rather than the chart.
FTL DETAILS, on a duty or flight bar in the crew screens, opens two tables:
Duty & FDP Sectors (report on, the sectors, report off) and FTL
Calculation Summary (group, title, limit, actual, status). Rows whose limit
shows - are informational and always green.
It warns; it does not block. In ops, FTL findings appear under Flight time
limits and the save button becomes SAVE IGNORING WARNINGS. In the beta
event calendar the equivalent is Save anyway. There is no acknowledgement or
sign-off recorded.
Only checks an administrator has set to Error in
General settings → Flight editing cannot be
overridden — and FTL is not one of them by default.
| Symptom | Cause | Fix |
|---|---|---|
| FTL sheet is blank | No crew member selected | Pick one — it is required |
| A limit looks wrong by a factor of 60 | Minutes shown as hh:mm |
60:00 means 60 hours |
| Chart and table disagree | The chart counts only FDP | Trust the table |
| Eligibility badge is amber but no violation | That badge ambers at 90% of limit | Not a violation; check the sheet |
| Draft roster does not count toward limits | Only published legs count | Publish, then re-check |