Fleet

Defects

Review and manage aircraft defects across the Aerolync Pilot app and the Fleet module.

Last updated 2026-03-27

The Defects tab is the technical issue workflow for a fleet aircraft. It combines pilot reporting from the Aerolync Pilot app with the maintenance and release workflow in Fleet.

Introduction

For fleet aircraft, defects are handled across both the app and the platform:

  • In the Aerolync Pilot app, pilots can see unresolved defects before departure when Show open defects in Aerolync-Pilot app is enabled on the aircraft.
  • The app also shows the current airworthiness status. If the aircraft becomes AOG, departure can no longer be registered in the app.
  • On arrival, pilots can report a technical issue from the app when Accept defect reporting in Aerolync-Pilot app is enabled.
  • App-reported defects are created in Fleet with status In Review, so maintenance or operations staff can review them first before they become active defects.

The Defects tab itself is split into a working layout: a defect list on the left and the selected defect details on the right.

Quickstart

  1. Open the aircraft in Fleet and go to Configuration.
  2. Enable Accept defect reporting in Aerolync-Pilot app if pilots should be able to submit defects on arrival.
  3. Optionally enable Show open defects in Aerolync-Pilot app if pilots should see unresolved defects before departure.
  4. Tell pilots what to expect:
    • before departure they can see airworthiness and unresolved defect information
    • after arrival they can submit a defect title, description, and photos
  5. Monitor the Defects tab for new items in In Review.
  6. Review each new report, then either:
    • assign a severity to accept it into the active defect workflow
    • reject it if it should not remain in the defects log
  7. If the aircraft must not dispatch, set the severity to Grounded (AOG) and activate a schedule block when needed.
  8. Use Remarks - Public for pilot-facing guidance and Remarks - Internal for internal coordination.

Creating a new defect

A new defect can start in two ways:

  • manually from the Fleet module
  • from the Aerolync Pilot app after arrival

A manually created defect requires:

  • Title
  • Description
  • Severity

You can also add:

  • Remarks - Internal
  • Remarks - Public
  • attachments such as images, PDFs, or documents

App-created defects are linked to the related aircraft log and start in In Review. Use internal remarks for maintenance coordination and public remarks for information that can be shown back to pilots in Aerolync Pilot.

Severity levels

At creation time you choose one of:

  • Minor
  • Major
  • Grounded (AOG)

Grounded or AOG defects can also drive schedule blocking behavior and can prevent the aircraft from being dispatched through the app until it is released back to service.

Status flow

The defect list is sorted by status. The active flow can include:

  • In Review
  • Open
  • In Progress
  • Closed
  • Rejected

New defects from the app enter as In Review and still need an explicit decision. Accepted defects move into the active workflow; rejected defects are kept out of the active defect log.

Handling in-review defects

For a defect in In Review, you must either:

  • assign a severity to accept it and move it into Open
  • reject it so it does not remain in the active defect log

This is the normal review step for defects reported from the app.

Defect detail

The detail view can show:

  • reporter
  • creation date
  • aircraft total time
  • severity
  • status
  • related flight
  • description
  • public and internal remarks
  • defect history

Remarks - Public are intended for pilot-facing information. When open defects are shown in the Aerolync Pilot app, these remarks are the right place for short operational guidance. Remarks - Internal stay for internal coordination only.

Schedule blocking from a defect

For Grounded or AOG defects, the detail view can manage a schedule block directly. You can:

  • enter a start and end time
  • preview booking conflicts
  • cancel conflicting reservations
  • activate or deactivate the schedule block

This is useful when technical issues must immediately affect aircraft availability. In practice, a grounded defect can therefore affect both booking availability in the platform and dispatch in the app.

Maintenance actions

Open defects without RTS can receive maintenance actions. Each action can include:

  • the work performed
  • the person who performed it
  • attachments
  • an optional Release To Service (RTS) statement

Once a defect has RTS, parts of the detail view become locked. When the defect closes, the linked schedule block can be deactivated and the aircraft can return to normal service.

  • enable Accept defect reporting in Aerolync-Pilot app only for aircraft where you want arrival-based pilot reporting
  • enable Show open defects in Aerolync-Pilot app when pilots should review unresolved issues before departure
  • review In Review defects quickly so pilots and staff are working from the same aircraft status
  • keep the title short and easy to scan in the list
  • use Grounded only when the aircraft must be taken out of service
  • keep public remarks pilot-focused
  • record completed work in maintenance actions, not only in the defect description