Aircraft Synchronization

It is used when an external system needs to read, create, update, or match aircraft records in FlightLogger Maintenance. In a FlightLogger integration setup, aircraft synchronization helps ensure that the aircraft used in flight operations can also be recognized correctly in the maintenance system.

Aircraft synchronization is important because aircraft records are the foundation for maintenance planning, usage tracking, defects, work orders, components, and technical records.

What aircraft synchronization is used for

Aircraft synchronization can support:

Reading aircraft records
Creating aircraft records
Updating aircraft records
Matching aircraft by call sign or registration
Configuring aircraft flight logs
Supporting later hours and cycles synchronization
Supporting defect synchronization
Reducing manual aircraft setup work

Aircraft synchronization helps connect the operational aircraft identity with the maintenance aircraft record.

Aircraft synchronization and maintenance control

Aircraft synchronization does not make FlightLogger the maintenance system of record.

FlightLogger may provide or update selected aircraft-related information, but FlightLogger Maintenance remains responsible for:

Maintenance status
Due logic
Repair handling
Defect handling from a maintenance perspective
Component configuration
Work orders
Work packages
Technical records
Compliance documentation

The aircraft record may be synchronized, but the maintenance workflow is still controlled in FlightLogger Maintenance.

How aircraft are identified

Aircraft synchronization uses aircraft identifiers to find the correct aircraft record.

The aircraft API looks for an aircraft by call_sign first. If no aircraft is found by call sign, it then tries to find the aircraft by registration.

This means call sign and registration values are very important.

If these values are inconsistent between systems, synchronization may not find the expected aircraft.

Call sign

The call sign is one of the key identifiers used when looking up an aircraft through the API.

If an aircraft has a call sign, integrations may use it to find the aircraft record.

Because call sign is checked first, it should be kept accurate and consistent when it is used as part of your integration setup.

Registration

Registration is also used to identify aircraft.

If the system does not find an aircraft by call sign, it tries registration.

Registration should be entered consistently across FlightLogger and FlightLogger Maintenance.

Small differences in formatting, spelling, spacing, or punctuation can create matching issues.

Why matching matters

Correct aircraft matching is critical.

If an aircraft is not matched correctly, the wrong aircraft may receive updates, or expected data may not appear.

Incorrect matching can affect:

Aircraft setup
Hours and cycles synchronization
Defect synchronization
Maintenance planning
Aircraft maintenance status
Troubleshooting sync issues

Before relying on synchronization, confirm that each aircraft is represented correctly in both systems.

Aircraft API access

Aircraft synchronization can use OAuth API access.

Supported aircraft API actions include:

List aircraft
Get a specific aircraft
Create an aircraft
Update an aircraft
Add or update aircraft flight-log configuration

The integration must have the required OAuth scopes.

For example:

aircraft_read is required to read aircraft data.
aircraft_write is required to create, update, or configure aircraft-related data.

Only grant the scopes the integration actually needs.

Aircraft data fields

Aircraft synchronization can include aircraft-related fields such as:

ID
Registration
Call sign
Type
Home airport
Current airport
Fuel capacity
Default engine type
Default PMF
Flight logs

The exact data used depends on the integration and the configured API flow.

Flight logs

Aircraft synchronization can also include flight-log configuration.

Flight logs are important because they define the usage counters that may later support hours, cycles, and due calculations.

Flight-log configuration updates use a logs array.

Each log entry should include values such as:

Type
Log type
Measurement type
Total seconds, where relevant

Correct flight-log setup is important before relying on usage-based maintenance planning.

Aircraft sync and hours/cycles sync

Aircraft synchronization and hours/cycles synchronization are connected, but they are not the same thing.

Aircraft synchronization helps ensure the aircraft exists and can be identified.

Hours/cycles synchronization provides usage data for that aircraft.

If the aircraft is not matched correctly, hours and cycles may not appear on the expected aircraft.

For that reason, aircraft synchronization should be verified before troubleshooting usage data.

Aircraft sync and defects

Aircraft synchronization can also affect defect synchronization.

Defects are linked to aircraft. If the aircraft cannot be found, defect data may not sync as expected.

Before troubleshooting missing defects, confirm that the aircraft exists and can be matched by call sign or registration.

Before configuring aircraft synchronization

Before configuring or testing aircraft synchronization, prepare:

A list of aircraft in FlightLogger
A list of aircraft in FlightLogger Maintenance
Registration values
Call sign values
Aircraft model information, if relevant
Flight-log requirements
OAuth Application scopes, if API access is used
FlightLogger Sync settings, if legacy sync is used
A plan for validating aircraft matching

This preparation helps reduce mismatches later.

How to verify aircraft synchronization

After setup, verify that aircraft synchronization works as expected.

Check:

The aircraft exists in FlightLogger Maintenance
The aircraft has the expected registration
The aircraft has the expected call sign
The correct aircraft model is assigned, if applicable
Flight logs are configured correctly
The integration has the required scopes
Sync logs do not show aircraft-related errors
Hours, cycles, or defects appear on the correct aircraft when those sync flows are used

Do not rely only on the existence of the aircraft name. Confirm the identifiers.

Common issues

Aircraft synchronization issues are often caused by setup or matching problems.

Common causes include:

Missing call sign
Incorrect call sign
Missing registration
Incorrect registration
Aircraft exists in one system but not the other
Aircraft is duplicated
Aircraft model is missing or inconsistent
Flight logs are not configured
OAuth scope is missing
FlightLogger Sync configuration is incomplete
The integration is looking in the wrong account or subdomain

When troubleshooting, start by confirming aircraft identity and account context.

Best practices

Keep aircraft registrations consistent across systems.
Use call signs consistently when they are part of your setup.
Avoid duplicate aircraft records.
Verify aircraft matching before go-live.
Confirm flight-log setup before relying on hours and cycles.
Review aircraft sync before troubleshooting defects.
Grant only the required OAuth scopes.
Document which aircraft are expected to synchronize.
Check sync logs during onboarding.
Review aircraft setup after major integration changes.

Summary

Aircraft synchronization helps FlightLogger and FlightLogger Maintenance identify and exchange selected aircraft data.

Aircraft are looked up by call sign first and then registration. Correct aircraft identifiers are therefore essential for reliable synchronization.

Aircraft sync supports integration setup, but FlightLogger Maintenance remains responsible for maintenance status, due logic, work execution, component configuration, technical records, and compliance documentation.