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

Aircraft Models

Aircraft models help you structure aircraft setup in FlightLogger Maintenance

An aircraft model represents the type or model of aircraft, such as a Cessna 172 or Piper PA-28. Individual aircraft can then be linked to the correct model.

Using aircraft models helps keep aircraft setup consistent, especially when several aircraft share the same type, maintenance requirements, specifications, or compatible inventory items.

Aircraft model vs aircraft

FlightLogger Maintenance separates aircraft setup into two levels:

  • Aircraft model: the shared model or type
  • Aircraft: the individual aircraft in your fleet

For example:

  • Aircraft model: Cessna 172
  • Aircraft: OY-ABC

The aircraft model describes shared information. The aircraft record represents one specific aircraft with its own registration, status, usage, components, defects, and maintenance history.

What an aircraft model is used for

Aircraft models can support several areas of FlightLogger Maintenance.

They can be used for:

  • grouping aircraft by type
  • storing model specifications
  • linking compatible inventory items
  • supporting model-level maintenance requirements
  • supporting expected counter roles
  • connecting synced model data from external sources
  • helping users select the correct model when creating aircraft

Aircraft models are especially useful when an organisation operates multiple aircraft of the same type.

Aircraft model information

An aircraft model can include:

  • name
  • manufacturer
  • model number
  • description
  • specifications
  • profile image
  • external ID
  • external data source
  • sync status

The name is required and must be unique within the account.

The manufacturer, model number, description, and specifications help users identify the model correctly.

Specifications

Specifications are key-value details that can be added to the aircraft model.

Examples include:

  • wingspan
  • engine type
  • max speed
  • fuel capacity
  • maximum takeoff mass
  • approved configuration notes

Specifications help document useful technical information about the model.

The exact specifications you add should match what your organisation needs for maintenance planning, support, and reference.

Aircraft linked to a model

When an aircraft is linked to an aircraft model, the aircraft can use the model as part of its maintenance setup.

This helps users understand which model the aircraft belongs to and can support model-level planning logic.

For example, if several aircraft are linked to the same aircraft model, it becomes easier to manage shared model information in one place.

Maintenance requirements

Aircraft models can be connected to model-level AMP program requirements.

When active model-level AMP program requirements exist, FlightLogger Maintenance can derive maintenance requirement information from those requirements.

This helps support maintenance planning for aircraft that belong to the model.

The aircraft model itself does not replace the aircraft’s operational history. Each aircraft still has its own hours, cycles, defects, work orders, components, and compliance status.

Compatible inventory items

Aircraft models can be linked to compatible inventory items.

This helps define which parts, consumables, or other inventory items are compatible with a specific model.

Compatibility can support inventory planning and reduce mistakes when preparing parts for maintenance.

For example, an inventory item may be marked as compatible with one aircraft model but not another.

Expected counter roles

Aircraft models can also have expected counter roles.

Expected counter roles help describe which counters are expected for aircraft of that model, such as hour-based or cycle-based counters.

This is relevant when maintenance requirements depend on usage values.

Search and filtering

Aircraft models can be searched by information such as:

  • name
  • manufacturer
  • model number

Aircraft models can also be filtered by manufacturer and by archive status.

This helps users find the correct model quickly, especially in accounts with many aircraft types.

Archiving aircraft models

Aircraft models can be archived when they are no longer needed.

However, a model cannot be archived if it is still in use by associated aircraft.

This protects aircraft records from being linked to an archived model while they still depend on it.

If a model should be archived, first review whether any aircraft are still linked to it.

External sync

Aircraft models can include external sync identifiers.

These fields are used when aircraft model data is connected to an external data source.

If a model is configured for external sync, FlightLogger Maintenance can preview and apply synced changes through the aircraft model sync workflow.

External ID and external data source should be set together. If one is present without the other, the model is not considered correctly configured for sync.

When to create an aircraft model

Create an aircraft model before creating aircraft when:

  • multiple aircraft share the same type
  • the model needs shared specifications
  • model-level AMP requirements will be used
  • compatible inventory items should be linked to the model
  • model sync will be used
  • users need a clear model selection when creating aircraft

If your organisation only has one aircraft of a type, the model is still useful because it keeps aircraft identity and aircraft-specific history separate.

Best practice

Create aircraft models carefully before linking aircraft to them.

A good setup process is:

  1. Create the aircraft model.
  2. Add manufacturer and model number.
  3. Add a clear description.
  4. Add relevant specifications.
  5. Link compatible inventory items, if used.
  6. Configure expected counter roles, if used.
  7. Configure sync identifiers, if applicable.
  8. Create or update aircraft and link them to the correct model.

This helps keep fleet setup consistent.

Common mistakes

Creating duplicate models

Avoid creating multiple aircraft models for the same aircraft type unless there is a real operational reason.

For example, do not create both C172, Cessna 172, and Cessna172 if they all mean the same model.

Linking aircraft to the wrong model

If an aircraft is linked to the wrong model, maintenance planning and compatible inventory information may be harder to trust.

Always check the model before saving or updating an aircraft.

Using the aircraft model as an aircraft record

An aircraft model is not an individual aircraft.

Do not use an aircraft model to track registration, status, defects, work orders, or usage history. That information belongs to the aircraft record.

Archiving a model too early

Do not archive an aircraft model that is still used by aircraft.

Review linked aircraft before archiving.

Summary

Aircraft models define shared information for a type of aircraft.

Aircraft records represent individual aircraft.

Using aircraft models helps standardise setup, support maintenance requirements, manage compatible inventory, and keep fleet data organised across FlightLogger Maintenance.