This document helps you quickly check whether the changes in this release affect your day-to-day operations. Changes are grouped by functional area — each department can review only the sections relevant to them. Impact statements are based on an analysis of the actual application code.
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.
Crew
Assign Crew window now respects the "Can only see crews assigned directly to the aircraft" restriction
What changed: When assigning crew on the Crew Timeline, users whose role has the restriction "Can only see crews assigned directly to the aircraft" enabled will now see only crew members assigned directly to the aircraft they have access to — instead of all crew members rated on the aircraft type. If flights on different aircraft are selected, a validation message will ask to plan them on the same aircraft. Works in both the traditional and pairing views.
Who is affected: Only operators who have this restriction enabled for some user roles. For those users, the list of available crew in the Assign Crew window will become shorter — previously the restriction was not applied in this window. Users without the restriction see no change.
Recommended action: If you use this restriction (for example, to give an ACMI aircraft operator limited crew planning access), verify after the release that the affected users can see the crew members they need — and that crew are correctly assigned to the aircraft in question.
Reference: LEON-48351, LEON-49628
New hotel booking statuses: PENDING and TO BE REQUESTED
What changed: Two new statuses are available in the hotel booking window on the Crew Timeline, letting you reflect the stage of accommodation arrangements more precisely.
Who is affected: No one until you start using them — these are additional options in the status list. Existing bookings and default behaviour are unchanged.
Reference: LEON-48595, LEON-49629
New "Rank" column in Crew Travel
What changed: The Crew Travel view now shows a "Rank" column next to the crew member's name, displaying their highest rating on the aircraft in the given group (e.g. CPT). Available in all tabs except Logs.
Who is affected: All operators using the Crew Travel view will see the new column immediately. This is a display-only addition — no data or workflow changes.
Reference: LEON-49510, LEON-49511
Visual feedback when applying FDP+
What changed: Clicking the FDP+ button now shows a loading indicator while the system recalculates the limits, so you can see the click was registered. The checkbox is marked right away and the recalculated values load in the background.
Who is affected: All users who apply FDP+. This is a visual improvement only — FTL calculations themselves are unchanged.
Reference: LEON-48909
Crew App
Crew dates of birth shown in the Crew tab
What changed: The Crew tab in the Crew App now shows crew members' dates of birth — the same way it already works for passengers.
Who is affected: Only crew members whose role has the "Show crew contact in App My Schedule" setting enabled will see this information — the same setting that already controls visibility of crew phone numbers in the app. If you keep crew contact details hidden in the app, dates of birth stay hidden too.
Reference: LEON-48912, LEON-49626
Crew Training
Mailing Rules for Crew Certificates: new "All certificates" option
What changed: In Admin → Crew Certificates → Mailing Rules, each rule can now either cover all certificates (newly created certificates are then included automatically) or only a selected list. Newly created certificates are no longer automatically added to rules with a manually narrowed certificate list.
Who is affected: Operators using Mailing Rules for crew certificates. Rules that previously covered every certificate will show as "All certificates" and keep working as before. Rules with a narrowed list will no longer automatically pick up newly created certificates — which is the intended fix, but it changes behaviour if you relied on new certificates joining every rule automatically.
Recommended action: After creating a new certificate definition, review your mailing rules and add the certificate manually to any narrowed rule that should include it.
Reference: LEON-49528, LEON-49529
Centrik integration: certificates cleaned up after removing the sync label
What changed: When the label controlling the scope of Centrik synchronisation is removed from a user and "Reset Integration Data" is clicked, certificates imported from Centrik are now removed automatically — previously this required assistance from Leon Support.
Who is affected: Only operators using the Centrik integration with label-based synchronisation scope. This restores the expected behaviour — no impact on current operations otherwise.
Reference: LEON-49062
OPS
New "FTL violation" validation in Flight Editing Warnings
What changed: A new validation can block (or warn about, with an option to ignore) saving flights where at least one crew member exceeds FTL limits.
Who is affected: No one until you enable it — the validation is switched off by default for all operators. To start using it, enable "FTL violation" in Settings → OPS Settings → Flight Editing Warnings, choosing whether it can be ignored and by whom.
Reference: LEON-49530, LEON-49742, LEON-49743
Flight editing warnings configurable per flight base
What changed: Instead of one warnings configuration for the whole operator, you can now switch to a per-base mode: for each base you decide whether a given validation applies, whether it can be ignored, and who can ignore it (everyone or selected people assigned to the base). The base is taken from the first flight of the trip.
Who is affected: No one until you switch the mode — the default remains the current per-operator configuration, and existing behaviour is unchanged until you select the per-base mode and save a base configuration.
Reference: LEON-49406, LEON-49536
New MVT scenario: "Missing landing"
What changed: An MVT message can now be sent when the landing time has not been entered 15 minutes after the reference time (ETA, or STA if no ETA is entered) — mirroring the existing logic for a missing take-off time.
Who is affected: No one until you enable this scenario. It only starts working for operators who have switched on sending this new MVT scenario — it does not activate automatically for operators already using MVT Messages.
Recommended action: If you want this alert, enable the "Missing landing" scenario in your MVT Messages configuration, and let your OPS team know that missing landing times will then trigger messages.
Reference: LEON-49663
Crew shown in the flight footer on OPS Calendar
What changed: A new "Crew" option in "Show in footer" displays crew codes in the bottom strip of each flight (cockpit and cabin separated by a slash), with a tooltip showing crew member details.
Who is affected: No one until you enable it — this is a per-user display option in the existing "Show in footer" menu. Each user chooses it individually.
Reference: LEON-49223
Two new approach types: "Steep approach" and "FGV"
What changed: Two new entries were added to the Enabled approaches list.
Who is affected: No one until you enable them — both are switched off by default and can be enabled in Settings.
Reference: LEON-49222
Faster Flight Brief generation for large trips
What changed: Generating Flight Brief documents for trips with a very large number of legs (around 20 or more) has been optimised — previously such documents could fail with a timeout, especially when airports with complex opening hours were involved.
Who is affected: This change should not affect your current operations — document content is unchanged; documents that previously failed will now generate correctly.
Reference: LEON-49331
MX
History of deleted entries in Scheduled Maintenance
What changed: Deleted maintenance entries no longer disappear permanently. A new filter lets you show deleted entries, a Status column (Active / Cancelled) indicates their state, and a change-history window is available for each entry.
Who is affected: All operators using Scheduled Maintenance. Deleting an entry now marks it as cancelled instead of removing it. Note that only entries deleted after this release can be shown — entries deleted before the release were removed permanently and cannot be recovered.
Reference: LEON-49173, LEON-49624
Manual AMOS export report supports a fixed flight number
What changed: The manually generated AMOS export report (REPORTS → MX → AMOS export) now applies a fixed flight number, matching the behaviour of the automatic AMOS integration. The fixed flight number can be entered directly in the report filter.
Who is affected: Only operators generating the AMOS export report manually. The new filter field works independently of whether the AMOS integration is enabled. Existing reports without a fixed flight number are unchanged.
Reference: LEON-49268
Sales
Fixed: quote created with an outdated airport after changing the RFQ route
What changed: We fixed a bug where changing an airport in the RFQ itinerary and then adding an aircraft created the new quote with the old airport.
Who is affected: This change should not affect your current operations — it restores the expected behaviour.
Reference: LEON-39207
Fixed: quote emails occasionally sent without the quote attachment
What changed: We fixed a randomly occurring problem where the default template did not load automatically when sending a quote, resulting in an email without the quote attachment. The form now always loads with the default template selected.
Who is affected: This change should not affect your current operations — it restores the expected behaviour.
Reference: LEON-47803
Fixed: aircraft filters with labels not restored after refresh
What changed: We fixed saving of aircraft filters — a combination of a selected label and all aircraft was not correctly restored after refreshing the RFQ list, Bookings, or the user list.
Who is affected: This change should not affect your current operations — it restores the expected behaviour.
Reference: LEON-40812
Day Note tooltip on the RFQ creation calendar
What changed: The calendar in the RFQ creation window now shows a tooltip with the Day Note content — previously available only on the quote editing calendar.
Who is affected: This change should not affect your current operations — it is a small display improvement.
Reference: LEON-49422
Wingman and MCP
New MCP tool: FTL violations for a crew member
What changed: AI assistants connected to Leon MCP can now retrieve a selected crew member's FTL violations in a given date range (up to one month), including the type of violation and comments.
Who is affected: No one until you use it — this is a new, optional capability for operators using Leon MCP. Access follows the same permission that already controls FTL data visibility, so only roles allowed to see FTL data can use it.
Reference: LEON-44716
Admin
Settings reorganisation: "Flight Editing" becomes "OPS Settings"
What changed: We continue moving settings from the old General Settings to the new Settings view. The "Flight Editing" tile is now called "OPS Settings" and contains a redesigned flight editing settings view: checkboxes and dropdowns save automatically on change, and text fields have a Save button. The MVT Email field and the Timeline additional markers configuration were moved to the new view, and the "Options and opportunities change position of aircraft" setting received a clearer name and a tooltip explaining that it applies to the OPS Calendar and Owner Board views.
Who is affected: All operators — but only the location and look of these settings change. All settings keep their values and work exactly as before.
Recommended action: If you cannot find a setting that used to be in the old General Settings, check the new OPS Settings tile in Settings first.
Reference: LEON-49446, LEON-49618, LEON-49625
New fields in the simplified user editing view
What changed: The simplified user editing view (Settings → Users) now includes a Crew ID field in the main tab, and new fields in the MISC tab: Airport ID, Laptop Device, and Drug Test (Yes/No). All new fields are also available as columns in the Users scope in Report Wizard.
Who is affected: No one until you use them — these are new, optional fields. Existing user data is unchanged.
Reference: LEON-48385, LEON-49627
Phonebook
Duplicate contact exports recorded in export history
What changed: Exporting duplicate contacts now creates entries in the Phonebook export history, just like a regular Excel export — closing a gap in the audit trail of exported data.
Who is affected: This change should not affect your current operations — it improves the completeness of your export audit records.
Reference: LEON-43211
Airport Directory
RefuelEU airport status tracked per calendar year
What changed: An airport's participation in the RefuelEU programme is now defined per calendar year, and you can override the applicable years for your own operation in the Airport Directory (for example, when you hold an individual exemption). The RefuelEU status is now interpreted based on the flight date rather than the current calendar year.
Who is affected: Operators who use the RefuelEU airport flag — for example in documents, templates, or checklists. For flights whose date falls in a different calendar year than today (e.g. around the new year, or when generating documents for past or future dates), the flag may now resolve differently than before, as it follows the flight date. Additionally, two airports (Reggio Calabria and Košice) were removed from the programme list to match the official EU documents.
Recommended action: If your documents or workflows rely on the RefuelEU flag, review them after the release and set any individual overrides you need in the Airport Directory.
Reference: LEON-44769
Internal changes
This release also includes internal technical improvements (performance, maintenance, security). These changes should not affect your current operations.