This document helps you quickly check whether the changes in this release affect your day-to-day operations. Changes are grouped by functional area, so 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.
-
More information links point to the related article on the Leon wiki.
OPS
AMOS integration: choosing which aircraft are sent
What changed: You can now choose which aircraft have their data sent from Leon to AMOS. The aircraft list is available on the AMOS integration tile in Add-ons.
Who is affected: Operators using the AMOS integration. After the release, data for all active aircraft is still sent, exactly as before, until you change the selection. No impact on current operations.
Recommended action: If you select only some aircraft, remember that aircraft added to your fleet later will not be sent to AMOS until you select them on the tile. If you select all aircraft, new aircraft are included automatically, as before.
World Kinect: fuel ordering through the WKC portal
What changed: Fuel can now be requested directly through the World Kinect (WKC) portal. The request goes from Leon straight to the supplier instead of being sent by email, so the supplier does not need to retype the data.
Who is affected: No one until you enable it. This is a new, optional feature for operators using the World Kinect integration. Until it is switched on, fuel requests are sent by email exactly as before. To start using it, tick "Fuel ordering enabled" in the WKC account settings on the World Kinect tile. Ordering through the portal works for flights with an aircraft assigned that is covered by an active WKC account.
Journey Log: new "Traumatic Event" checkbox
What changed: The Journey Log has a new checkbox, "Traumatic Event", which lets you record a traumatic event on a flight. This supports Fatigue Risk Management (FRM) policies. The field is also available as the "Traumatic event [JL]" column in Report Wizard (Flight scope).
Who is affected: No one until you enable it. The field is disabled for all operators after the release. To start using it, enable "Traumatic event" in the Journey Log settings (Disabled, Selected Aircraft, Selected Base or Always). To fill it in from the Crew App, crew need the latest version of the Crew App.
Crew
Deleting duties with the Delete key
What changed: You can now delete selected duties on the Crew Calendar and the Crew Timeline by pressing the Delete or Backspace key, without opening the menu. You can select several duties at once. A confirmation window appears before anything is deleted. The context menu now shows this shortcut next to the delete options.
Who is affected: Users who can edit the Crew Calendar or the Crew Timeline. The shortcut follows the same rules as deleting from the context menu: if you work without drafts, the deletion is published immediately; in draft mode, it is published with your next Publish.
Recommended action: Let your planners know about the new shortcut. The Delete button in the confirmation window is selected by default, so pressing Enter confirms the deletion.
Crew Training
More accurate Crew Currency status dot on the Crew Calendar
What changed: When the Crew Calendar is grouped by aircraft ("Aircraft (based on preferred crew)" or "Aircraft (based on ratings)"), the Crew Currency status dot now checks only the currencies that apply to the aircraft type of that group. You will no longer see a red dot only because a qualification also covers other aircraft types the crew member does not fly.
Who is affected: Users who view the Crew Calendar grouped by aircraft. Some red dots that were caused by other aircraft types covered by the same qualification will disappear. With any other grouping, currency is checked for all types, exactly as before.
FTL
Required local nights shown clearly in FTL details
What changed: The FTL details window now has the rows "Local nights before duty" and "Local nights after duty", which clearly show how many local nights are required for the minimum rest (for example after a time zone change). Previously this was shown only in a tooltip.
Who is affected: Operators whose FTL settings require local nights of rest (for example after a time zone change, a long duty or a series of night duties). For other operators the rows are not shown. FTL calculations have not changed. This change should not affect your current operations.
New FTL settings: positioning counted as duty and separate reporting time for cabin crew
What changed: Two new FTL options let you reflect more rules from your operations manual in Leon:
-
positioning longer than a set threshold can be partly counted as duty time (for example half of the time), unless the crew member gets a long enough rest before the next duty;
-
the reporting time and the duty end time can differ between cabin crew and other crew (for example a longer reporting time for cabin crew when departing from base).
Who is affected: No one until it is configured. These options are empty by default, so your FTL calculations stay the same. To start using them, contact Leon Support, who will configure them in your FTL settings.
Crew App
Choosing the airport when requesting a duty
What changed: When requesting a duty from the Crew App, crew can now change the airport where the duty is registered. Previously, the crew member's home base was always used. Crew members without a home base can now also send duty requests by choosing the airport themselves.
Who is affected: Crew who request duties in the Crew App, once they update to the latest version of the Crew App. The home base is still filled in by default, so nothing changes unless the crew member picks another airport. Older versions of the app keep working as before.
Recommended action: Remember that a duty registered at an airport other than the home base is treated as away from base, for example in FTL rules that depend on the home base.
PNR number in hotel reservations
What changed: Hotel reservation details in the Crew App now show the PNR number entered in the web version of Leon, so crew have all the information they need at check-in in one place.
Who is affected: Crew App users with hotel reservations that have a PNR number filled in, once they update to the latest version of the Crew App. This change should not affect your current operations.
Sales
Norwegian Air Passenger Tax
What changed: Leon now calculates the Norwegian Air Passenger Tax automatically for flights departing from Norway on or after 2 November 2026. The rate depends on the final destination of the passenger's journey: one rate for destinations in Norway (including Svalbard, with VAT), one for European countries in the low rate group, and one for all other destinations. Flights departing from Svalbard, non-commercial flights, ambulance flights, infants under 2 and animals are not taxed. The tax is available in Sales and in Report Wizard.
Who is affected: Operators who prepare quotes for flights departing from Norway and have "Automatically add taxes to the quote" enabled (Settings > Sales > Quote Tax), unless the client contact is set not to calculate taxes. For other operators the tax is only available as an item you can add manually. Saved quotes do not change, but when such a quote is recalculated, the tax is added and the price may increase. Report Wizard shows this tax for all flights departing from Norway from 2 November 2026, whether or not it is included in the quote.
Recommended action: If you operate flights departing from Norway, review a few quotes after the release to make sure the tax is shown as you expect, and remove any manual entries you used for this tax so that it is not charged twice.
Report Wizard
FTL duty scope: new columns and a corrected "Days off" column
What changed: The FTL duty scope in Report Wizard has new columns for tracking double days off and quadruple days off limits (shown when these limits are set in your FTL settings), as well as further cumulative columns such as FDP time, standby, split duty, night duties, early starts and weekly rest. In addition, an error has been fixed: the cumulative "Days off" column previously showed FDP extension values. It now shows the actual days off, and FDP extension has its own column.
Who is affected: Operators who use the FTL duty scope in Report Wizard. New columns are not added to your saved reports automatically. Saved reports that include the cumulative "Days off" column will now show different, correct values.
Recommended action: If you use the cumulative "Days off" column in saved or scheduled reports, check them after the release, and add the "FDP extension" column if you used the old values for that purpose.
Admin
Two factor authentication: passkeys and a new management page
What changed: Passkeys are now available to all users as an additional option for two factor authentication. Edit Profile has a new "Two factor authentication" section with a "Manage two factor authentication" link, which opens a page where you manage passkeys and your authenticator app after confirming your password. Setting up an authenticator app now has to be confirmed with a code. Users receive an email when a factor is added, removed or reset, and administrators can reset two factor authentication for another user with the "Reset two factor authentication" option.
Who is affected: All users will see the new section in Edit Profile. Using a passkey is optional and your current two factor authentication keeps working. Operators with "Force two factor authentication for all users" enabled: a passkey counts as the second factor, and users who have not finished setting up two factor authentication cannot log in until they do.
Recommended action: If you require two factor authentication, setup links sent by email before the release may no longer work. Users who did not finish the setup can get a new link from an administrator using "Reset two factor authentication".
API keys for Sandbox only
What changed: An API key can now be marked as intended for Sandbox environments only. Such a key does not work in production, which protects your production data while you test integrations. The option is available when creating or editing an API key (Settings > System > API Keys).
Who is affected: No one until you use it. Existing API keys are not changed and keep working as before.
Microsoft sign-in when authorising external applications
What changed: The authorisation window used by external applications to connect to Leon now has a "Confirm using Microsoft" button, in the same way as the standard Leon login. Users of operators who have turned off login and password access can now authorise external applications without problems.
Who is affected: Operators who use Microsoft sign-in (set in Operator settings > Security) and whose users connect external applications to their Leon account. Authorisation with login and password, and with other single sign-on providers, works as before.
Remaining free trainings in Manage Leon Account
What changed: Manage Leon Account has a new "Training status" tab, which shows how many free trainings you have left and until when they are available.
Who is affected: Users with access to Manage Leon Account will see the new tab. This change should not affect your current operations.
User names similar to "Leon Support" are blocked
What changed: For security, user accounts can no longer be named "Leon Support" or similar variants, so that no one can pretend to be the Leon Support team. The first name or surname "Leon" can still be used as usual.
Who is affected: Administrators who create or edit user accounts. If an existing user account already has such a name, saving changes to it will be blocked until the name is changed. Integrations that create or rename crew members through the API will receive an error for such names.
Recommended action: If you have a user account named like "Leon Support" that is not the official Leon Support account, rename or deactivate it.
Airport Directory
Airport change history
What changed: You can now see the history of changes to airport data. Audit Logs have a new "Airports" event type covering changes to an airport and all of its data, and the change history window for an airport can be opened from Audit Logs or directly from the airport in the Airport Directory. The history starts from this release; earlier changes are not included.
Who is affected: Users who can view the Airport Directory or Audit Logs will see the new history. This change should not affect your current operations.
Internal changes
This release also includes internal technical improvements (performance, maintenance, security). These changes should not affect your current operations.