This section allows you to review the FTL Settings that are implemented based on OM part 7.
Apart from very specific settings you can also:
Cumulative Duty Limit Notification Service is explained below.
Cumulative Duty Notification is a facility that provides information when cumulative duty is close to the maximum level (just before it is exceeded).
There are following options available:
When this is defined, a notification email is sent whenever Cumulative duty hours for a member of the crew are over the stated value.
It is possible to select an extension mode. In order to do that please contact email@example.com
Each of the modes will affect how 'FDP extensions' should work: whether it should apply manually or only in case of violation (default setting).
There are 2 modes to choose from in 'FTL Settings':
Additionally, it is possible to apply FTL extension mode that allows applying FDP+ manually, even if the schedule would suggest that it is not needed. In order to activate it go to 'Flight editing' settings and activate 'Require manual enabling of FDP+' checkbox (if this checkbox is ticked, 'FDP+' in 'CREW“ tab is unticked by default).
This will not affect any existing flights and assignments, but for all the new flights it will result in FDP+ being disabled by default, and will require manual selection of FDP+ checkbox for the extension to be enabled. However, if enabled, it will be applied regardless of any FDP violation or lack thereof.
Most FTL regulations contain a requirement for scheduling an extended recovery recurrent rest period once every few days, usually called a weekly rest. For example:
“(…) minimum 36 continuous hours, including two consecutive recovery nights, in a seven-day period.”
or, more precisely:
(…) weekly rest period, being a 36-hour period including two local nights, such that there shall never be more than 168 hours between the end of one weekly rest period and the start of the next.
It is reflected in Leon’s FTL Settings by weekly_rest_min_length (in this case, 36 hours) and weekly_rest_max_separation (in this case, 168 hours). Other settings can be used to specify whether the weekly rest should include local nights, or whether it can be reduced, or performed outside the crew member’s home base.
However, this is rarely that simple. Some regulations allow for an alternative rest instead of the regular one, for example:
(…) rest periods will be extended at least:
which often leads to some confusion, especially in the case of alternating 36/60 “weekly” rest patterns.
So far this has been implemented in Leon in a way that FTL would require the basic (36-hour) rest to happen within the first 7 days following the previous weekly rest. If such rest is not scheduled in that period, FTL starts to require the alternative (longer) extended rest period. It can be illustrated with the following example:
Recently, we encountered a different phrasing of the weekly rest regulations, suggesting that the opposite interpretation may actually be more appropriate:
Before beginning an FDP or standby, an FCM must have had at least 1 of the following:
From the previous example, one can infer that the FDPs on 14-DEC and 15-DEC are actually not permitted, since there is neither a 36-hour rest in the previous 7 days (08-DEC–14-DEC) nor a 72-hours in the previous 10 days (05-DEC–14-DEC). The correct illustration would be as follows:
This new “forward” mode of calculating weekly rest can be enabled by setting weekly_rest_alternative_forward. This will only affect the regulations with an additional “alternative” definition of a weekly rest. Please contact customer support for more information.
In this section, we explain the purpose of some of the settings: