Create Components

A component can be created before it is installed, or it can be created directly from an aircraft and installed during creation. Components can also be linked to serialized inventory items when they represent a specific physical part.

This article explains how to create the component record. Installing, removing, and reviewing component history are covered in separate articles.

Before you start

Before creating a component, make sure the required setup is ready.

You may need:

• the aircraft, if the component should be installed immediately
• the parent component, if the component will later be installed under another component
• the serialized item, if the component represents a specific physical unit
• component name
• component type
• installation position, if creating it directly on an aircraft
• ATA position, if used by your organisation

If the component should be linked to a serialized item, the serialized item must already exist in inventory.

What creating a component means

Creating a component creates the component record in FlightLogger Maintenance.

The component record can then be used for:

• aircraft configuration
• installation tracking
• removal tracking
• component hierarchy
• component state
• serialized item linking
• workshop handling
• maintenance traceability

Creating a component does not always mean the component is installed. A component can exist on stock before it is installed.

Create a component from the Components page

Use this method when you want to create a component first and install it later.

To create a component:

1. Go to Aircraft Management.
2. Open Components.
3. Select New Component.
4. Enter the component information.
5. Link a serialized item, if relevant.
6. Save the component.

When created this way, placement is handled after creation through the component’s Install and Remove actions.

Create and install a component from an aircraft

You can also create a component from an aircraft context.

When the component is created from an aircraft, FlightLogger Maintenance can create the component and install it on that aircraft at the same time.

In this flow, the form can include installation details such as:

• position
• ATA position

After saving, the component is created and installed on the selected aircraft.

This is useful when you are building the aircraft’s installed component structure directly from the aircraft page.

Component name

The component name is the display name users will see in FlightLogger Maintenance.

Examples:

• Lycoming O-320
• Main Battery
• Left Magneto
• Propeller
• Nose Landing Gear

Use a name that is easy for maintenance users to understand.

The component name should describe the component clearly enough that users can identify it without opening several related records.

Component type

Component type describes what kind of component it is.

Examples:

• engine
• propeller
• battery
• avionics
• landing gear
• alternator

Use consistent component types across your organisation. Consistent naming makes filtering, review, and reporting easier.

Depending on your account setup, component type may be required.

Linked serialized item

A component can be linked to a serialized item.

Use this when the component represents a specific physical unit with a serial number.

For example:

• component: Propeller
• linked serialized item: Propeller serial number SN-12345

The serialized item remains an inventory record. The component represents how that physical unit is tracked in the maintenance structure.

Only serialized items that are valid for linking can be selected. FlightLogger Maintenance prevents invalid serialized item links, such as linking an item from another account or linking an item in a status that should not be used.

Components without serialized items

A component does not always need a linked serialized item.

You may create a component without a serialized item when the component represents:

• an installation position
• a structural slot
• an assembly placeholder
• a parent component that will hold sub-components
• a component that will be linked to a serialized item later

For example, you might create an “Engine” component as a parent and later install sub-components beneath it.

Position

Position describes where the component is installed.

Examples:

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

Position is especially useful when the aircraft or assembly can have more than one similar component.

For example, “Left main gear” and “Right main gear” are clearer than simply “Landing gear”.

Position is recorded when the component is installed.

ATA position

ATA position can be used to record the ATA reference for the component.

Examples:

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

Use ATA positions consistently if your organisation relies on ATA structure for maintenance planning, compliance, or technical records.

Depending on your account setup, ATA position may be optional or required.

Required fields may vary

The fields shown on the component form may depend on your account setup.

Some organisations may require:

• component type
• linked serialized item
• position
• ATA position

Other organisations may keep some of these fields optional.

If a field is required in your account, FlightLogger Maintenance will ask for it before the component can be saved.

What happens after saving

After saving a component, FlightLogger Maintenance either:

• creates the component as a standalone component, or
• creates and installs it on an aircraft, if it was created from an aircraft context

If the component is created without installation, you can install it later from the component page.

If the component is created and installed on an aircraft, FlightLogger Maintenance records the installation as part of the component’s installation history.

After creating the component

After the component is created, review the component page.

Check that:

• the name is correct
• the component type is correct
• the linked serialized item is correct, if used
• placement is correct
• position is correct, if installed
• ATA position is correct, if used
• state is appropriate
• the component appears under the correct aircraft or component

This validation is important before the component is used in maintenance planning.

Best practice

Create components with enough information to support future maintenance tracking.

A good setup process is:

1. Create or import the related inventory item.
2. Create or import the serialized item, if the component is serialized.
3. Create the component.
4. Link the serialized item, if relevant.
5. Install the component on the aircraft or parent component.
6. Add position and ATA position.
7. Review the aircraft component structure.
8. Confirm that component history starts correctly.

This keeps inventory, aircraft configuration, and maintenance traceability aligned.

Common mistakes

Creating a component before the serialized item exists

If the component represents a specific physical part, create or import the serialized item first.

This makes it easier to link the component correctly.

Using unclear names

Avoid generic names such as “Part” or “Component”.

Use names that maintenance users can recognise.

Forgetting the position

If the component is installed on an aircraft, position is often important.

A component named “Battery” is less useful than “Main Battery” or “Emergency Battery” if the aircraft has multiple relevant positions.

Creating the component in the wrong context

If you want the component to be installed immediately, create it from the aircraft context.

If you want to create it first and install it later, create it from the Components page.

Confusing component creation with installation

Creating a component is not always the same as installing it.

If the component was created without an aircraft context, use the Install action afterwards.

Summary

Create components when you need to track parts, assemblies, or installation positions in FlightLogger Maintenance.

A component can be created on its own, linked to a serialized item, and installed later. It can also be created directly from an aircraft and installed during creation.

Good component setup makes aircraft configuration, maintenance tracking, and lifecycle history easier to manage.