We have recently initiated the deployment of a new version of Leon. Over the next coming days, customers will gradually transition to the updated version. If you encounter any functions that are not working as expected, please notify us via the Customer Portal (https://customer.leon.aero).
Important Notices
-
From the beginning of 2027, ForeFlight integration will support only API V2. API V1 will no longer be available. If your ForeFlight in Leon still uses API V1, switch it to API V2 before the end of 2026. More information: https://wiki.leonsoftware.com/wiki/foreflight
Admin
-
We have improved the password reset email for development accounts. It now clearly states that the reset applies only to the Sandbox environment account and takes effect the following day. The message has also been reformatted for better readability.
-
Another batch of Sales settings has been moved from General Settings to the dedicated Sales settings page. This continues the work of keeping each module's settings in one predictable place.
Crew Training
-
Certificates can now be linked to specific airports. You can assign one or more airports to a certificate and specify whether the requirement applies to departure, arrival, or both. The certificate is then checked only on flights to or from the selected airports, and airport codes are shown in the certificate list. More information: https://wiki.leonsoftware.com/wiki/certificates-configuration
-
We have added a setting to the Crew Calendar that controls which certificates are included in the crew status dot validation. You can choose whether all certificates are considered or only those marked as "Warn if expired". The "Show non mandatory qualifications" option is available in Settings (three-dot menu), and non-mandatory certificates are displayed in a separate "Certificates (non mandatory)" section. More information: https://wiki.leonsoftware.com/wiki/crew-calendar#Checking-crew-certificates-and-currency
FTL
-
It is now possible to configure non-default reporting times in the FTL module for EROPS flights. When the EROPS checkbox is selected in the "ATC Flight plan" event, separate reporting times are applied to such flights.
-
The Duty Notification Service now allows email addresses to be defined separately for each AOC. Previously, an address entered for one AOC was copied to all others – now FTL exceedance notifications can be routed precisely per AOC.
-
FTL settings now allow night duties to be distinguished by length (e.g. shorter or longer than 8 hours). Separate FDP limits and minimum rest can be defined for each variant, making it possible to reflect OM-A provisions that differentiate between short and long night duties.
OPS
-
We have changed how LDM messages are parsed when passengers disembark at multiple destinations. The first leg now records the total passengers and cargo from all sectors listed in the message, so the correct combined PAX count is passed to Flight Watch.
-
In the Ops Calendar, the two separate footer options – Tags and Flight Number – have been merged into a single "Tags & Flight number" setting. When enabled, the flight number (including the EROPS indicator) is displayed first, followed by the tags.
-
Manual MVT message sending has been extended so messages can be sent without a recipient in the "TO" field, as long as at least one recipient is defined in CC or BCC. This makes it easier to use templates where recipients are listed in CC. More information: https://wiki.leonsoftware.com/wiki/mvt-messages#Sending-MVT-messages-manually
-
The positioning create/edit window is now available directly from the OPS view.
Sales
-
We have added a new Sales Checklist item (per Trip) called "Recharge Invoice Sent", which – like the existing Invoices item – automatically changes its status to "Sent" once a Recharge Invoice document has been sent. This lets you track recharge invoices in the same way as standard invoices.
-
MVT Messages can now be sent to all passengers on a flight. Simply select the relevant recipient option – each passenger receives a message without seeing the other recipients. More information: https://wiki.leonsoftware.com/wiki/mvt-messages
Sched
-
In the Fleet Planning generator, maintenance events marked as "option" are no longer taken into account when planning the schedule – the planner considers only confirmed maintenance, so the plan better reflects actual fleet availability. More information: https://wiki.leonsoftware.com/wiki/fleet-auto-planner
-
We have added a tooltip to the "Include ferry" toggle in the Fleet Planning generator window, explaining that this option includes existing ferry flights in the schedule optimisation. More information: https://wiki.leonsoftware.com/wiki/fleet-auto-planner
Release Impact Overview
New with this release: a quick overview of how the changes may affect your day-to-day work in Leon. Changes are grouped by area and marked as affecting all operators or optional, with a short note on what to do, if anything. See: https://wiki.leonsoftware.com/wiki/sprint-227-release-impact-overview
In addition to the features mentioned above, changes have been made to Leon API, which can be reviewed in the provided changelog link (https://apidoc.leonsoftware.com/changelogs/changelog-227/).