Install Components

Installing a component is more than updating a location. It records where the component is installed and creates installation history so the component can be tracked over time.

A component can be installed on:

• an aircraft
• another component

This allows you to build both aircraft-level component structures and component hierarchies.

Before you start

Before installing a component, make sure:

• the component has already been created
• the aircraft exists, if the component will be installed on an aircraft
• the parent component exists, if the component will be installed on another component
• the component is not already installed in the wrong place
• the position is known, if your organisation uses positions
• the ATA position is known, if your organisation uses ATA references
• the linked serialized item is correct, if the component represents a physical serialized unit

If the component has not been created yet, create the component first.

What installation means

When you install a component, FlightLogger Maintenance sets the component’s placement.

The component is no longer just on stock. It becomes part of an aircraft configuration or part of another component’s structure.

The system also records an installation period. This makes it possible to track where the component was installed and when that installation started.

Install a component

To install a component:

1. Go to Aircraft Management.
2. Open Components.
3. Open the component you want to install.
4. Select Install.
5. Choose whether to install it on an aircraft or another component.
6. Select the installation target.
7. Enter position, if relevant.
8. Enter ATA position, if relevant.
9. Save the installation.

After saving, the component page shows the new placement.

Install on an aircraft

Install a component on an aircraft when the component should become part of that aircraft’s configuration.

Examples:

• engine installed on an aircraft
• propeller installed on an aircraft
• battery installed on an aircraft
• landing gear installed on an aircraft

Once installed, the component is connected to the aircraft and can appear in the aircraft’s component structure.

Install on another component

Install a component on another component when it belongs inside or under a parent component.

Examples:

• alternator installed on an engine
• sensor installed on an engine
• sub-assembly installed on a major assembly

This creates a component hierarchy.

FlightLogger Maintenance prevents invalid hierarchy loops. A component cannot be installed on itself or on one of its own descendants.

Position

Position describes where the component is installed.

Examples:

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

Use clear and consistent position names. This makes the aircraft structure easier to understand and helps users interpret installation history later.

ATA position

ATA position can be used to record the relevant ATA reference for the installation.

Examples:

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

If your organisation uses ATA structure, enter ATA positions consistently.

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

Installation history

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

An installation period can include:

• installed component
• installation target
• installed date
• recorded by user
• position
• ATA position

This installation history helps answer questions such as:

• where was this component installed?
• when was it installed?
• what aircraft or parent component was it installed on?
• what position was recorded?
• when was it later removed?

This is important for traceability and technical review.

Reinstalling a component

If a component already has an installation placement and is installed again somewhere else, FlightLogger Maintenance closes the existing open installation period and records the new installation.

This helps keep installation history chronological.

Before reinstalling, check whether the component should first be removed through the normal removal workflow. Your organisation may require removal details, workshop placement, or work order references before the component is installed elsewhere.

Components linked to serialized items

If the component is linked to a serialized item, review the serialized item before installation.

Check that:

• the serialized item is the correct physical unit
• the serial number is correct
• the item is in a suitable status
• the item is not scrapped or lost
• the current location makes sense

The component and serialized item are connected, but they are still separate records. The serialized item represents the physical unit. The component represents the maintenance placement and structure.

After installation

After installing the component, review the component page.

Confirm that:

• placement is correct
• aircraft or parent component is correct
• position is correct
• ATA position is correct
• linked serialized item is correct
• component state is appropriate
• installation history has been created

If the component was installed on an aircraft, also review the aircraft’s component view to confirm that it appears in the expected structure.

Best practice

Install components as part of a controlled maintenance or setup process.

A good process is:

1. Confirm the component record.
2. Confirm the linked serialized item, if relevant.
3. Confirm the installation target.
4. Enter a clear position.
5. Enter ATA position, if used.
6. Save the installation.
7. Review the component page.
8. Review the aircraft or parent component structure.

This helps keep component tracking accurate from the beginning.

Common mistakes

Installing on the wrong aircraft

Always confirm the aircraft registration before saving the installation.

Incorrect aircraft placement can affect component history and maintenance traceability.

Installing under the wrong parent component

When building component hierarchies, confirm that the selected parent component is correct.

An incorrect parent can make the aircraft structure difficult to understand.

Leaving position blank

Position may be optional in some accounts, but it is often important for traceability.

Use clear position values whenever possible.

Confusing location with installation

A stock location is not the same as an installation target.

A component on stock can have a location. An installed component is placed on an aircraft or another component.

Forgetting to review installation history

After installation, check that the component history reflects the intended placement.

Summary

Install components when they need to become part of an aircraft or component structure.

Installation records placement and creates installation history, helping your organisation track where components are installed and how they move over time.