Leon 220 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 the Customer Portal.

Admin

• We added a screen that encourages administrators to enable 2FA or SSO. If an admin (System or Operational) logs in with a password only — without SSO and without 2FA — they will see an additional screen after a successful login explaining why stronger sign-in is worth enabling, with links to the instructions. The screen applies to the web app and is not shown again for the next 24 hours.

Cargo

• We extended the LDM message parser to read how cargo weight is distributed across the aircraft's individual loading points / "compartments" — some operators send this data via LDM instead of CPM. The data is matched to the loading points configured on the aircraft and saved to the ULD model. We also updated the labels in the Fleet module: the LDM column is now ULD Bay, and the configuration window is now ULD Bay Configuration. More information here

Crew

• Crew Calendar — the DAYS ON / DAYS OFF columns and tooltips now calculate according to the time zone selected on the view (BT/LT), not only UTC. Operators planning in base/local time see the correct values without doing the conversion in their heads.
• The arrow marking a duty that crosses midnight now also appears in the Crew Calendar for positions excluded from FTL counting (the "Ignored" flag). For those cases, we use block time, and when there is no FTL duty on a given day, it is enough for at least one flight or positioning to cross midnight.
• The SAFTE-FAST analysis result can now be downloaded to a file — a "Download result" link appeared beneath the result table to fetch the ready file.
• We added a filter to the SAFE Export report that lets you generate data based on drafts — under the same rules as in the Crew Calendar.
• The FTL Violations report can now be generated from draft data — we added a toggle in the filter that controls this.
• In the definition of a "duty"-type duty, we added a "Default to homebase" setting that controls the default airport of the duty. You can choose the aircraft base (Aircraft homebase) or the crew member base (Crew homebase), so new duties suggest the right location without manual corrections.

Crew App

• Links entered in the Pilot Notes field (Airport Directory) are now clickable in the Crew App. Crew can open them directly from the app (e.g. airport pages, AIP) without retyping addresses.

Crew Training

• We added the ability to control the list of crew positions visible in the simulator window. A new Simulators view appeared in the Admin panel (Crew settings group) with a Positions setting — using multiselect checkboxes, you choose which positions (e.g. LTC, TRI, TRE, FE) are available when adding a simulator session. The previously available positions are selected by default, but you can pick any of the Cockpit and Cabin positions. As a result, operators no longer have to wait for code changes when they need a new position in the SIM. More information here

OPS

• We added a new "WX report missing" warning in the Warnings section. It activates when one of the weather messages — METAR or TAF — is missing for the nearest flights (from 6 hours back to 24 hours ahead). The airport code affected by the gap is highlighted, so you immediately know where to fill in the data.
• The aircraft profile now shows two additional informational fields: the aircraft type ICAO code and the category (e.g. midsize). The fields are non-editable — they exist solely to give the user complete information about the aircraft in one place.
• We unified the way fuel prices are displayed across the OPS module and the Crew App. Fuel prices in the Crew App now reflect the same setting (Base / Total) as in the web app — previously, the Crew App always showed base prices.
• We extended the Journey Log with new items:
  • Fuel delivery attachment — a file uploader (fuel receipts). We also added a dedicated permission and API mutations, so receipts can be pulled directly into an external accounting program integrated via the API.
  • Handling/Landing payment method (ADEP and ADES) — a static selection list of the payment methods (the same options as in the Airport Directory).
  • A set of fields related to the ForeFlight integration (correctness of Jeppesen charts, Electronic OFP/Navlog, WX & NOTAM, a comments field) — required by some aviation authorities; all available in the Report Wizard.
• We added a new ICAO Mode-S code field to the aircraft profile. In the Report Wizard (Flight scope), we also made available three additional columns presenting this code in hexadecimal, binary, and octal format, and in the Flight Watch tab, a button with a link to track the aircraft in flight.

Sales

• In the Sales App, the aircraft category is now filled in automatically based on the selected aircraft (the lowest category of the chosen aircraft is selected) — the same as it already works in the web version.
• We fixed the assignment of the requester's account to new passengers. If the requester is not an account but has an account assigned, we now assign that account to new pax (previously nothing was assigned). Works in Sales and OPS.
• We fixed a bug where a realization created from an RFQ generated from a trip had no booking time set. The missing time caused errors, among others, when recalculating the price into another currency in the bookings report.

Wingman and MCP

• We added a tool to the MCP server that pulls data from a selected crew member's FTL Sheet. The tool takes a crew member identifier and a date range (up to 2 months) and returns the same data presented on the FTL Sheet report.

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