FlightLogger vs FlightLogger Maintenance

FlightLogger is used for flight operations and training activity. FlightLogger Maintenance is used to manage the maintenance process around aircraft, components, inventory, purchasing, workshop execution, technical records, and compliance.

If your organization uses both systems, it is important to understand which system is responsible for what. This helps avoid confusion when aircraft data, flight hours, cycles, defects, maintenance status, or technical records are involved.

The short explanation

FlightLogger supports the operational side of flying and training.

FlightLogger Maintenance supports the maintenance side of the aircraft lifecycle.

When the systems are connected, FlightLogger can provide operational inputs such as aircraft usage, hours, cycles, and pilot-reported defects. FlightLogger Maintenance uses maintenance data and maintenance rules to support planning, due tracking, repair handling, work execution, component tracking, and compliance documentation.

In simple terms:

FlightLogger helps describe what happened operationally.

FlightLogger Maintenance helps decide, plan, perform, and document what needs to happen from a maintenance perspective.

What FlightLogger is typically responsible for

FlightLogger is used for flight operation and training-related activity.

Depending on your setup, FlightLogger may provide information such as:

• Aircraft activity
• Flight usage
• Hours
• Cycles
• Pilot-reported defects
• Operational aircraft information used by the integration

This information can be valuable for maintenance planning because usage data and defects may affect when maintenance is due and what work needs attention.

What FlightLogger Maintenance is responsible for

FlightLogger Maintenance is the maintenance system of record.

It is used to manage:

• Aircraft maintenance status
• Maintenance planning
• Recurring maintenance
• AMP requirements
• CMP requirements
• Defects from a maintenance perspective
• Work orders
• Work packages
• Components and installation history
• Inventory and stock availability
• Purchasing and receiving
• Workshop execution
• Time entries, tool usage, findings, and signoffs
• Technical records
• Airworthiness and compliance documentation
• User roles, permissions, authorizations, and maintenance setup

This means that maintenance decisions and maintenance records belong in FlightLogger Maintenance.

Why the distinction matters

The distinction matters because flight operations and maintenance operations answer different questions.

FlightLogger may answer questions such as:

• Which aircraft was used?
• What flight activity took place?
• What hours or cycles were recorded?
• Was a defect reported during operation?

FlightLogger Maintenance answers questions such as:

• Is maintenance due?
• Why is maintenance due?
• Which work order should be created?
• Which parts are required?
• Is stock available?
• Has the work been released to the workshop?
• Who performed the work?
• Which parts and tools were used?
• Has the work been completed and closed?
• Which technical records support the aircraft status?
• Is the compliance status documented?

Both perspectives are important, but they should not be mixed together.

How data can move between the systems

When FlightLogger and FlightLogger Maintenance are connected, data can move through configured integration flows.

Depending on your setup, this may include:

• Aircraft synchronization
• Aircraft model synchronization
• Hours and cycles synchronization
• Defect synchronization
• API access through OAuth applications
• Selected outbound updates or webhooks

The exact behavior depends on your account configuration and enabled integration setup.

What FlightLogger can provide to Maintenance

FlightLogger can provide operational input that helps maintenance users work with current aircraft information.

Examples include:

• Aircraft usage data
• Hours and cycles
• Pilot-origin defects
• Aircraft or aircraft model data, depending on configuration

This data can support maintenance planning, but it does not replace the maintenance workflow.

What FlightLogger Maintenance does with the data

FlightLogger Maintenance uses operational input together with maintenance setup and maintenance records.

For example:

• Hours and cycles may support due calculations
• Defects may create maintenance demand
• Aircraft and model data may support setup and matching
• Usage data may help planners understand upcoming maintenance

However, FlightLogger Maintenance remains responsible for the maintenance interpretation of that data.

Maintenance decisions stay in FlightLogger Maintenance

FlightLogger Maintenance is responsible for:

• Maintenance status
• Due logic
• Repair handling
• Defect closure from a maintenance perspective
• Component configuration
• Work order lifecycle
• Workshop execution
• Technical record approval
• Compliance documentation

This is important because maintenance decisions must be traceable, controlled, and auditable.

FlightLogger does not become a full copy of Maintenance

The integration does not mean that FlightLogger becomes a complete mirror of FlightLogger Maintenance.

Some selected information may be exchanged, but you should not assume that all maintenance state, all work order information, all component history, or all technical records are available in FlightLogger.

For maintenance work, always use FlightLogger Maintenance as the primary source.

Defects and synchronization

Defects are one of the areas where the distinction is especially important.

A defect may be reported in FlightLogger and then synchronized into FlightLogger Maintenance. Once it is in FlightLogger Maintenance, it can become part of the maintenance process.

From there, maintenance users can assess, plan, link, work on, rectify, or close the defect according to the maintenance workflow.

Defect matching between systems may use best-effort rules. This means users should review synchronized defects carefully, especially if troubleshooting duplicates or unexpected defect updates.

Hours and cycles

Hours and cycles are another key integration area.

FlightLogger may provide aircraft usage data. FlightLogger Maintenance can use this data to support maintenance planning and due calculations.

If hours or cycles are missing, delayed, duplicated, or mapped incorrectly, due maintenance may appear incomplete or uncertain. In those cases, users should review the integration setup, aircraft matching, and counter configuration.

Can FlightLogger Maintenance work without FlightLogger?

Not yet.

FlightLogger Maintenance will eventually work as a standalone maintenance system. Aircraft, defects, usage records, inventory, purchasing, workshop execution, technical records, and compliance workflows can still be managed even if FlightLogger is not connected.

The integration is useful when your organization uses FlightLogger for operations, but it is not required for the core maintenance workflow to exist.

Which system should I use?

Use FlightLogger when you are working with flight operations or training activity.

Use FlightLogger Maintenance when you are working with maintenance setup, maintenance planning, inventory, purchasing, workshop execution, components, technical records, or compliance.

If you are unsure, ask this question:

“Am I working with flight activity, or am I working with maintenance control and documentation?”

If the answer is maintenance control and documentation, use FlightLogger Maintenance.

Summary

FlightLogger and FlightLogger Maintenance work together, but they have different responsibilities.

FlightLogger provides operational context.

FlightLogger Maintenance manages the maintenance process.

Keeping this distinction clear helps your organization maintain accurate aircraft status, reliable due tracking, controlled work execution, and traceable compliance records.