Leon 224 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

• We have rebuilt the password reset mechanism. After entering their login, the user receives an email with a single-use link and sets the new password in a form inside the application – the email no longer contains any login credentials. The link is generated securely, expires after 30 minutes and is deactivated immediately after use. If 2FA is enabled, the user must also provide a TOTP code More information here
• In the Audit Logs view, we have added a "Changed by" filter, allowing you to narrow the change history down to a single user. Finding out who changed something and when is now much faster.

Airport Directory

• Airport membership in the Refuel EU programme is now stored per year, allowing Leon to keep track of historical changes in the list of covered airports. Operators can override the applicable years for individual airports in the Airport Directory, with changes applying only to their account. For flights, Leon determines the applicable Refuel EU status based on the year of the flight date. More information here

API

• The API query returning modified flights (getModifiedFlightList) now returns two additional fields: createdFlightNidList and modifiedFlightNidList, which list the IDs of newly created and modified flights separately.

Crew

• In the Crew Calendar, positionings that cross midnight now show an arrow – exactly as flights do. If the positioning is part of a duty, the duty determines the arrow; otherwise, the positioning times are used.
• The Crew Timeline now suggests missing hotels (red H) also for crew positions excluded from FTL calculations, such as engineers or ground staff, whenever they end an activity away from their home base with more than 10 hours before the next one. More information here
• We have fixed an issue where publishing a roster draft from the Crew Timeline could delete previously published duties. After this change, the roster state after publication matches the published draft exactly.
• In the Edit duty window, you can now decide which notes should be cleared. Previously, the "Clear notes" checkbox removed Planner, Pilot and Day trading notes all at once. More information here
• Assigning crew in the Assign Crew window now checks whether the crew member already has a duty planned in the selected period. The validation works for both flights and pairings and can be ignored if needed. The checked period is based on the start and end of the pairing, or the start of the first and end of the last selected flight.
• In the positioning add and edit window, we now display a time zone marker (Z, BT or LT) next to the STD and STA fields. The marker updates immediately when the time zone is changed.

Crew App

• The hotel booking preview in the Crew App now shows more details – the Booking / Confirmation number and the airport the booking relates to. Previously, crew members only saw the check-in/out dates and the hotel name, even if the remaining data had been entered in the web version.

Crew Planning

• The Edit Crew Composition window in pairings now supports positionings. Positionings that are part of a pairing appear as separate tabs, where crew members can be added and removed.
• The maximum layover length and the maximum pairing length are now configurable in General Settings – Crew Planning – Pairing settings. The defaults are 24h (layover) and 72h (pairing), with maximum values of 72h and 168h. More information here
• We have fixed overlapping crew member labels in the Pairings – Assign crew window. With larger crew compositions the list is finally legible.
• The above changes apply to the Beta Crew Pairings feature, currently available only to selected customers. If you would like to test it, please contact our support team.

Crew Training

• A new "Instructor recognised by" setting in General settings – Crew planning lets Leon recognise a Line Training instructor either by their position on the flight (LTC/TRI, as before) or by their rating on the sector's aircraft type, so an instructor flying as CPT or FO no longer triggers a warning. More information here
• We have introduced a new, cleaner and more usable view for configuring required certificates / endorsements – Qualification Configuration has been rewritten from scratch and is now available to all operators, with no need for us to enable it on our side. More information here

OPS

• We have extended the Journey Log with several new items requested by operators – they allow more flight information to be kept directly in the JL instead of in notes on the trip. More information here
• In the FW tab, we have added a dedicated Return to Ramp (RTR) section for recording situations where an aircraft leaves the gate but returns to the ramp without performing the flight. RTR entries can include Off block / On block times and a note, and can be added or edited directly from the FW panel. More information here

Phonebook

• The Phonebook now takes operator bases (offices) into account. A contact is assigned to specific bases, and when creating or editing a contact, you can only select the bases you have permissions for. More information here

Sales

• In the Avinode configuration we have separated two functions that were previously controlled by a single checkbox: receiving standard requests (RFQ) and searching for subcharters (sourcing). Operators without the "API-Sourcing Trips" add-on purchased on the Avinode side will no longer receive 403 errors or lose regular RFQs. More information here

Sched

• Flights published from the Sched module now receive a calculated flight time (block time minus taxi in/out from the airports). As a result, MVT messages have the flight time filled in correctly instead of being empty due to a missing Flight Time in the FLIGHT tab. 

Wingman and MCP

• We have added a new MCP tool returning a list of crew members, i.e. people holding at least one rating on any aircraft type. The result can optionally be narrowed down to a specific aircraft type.

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