How to read this document
-
Who is affected tells you whether the change applies to you, based on the features you use, the way you work, or your configuration.
-
Entries marked "No impact on current operations" require no action.
-
More information links point to the related article on the Leon wiki.
OPS
LDM messages with multiple destinations
What changed: When an LDM message lists passengers and cargo for several destinations, Leon now adds up the figures from all listed sectors and saves the total on the first flight only. Following flights are no longer updated from that message. If the Load Distribution checklist item on that flight has not been touched yet, its status is set to "?".
Who is affected: All operators who receive LDM messages through the mailbox configured in Leon, in particular those receiving LDMs that list more than one destination.
Recommended action: If your team relied on LDM data being written to later flights of a multi-stop route, review Flight Watch figures on those flights after the release.
Ops Calendar: "Tags & Flight number" footer option
What changed: The Tags and Flight Number footer options are merged into one "Tags & Flight number" setting, which shows the flight number (with the EROPS indicator) followed by the tags.
Who is affected: No one until you select it. Previously saved footer choices keep working and display exactly as before. To start using it: Ops Calendar > three-dot menu > Show in Footer > Tags & Flight number.
Manual MVT messages without a "TO" recipient
What changed: MVT messages can now be saved and sent when the "TO" field is empty, as long as at least one CC or BCC recipient is defined.
Who is affected: No one until you use it. Messages and rules that already have a "TO" recipient work exactly as before.
Positioning window in the OPS view
What changed: Creating and editing positionings from the OPS view now opens the same window that is used in Crew Calendar and Crew Timeline, instead of the side panel. Positionings created from OPS are published immediately (not saved as drafts).
Who is affected: All users who create or edit positionings from the OPS view (via New positioning or by clicking a positioning in OPS Table).
Recommended action: Let OPS users know about the new window. If you need the previous side panel back temporarily, contact Leon Support.
Sched
Fleet Planning ignores maintenance marked as "option"
What changed: The Fleet Planning generator now takes into account only confirmed maintenance. Maintenance entries saved as "option" no longer block aircraft during schedule optimisation.
Who is affected: Operators who use the Fleet Planning generator and enter maintenance with the "option" status.
Recommended action: If an aircraft must stay unavailable during planned maintenance, make sure that maintenance is confirmed before running the generator.
Tooltip for "Include ferry" in Fleet Planning
What changed: A tooltip now explains what the "Include ferry" toggle does.
Who is affected: This change should not affect your current operations.
Sales
New Sales Checklist item "Recharge Invoice Sent"
What changed: A new per-trip Sales Checklist item changes its status to "Sent" automatically when a Recharge Invoice document is sent. The existing Invoices item is not affected.
Who is affected: No one until you enable it. This is a new, optional feature. To start using it: enable the item in Settings > Checklist Configuration, then add it to your Sales Checklist.
MVT Messages to all passengers
What changed: MVT message rules can now be set to send the message to all passengers on the flight. Each passenger receives the message without seeing the other recipients.
Who is affected: No one until you select the new recipient option in an MVT message rule. Existing rules work exactly as before.
Another batch of Sales settings moved
What changed: Another batch of settings has been moved from General Settings to the dedicated Sales settings page. Their values are kept.
Who is affected: Users who edit these settings. They will now find them on the Sales settings page.
Crew Training
Certificates linked to specific airports
What changed: Airports can now be assigned to a certificate, with a choice of departure, arrival or both. Such a certificate is then checked only on flights to or from those airports.
Who is affected: No one until you assign airports to a certificate. Certificates without airports continue to be checked on all flights, exactly as before.
Crew Calendar: non-mandatory qualifications
What changed: A new "Show non mandatory qualifications" option in Crew Calendar Settings (three-dot menu) includes non-mandatory certificates in the crew status dot and shows them in a separate "Certificates (non mandatory)" section.
Who is affected: No one until a user ticks the option. It is off by default, so the status dot is calculated as before.
FTL
Reporting times for EROPS flights
What changed: FTL reporting time rules can now distinguish flights with the EROPS checkbox ticked in the ATC Flight plan checklist item.
Who is affected: No one until an EROPS-specific reporting time rule is added to your FTL configuration. Without such a rule, FTL results do not change. Ticking or unticking EROPS on a flight refreshes its FTL calculation.
Duty Notification Service: email addresses per AOC
What changed: Email addresses for FTL exceedance notifications are now stored separately for each AOC. Your current addresses have been copied to every AOC, so notifications keep going to the same recipients.
Who is affected: All operators using the Duty Notification Service. Day-to-day behaviour does not change after the release.
Recommended action: From now on, changing an address applies only to the selected AOC. If you want a change to apply everywhere, update each AOC.
Night duties split by length
What changed: FTL rules can now distinguish night duties by their length (for example shorter or longer than 8 hours) and apply separate FDP limits and minimum rest to each.
Who is affected: No one until such rules are added to your FTL configuration. Existing FTL calculations do not change.
Admin
Password reset email for development (Sandbox) accounts
What changed: The password reset email for development accounts now clearly states that it applies only to the Sandbox environment and takes effect the following day.
Who is affected: This change should not affect your current operations. It concerns only Sandbox accounts.
Internal changes
This release also includes smaller internal technical improvements (performance, maintenance, security). These changes should not affect your current operations.