Skip to content
  • There are no suggestions because the search field is empty.

Configure Aircraft Model Sync

Aircraft Model Sync is used to synchronize aircraft model data into FlightLogger Maintenance from a configured external data source.

Aircraft models are important because they help define shared aircraft structure, model-level information, and setup that can be reused across aircraft. Correct aircraft model data supports aircraft setup, maintenance planning, applicability, and later workflow consistency.

Aircraft Model Sync should be configured carefully because it can create or update aircraft model records in your account.

What Aircraft Model Sync is used for

Aircraft Model Sync helps your organization bring aircraft model data into FlightLogger Maintenance.

Depending on your configuration, it can be used to:

  • Connect an external aircraft model data source
  • Pull model data from that source
  • Create aircraft models in FlightLogger Maintenance
  • Update existing aircraft models
  • Review recent sync logs
  • Monitor sync status
  • Identify models that are connected to an external source

Aircraft Model Sync is separate from normal aircraft sync. Aircraft models describe shared model-level data, while aircraft records represent individual aircraft.

Why aircraft model sync matters

Aircraft models are used as shared reference data.

A model may be used by several aircraft. If model data is inconsistent or incomplete, it can affect aircraft setup and planning later.

Aircraft model data may support:

  • Aircraft creation
  • Aircraft model selection
  • Model-level descriptions
  • Manufacturer information
  • Model numbers
  • Specifications
  • Maintenance requirements
  • External source tracking

When this data comes from another system, sync helps reduce manual entry and keep model information aligned.

Aircraft models vs aircraft

An aircraft model is not the same as an aircraft.

An aircraft model describes the shared model or type.

An aircraft is a specific aircraft in your fleet.

For example, an aircraft model might describe a general aircraft type, while individual aircraft records have their own registration, usage, defects, components, work orders, and technical records.

Aircraft Model Sync deals with the model-level record, not the full aircraft maintenance record.

How Aircraft Model Sync matches records

Aircraft Model Sync uses two key values to identify model records:

  • external_id
  • external_data_source

Together, these values are used to find an existing aircraft model or create a new one.

This means the same external ID can only be understood correctly when the data source is also known.

For example, a model from one external source should not accidentally update a model from another source.

What data can be synchronized

The syncable aircraft model fields include:

  • Name
  • Manufacturer
  • Model number
  • Description
  • Specifications
  • Maintenance requirements

The exact data depends on what the external source provides.

If required external identifiers are missing, the sync cannot reliably create or update the correct model.

Data source configuration

Aircraft Model Sync uses data source configurations.

A data source configuration may include:

  • Name
  • Endpoint
  • Status
  • Sync frequency
  • API key
  • Authentication type

The data source name is important because it can be used as the external data source value for model matching.

Endpoint

The endpoint is the external source that Aircraft Model Sync uses to fetch aircraft model data.

Before configuring the endpoint, confirm that:

  • The endpoint is correct
  • The endpoint returns aircraft model data
  • The endpoint is reachable
  • The endpoint belongs to the expected source
  • The endpoint is suitable for use by FlightLogger Maintenance

If no endpoint is configured, sync cannot fetch data from the external source.

API key

Aircraft Model Sync can use an API key configured on the data source connection.

The sync service uses the connection’s own API key.

This is important: Aircraft Model Sync does not fall back to the general FlightLogger API key used by other FlightLogger sync flows.

If no API key is configured for the aircraft model data source, sync may fail.

Treat the API key as sensitive. Only trusted administrators should manage it.

Sync status

The Aircraft Model Sync page can show sync status information.

The status may reflect:

  • Whether sync is active
  • Whether the setup is inactive
  • Whether the setup is degraded
  • Last sync time
  • Last sync status
  • Error count
  • Number of configured connections

This helps administrators understand whether aircraft model sync is configured and whether recent sync activity has succeeded.

Sync logs

Aircraft Model Sync includes sync logs for aircraft model records.

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

They can show information such as:

  • Which aircraft model was affected
  • Whether the sync created or updated a record
  • Whether the sync succeeded or failed
  • Which integration connection was used
  • Recent errors

Use sync logs when troubleshooting missing or unexpected aircraft model updates.

Recent errors

  • The Aircraft Model Sync area can show recent failed sync logs.

  • Recent errors are useful during setup, testing, and go-live validation.

  • If aircraft model data is not appearing as expected, review recent errors before changing aircraft model records manually.

  • Models with sync

  • The Aircraft Model Sync page can show models that already have external source information.

  • This helps administrators identify which aircraft models are connected to an external data source.

  • A model must have external source information for single-model sync to find the matching data source.

  • Sync one model
  • Aircraft Model Sync can queue a sync job for a single aircraft model.

This requires:

  • A selected aircraft model
  • External source information on the aircraft model
  • A matching active data source configuration
  • Permission to manage the integration connection
  • Permission to update aircraft models

This permission requirement is important. Managing the integration connection alone should not allow a user to change aircraft model data.

Sync all models

Aircraft Model Sync can also queue sync jobs for active configured data sources.

This is useful when you want to pull model data from one or more configured sources.

If no active outbound data sources are configured, sync all cannot run.

The sync jobs run in the background.

Previewing changes

The aircraft model API can support previewing changes before persisting them.

When preview is used, the system can return the changes that would be applied without saving them.

This is useful when an integration needs to review what would change before applying updates.

Old values are only included in the preview when the caller has the required read access.

Required permissions

Aircraft Model Sync can change aircraft model data.

For that reason, users need the correct permissions.

Depending on the action, a user may need permission to:

  • Read integration connections
  • Create or update integration connections
  • Manage integration connections
  • Update aircraft models
  • Read aircraft model sync logs

If a user can see the sync page but cannot run a sync, review both integration permissions and aircraft model permissions.

Common setup issues

If Aircraft Model Sync does not work as expected, check:

  • Is there an active data source configuration?
  • Is the endpoint configured?
  • Is the API key configured?
  • Is the data source name correct?
  • Does the remote data include external_id?
  • Does the aircraft model have external_id and external_data_source?
  • Does the model’s external data source match an active connection name?
  • Does the user have permission to manage sync?
  • Does the user have permission to update aircraft models?
  • Do sync logs show a failure?
  • Is the external source returning data in the expected format?

Many aircraft model sync issues are caused by missing identifiers or missing data source configuration.

Best practices

  • Configure the data source before syncing models.

  • Use clear data source names.

  • Keep API keys secure.

  • Confirm that external IDs are stable.

  • Do not manually change external source values unless you understand the sync impact.

  • Review sync logs after setup.

  • Test with one model before syncing all models.

  • Make sure administrators understand the difference between aircraft sync and aircraft model sync.

  • Limit sync permissions to users who are allowed to update aircraft model data.

  • Document the external source used for aircraft model data.

Summary

Aircraft Model Sync connects aircraft model records in FlightLogger Maintenance to an external data source.

It uses external_id and external_data_source to create or update aircraft models. It can sync one model or queue sync jobs for configured active data sources.

Because aircraft model sync can change model records, it should be configured and run by users with the correct integration and aircraft model permissions.