LEON User Guide

Overview of Integration

System Descriptions

Partner: LEON - Flight Planning and Scheduling Software

Integration Summary: Bidirectional synchronization between LEON and TechLog for flight scheduling, crew assignments, and post-flight operational data

Integration Type: Bidirectional

 

Objectives & Benefits

• Automated flight scheduling synchronization reduces manual data entry
• Real-time post-flight data transfer improves operational efficiency
• Seamless crew assignment integration streamlines flight operations
• Enhanced operational visibility through synchronized journey log data

 

Functionality Overview

The integration between LEON and TechLog runs every 5 minutes. The following capabilities are supported:

• Import confirmed trips and flights from LEON to TechLog
• Export completed flight data from TechLog to LEON journey logs
• Automatically create and assign crew members based on LEON flight assignments
• Synchronize flight scheduling changes including updates and cancellations

 

Data Flow Diagrams

Entity Mappings

 

 

Detailed Functionality

Data Exchange Overview

Aircraft Registration

The integration operates within the context of aircraft registrations, and aircraft must exist in both LEON and TechLog before flights can be synchronized. The integration applies to all aircraft in the system unless specifically restricted in LEON configuration.

Note: As of mid-July 2025, LEON has changed their integration process so that after each OAuth authorization, operators must manually select which aircraft to grant TrustFlight access to in their LEON system. By default, all aircraft are unselected after OAuth authorization, requiring manual selection in the LEON admin panel for the integration to function properly. Please visit “Credentials and Authentication” section under “Integration Setup & Configuration” for more details.

 

Trip Status Requirements

Only trips with "Confirmed" status in LEON are imported into TechLog. Trips with other statuses such as "Option" or "Opportunity" are ignored. If a confirmed trip changes to another status, it will be automatically deleted from TechLog.

 

Crew Assignment

Crew members are automatically linked to TechLog based on their email addresses from LEON. If a crew member does not exist in TechLog, they will be created without login access. The system supports both PIC (Pilot in Command) and SIC (Second in Command) assignments based on LEON crew positions, with the first flight's crew determining the trip-level assignments.

 

 

Flight Grouping Options

The integration supports multiple flight grouping methods to accommodate different operational workflows:

• One trip, one flight: Each LEON flight creates a separate trip in TechLog
• Group by date: All flights on the same day are grouped into a single trip with multiple sectors
• External Trip Grouping: Trips and sectors in TechLog mirror the exact grouping structure from LEON (This is the default behaviour)

Pushing Journey Log 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. When the sync completes successfully, this data will be visible in LEON Dashboard under the FW & JL tab, under JL.

 

 

Frequency of Data Sync

The integration operates on standard polling intervals, currently set to every 5 minutes. Synchronization also includes automatic retry mechanisms for failed operations.

Data Fetch Window Configuration: The integration can be configured to limit how far into the future flights are fetched from LEON. This configuration option can be set between 1 and 89 days (defaults to 89 days, which is the maximum allowed by LEON API).

 

Error Handling and Logging

The integration includes comprehensive error handling with structured error responses. We automatically retry data synchronization when facing errors related to server downtimes, but authentication failures and user input errors will not be retried. Detailed error logs are maintained for troubleshooting integration issues.

 

Other Implementation Details

Journey Log Status Configuration

Post-flight data can be sent to LEON with different journey log completion statuses. This is configurable at the operator level to either create open journey logs (default) or closed/completed journey logs based on operational requirements.

The successfully transferred data can be identified by one of two ways depending on the setup of your integration; each 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 as closed i.e. complete

 

To change from the default, please contact TrustFlight support at support@trustflight.com for further assistance.

 

Airport Mapping

Airports are linked between systems using 4-letter ICAO codes. If an airport code is not recognized in TechLog, the system assigns a placeholder code "ZZZZ" to maintain flight data integrity while allowing manual airport addition later.

 

Signed Data Protection

Once postflight data has been signed in TechLog, no further updates from LEON will be applied to that specific flight. This ensures the integrity and immutability of signed operational records.

 

 

 

Data Mapping

The field mappings are organized by entity type based on the data flow shown in the Data Flow Diagrams section. Each entity has specific field mappings configured for synchronization between systems.

 

Trips - Unidirectional Sync (LEON to TechLog)

LEON to TechLog

The fields listed below are configured for importing trip data from LEON to TechLog.

 

LEON Field	TechLog Field	Notes
flight.startTimeUTC	Trip Date	Date extracted from first flight start time
isCommercial	Trip Category	Mapped as "Commercial" if true, otherwise "Private"
flight.flightNo	Trip Number	Flight number used as trip identifier
Aircraft registration	Aircraft	Aircraft registration from LEON flight data
Aircraft registration	Callsign	Uses same registration as callsign
Crew Member who's position is one of: ['CPT', 'PIC', 'LTC', 'TRI']	Pilot In Command	Attempts to match existing users on email address. If none exists we create a simplified version.
Crew Member who's position is one of: ['CPT2', 'SIC', 'FO', 'CPT-', 'FO-', 'CPT*', 'FO*', 'FO/T', 'CPT/T', 'CPT/R', 'LCC', 'LCC/O', 'SAFE']	Second In Command	Attempts to match existing users on email address. If none exists we create a simplified version.

 

 

