Leon 219 released

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.

Important Notices

• Starting July 1st, anonymous ticket submissions will no longer be supported in the Customer Portal. All users will be required to log in before submitting a support request. If you haven't registered yet, please create an account at Customer Portal.

Admin

• Added integration with the Prodefis system, allowing operators to connect Leon with the Prodefis platform for operational data exchange.
• Added a new section in Admin → Flight Editing: Enabled Approach Types. It is possible to enable approach types which then will show in the Journey Log.

Crew

• Added a warning when saving a flight to inform users that a tail swap (aircraft type change) may result in crew members without the required rating being removed from the flight. The validation is disabled by default and can be enabled in Admin → Flight Editing → Flight editing warnings.
• Fixed the display of the midnight-crossing duty arrow in Crew Calendar. The arrow is now also visible for positions excluded from FTL calculations (marked as “Ignored”). If there is no FTL duty on a given day, the arrow appears when at least one flight or positioning crosses midnight.
• Added support for draft data in Roster Validations. When draft mode is enabled on Crew Calendar or Crew Timeline, roster validation now takes draft data into account, giving planners early feedback on issues before changes are confirmed.
• Introduced a new oAuth client type: User Access. This extends the existing authorisation mechanism by allowing integrations to operate with the permissions of a specific Leon user, providing context-based access for integrators.

Crew App

• Added OCR support when creating passengers in the Crew App mobile application. Users can now scan identity documents (passports, ID cards) and automatically populate passenger details from the OCR scan, eliminating manual data entry. More information here

Crew Training

• Extended the Crew Currency system with a new option for the Pilot Monitoring position. Currency requirements can now be configured separately for pilots acting as Pilot Monitoring, which is important for operators using special PM procedures.

FTL

• Added the ability to generate FTL Sheets for multiple crew members at once. The new endpoint and backend model support bulk generation and distribution of FTL sheets, significantly speeding up the workload for planners when processing large crew groups. More information here

OPS

• Added the ability to configure the Approach Type list in Flight Editing settings — analogous to the existing Approaches list. This ensures that only the approach types previously activated by the operator are visible in the Journey Log, keeping data tidy and tailored to actual operations. Configuration is available in Admin → Flight Editing.
• Extended Journey Log element configuration with per-base support. It is now possible to specify which operational bases (offices) a given JL element should be active for, independently of per-aircraft settings. Both configurations can be used simultaneously — an element will be available on flights meeting at least one of the conditions. More information here
• Added a new Plan Remaining field to the Fuel element in the OPS checklist. This field allows the planned remaining fuel after a flight to be recorded, making fuel management and reporting easier. The value is also available as a column in Report Wizard (scope: Flight).
• Added support for the Schedule Revision Reason field in the OPS checklist. A selector with a list of standard schedule change reasons (e.g. AOG, Weather Conditions, Client Request, Permit Status, and others) has been added to the checklist element. The selected reason is also available as a column in Report Wizard (scope: Flight). The list of values matches the same list available in the Journey Log. More information here
• Added ForeFlight integration for importing Actual Take-Off Weight (TOW) into the Journey Log in Leon. Data is automatically retrieved from the flight plan in ForeFlight and available as columns in Report Wizard. This feature facilitates emissions reporting under EU ETS.
• Extended the SSIM import with a change preview before confirmation. When importing updates to existing flights, the system now shows exactly which parameters will be modified — the schedule and flight data are presented in a “before → after” format with clearly highlighted changed values. Flights are grouped into sections: modified, added, removed.
• Added the ability to set a fixed flight number for Future Flights and Executed Flights files in the AMOS integration. If an operator's flight numbers contain no digits (consisting only of a code), the files generated for AMOS were not being created correctly. The new Fixed flight number configuration field provides a workaround for this limitation. Configuration is available in the AMOS integration settings.

Sales

• Added MVT message support for non-boarded passengers. The system can now generate and send MVT messages when passengers have not been boarded on a flight. This is an important feature for operators required to report the absence of passengers under the IATA standard.
• Added an AOC filter to the RFQ (Request for Quotation) list. Users can now filter quote requests by AOC (Air Operator Certificate), making it easier to manage large RFQ lists in multi-operator environments.
• Added an AOC filter to the Quote scope in Report Wizard. Quotation reports can now be narrowed down to a specific AOC, improving the accuracy of sales analyses across multiple certificates.
• Extended the tax calculation logic to take into account data from boarding and the Journey Log. Taxes will now be calculated using actual operational data (passenger boarding, JL closure) rather than planning data alone, improving the accuracy of tax calculations and invoices.
• Added new elements to the Phonebook, when creating a New Contact: VAT Holder, Client Remarks, AOC Certificate, AOC Number, AOC Notes, WWW, Fax.

In addition to the features mentioned above, changes have been made to Leon API, which can be reviewed in the provided changelog.