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

Getting started with Maintenance

FlightLogger Maintenance is the operational system used to manage aircraft maintenance, inventory, purchasing, workshop execution, and compliance in one connected platform.

It helps maintenance organizations move away from disconnected spreadsheets, manual follow-ups, and separate records by keeping planning, parts, work orders, technical records, and audit-relevant information together.

FlightLogger Maintenance can be used as a standalone maintenance system (from 2027). It can also be connected with FlightLogger, where FlightLogger provides operational inputs such as aircraft usage, hours, cycles, and pilot-reported defects.

FlightLogger Maintenance remains the system where maintenance planning, due calculations, work execution, component tracking, repair closure, and compliance records are managed.

What FlightLogger Maintenance is used for

FlightLogger Maintenance supports the full maintenance loop:

  • Set up aircraft, aircraft models, components, users, roles, and permissions
  • Track aircraft status, usage, recurring maintenance, defects, and due work
  • Manage inventory items, stock, batches, serialized items, tools, and traceability
  • Purchase parts, manage suppliers, receive goods, and process invoices
  • Plan work orders and work packages
  • Execute released maintenance work in the workshop
  • Record time, parts usage, tool usage, findings, signoffs, and non-conformities
  • Manage technical records, airworthiness directives, service bulletins, and service letters
  • Keep maintenance records structured and ready for review or audit

The system is built around traceability. This means that important maintenance information is not only stored, but connected to the aircraft, component, stock item, work order, inspection, signoff, or technical record it belongs to.

How FlightLogger Maintenance is structured

FlightLogger Maintenance is organized around the main areas of a maintenance operation.

Inventory
Used to manage parts, stock, batches, serialized items, locations, tools, receiving inspections, holds, reservations, pick lists, stock counts, and stock movements.

Purchasing
Used to manage suppliers, order requests, purchase orders, receiving-related purchasing status, invoices, and purchasing documentation.

Operations/Engineering
Used to manage aircraft, aircraft models, recurring maintenance, work packages, work orders, task libraries, AMP programs, defects, components, technical records, and airworthiness-related assignments.

Workshop
Used by technicians and workshop staff to work on released work orders, record time, use tools, report non-conformities, and complete maintenance tasks.

Administration
Used to manage account settings, users, roles, authorizations, units of measure, templates, OAuth applications, FlightLogger Sync, aircraft model sync, exchange rates, and other account-level settings.

A typical workflow

A typical maintenance workflow may look like this:

  1. Aircraft, users, permissions, inventory, and integration settings are configured.
  2. Flight usage, defects, recurring maintenance, AMP requirements, or compliance requirements create maintenance demand.
  3. Maintenance planners prepare work orders or work packages.
  4. Inventory and purchasing help ensure the required parts are available.
  5. Work is released to the workshop.
  6. Technicians complete the tasks and record time, parts, tools, findings, and signoffs.
  7. Work orders are completed and closed.
  8. Technical records and compliance documentation are generated, reviewed, and preserved.

This connected workflow helps ensure that maintenance activity can be followed from planning to execution and documentation.

FlightLogger and FlightLogger Maintenance

FlightLogger and FlightLogger Maintenance are connected, but they do not have the same role.

FlightLogger is used for flight operations and training activity. When connected, it can provide operational inputs such as aircraft hours, cycles, and pilot-origin defects.

FlightLogger Maintenance is used to manage the maintenance process. It calculates maintenance status and due work, manages components and inventory, controls work execution, and preserves technical records and compliance documentation.

In short: FlightLogger can provide operational data, while FlightLogger Maintenance manages the maintenance decisions and records.

Why this matters

Maintenance work depends on reliable information. A missing part, an outdated aircraft status, an incomplete work order, or an unsigned technical record can create delays and compliance risk.

FlightLogger Maintenance is designed to give each team a shared operational picture:

  • Planners can see what maintenance is due
  • Stores teams can see whether parts are available
  • Purchasing can react to missing material
  • Technicians can work from released tasks
  • Compliance and engineering users can review records and approvals
  • Account administrators can control access and setup

By keeping these workflows connected, FlightLogger Maintenance helps teams plan, execute, and document maintenance in a controlled and traceable way.