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

Component History

Component history helps you understand where a component has been installed, when it was installed, when it was removed, and what has been installed on it.

In FlightLogger Maintenance, component history is built from installation periods. Each installation period records a component’s placement over time, including the installation target, installation date, removal date, position, and ATA position.

This history is important for traceability, technical review, and maintenance documentation.

What component history is used for

Component history helps answer questions such as:

  • where is this component installed now?
  • where was this component installed before?
  • when was it installed?
  • when was it removed?
  • what position was recorded?
  • what ATA position was recorded?
  • what sub-components were installed on it?
  • was the component returned to stock, workshop, or another placement after removal?

This is especially useful for major assemblies, serialized parts, life-limited components, and components that move between aircraft.

Installation periods

FlightLogger Maintenance tracks component history using installation periods.

An installation period starts when a component is installed.

An installation period ends when the component is removed.

An installation period can include:

  • the installed component
  • the installation target
  • installed date and time
  • removed date and time
  • recorded by user
  • position
  • ATA position
  • work order, when relevant

If the component is currently installed, the installation period remains open until the component is removed.

Current installation

A component’s current installation is the open installation period.

This shows where the component is installed now.

The current placement may be:

  • an aircraft
  • another component

If there is no open installation period, the component is not currently installed.

Closed installation history

When a component is removed, FlightLogger Maintenance closes the open installation period.

This creates a historical record showing where the component was installed and when that installation ended.

Closed installation periods help preserve traceability even after the component has moved elsewhere.

Installation target

The installation target is where the component was installed.

The target can be:

  • an aircraft
  • another component

For example:

  • Propeller installed on aircraft OY-ABC
  • Alternator installed on engine
  • Sensor installed on avionics unit

This makes it possible to track both aircraft-level and component-level installation history.

Position

Position describes where the component was installed.

Examples:

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

Position helps make the history understandable, especially when the same aircraft or assembly can contain several similar components.

ATA position

ATA position can be recorded as part of the installation history.

Examples:

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

If your organisation uses ATA references, consistent ATA positions make component history easier to search, review, and compare.

Sub-component history

A component can have sub-components installed on it.

For example, an engine component may have several sub-components installed beneath it.

The component page can show installation history for items and components that have been installed on that component. This helps users understand the structure beneath a parent component over time.

This is useful when reviewing assemblies, major components, or component hierarchies.

Component state history

Component history should also be reviewed together with the component’s state.

A component can have states such as:

  • serviceable
  • in maintenance
  • pending verification
  • scrapped

The state describes the component’s current condition or workflow status. Installation history describes where the component has been placed over time.

Both are important for understanding the component lifecycle.

Linked serialized item history

A component may be linked to a serialized item.

The serialized item represents the physical unit with a serial number. The component represents the maintenance structure and placement.

Serialized items can also have lifecycle events, such as installation, removal, repair, overhaul, send-out, repair return, status changes, and life-tracking values.

When reviewing component history, also review the linked serialized item if the component represents a specific physical unit.

Removals

When a component is removed, the open installation period is closed.

After removal, the component may be placed:

  • on stock
  • at workshop
  • approved or sent on

The removal keeps the component record and preserves its installation history. This is different from deleting the component.

Removal history is important because it shows when the component stopped being part of an aircraft or parent component.

Moving components after removal

A component can only be moved as stock when it is no longer installed.

If a component is installed, it must be removed before it can be moved to a stock location.

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

What to review on the component page

When reviewing component history, check:

  • current placement
  • current position
  • ATA position
  • component state
  • linked serialized item
  • sub-components
  • installation history
  • batch usage, if relevant
  • removal status
  • workshop or stock placement

This gives a complete view of the component’s lifecycle.

Why component history matters

Component history supports traceability.

It helps users understand:

  • aircraft configuration over time
  • component movements
  • installation and removal records
  • sub-component structure
  • technical review
  • audit preparation
  • maintenance context

Without accurate component history, it becomes harder to prove where a component was installed and how it moved through the maintenance process.

Best practice

Keep component history accurate by recording installation and removal actions as they happen.

A good process is:

  1. Create the component.
  2. Link the serialized item, if relevant.
  3. Install the component on the correct target.
  4. Record position and ATA position.
  5. Remove the component when it is no longer installed.
  6. Select the correct removal placement.
  7. Review the component page after each change.
  8. Review the linked serialized item when applicable.

This keeps the component lifecycle clear and reliable.

Common mistakes

Updating fields instead of using install/remove actions

Do not try to represent installation history only by editing component details.

Use the install and remove workflows so installation periods are recorded correctly.

Missing position or ATA position

If position and ATA position are part of your organisation’s process, enter them consistently.

Missing or inconsistent values make later history review harder.

Forgetting sub-components

When reviewing a parent component, remember to review what has been installed beneath it.

Sub-component history may be important for the full technical picture.

Confusing component history with inventory history

Component history focuses on maintenance placement and installation periods.

Inventory history focuses on stock movement, serialized item status, transactions, and inventory location.

If the component is linked to a serialized item, review both when needed.

Summary

Component history shows how a component has moved through the aircraft maintenance structure.

It records installation periods, placement, position, ATA position, removals, and sub-component relationships.

Accurate component history gives your organisation better traceability and a clearer view of each component’s lifecycle.