HCM v26.11.0 - Splitting the Difference

November’s first update to HCM is primarily a compatibility update for a new version of our FTL Engine, which impacts and upgrades split time handling, calculations for Off Day duty types and improvements for logbook-sourced Recency Items.

What’s new?

Configure your own split time behaviour

For each duty template in your operation, you can now determine how recorded split values are handled by the engine when calculating your totals for Duty and FDP, resulting in different per day and cumulative limits. These changes will apply on the templates if you decide to manage them differently according to your regional regulations or operational requirements.

Options available now for each total are:

1. None: nothing is taken off; the split counts in full.
2. Full split: the whole split is taken off.
3. EASA: nothing under 3 hours; half the split from 3 hours.
4. CAP 371: nothing under 2 hours; 1 hour for 2 to 3 hours; half the split from 3 hours.

By default, all templates take the full split off duty totals, and CAP 371 rules apply to FDP - which is how HCM has always handled split. If you want things to stay as they are - you won’t need to make any changes.

This update to how splits are handled can now have many hundreds of possible configurations to support global rule applications - so you can read more about the specifics in this support article here.

Split time is now split over midnight

Each duty record can now also contain splits that occur overnight locally, with the ability to add independent timings for before and after midnight if the duty itself ends on the next day.

This means the credit of each value will now propagate to each corresponding day - otherwise you can just use the Split before midnight value to keep HCM calculating splits as before.

Calculations on Off Days

In HCM, rules are checked dynamically based on the Duty Type of your duty templates. This means we don’t need to check your shift lengths or hours flown in a day on your days off - but only the ones that matter for that type.

In this update, we’ve expanded the rules list that is checked against for duties marked as days off, to make sure nothing falls through the gaps. This means you may see more rules included in the calculations for Off Days, depending on your template definitions and ruleset setups.

We also tweaked & fixed:

1. Fixed some credit validation issues that affected recency items using logbook source.

If you have any problems yourself as a result of this update, or have anything to report or suggest in general - submit a ticket for our team here.