Understanding Components

In FlightLogger Maintenance, components help connect inventory, aircraft configuration, maintenance planning, and traceability. A component can be installed on an aircraft, installed on another component, kept on stock, moved to workshop, or linked to a serialized inventory item.

Components are important when you need to know not only which part exists, but where it is installed, what state it is in, and how it has moved through its lifecycle.

What a component is

A component is a maintenance-tracked record that represents a part, assembly, or position that can be managed in relation to an aircraft.

Examples of components can include:

• engine
• propeller
• landing gear
• avionics unit
• battery
• life-limited part
• major assembly
• tracked installation position

A component can be tracked on its own or as part of a component hierarchy.

Components vs inventory items

It is important to understand the difference between inventory items, serialized items, and components.

An inventory item describes what the part is.

A serialized item represents one physical unit of a serial-tracked inventory item.

A component represents how that part or unit is tracked in the aircraft maintenance structure.

For example:

• Inventory item: Propeller model ABC
• Serialized item: Serial number SN-10045
• Component: Propeller installed on aircraft OY-ABC

These records can be connected, but they are not the same thing.

Why components are important

Components help maintain traceability.

They allow your organisation to see:

• what is installed on an aircraft
• what has been removed
• what is currently on stock
• what is at workshop
• what is linked to a serialized item
• what is installed on another component
• which components are serviceable or not serviceable
• where a component has been installed over time

This is especially important for regulated, expensive, serialized, or life-limited parts.

Component placement

A component can be placed in different ways.

It can be:

• installed on an aircraft
• installed on another component
• on stock
• at workshop
• approved or sent on

When a component is installed, FlightLogger Maintenance records its placement as part of the installation history.

When a component is not installed, its placement type helps describe where it is in the process.

Installed on aircraft

A component can be installed directly on an aircraft.

When installed on an aircraft, the component becomes part of that aircraft’s configuration.

Examples:

• engine installed on aircraft OY-ABC
• propeller installed on aircraft OY-ABC
• landing gear installed on aircraft OY-ABC

The aircraft page can then show the component as part of the aircraft’s component structure.

Installed on another component

A component can also be installed on another component.

This allows you to build a hierarchy.

For example:

• engine installed on aircraft
• alternator installed on engine
• sensor installed on engine

FlightLogger Maintenance prevents invalid component hierarchies, such as installing a component on itself or creating a circular placement structure.

On stock

A component that is not installed can be on stock.

This means the component is not currently installed on an aircraft or another component.

If the component is linked to a serialized item, the serialized item’s location can be used as the effective location for the component.

Components that are on stock can be moved to a stock location.

At workshop

A component can be removed to workshop.

This is useful when a component has been removed from an aircraft and is being inspected, repaired, overhauled, or otherwise handled outside the aircraft.

A component at workshop can be linked to a work order when relevant.

Approved or sent on

A removed component can also be marked as approved or sent on.

This placement type can be used when the component is no longer installed but is not simply on stock or at workshop.

Use this according to your organisation’s internal process.

Component states

Components can have different states.

The available states include:

• serviceable
• in maintenance
• pending verification
• scrapped

The state helps users understand whether the component is available and acceptable for use.

If a component has sub-components, FlightLogger Maintenance can also determine an effective state based on the component and its descendants. This means a parent component may be affected by the state of its installed sub-components.

Linked serialized item

A component can be linked to a serialized item.

This is useful when the component represents a specific physical part with a manufacturer serial number.

Only valid serialized items in a linkable status can be attached to a component. This helps prevent incorrect links to items that should not be installed or used.

When a component is linked to a serialized item, the component and serialized item can remain connected through movement and placement changes.

Installation history

When a component is installed, FlightLogger Maintenance records an installation period.

An installation period can include information such as:

• installation target
• installed date
• removed date
• position
• ATA position
• user who recorded the installation

This helps build a history of where the component has been installed over time.

Installation history is important for traceability, maintenance review, and technical records.

Position and ATA position

When installing a component, you can record the position and ATA position.

Examples of position values:

• Engine 1
• Left main gear
• Right wing
• Propeller
• Battery compartment

Examples of ATA position values:

• 24-00-00
• 32-00-00
• 72-00-00

Use position and ATA position consistently across your organisation. Consistent naming makes component history easier to read and compare.

Removing components

When a component is removed from an aircraft or another component, its current installation period is closed.

The component can then be placed:

• on stock
• at workshop
• approved or sent on

If the component has sub-components installed beneath it, removing the parent component also affects the descendant component placement.

This helps keep the component hierarchy consistent.

Moving components

A component can be moved to a stock location when it is not installed.

If the component is currently installed, it must be removed from installation before it can be moved as stock.

This protects the installation history and prevents a component from being both installed and moved as stock at the same time.

Verification

A component can be marked as verified when it is in pending verification.

Verification sets the component state to serviceable.

Use verification according to your internal maintenance and quality process.

Components and batch usage

Components can also record batch usage.

This is useful when consumables or batch-controlled materials are used during maintenance on a component.

Batch usage helps maintain traceability between maintenance activity and inventory batches.

When to use components

Use components when the part or assembly needs lifecycle traceability.

You should consider using components for:

• major assemblies
• serial-tracked parts
• life-limited parts
• regulated components
• parts that move between aircraft
• parts that require installation and removal history
• parts that require maintenance tracking

Not every inventory item needs to be a component.

For simple consumables or low-value stock, inventory tracking may be enough.

Best practice

Before creating components, make sure the supporting data is ready.

A good setup process is:

1. Create or import inventory items.
2. Create or import serialized items.
3. Create aircraft.
4. Create components.
5. Link components to serialized items where relevant.
6. Install components on aircraft or parent components.
7. Record position and ATA position consistently.
8. Review component state and placement.
9. Keep installation and removal history up to date.

This gives you a clear component structure and better long-term traceability.

Common mistakes

Confusing inventory items with components

An inventory item is not automatically a component.

Create a component when the part needs aircraft-related tracking, placement, or installation history.

Forgetting to link the serialized item

If a component represents a specific serialized physical unit, link it to the correct serialized item.

This improves traceability between inventory and maintenance planning.

Installing components in the wrong hierarchy

Make sure components are installed on the correct aircraft or parent component.

Incorrect hierarchy can make maintenance history difficult to understand.

Moving an installed component as stock

A component must be removed from installation before it can be moved as stock.

Using inconsistent position names

Use consistent position and ATA position values to make component history easier to read.

Summary

Components connect inventory, aircraft configuration, and maintenance traceability.

They help you track where important parts are installed, where they have been, what state they are in, and how they move through maintenance.

Use components for parts and assemblies that require lifecycle tracking beyond simple inventory management.