Skip to main content
By following this guide, you will record reliability program events, analyze failure trends by ATA chapter and aircraft, understand the three-stage alert system, and use reliability data to support your continuing airworthiness maintenance program (CAMP).
Who should read this: Directors of maintenance, reliability program managers, and maintenance controllers responsible for statistical analysis of fleet maintenance events as required for operators of turbine-powered large aircraft.Required permission: maintenance_ops — read to view reliability data, update to create events and manage alert levels.Regulatory basis: 14 CFR 135.421(e) requires certificate holders operating turbine-powered large aircraft to have a reliability program as part of their continuing analysis and surveillance system (CASS). The program must provide statistical analysis of maintenance events to identify adverse trends and take corrective action before they result in failure during operations.

​
Reliability Program Overview

The reliability program in PlaneConnection collects and analyzes five categories of maintenance events to identify adverse trends:
Event TypeSource
PIREPPilot Reports — mechanical discrepancies reported in flight
MAREPMaintenance Reports — defects found during scheduled maintenance
Component FailureUnscheduled component removals due to failure
DelayMechanical delays exceeding threshold (typically 15 minutes)
CancellationFlight cancellations due to mechanical reasons
Events are categorized by ATA 100 chapter code, enabling system-level trend analysis across the fleet.

​
The Reliability Dashboard

Navigate to Maintenance > Reliability to see the reliability program dashboard. The page provides:
  • Event summary cards — Total events by type for the selected period
  • Trend charts — Event rates over time by ATA chapter
  • Fleet comparison — Per-aircraft event rates normalized by flight hours
  • Alert status — Active Stage 1, 2, and 3 alerts

​
Record a Reliability Event

1
Open the new event form
2
From the Reliability dashboard, click New Event.
3
Select event type and aircraft
4
  • Event Type — PIREP, MAREP, Component Failure, Delay, or Cancellation
  • Aircraft — Select the aircraft registration
  • Event Date — When the event occurred
    • 5
    Enter event details
    6
  • ATA Chapter — The ATA 100 chapter code for the affected system (e.g., “24” for Electrical Power, “32” for Landing Gear, “72” for Engine)
  • Description — Detailed description of the event
  • Corrective Action — What was done to address the issue
    • 8
  • Pilot Report ID — Link to the pilot report if the event originated from a PIREP
  • Work Order ID — Link to the work order that addressed the issue
    • 9
    Set the alert level
    10
    Based on your reliability program manual’s alert criteria, assign the appropriate alert level. PlaneConnection supports configurable multi-stage alert escalation that aligns with your FAA-approved reliability program manual.
    11
    Alert thresholds and escalation criteria are fully configurable per workspace to match your reliability program manual’s definitions. PlaneConnection tracks alert levels and trends but your program manual defines the specific criteria for escalation.
    12
    Save the event
    13
    Click Save. The event is recorded and the dashboard charts update to reflect the new data.
    The reliability dashboard provides several analysis views:

    ​
    Event rate charts

    Bar and line charts show event rates per 1,000 flight hours by ATA chapter. Use the date range selector to compare different periods (monthly, quarterly, annually).

    ​
    Top systems

    A ranked list of ATA chapters by event count highlights the systems with the most reliability concerns. Click any ATA chapter to drill down into the individual events.

    ​
    Per-aircraft comparison

    Compare reliability metrics across aircraft in your fleet to identify tail-number-specific issues versus fleet-wide trends.
    Review reliability data monthly as part of your CASS program. Present findings and trend analysis to your safety review board or maintenance steering group. Document all reviews and corrective actions per your reliability program manual.

    ​
    Respond to Alerts

    When an alert is triggered:
    1
    Acknowledge the alert
    2
    Review the events that triggered the alert threshold. Document your initial assessment.
    3
    Investigate (Stage 2+)
    4
    For Stage 2 and Stage 3 alerts, conduct a root cause investigation:
    5
  • Review all related events, work orders, and discrepancies
  • Analyze commonalities (same component, same vendor, same maintenance procedure)
  • Determine whether the trend represents a systemic issue or isolated events
    • 6
    Take corrective action (Stage 3)
    7
    Implement corrective actions such as:
    8
  • Revised maintenance procedures or intervals
  • Component replacement programs
  • Additional inspections or monitoring
  • Manufacturer or vendor coordination
    • 9
    Document resolution
    10
    Record the corrective action taken, the responsible person, and the expected impact. Continue monitoring to verify the corrective action is effective.

    ​
    Integration with Safety Module

    Reliability events with Stage 2 or Stage 3 alerts should be reported to the Safety Management System for inclusion in the organization’s safety risk management process per 14 CFR Part 5. From any reliability event, click Report to Safety to create a linked safety report.

    Manage Discrepancies

    Discrepancies feed into the reliability program as MAREPs.

    Compliance Dashboard

    Monitor fleet compliance alongside reliability metrics.

    Maintenance Forecast

    Plan maintenance actions driven by reliability findings.

    Manage Work Orders

    Create work orders for reliability-driven corrective actions.
    Last modified on April 5, 2026