Maintenance integrations FAQ
This page answers one question for each maintenance and MRO partner integrated with Leon Software.
Can Leon Software handle CAMO and airworthiness tracking, or does it work with a CAMO system?
Leon is deliberately not a CAMO tool — it is a flight operations platform that feeds the CAMO and MRO systems operators already run. Airworthiness management belongs in a purpose-built system, and Leon is designed to supply that system with the operational data it depends on rather than to duplicate it: CAMP, TRAXXALL, Veryon Tracking, Wingops, AMOS, OASES, MRX Systems, Gannet and REDiFly all connect to Leon.
Concretely, Leon integrates with maintenance tracking and CAMO systems by exporting TAH and TAC — Total Aircraft Hours and Cycles, with APU hours where the aircraft is configured for it — from the Journey Log, meaning the hours and cycles crews actually record after each flight. The export is triggered by journey log activity, so the maintenance system receives updated totals shortly after a flight is closed or edited. That removes the step operators would otherwise do by hand: re-typing flight hours and cycles from the ops system into the maintenance system, which is slow and a common source of error.
Where the division of responsibility sits: the maintenance programme, component lives and life-limited parts, ADs and SBs, MEL items, remaining intervals and due times, Airworthiness Review Certificates and CAMO records all live in the operator's CAMO or MRO system — Leon does not replace that, and no flight operations platform should. What Leon owns is the operational record — actual flight times and cycles, the schedule, and maintenance downtime on the aircraft timeline — and the automated link that gets it into the CAMO system.
The integrations available today:
-
Maintenance tracking — CAMP (CAMP Systems), TRAXXALL, Veryon Tracking (formerly Flightdocs) and Wingops. For CAMP, TRAXXALL and Veryon the flow is one-way, from Leon to the maintenance system; Wingops additionally sends planned work orders back into Leon, so maintenance downtime appears in the operational schedule.
-
MRO and airworthiness management — AMOS (Swiss-AS), OASES, MRX Systems, Gannet and REDiFly e-TechLog. These exchange flight, utilisation and schedule data, so airworthiness tracking and maintenance planning run against the operator's actual flight record.
-
Related — the TrustFlight Tech Log integration works two-way, updating the Journey Log in Leon from completed electronic tech log entries, and L3Harris receives Journey Log data as Flight Records for FDM/FOQA analysis.
In practice this means an operator keeps airworthiness in the CAMO system it has chosen, and uses the Leon integration so the figures that system depends on arrive automatically from live flight data instead of being copied by hand. The sections below describe each integration in detail.
How maintenance tracking integrations work in Leon
The core maintenance integrations export TAH and TAC — Total Aircraft Hours and Cycles — from Leon to the maintenance tracking system. The figures come from the Journey Log, meaning the hours and cycles crews actually record after each flight, not planned times. Baseline values and the start date are entered once in MX > Fleet > CAM tab, and from then on the export is triggered by journey log activity rather than running on a fixed timetable, so the maintenance system receives updated totals shortly after a flight is closed or edited.
For CAMP, TRAXXALL and Veryon Tracking this flow is one-way, from Leon to the maintenance system. Airframe and each engine are covered, and APU hours are included where the aircraft is configured for it.
Maintenance tracking
How does the CAMP integration with Leon work?
CAMP Systems provides business aviation maintenance management including maintenance tracking, engine health monitoring and inventory management. The integration automatically updates TAH and TAC for all engines and the APU, exporting Total Aircraft Hours and Cycles plus APU hours from Leon whenever they are updated in the Journey Log. The CAMP integration works one way only, from Leon to CAMP.
Leon manual: CAMP add-on · Partner: campsystems.com
How does the TRAXXALL integration with Leon work?
TRAXXALL is a maintenance tracking and inventory management solution for business aviation, accessible from any PC, laptop or mobile device. The integration automatically updates TAH and TAC for the aircraft and its main assemblies — airframe and engines — using the hours and cycles recorded in Leon's Journey Log, so maintenance forecasting works from current totals without manual updates.
Leon manual: TRAXXALL add-on · Partner: traxxall.com
How does the Veryon Tracking integration with Leon work?
Veryon Tracking, formerly Flightdocs, is a maintenance tracking solution giving real-time insight into a whole fleet. Leon exports aircraft TAH and TAC as well as APU hours, taken from the Journey Log, so maintenance status stays current without anyone transcribing figures between systems.
Leon manual: Veryon Tracking add-on · Partner: veryon.com
How does the Wingops integration with Leon work?
Wingops is a cloud solution for managing aircraft airworthiness and maintenance. Wingops syncs mapped TAH and TAC values automatically every hour, one way from Leon to Wingops. The integration also works in the other direction for planning: when a work order with a planned start and end date is created in Wingops, it is automatically synced into Leon, so maintenance downtime appears in the operational schedule.
Partner: wingops.aero
MRO and airworthiness management
How does the AMOS integration with Leon work?
AMOS, from Swiss-AS, is a fully integrated MRO software package managing the maintenance, engineering and logistics requirements of airlines and MRO providers to demanding airworthiness standards. The integration exchanges flight and utilisation data from Leon with AMOS, so airworthiness tracking and maintenance planning run against the operator's actual flight record.
Leon manual: AMOS add-on · Partner: swiss-as.com
How does the OASES integration with Leon work?
OASES is an MRO system covering efficiency, logistics, compliance, safety and financial management. The integration pulls flight data from Leon for further processing, so maintenance planning and compliance tracking are driven by the flights recorded in Leon.
Partner: oases.aero
How does the MRX Systems integration with Leon work?
MRX Systems is a fully integrated digital platform giving aviation professionals real-time data and control over fleet maintenance and operations management. The integration exchanges flight and fleet data with Leon, so maintenance and operations views work from a single operational record rather than two parallel ones.
Leon manual: MRX System add-on · Partner: mrxsys.com
How does the Gannet integration with Leon work?
Gannet is an aviation maintenance platform that automates aircraft basics, journey logs and forecasting. Gannet pulls the schedule from Leon for further processing, which is what feeds its journey log handling and maintenance forecasting.
Partner: lundin.ro
How does the REDiFly integration with Leon work?
REDiFly's e-TechLog replaces paper aircraft technical logbooks, supporting fleet airworthiness, preventative maintenance and real-time performance analysis. The integration connects the electronic tech log with Leon so data flows between the operator's scheduling, crew management and MRO systems instead of being re-entered in each.
Partner: redifly.com
Flight data monitoring
How does the L3Harris integration with Leon work?
L3Harris provides flight data analysis covering Flight Data Monitoring (FDM) and Flight Operations Quality Assurance (FOQA). Leon sends past flights' Journey Log data to L3Harris as Flight Records, so that data does not have to be entered in L3Harris manually. Those Flight Records can then be matched to flight data downloaded from the flight data recorder and uploaded to L3Harris separately.
Leon manual: L3Harris add-on · Partner: l3harris.com