Overview
The integration between TrustFlight Tech Log and LEON is designed to streamline the flow of data between the two systems. This two-way integration automates the import of Trip, Flight, and Crew details from LEON into the Tech Log and, once a flight is complete, updates LEON with sector data.
Enabling the integration ensures minimal disruption to current workflows and helps automate data synchronisation for enhanced operational efficiency.
Once the integration has been added to your agreement, the visibility to enable the integration can then be enabled by a TrustFlight Administrator, allowing you to create the link between Tech Log and LEON. Please note, in order to complete this setup you will also need administrative access in LEON.
Functionality
Overview
The integration between LEON and TrustFlight Tech Log allows for seamless data transfer, automatically creating flights in Tech Log when they are scheduled in LEON and syncing pilot and flight information between the two systems. The integration helps streamline workflows by reducing manual input and keeping both systems synchronised in real time.
Aircraft
Once the integration is enabled, all aircraft in Tech Log are automatically included. To ensure proper data flow, required fields in Tech Log must be completed before the integration is activated.
Syncing Trips & Flights
Summary
- If a flight is created in LEON and Status is set to 'Confirmed', it will be automatically created in Tech Log.
- If a flight is deleted in LEON, it will be deleted in Tech Log.
- If a flight is updated in LEON, it will be updated in Tech Log.
- LEON and Tech Log will sync every 5 minutes (e.g. 10:30, 10:35, 10:40…)
Importing Data to TrustFlight
Trip Data
The following key fields are mapped from LEON to Tech Log for both trips and flights:
- Trip Date: From scheduleStartDay
- PIC and SIC: From crewList
- Trip Category: Mapped as "Commercial" if specified, otherwise set as "Private"
Flight Data
Once the trip is marked as confirmed in LEON; resulting in the creation in Tech Log. The following trip data is mapped.
- Date: This is created as the trip date in the Tech Log
- Aircraft: The aircraft to assign the Trip and Flight detail to
- Departure: Departure on the Tech Log Preflight Tab
- Destination: Arrival on the Tech Log Preflight Tab
- STD: Take off time on the Tech Log Postflight Tab
- STA: Landing time on the Tech Log Postflight Tab
Crew
Crew members are automatically linked to Tech Log based on their email addresses. If a crew member does not exist in Tech Log, they will be created without login access. The system supports both PIC (Pilot in Command) and SIC (Second in Command), with the first flight’s crew determining the trip-level assignments.
Passengers and Fluids
Passenger numbers must be entered manually into Tech Log, as LEON provides only a total count before the flight. Fluid data (fuel, oil, hydraulic) must also be recorded in Tech Log, as it is not imported from LEON.
Statuses
Only trips marked as "Confirmed" in LEON are imported. Trips with statuses like "Option" or "Opportunity" will be ignored. If a trip changes from "Confirmed" to another status, it will be deleted from Tech Log.
Updating and Deleting Trips/Flights
Changes in LEON, including flight creation, updates, or deletions will be reflected in Tech Log automatically, however, if you delete a trip or flight in Tech Log, this will need to be manually deleted in LEON. Please note the limitation with Updating/Adding Crew below.
Pushing Data to LEON
Once the postflight has been signed off and synced in Tech Log, the data will automatically sync back to the corresponding trip/flight in LEON (using the sync rules mentioned in the above Summary). This completed data passed through the API goes into the FW & JL tab, under JL; when data has been successfully synced back.
Identifying Tech Log Data in LEON
This successfully transferred data can be identified by one of two ways depending on the setup of your integration; both of which have different meanings.
An orange spot against the trip row - TrustFlight sends the data to the JL as open (default)
A green spot against the trip row - TrustFlight sends the data to the JL closed i.e. complete
To change from the default, please contact TrustFlight support at support@trustflight.com for further assistance.
Field Mapping Overview
LEON to Tech Log (Trip)
These are the fields transferred from LEON to Tech Log when a trip is created or updated:
| Tech Log Field | LEON Field | Notes |
| Date | flight.startTimeUTC | We remove the time and only take the date. |
| Trip Category | if isCommercial then commercial else private | |
| Number | flight.flightNo | |
| Aircraft | Acft registration | |
| Callsign | Acft registration | |
| Pilot In Command | Crew Member who's position is one of: ['CPT', 'PIC', 'LTC', 'TRI'] | Attempts to match existing users on email address. If none exists we create a simplified version. |
| Second In Command | Crew Member who's position is one of: ['CPT2', 'SIC', 'FO', 'CPT-', 'FO-'] | Attempts to match existing users on email address. If none exists we create a simplified version. |
LEON to Tech Log (Flight)
These are the fields transferred from LEON to Tech Log when a flight is created or updated:
| Tech Log Field | LEON Field | Notes |
| Departure Airport | Start Airport | |
| Arrival Airport | End Airport | |
| Pilot In Command | Crew Member who's position is one of: ['CPT', 'PIC', 'LTC', 'TRI'] | Attempts to match existing users on email address. If none exists we create a simplified version. |
| Second In Command | Crew Member who's position is one of: ['CPT2', 'SIC', 'FO', 'CPT-', 'FO-'] | Attempts to match existing users on email address. If none exists we create a simplified version. |
| Takeoff Time | Start Time UTC | |
| Landing Time | End Time UTC | |
| preflightCustomData.flight_id | If the value exists in Preflight custom fields, we will populate it. | |
| preflightCustomData.flight_type | If the value exists in Preflight custom fields, we will populate it. |
Tech Log to LEON (JL)
These are the fields transferred from Tech Log to LEON after a flight is completed:
| LEON Field | Tech Log Field | Notes |
| catering | Leon throws an error if this is not set, we set this value as false. | |
| adep | Departure Airport | |
| ades | Arrival Airport | |
| bloffUTC | Block off time | |
| toTimeUTC | Take off time | |
| ldgTimeUTC | Landing Time | |
| blonUTC | Block on Time | |
| children | passengersChildren | |
| fuelBeforeUplift | fuelSummary.preUpliftFuel | |
| landings | landings | |
| pilotFlying | PIC | |
| pilotMonitoring | SIC | |
| pax | preflightCustomData.pax_total OR postflightCustomData.pax_total | |
| flightLog | Joining of aircraft registration, trip date, trip srpNumber. | |
| status | An operator level config can be set to set the journey log as open or closed. | |
| distance | If the distance is set from the Leon flight, we take this value. | |
| deicing | If deicing events exist on the Tech Log Sector, true. | |
| oiluplift | Map through fluid uplifts on flight, matching fluid destination to the Leon engine type, then storing uplift value against the engineId from Leon. | |
| safFuelBlend | fuelUplift.safPercentage | multiplied by 100 (0.05 to 5). |
| safUsed | Does safPercentage exist? | |
| fatigueScoreCpt | postflightCustomData.pic_fatigue | |
| fatigueScoreFo | postflightCustomData.sic_fatigue | |
| notes | postflightCustomData.notes | |
| discretion | postflightCustomData.extension_descretion | |
| blockFuel | usedFuel + remainingFuel. | |
| usedFuel | fuelSummary.usedFuel | |
| hud_evs | postflightCustomData.hud_evs | |
| cat_2_approach_lnd | postflightCustomData.cat_ii | |
| totalApuHours | apuReading | divided by 3600. |
| totalApuCycles | apuCyclesReading | |
| remainingFuel | fuelSummary.remainingFuel | |
| maxFl | maxFlightLevel | |
| fuelUplift | fuelSummary.postUpliftFuel - fuelSummary.preUpliftFuel | |
| approachList | postflightCustomData.approach_list |
Limitations
- Aircraft Synchronisation: Flights will only be transferred if the aircraft exists in both LEON and Tech Log. Ensure that all aircraft are correctly configured in both systems before the integration is enabled.
- Trip Confirmation: Only trips that have a "Confirmed" status in LEON will be imported into Tech Log. Any trips with other statuses like "Option" or "Opportunity" will be ignored. If a confirmed trip is later downgraded to another status, it will be deleted from Tech Log.
- Flight Creation, Update, and Deletion: As mentioned in the Functionality section, flight creation, updates, and deletions in LEON will be reflected in Tech Log automatically. There is no manual intervention required, and the system will keep both platforms synchronised. However, if a trip or sector is removed in Tech Log, this will need to be manually deleted from LEON.
- Updating/Adding Crew will currently not update in Tech Log unless a change has been made to the Trip or Flight in LEON.
- When using the grouping method External Trip Grouping and the trips in LEON are across multiple days, Tech Log duty becomes unusable.
Cost
The LEON integration incurs an additional cost per tail. Please contact the TrustFlight sales team for more information on pricing and to ensure that the integration is added to your contract before proceeding with its activation.
Implementation
The ability to enable the LEON integration can be granted by a TrustFlight Administrator, allowing the customer to create the link between Tech Log and LEON. In order to enable the integration, the customer must also have administrative access to the LEON system. The integration must be enabled separately for each operator (e.g., AOC) that you manage.
Please follow the three sections below (Enabling the Integration (TrustFlight), Setup in LEON (Journey Log) and Restrict Aircraft to Integrate (LEON)) for a successful implementation. If after completing the guided steps the integration is not successfully enabled, please contact TrustFlight support at support@trustflight.com for further assistance.
Enabling the Integration (TrustFlight)
1. Navigate to the Settings section within the TrustFlight Dashboard.
2. Select Integrations and locate the LEON integration under the relevant operator.
3. Click Enable underneath the LEON integration.
4. Enter your LEON Operator ID (e.g., “myoperator” from “https://myoperator.leon.aero”) and select ‘Link’
5. Input your login and password; then confirm
Setup in LEON (Journey Log)
In order to successfully push data to LEON, the integration requires that the system be allowed to submit partial Journey Log data. You must enable this option within the Leon User Interface:
- Go to ‘Settings’⚙️
- Under System, select the ‘Journey Log’ icon✈️✅
- Click on Additional settings ☰🌍
- Enable the option ‘Allow not completed JL to be entered’
Restrict Aircraft to Integrate (LEON)
By default, all aircraft will be included on the integration between TrustFlight and LEON, however, if you wish to restrict which aircraft are to have data passed through the API, this can be achieved through the LEON settings using the following steps.
- Go to ‘Settings’⚙️
- Select ‘Add-ons’🧩
- Find and select ‘TrustFlight’
- Click on 'Configuration'
- Select the aircraft registrations you wish to integrate with TrustFlight
6. ‘Save’
Flight Grouping
Please speak to your TrustFlight representative to specify how you wish to group flights in Tech Log, by one of the following:
- One trip, one flight - One trip and flight in LEON will be reflected as one trip and sector in Tech Log
- One trip, multiple flights (group by date) - All trips/flights in LEON with the same date will be grouped in Tech Log with one trip and multiple sectors
- External Trip Grouping - Trips and Sectors in Tech Log will be grouped identical to Trips and Flights in LEON. Please see Limitations on this configuration above.
Requesting Enhancements
As the LEON integration continues to evolve, new features and enhancements may be developed based on customer feedback and operational needs. If your organisation requires additional functionality that is not currently covered by the existing integration, please contact TrustFlight support at support@trustflight.com to discuss possible improvements or customisations.
Terminology
| Term | Definition |
| LEON | A flight scheduling and management system used by aviation operators. |
| Tech Log | TrustFlight's electronic technical logbook system that tracks aircraft operations and maintenance. |
| Trip | A series of flights or a single flight planned and operated within LEON, transferred to Tech Log for operational data. |
| Flight | A single flight sector, with detailed data on departure, arrival, crew, and aircraft performance. |
| PIC | Pilot in Command—the main pilot responsible for operating the flight. |
| SIC | Second in Command—the co-pilot assisting the PIC. |
| Sector | A single flight leg (e.g., from one airport to another). |
| Block Off/Block On | The times when the aircraft starts (Block Off) and stops (Block On) moving on the ground. |
| Journey Log (JL) | A record of a flight's details, synced from Tech Log back to LEON after the flight. |
| STD | Scheduled Time of Departure—the planned takeoff time of the flight. |
| STA | Scheduled Time of Arrival—the planned landing time of the flight. |