Sectors (Flights) - Unidirectional Sync (LEON to TechLog)

LEON to TechLog

The fields listed below are configured for importing flight data from LEON to TechLog.

 

LEON Field	TechLog Field	Notes
Start Airport	Departure Airport	ICAO code for departure location
End Airport	Arrival Airport	ICAO code for arrival location
Start Time UTC	Takeoff Time	Scheduled takeoff time
End Time UTC	Landing Time	Scheduled landing time
Crew (PIC positions)	Pilot In Command	Crew member with position CPT, PIC, LTC, or TRI
Crew (SIC positions)	Second In Command	Crew member with position CPT2, SIC, FO, CPT-, FO-, CPT*, FO*, FO/T, CPT/T, CPT/R, LCC, LCC/O, or SAFE
Custom flight_id	preflightCustomData.flight_id	Populated if custom field exists in TechLog
Custom flight_type	preflightCustomData.flight_type	Populated if custom field exists in TechLog

 

The following is how the trip and flight data is is populated in TechLog.

• 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

 

 

Post-flight Data - Unidirectional Sync (TechLog to LEON)

TechLog to LEON Journey Log

The fields listed below are configured for sending completed flight data from TechLog to LEON journey logs.

 

TechLog Field	LEON Field	Notes
Departure Airport	adep	ICAO code for actual departure
Arrival Airport	ades	ICAO code for actual arrival
Block Off Time	bloffUTC	Actual block off time
Take Off Time	toTimeUTC	Actual takeoff time
Landing Time	ldgTimeUTC	Actual landing time
Block On Time	blonUTC	Actual block on time
passengersChildren	children	Number of child passengers
fuelSummary.preUpliftFuel	fuelBeforeUplift	Fuel quantity before uplift
landings	landings	Total number of landings
PIC	pilotFlying	Pilot in command identifier
SIC	pilotMonitoring	Second in command identifier
Total Passengers	pax	From custom fields preflightCustomData.pax_totalor postflightCustomData.pax_total
Aircraft registration + trip date + SRP number	flightLog	Composite journey log identifier
Journey log status	status	Configurable as open or closed based on operator settings
LEON flight distance	distance	Distance from original LEON flight if available
Deicing events	deicing	True if deicing events exist on sector
Oil uplifts by engine	oiluplift	Oil uplift mapped to LEON engine types and IDs
fuelUplift.safPercentage * 100	safFuelBlend	SAF percentage converted from decimal to percentage (0.05 to 5)
SAF percentage exists	safUsed	Boolean indicating if SAF was used
postflightCustomData.pic_fatigue	fatigueScoreCpt	PIC fatigue score from custom field
postflightCustomData.sic_fatigue	fatigueScoreFo	SIC fatigue score from custom field
postflightCustomData.notes	notes	Flight notes from custom field
postflightCustomData.extension_descretion	discretion	Extension discretion from custom field
usedFuel + remainingFuel	blockFuel	Total fuel on board calculation
fuelSummary.usedFuel	usedFuel	Fuel consumed during flight
postflightCustomData.hud_evs	hud_evs	HUD/EVS usage from custom field
postflightCustomData.cat_ii	cat_2_approach_lnd	Category II approach from custom field
apuReading / 3600	totalApuHours	APU hours converted from seconds
apuCyclesReading	totalApuCycles	APU cycles count
fuelSummary.remainingFuel	remainingFuel	Fuel remaining at end of flight
maxFlightLevel	maxFl	Maximum flight level achieved
Calculated fuel uplift	fuelUplift	Calculated from fuelSummary: postUpliftFuel - preUpliftFuel
postflightCustomData.approach_list	approachList	List of approach types from custom field
postflightCustomData.SAFARampcheck	safaRampInspection	SAFA ramp inspection indicator from custom field
postflightCustomData.ACDisinfected	acDisinfected	Aircraft disinfection status from custom field

 

 

 

Limitations & Constraints

Known Limitations

• Aircraft must exist in both LEON and TechLog before flights can be synchronized. The integration will not automatically create aircraft records in either system, requiring manual setup of aircraft configurations prior to data synchronization.
• Only trips with "Confirmed" status in LEON are imported into TechLog. Trips with 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.
• Crew assignment updates require changes to be made at the trip or flight level in LEON. Standalone crew changes without flight modifications will not trigger synchronization to TechLog. Only changes in trips and flights will trigger a data sync.
• When using External Trip Grouping method with multi-day trips in LEON, TechLog duty time calculations become unusable due to date spanning limitations.
• The integration has a configurable data fetch window (daysToFetch parameter) with a maximum limit of 89 days into the future. Flights scheduled beyond this window will not be synchronized until they fall within the configured timeframe.

 

