Sprint 224 — Operational Impact Assessment
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.
OPS
New Journey Log items: Late booking, Shared flight, PAX transport note, Fuel payment note
What changed: Four new items can now be used in the Journey Log — Late booking (a tick box), Shared flight (a client selected from the Phonebook), PAX transport note and Fuel payment note. All four are also available as columns in the Report Wizard, Flight scope.
Who is affected: No one until you enable them — these are new, optional fields, switched off for every operator, including newly created accounts. To start using them, go to Settings > Journey Log configuration and set each field to Always, Selected aircraft or Selected base. Until then the Journey Log looks exactly as it does today. Note that the matching Report Wizard columns appear in the full list of available columns straight away, but they are not added to any of your existing or default column sets.
Reference: LEON-47445, LEON-49863
New Journey Log items: TETI and TETO
What changed: Two new tick boxes — TETI (Twin Engine Taxi In) and TETO (Twin Engine Taxi Out) — for operators who report taxi on two engines. Both are also available as Report Wizard columns in the Flight scope.
Who is affected: No one until you enable them — both fields are switched off by default for all operators. To start using them: Settings > Journey Log configuration.
Reference: LEON-49221
Return to Ramp and the reorganised FW tab
What changed: The FW tab is now split into three sections — MVT (the fields you have today), Return to Ramp, and Notes. Return to Ramp lets you record a situation where the aircraft left the gate and came back without flying: use "+ Add" to create an entry, or click an existing row to edit it. Each entry stores a date and Off block / On block times in UTC (required), plus optional fuel and a note.
Who is affected: All operators — the FW tab is reorganised for everyone, there is no setting to keep the old layout. Your existing MVT values and notes are untouched and stay in the same fields. One point to be aware of: a Return to Ramp entry is stored as a separate sector, and it counts towards the Flight Duty Period and block time. Return to Ramp data is not currently carried into the Journey Log, the Report Wizard or MVT messages.
Recommended action: Brief OPS staff on the new tab layout, and make sure whoever records Return to Ramp understands that these entries feed FTL and block time calculations.
Reference: LEON-48803, LEON-49845
Crew
Overnight positionings marked with an arrow in Crew Calendar
What changed: Positionings that cross midnight now show an arrow, the same way flights do. If the positioning sits inside a duty, the duty decides; otherwise the positioning times decide.
Who is affected: Everyone who can see positionings in Crew Calendar. This is a display change only — arrows will start appearing on positionings that are already in your roster. Nothing is recalculated or stored differently.
Reference: LEON-46945
Hotel suggestions for every crew position
What changed: Crew Timeline now flags missing hotels (the red H) for all crew members regardless of the position they hold on the flight, including positions excluded from FTL calculations. For those positions a hotel is suggested when the stay away from base at an airport exceeds 10 hours.
Who is affected: All operators using Crew Timeline. The suggestions are only visible if a planner has "Required Hotel" switched on in the Show menu — that option is set per user and is off by default. Planners who use it will see new red H markers on flights that are already planned and were previously clear, without anything having changed in the roster. The 10-hour threshold is fixed and cannot be configured.
Recommended action: Expect a one-off increase in hotel suggestions after the release and review them before treating them as an error.
Reference: LEON-48941
Edit duty — choosing which notes are cleared
What changed: The single "Clear notes" tick box has been replaced by a separate tick box under each note, so you can clear the pilot, planner, day trading or manager note individually instead of losing all of them at once.
Who is affected: All operators using Edit duty. If your planners relied on "Clear notes" to wipe everything, that single tick box no longer exists — clearing all notes now means ticking each one. Separately, if you edit duties directly through our API, the old note fields are still accepted by the interface but are no longer processed: values sent in them are ignored without an error being returned.
Recommended action: If you have an integration that edits duties through the API, move it to the new note structure before this release goes live, otherwise note changes will silently stop taking effect.
Reference: LEON-47914
Duty overlap check when assigning crew
What changed: When you assign crew in the Assign Crew window, Leon now checks whether the crew member already has a duty planned in the period concerned — the start and end of the pairing, or the start of the first and end of the last selected flight.
Who is affected: All operators who assign crew from Crew Timeline, on both flights and pairings. The check is a warning, not a block: you will see the message in the validation window and can still confirm and save.
Reference: LEON-49772
Time zone marker on positioning STD and STA
What changed: The add and edit positioning window now shows a time zone marker (Z, BT or LT) next to STD and STA, and the marker updates when you switch the time zone.
Who is affected: Everyone who adds or edits positionings. This is a display change only — how times are entered, stored and converted is unchanged.
Reference: LEON-49833
Crew Training
New way of recognising an instructor on a Line Training flight
What changed: A new setting, Instructor recognised by, in General settings > Crew planning, with two options: Instructor position (how Leon works today — it looks at the position held on the flight, such as LTC or TRI) and Instructor rating (Leon instead checks whether the person in the CPT or FO position holds an instructor rating on the aircraft type flown on that sector).
Who is affected: No one until you change it — the setting defaults to Instructor position for every operator, which is exactly the behaviour you have today. Switching to Instructor rating is useful if your instructors fly as CPT or FO and you currently get a missing-instructor warning despite them holding the rating, or if you have been assigning the same person twice (as CPT and as instructor) to work around it. The setting only affects that warning; it does not change what Leon sends to external flight planning systems.
Reference: LEON-47760
Qualification Configuration available to all operators
What changed: The configuration view for required certificates and endorsements has been rebuilt and is now available to every operator, without Leon having to switch it on.
Who is affected: Operators who did not already have the new view — they will now see it in place of the previous certificates configuration screen, which has been removed. Your existing configuration and data are unchanged and nothing needs to be migrated. Two differences are worth knowing about: the aircraft type selection now lists only the types in your fleet and currently has no "select all" option, and the view can also be reached from the CREW menu and granted through its own permission, so users without full administrator rights can be given access to it. As before, the view is part of the Pro version of Leon.
Recommended action: Decide who in your crew team should be granted the new permission.
Reference: LEON-49926
Crew Planning
Positionings in the Edit Crew Composition window
What changed: Positionings that are part of a pairing now appear as separate tabs in Edit Crew Composition, where crew members can be added and removed. Validation checks that the crew composition is consistent across all activities in the pairing.
Who is affected: Only operators using Crew Pairings, which is currently a beta feature enabled on request by Leon Support. If it is not enabled for you, the Pairings module is not visible and nothing changes.
Reference: LEON-49782, LEON-49870
Configurable maximum layover and pairing length
What changed: The maximum layover length and maximum pairing length can now be set in General Settings > Crew Planning > Pairing settings. The defaults are 24 hours for a layover and 72 hours for a pairing; the highest values allowed are 72 hours and 168 hours, and a layover cannot be longer than the pairing.
Who is affected: Only operators using Crew Pairings (beta, enabled by Leon Support). The defaults match how pairing generation works today, so nothing changes until you raise them. Pairings that have already been generated are not recalculated — new values apply the next time you generate. Be aware that values close to the upper limits noticeably increase how long generation takes.
Reference: LEON-49784, LEON-49872
Crew labels in Pairings > Assign crew
What changed: Overlapping crew member labels in the Assign crew window have been fixed, so larger crew compositions are readable.
Who is affected: Only operators using Crew Pairings (beta, enabled by Leon Support). This is a display fix and requires no action.
Reference: LEON-49783
Crew App
More detail in the hotel booking preview
What changed: The hotel booking preview in Crew App now also shows the booking or confirmation number and the airport the booking relates to, instead of only the check-in/check-out dates and hotel name.
Who is affected: Crew using Crew App, including for bookings created in the web version — the details come from the same booking record regardless of where it was entered. Crew who open Crew App in a browser will see the change as soon as the release is live; crew using the app installed from the App Store or Google Play will see it only after updating to the new version, so for a period some of your crew will see the new details and some will not.
Reference: LEON-49744, LEON-49745
Sales
Separate control for subcharter search in Avinode
What changed: Receiving standard requests for quotes and searching for subcharters were previously controlled by a single tick box. A new switch, Allow charter search, has been added to the Avinode account settings and works independently of Download requests for quotes.
Who is affected: Nothing changes for anyone by default — the new switch is on for all existing Avinode accounts. It matters if you do not have the sourcing add-on on the Avinode side and have been receiving authorisation errors: you can now turn subcharter search off and keep receiving standard requests for quotes, instead of losing both. You can change this yourself in Settings > Add-ons > Avinode.
Reference: LEON-49487
Control over quotes for aircraft outside your Avinode configuration
What changed: A new setting decides whether Leon accepts quotes arriving from Avinode for aircraft that are not included in your Avinode Schedule Export configuration. There is one setting per Avinode account.
Who is affected: Nothing changes by default — the setting is on, which matches how Leon behaves today. It is relevant if only part of your fleet is connected to Avinode and you have been surprised by quotes appearing for the rest. If you turn it off, quotes for aircraft outside the configuration are simply not created, without an error message; the aircraft requested still appears on the RFQ list as before.
Reference: LEON-49429
Recalculate on a quote with an invalid leg date
What changed: Recalculating a quote where a leg carried an invalid date returned an error instead of pricing the quote. The value in the field is now corrected after editing.
Who is affected: This change should not affect your current operations.
Reference: LEON-49691
Sched
Flight time calculated on flights published from Sched
What changed: When a flight is published from Sched, Leon now calculates and sets the flight time as block time minus the taxi in and taxi out times from the airports. This means MVT messages have the flight time filled in instead of left empty.
Who is affected: All operators using Sched. One point to be aware of: the flight time is recalculated whenever the block time changes in Sched, including on flights that are already published and including cases where a dispatcher typed the flight time in manually in OPS. The recalculation preserves the taxi time implied by the earlier value, but the resulting figure moves with the block time.
Recommended action: If your dispatchers correct flight time manually on flights that originate from Sched, be aware that a later schedule change in Sched will overwrite that correction.
Reference: LEON-49741
Wingman and MCP
New tool returning the list of crew members
What changed: A new tool returns the list of crew members — people holding at least one rating on any aircraft type — and can optionally be narrowed down to a single aircraft type.
Who is affected: Only operators connecting to Leon through MCP, for example with Wingman or another AI tool. There is no effect on the Leon interface or on the standard API. The tool returns only the data the connecting account is already permitted to see.
Reference: LEON-49638
API
Flight identifiers added to the modified flights query
What changed: The query that returns flights modified after a given time now also returns plain lists of created and modified flight identifiers, without the full flight data. Integrations that synchronise large volumes of flights can fetch the identifiers first and then load the details separately — for example through a queue — instead of pulling everything in one response.
Who is affected: No one until you use it — the existing fields and their behaviour are unchanged, and no current integration needs to be adjusted.
Reference: LEON-49469
Admin
New password reset process
What changed: After entering their login, a user receives an email with a one-time link and sets the new password in a form inside the application. The email no longer contains any credentials. The link expires if it is not used within 30 minutes, and it is deactivated immediately once the password has been changed. Users with two-factor authentication also enter their code in the same form.
Who is affected: All users, at every operator. The previous process stops working the moment this release goes live — there is no transition period and the old style of email is no longer sent. The 30-minute expiry is fixed and cannot be set per operator; the invitation email sent when a new user account is created stays valid longer, for 24 hours. There are no additional restrictions for accounts that sign in through single sign-on.
Recommended action: Update any internal onboarding, helpdesk or training material that describes the old reset email, and tell users to complete the reset within 30 minutes of requesting it.
Reference: LEON-45106
"Changed by" filter in Audit Logs
What changed: Audit Logs can now be narrowed down to changes made by a single user.
Who is affected: Everyone with access to Audit Logs. The filter is optional and nothing about the existing view or its data changes.
Reference: LEON-49659, LEON-49869
MVT Email and Timeline Additional Markers moved to the new Settings view
What changed: Two more settings — MVT Email and the Timeline Additional Markers window — have been moved from the old General Settings into the new settings view, as part of the gradual tidy-up of the configuration.
Who is affected: All operators, but only in terms of where the settings live. Your values are preserved exactly as they are; MVT Email is shown as read-only in its new location. The items are no longer in the old place, so any bookmarks or internal instructions pointing there need updating.
Reference: LEON-49618
Airport Directory
Refuel EU tracked per year
What changed: Whether an airport is covered by the Refuel EU programme is now recorded per year instead of as a single flag, because the list changes from year to year and reporting requires knowing the historical position. In Airport Directory you can override the years for a given airport; the override applies only to your own account, which allows you to handle individual exemptions.
Who is affected: Operators who use Refuel EU information in documents, reports or through the API. The existing Refuel EU indicator is now worked out for the current calendar year and takes your own overrides into account, so for airports whose status has changed over time — or where you hold an exemption — it may return a different value than before this release. A separate list of all years is now available for more detailed reporting. Where the indicator is used in the context of a flight, Leon uses the year of the flight date. Overrides can only exclude an airport from the programme for your account, not add one that is not on the central list, and they require the existing Airport Directory editing rights.
Recommended action: If you report on Refuel EU, check the values you get after the release and record any exemptions that apply to you.
Reference: LEON-44769
Internal changes
This release also includes internal technical improvements (performance, maintenance, security). These changes should not affect your current operations.