"Duty Hours" Work Practice Controls define limits for Duty or Flying Duty Periods (FDP). These controls are used to monitor compliance with operational or regulatory limits, ensuring personnel do not exceed approved working hours.
This guide covers:
Access Requirements
To create or edit Work Practice Controls, you need "Modify All" access to Work Practices.
Settings Reference Table
The following settings are part of the Work Practice Setup for multiple controls.
A single period – Applies the control to each individual duty or FDP rather than cumulatively across multiple periods.
This causes the Sector Lookup Table to appear, which includes:
Local Start Time and Hours on Standby Prior to Callout – Defines the range of start times that will enforce the Duty/FDP limit entered into that row.
Do not check individual duties within split shift – Prevents individual segments of a split shift from being assessed separately.
Unless deadheading at the end of the shift – Excludes duties that conclude with deadhead travel from the control.
Allow personnel to extend shift at their discretion by [hours] – Permits users to manually extend their duty or FDP limit by the specified number of hours.
Applies To – Select whether the rule applies to Duty (total time on duty) or Flying Duty Period (FDP) (flight-related duties only).
Must – Defines the rule condition:
not exceed – maximum threshold (e.g. “must not exceed 60 hours”).
be at least – minimum threshold (used in other rule types).
Hours / Days / Months / Years – Specifies the cumulative monitoring period (e.g. 168 consecutive hours = 7 days).
Offset – Shifts the beginning of the monitoring window by a set number of days or hours.
Only check at start/end of duties performed on this day and at end of day – Counts the Duty/FDP hours towards the limit of the day the shift started on if the shift goes over midnight.
Start from a standby shift instead of midnight – Starts the evaluation period from the beginning of a standby shift rather than midnight. If no standby is entered, it defaults to midnight.
Calendar weeks (beginning [Day]) – Uses fixed calendar weeks, starting on the selected day (e.g. Sunday).
Using a standalone period beginning [Date] – Sets a fixed start date for a control period, which can be overridden for individual users.
Where the above period contains at least [number] duties involving Late Night Operations – Adds a conditional restriction if a certain number of late-night duties occur within the defined period.
Include Non-Cumulative Hours in Duty Sum – Includes hours marked as non-cumulative in total duty calculations (leave unchecked to exclude).
Include standbys in which no callout occurs – Counts standby periods as duty time, even when no callout is made.
For split shifts, when the rest is < / = / > [hours], count the rest as duty, otherwise don’t – Overrides global split duty settings.
If the rest period meets the defined comparison, the rest is treated as duty.
🔸 This supersedes the global setting that counts a percentage of split duty rest as duty and ignores split duty rest period reduction rules in other controls.
Check Type: Roster / Actual – Defines which data source to evaluate:
Roster – scheduled duties.
Actual – logged or recorded duties.
Both can be selected together.
Flag exceedences on non-duty days – Shows exceedance alerts even on days where no duty is rostered.
Notice Threshold / Caution Threshold – Sets when warnings appear as personnel approach their limits.
Default – uses global thresholds.
Other – specify a custom %.
Disabled – disables that threshold.
Work Practice Details Label – Optional text label used to describe or identify the control for reporting or reference purposes.
Creating a Duty Hours Control for a Single Duty Period
Use this setup to limit the maximum Duty or FDP allowed within one duty period.
The control in this configuration will count the number of hours between the Start and End times entered into the Duty or FDP control in the user's timesheet.
How to set it up:
Go to System Setup > Work Practices.
Click New Control.
Set Control Type to Duty Hours.
Under Applies To, select Flying Duty Period (or Duty, depending on which limit you are setting).
Select A single period.
Define maximum hours by filling the grid under Local Start Time and Hours on Standby Prior to Callout.
Each cell defines the maximum hours allowed based on the local start time and the number of sectors.
(Optional) Enable Allow personnel to extend shifts at their discretion to allow manual extensions (this will automatically apply the number of hours entered to the Duty/FDP limit once it is reached)
Choose whether to check individual duties within split shifts.
Adjust Composite Options as needed (Home Base / Away Base).
Click OK to save.
This configuration enforces the maximum permitted duty or FDP for each duty period.
Below is an example of tracking a daily FDP limit.
Creating a Cumulative Duty Hours Control
Use this setup to track total Duty or FDP over a defined period (e.g. 7 days, 28 days).
The control in this configuration will count back from the End time entered in the Duty or FDP fields in the user's timesheet by the period specified.
How to set it up:
Go to System Setup > Work Practices.
Click New Control.
Set Control Type to Duty Hours.
Under Applies To, choose either Duty or Flying Duty Period.
In the Must not exceed field, enter the cumulative limit (e.g. 60 hours).
-
Select the tracking period, for example:
168 consecutive hours (7 days), or
1 calendar week, beginning on Sunday.
Choose whether to include non-cumulative or standby hours.
Select Roster and/or Actual under Check Type.
Set Composite Options and threshold preferences.
Click OK to save.
This configuration tracks cumulative hours across a continuous or calendar-based timeframe.
Below is an example of tracking a limit of 60 hours in a 168-hour period
Comments
0 comments
Please sign in to leave a comment.