Veryon Tracking+ User Guide

1. Overview

2. Prerequisites & Setup

3. Flights

4. Defects

5. Scheduled Maintenance

6. Known Limitations & Workarounds

7. Troubleshooting & FAQs

8. Glossary

1. Overview

What This Integration Does

The Tech Log and Veryon Tracking+ integration automatically synchronises data between your electronic technical log and your maintenance tracking system, reducing manual re-entry and keeping both systems aligned.

Systems Involved

Source of Truth by Data Type

Sync Frequency

The integration polls for changes every 5 minutes. Any action taken in either system may take up to 5 minutes to appear in the other.

2. Prerequisites & Setup

Before the integration can function, the following must be in place. Your TrustFlight implementation contact will confirm these during onboarding.

Matching User Accounts

Users must have matching email addresses in both Tech Log and Veryon Tracking+. This is required for user attribution on flights and defects.

Dedicated Integration User

For defect closure actions, Veryon Tracking+ requires a "Closed By" user. Where direct user mapping is not possible, a dedicated integration user account should be created in Veryon Tracking+. This account will be used for all integration-driven closures. Discuss the appropriate account name and setup with your TrustFlight implementation contact.

Aircraft Registration Configuration

Aircraft must exist in both systems before any data can be synchronised. The integration will not automatically create aircraft records. Confirm with TrustFlight which registrations are in scope for your integration.

Airport / Place Records

All departure and arrival airports must exist as place records in Veryon Tracking+ (matched by ICAO code). If a required airport is missing, flights to or from that airport will not synchronise until the place record is created in Veryon Tracking+.

Enabling the Integration

Once the above prerequisites are in place, enable the integration in Tech Logby following these steps:

1. In the left-hand navigation bar, click Settings.

   

    

2. Click Integrations.

   

    

3. Find the Veryon Tracking+ integration card and click Enable.

   

    

4. Fill out the configuration form and click Link.

   

3. Flights

3.1 Completed Flights (Tech Log→ Tracking+)

What happens: When a flight sector is completed in eTechLog, the integration automatically creates a corresponding technical log record in Veryon Tracking+, including sector timing, utilisation data, and fuel values.

Key points:

• Sector timing, airport information (ICAO), and utilisation values (hours, cycles, landings) are included.

• Fuel data is sent as a follow-up immediately after the flight record is created.

• This is a one-time sync at completion - subsequent edits to a completed flight in Tech Log will not be reflected in Veryon Tracking+.

• Both departure and arrival airports must exist as place records in Veryon Tracking+ for the sync to succeed.

3.2 Trip Updates (Tech Log→ Tracking+)

What happens: Trip updates (e.g. ground runs, totals adjustments) created in Tech Log are pushed to Veryon Tracking+ as maintenance-entry technical log records. This keeps utilisation totals aligned between both systems.

Key points:

• These appear in Veryon Tracking+ as maintenance-entry records, not standard flight entries.

• This is a one-time sync - subsequent edits to a trip update in Tech Log will not be reflected in Veryon Tracking+.

4. Defects

Important: Tech Log is the primary system for defect management. The integration supports a specific set of lifecycle events as described below. Defects created directly in Veryon Tracking+ are not synchronised back to Tech Log(except for the deferral alignment described in Section 4.4).

4.1 Defect Creation (Tech Log→ Tracking+)

What happens: When a new defect is raised in eTechLog, it is automatically created in Veryon Tracking+.

Key points:

• The defect description, ATA reference, aircraft registration, and defect type are included.

• The defect will appear in Veryon Tracking+ using a distinct reference prefix to avoid conflicts with defects raised natively in Veryon Tracking+.

• User matching via email address is required for correct attribution.

4.2 Defect Closure (Tech Log→ Tracking+)

What happens: When a defect is closed in eTechLog, it is automatically closed in Veryon Tracking+.

Key points:

• Closure details including action text, time spent, and the closing user are synchronised.

• The defect must be associated with a flight sector that has previously been synchronised to Veryon Tracking+. Defects not linked to a synced sector cannot be automatically closed in Veryon Tracking+.

• A matched user account (or dedicated integration user) is required for the "Closed By" field in Veryon Tracking+.

4.3 Defect Deferral from Tech Log(Tech Log → Tracking+)

What happens: When a defect is deferred in eTechLog, the deferral is pushed to Veryon Tracking+, including the MEL category, deferral reason, and target date.

Key points:

• The defect must be associated with a previously synced flight sector. Deferrals on defects without a linked synced sector will not synchronise automatically.

• Where Tech Log does not provide a specific due date (e.g. MEL A with cycle-based limits), the integration calculates a fallback target date using standard MEL category intervals:

• Deferral extensions (changes to target date or deferral reference) are not automatically synchronised. See Section 6 for the manual workaround.

4.4 Defect Deferral from Tracking+ (Tracking+ → Tech Log)

What happens: When a deferral update is made in Veryon Tracking+, it is reflected back in eTechLog.

Key points:

• This only applies to defects that originated in Tech Log and have an established sync relationship with Veryon Tracking+.

• Defects created natively in Veryon Tracking+ are not synchronised back to eTechLog.

• If a deferral is applied in both systems within the same 5-minute polling window, a discrepancy may occur. In this case, verify both systems and correct manually as needed.

4.5 Defect Metadata Updates (Tech Log → Tracking+)

What happens: Changes to defect details in Tech Log (e.g. description, ATA chapter, status) are pushed to Veryon Tracking+.

Key points:

• No known limitations for this flow under normal operating conditions.

5. Scheduled Maintenance

5.1 Maintenance Tasks (Tracking+ → eTechLog)

What happens: Scheduled maintenance items from Veryon Tracking+ are pulled into Tech Log when they fall within configured due thresholds. These appear as one-off maintenance items in Tech Log for tracking and resolution.

Default thresholds:

These thresholds are configurable. Contact your TrustFlight implementation contact to adjust them for your operation.

Key points:

• Veryon Tracking+ remains the source of truth for scheduling cadence and repeat intervals. Repeating schedules are not recreated in eTechLog.

• The integration synchronises absolute due thresholds. Remaining values displayed in Tech Log depend on eTechLog's own aircraft totals - ensure totals are aligned between both systems for accurate presentation.

• Landings-based items are supported. Due information is visible on the item record in eTechLog.

6. Known Limitations & Workarounds

7. Troubleshooting & FAQs

Q: A completed flight hasn't appeared in Veryon Tracking+ after more than 5 minutes. What should I check?

Check that both the departure and arrival airports are configured as place records in Veryon Tracking+ (ICAO code match). If a place record is missing, create it in Veryon Tracking+ and contact TrustFlight support to retry the sync.

Q: A defect was closed in Tech Log but it's still showing as open in Veryon Tracking+.

Confirm that the defect is associated with a flight sector that was previously synchronised to Veryon Tracking+. If the sector was never synced, the closure cannot be automatically aligned - the defect will need to be manually closed in Veryon Tracking+.

Q: A deferral was updated in Tech Log but the change isn't showing in Veryon Tracking+.

Deferral extensions are not supported by the Veryon Tracking+ API. The updated deferral details must be manually re-entered in Veryon Tracking+. See Section 6.

Q: A scheduled maintenance item is showing different remaining values in Tech Log vs Veryon Tracking+.

This is typically caused by aircraft totals being out of alignment between the two systems. Verify that hours, cycles, and landings totals match in both systems. Contact TrustFlight support if you need assistance investigating the discrepancy.

Q: How do I contact TrustFlight support?

Please contact TrustFlight support at support@trustflight.com or contact your TrustFlight account representative directly.

8. Glossary