FlightLogger Sync Overview

It helps maintenance teams work with aircraft usage and operational inputs without relying only on manual updates. This can support maintenance planning, due tracking, defect handling, and aircraft status review.

FlightLogger Sync is part of the integration setup between FlightLogger and FlightLogger Maintenance, but it is important to understand what it does and what it does not do.

What FlightLogger Sync is used for

FlightLogger Sync supports selected data flows between FlightLogger and FlightLogger Maintenance.

Depending on your configuration, it may be used for:

• Aircraft synchronization
• Manual aircraft sync
• Hours and cycles sync
• Manual hours/cycles sync
• FlightLogger API key and endpoint configuration
• Sync log review
• Supporting operational data used in maintenance planning

FlightLogger Sync helps bring operational input into the maintenance workflow, but it does not replace maintenance planning or compliance control.

FlightLogger Sync and OAuth Applications

FlightLogger Sync and OAuth Applications are both related to integration, but they are not the same thing.

FlightLogger Sync is used for legacy sync configuration and selected synchronization services. It can store the FlightLogger API key and endpoint used by manual sync services.

OAuth Applications are used for controlled API access with client credentials and scopes.

Your integration setup may use one or both, depending on the design.

Do not assume that creating an OAuth Application automatically configures FlightLogger Sync. Do not assume that FlightLogger Sync automatically grants API access through OAuth.

What data can sync

The exact data depends on your account setup and configured integration flows.

FlightLogger Sync may support operational data such as:

• Aircraft information
• Aircraft usage
• Hours
• Cycles
• Data needed to support maintenance planning

Other integration flows may also involve defects, aircraft models, OAuth API access, or outbound webhooks. These are covered in separate integration articles.

Why sync matters for maintenance

Maintenance planning often depends on current aircraft usage.

If hours or cycles are not updated, maintenance due calculations may become incomplete, outdated, or uncertain.

For example, sync can help planners understand:

• Whether an aircraft is approaching due maintenance
• Whether usage-based requirements are affected by recent flights
• Whether aircraft usage has changed since the last planning review
• Whether data from FlightLogger is available for maintenance planning

This helps reduce manual data entry and supports more reliable maintenance planning.

What FlightLogger Maintenance owns

Even when FlightLogger Sync is enabled, FlightLogger Maintenance remains the maintenance system of record.

FlightLogger Maintenance owns:

• Maintenance status
• Due logic
• Recurring maintenance
• AMP-related maintenance handling
• Defect handling from a maintenance perspective
• Repair closure
• Work orders
• Work packages
• Component configuration
• Technical records
• Compliance documentation

FlightLogger may provide operational input, but maintenance decisions and records remain in FlightLogger Maintenance.

What sync does not mean

FlightLogger Sync does not mean that every record is mirrored between systems.

Do not assume that FlightLogger receives or stores a full copy of:

• Work orders
• Work packages
• Component history
• Inventory records
• Technical records
• Compliance documentation
• Full maintenance status details

The integration is selective and should be understood as a controlled data connection, not a complete shared system.

FlightLogger Sync configuration

FlightLogger Sync configuration may include a FlightLogger API key and endpoint.

These settings are used by legacy sync services, including manual aircraft sync and manual hours/cycles sync.

Configured endpoints must be valid public http or https URLs. Private, loopback, link-local, or reserved addresses are not accepted.

This helps ensure that the sync configuration points to an accessible and appropriate endpoint.

Manual aircraft sync

Manual aircraft sync can be used to bring aircraft-related data into FlightLogger Maintenance through the configured sync connection.

Before relying on aircraft sync, make sure aircraft records are matched correctly between systems.

Aircraft matching is important because maintenance planning depends on the correct aircraft being connected to the correct operational data.

Manual hours and cycles sync

Manual hours/cycles sync can be used to update FlightLogger Maintenance with usage data from FlightLogger.

Hours and cycles are important because they may affect:

• Due maintenance
• Recurring maintenance
• Forecasting
• Aircraft maintenance status
• Usage-based requirements

If usage data is missing or incorrect, planners should review both the sync setup and the aircraft counter configuration.

Sync logs

The FlightLogger Sync area includes sync logs.

Sync logs help administrators and support users understand recent sync activity.

They may show:

• Whether sync actions succeeded
• Whether sync actions failed
• Short failure summaries
• More detailed technical error information for administrators

Detailed sync log messages are mainly intended for troubleshooting and support. They should be reviewed carefully before being shared in customer-facing communication.

When to check FlightLogger Sync

You should check FlightLogger Sync when:

• Setting up the integration for the first time
• Aircraft data is not appearing as expected
• Hours or cycles are not updating
• Maintenance status looks incorrect
• A planner reports missing usage data
• Sync logs show failures
• FlightLogger endpoint or API key settings change
• Preparing for go-live
• Troubleshooting integration issues

Regular checks are especially useful during onboarding and shortly after go-live.

Common causes of sync issues

If data does not appear as expected, check:

• Whether FlightLogger Sync is configured
• Whether the endpoint is correct
• Whether the API key is correct
• Whether the endpoint is publicly reachable
• Whether the aircraft exists in both systems
• Whether aircraft matching is correct
• Whether hours/cycles are available in FlightLogger
• Whether the relevant aircraft counters exist in FlightLogger Maintenance
• Whether sync logs show an error
• Whether the user has permission to view the relevant data

Some issues are caused by setup or mapping, not by the sync process itself.

FlightLogger Sync and defects

Defect synchronization is part of the wider FlightLogger integration, but it should be understood carefully.

Pilot-origin defects may enter FlightLogger Maintenance from FlightLogger depending on the configured integration flow.

Once defects are in FlightLogger Maintenance, they become part of the maintenance process. They can be assessed, linked to work, deferred, rectified, or closed according to maintenance workflows.

Defect matching may use best-effort rules, so users should review unexpected duplicates or missing updates carefully.

Best practices

• Confirm aircraft matching before relying on sync.

• Review hours and cycles after setup.

• Monitor sync logs during onboarding.

• Do not assume sync means full data mirroring.

• Keep FlightLogger Sync credentials secure.

• Use OAuth Applications separately when API access is required.

• Document who owns the integration setup.

• Check sync after configuration changes.

• Review sync before go-live.

• Investigate mismatches early.

Summary

FlightLogger Sync helps connect selected FlightLogger operational data with FlightLogger Maintenance.

It can support aircraft and usage-related sync flows that help maintenance planners work with current operational information. However, FlightLogger Sync is not a full mirror between systems.

FlightLogger can provide operational input. FlightLogger Maintenance remains the system where maintenance status, due logic, work execution, repair handling, technical records, and compliance documentation are managed.