NCR performance and AOG frequency are linked, but rarely by a single metric. In most regulated aerospace environments, you establish a traceable chain of metrics from nonconformances to part availability, release status, and actual AOG events. The specifics depend strongly on data quality, system integration, and how consistently NCRs and AOGs are coded.
1. Core linkage concept
You will not get a single “NCR-to-AOG” KPI that is universally reliable. Instead, you combine three layers of metrics:
- NCR characteristics (origin, severity, disposition, cycle time, escape paths).
- Operational impact (delays, deferrals, cannibalizations, part shortages, line interruptions).
- AOG events (frequency, duration, root cause coding, affected part/assembly, maintenance location).
The link is made through traceability: part numbers, serials, work orders, repair orders, and maintenance events must be consistently referenced across QMS, MES/ERP, and MRO/M&E systems. Without that, any metric will be directional at best.
2. NCR-side metrics that matter for AOG risk
The following NCR metrics are most useful when trying to understand contribution to AOGs:
3. AOG-side metrics that can be tied back to NCRs
From the AOG side, the most useful metrics depend on how maintenance and AOG events are recorded:
- AOG events attributed to quality-related causes
Count and rate of AOGs where root cause coding (in the MRO/M&E system) is quality-related, such as manufacturing defect, repair quality issue, or incorrect configuration. This requires disciplined coding and mapping of cause codes to NCR root causes.
- AOG duration linked to part unavailability
Share of AOG hours where the primary delay driver is waiting for a replacement part or repair release. Among these, you can segment by whether the part or repair delay is tied to an open NCR or rework ticket.
- Unscheduled removals linked to prior NCRs
Rate of in-service part removals where the removed unit or its build records show a history of NCRs, concessions, or repairs. This depends on good serialization and genealogy; in many brownfield environments the link is only partial.
- Cannibalization events with quality-related trigger
Number of cannibalization actions triggered by premature failure, concessioned parts, or known nonconformances. Cannibalization chains often signal both quality and supply issues that feed AOGs.
4. Cross-metrics that directly link NCR performance to AOG
Once traceability is in place, you can define more explicit linkage metrics:
- Percent of AOG events with an upstream NCR
Among AOG events, proportion where the implicated part, assembly, or repair order has at least one prior NCR or concession in its history. This shows how often nonconformances that were “accepted” or “repaired” later surface as operational disruptions.
- NCR-related AOG hours per 10,000 flight hours
For fleets with good data integration, you can count AOG hours whose primary cause is traced to a part or repair with an associated NCR, normalized by fleet utilization. This is a strong but demanding metric from a data perspective.
- NCR-induced part shortage events
Count of part shortage incidents where the shortage is explicitly due to scrap/rework from NCRs (for example, multiple units rejected from a batch), and the number of AOGs that result from these shortages.
- Lead time extension due to NCRs vs planned lead time
Average difference between planned availability date and actual availability date when NCRs occur on AOG-critical parts, and how many resulting maintenance deferrals or AOGs are recorded. This connects NCR delays to operational impact.
These cross-metrics will only be robust if:
- Part and serial identifiers are consistent across QMS, MES/ERP, and MRO systems.
- Root cause and effect coding is mandatory and reviewed.
- Change control and concession records are properly linked to serials and configurations.
5. Data and system constraints in brownfield environments
In most real plants and MRO operations, the main obstacle is system coexistence and data quality, not metric definition:
- Multiple legacy systems mean NCRs may live in one QMS, while AOG and unscheduled removal data live in a separate MRO/M&E platform. ERP/MES may hold work orders and part genealogy only partially.
- Tracing serials and configurations across these systems requires data integration work, and in some cases manual mapping or intermediate data warehouses. Full system replacement is rarely practical because of validation effort, downtime risks, and requalification of established records.
- Incomplete historical coding is common; older AOG events may not have clean root cause codes, or NCRs may not reference serials that match maintenance records. Metrics for current and future periods are usually more trustworthy than back-cast trend lines.
Because of these realities, many organizations start with:
- Focused pilots on a small set of programs, fleets, or AOG-critical part families.
- Data-cleansing and mapping exercises to standardize part numbers, serial formats, and cause codes.
- Manual correlation for initial analyses before automating dashboards.
6. Practical starting set of metrics
A minimal, realistic dashboard linking NCRs to AOGs might include:
- NCRs per 1,000 opportunities on an AOG-critical part list, by part family and origin (internal, supplier, repair).
- Average and 90th percentile NCR cycle time for those parts, split by disposition.
- Count and rate of AOG events attributed to those same part families.
- Percent of AOG events where the implicated part or repair has a prior NCR recorded.
- Total AOG hours attributed to parts with prior NCRs, normalized by fleet flight hours.
From there, you can refine with better root cause linkage, concession tracking, and explicit shortage-event tagging as data maturity improves.
7. Interpreting the metrics and limitations
Even with good linkage, keep these limitations in mind:
- Correlation is not causation. Parts with many NCRs may also be complex, heavily used, and subject to aggressive operating environments, all of which contribute to AOGs.
- Operational and supply chain factors (buffer stock levels, repair network capacity, logistics performance) can amplify or dampen the AOG impact of a given NCR rate.
- Regulatory and contractual constraints can limit options to change inspection thresholds or acceptance criteria, even when you detect strong correlations.
- Validation and change control are needed before you use these metrics to drive high-stakes decisions or commitments; metric definitions, data pipelines, and dashboard logic should be under configuration management.
Used with these constraints understood, NCR and AOG linkage metrics can highlight which nonconformances truly matter to fleet availability, and where improvements in process control, repair responsiveness, or spares strategy will most reduce AOG frequency and duration.