Operational Constraints

• Flight creation, updates, and deletions in LEON are automatically reflected in TechLog, but manual deletions of trips or sectors in TechLog must be manually removed from LEON as this action is not synchronized back.
• Post-flight data synchronization requires completion and sign-off of the postflight in TechLog. Only signed flight data is eligible for transfer to LEON journey logs.
• Journey log status in LEON (open vs. closed) is determined by operator-level configuration and cannot be modified on a per-flight basis. Default behavior creates open journey logs unless specifically configured otherwise.
• 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.
• Custom field mappings for passenger counts, fatigue scores, and other operational data require proper configuration in TechLog before integration activation to ensure successful data transfer.
• Since mid-July 2025, after each OAuth authorization in LEON, operators must manually select which aircraft to grant TrustFlight access to in the LEON admin panel, as all aircraft are unselected by default after authorization.

 

Workarounds and Mitigation Strategies

• For missing aircraft in either system, coordinate with both LEON and TechLog support teams to ensure aircraft registrations exist in both platforms before enabling integration synchronization.
• When airport codes are not recognized in TechLog, the system assigns placeholder code "ZZZZ" to maintain flight integrity. Contact TechLog support to add missing airports for future flight synchronization accuracy.
• If crew members lack email addresses in LEON, they cannot be automatically assigned in TechLog. Ensure all crew members have valid email addresses configured in LEON before flight assignments.
• For External Trip Grouping limitations with multi-day trips, consider using alternative grouping methods (one trip per flight or group by date) to maintain usable duty time calculations in TechLog.
• When post-flight data fails to synchronize due to missing custom fields, verify that all required custom fields are properly configured in TechLog and match the expected field names for successful data mapping.
• For aircraft authorization issues after OAuth, ensure that aircraft selection is completed in LEON's admin panel under Add-ons → TrustFlight → Configuration tab after each integration authorization.

 

 

 

Integration Setup & Configuration

Step-by-Step Setup Guide

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 sections below 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:

1. Go to ‘Settings’⚙️
2. Under System, select the ‘Journey Log’ icon✈️✅
3. Click on Additional settings ☰🌍
4. 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.

1. Go to ‘Settings’⚙️
2. Select ‘Add-ons’🧩
3. Find and select ‘TrustFlight’
4. Click on 'Configuration'
5. 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 refer to the Limitations section for more info about this configuration.

 

Credentials and Authentication

Important Aircraft Authorization Requirement: As of July 2025, LEON has introduced new changes regarding API access to aircraft resources. After each OAuth integration authorization, the operator must choose which aircraft to grant access to the integrator, as by default all aircraft are unselected.

Required Steps After OAuth Authorization:

1. After completing the OAuth authorization process in the TrustFlight dashboard, you must immediately go to your LEON system
2. Navigate to the Admin Panel in LEON
3. Open the Add-ons section and find your TrustFlight integration
4. Go to the Configuration tab
5. Select the aircraft you want to grant TrustFlight access to (or click "Select all" to select all aircraft)
6. Save the changes

Important: This aircraft selection process must be completed every time you perform a new OAuth authorization with LEON. If you require assistance with this process, please contact TrustFlight support at support@trustflight.com for further assistance.

For Testing on Sandbox Environment: If you are performing any tests on a sandbox environment, you must follow the same aircraft selection process after each OAuth authorization to ensure proper integration functionality.

 

 

 

Cost and Licensing

Pricing Information

The LEON integration incurs an additional cost per tail. Please contact your TrustFlight account manager for more information on pricing and to ensure that the integration is added to your contract before proceeding with its activation.

 

 

 

Change Management

Process for Requesting Changes or Enhancements

As the LEON integration continues to evolve, new features and enhancements may be developed based on customer feedback and operational needs.

If your organization 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 customizations.

 

 

 

Appendices

Appendix A: Glossary and Terminology

Term	Definition
LEON	Flight planning and scheduling software system used by aviation operators
TechLog	TrustFlight's electronic technical logbook system for aircraft operations and maintenance
Trip	A series of flights or single flight planned in LEON, transferred to TechLog for operational data
Sector/Flight	Individual flight segment from departure to arrival airport
PIC	Pilot in Command - primary pilot responsible for flight operations
SIC	Second in Command - co-pilot assisting the PIC
Journey Log	LEON's record of completed flight details synchronized from TechLog
External Trip Grouping	Flight grouping method that mirrors LEON's trip structure in TechLog
SAF	Sustainable Aviation Fuel - alternative fuel type tracked in fuel blend percentages
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.
daysToFetch	Configuration parameter that controls how far into the future (1-89 days) flights are fetched from LEON