There is no single fixed number of days that is correct for every aerospace NCR. The escalation point should be defined by your quality system, product risk, contractual obligations, and the operational impact of leaving the NCR open.
In practice, an NCR should escalate when it is open long enough to create unmanaged risk, delay disposition, weaken traceability, or allow recurrence without effective containment. For aerospace environments, that often means using tiered aging rules rather than one blanket deadline.
Severity and criticality: Potential airworthiness impact, flight safety relevance, special process exposure, escaped nonconformance, and configuration impact should escalate faster than routine workmanship issues.
Containment status: If suspect material is not fully identified, segregated, and controlled, escalation should happen quickly regardless of NCR age.
Production impact: Line stoppage, blocked assemblies, shortage creation, or repeated use-as-is decisions are signs the issue should not sit in a queue.
Recurrence: Repeated NCRs on the same part, process, tool, supplier, or failure mode usually warrant earlier management review.
Disposition path: Cases needing MRB, engineering review, customer approval, supplier response, or concession workflows often take longer, but that is not a reason to leave them unmanaged. Aging controls still need checkpoints.
Customer and internal requirements: Some programs, contracts, or internal procedures define explicit response and closure windows. Those must govern if they exist.
A common approach is to set formal review thresholds such as:
initial review within 24 to 72 hours for triage, containment, and ownership
management visibility after a defined aging point such as 7, 14, or 30 days depending on risk class
senior quality or operations escalation for overdue disposition, blocked material, repeat events, or customer-impacting issues
That does not mean every NCR should close in a week. Some aerospace NCRs legitimately remain open longer because root cause work, engineering assessment, supplier investigation, or approval workflows take time. The control point is not just total age. It is whether the record shows timely containment, clear ownership, documented status, and justified delay.
An NCR should not remain open indefinitely because the plant is busy, the responsible function is unclear, or the disposition process is fragmented across QMS, ERP, MES, PLM, and email. In brownfield environments, this is common. Open NCR aging often reflects system handoff failures as much as product quality issues.
If your process spans multiple systems, escalation rules should account for that reality. For example, an NCR may be created in QMS, tied to hold status in ERP, linked to genealogy or traveler data in MES, and require engineering action from PLM or a separate workflow tool. If those integrations are weak, aging metrics can be misleading unless ownership and status synchronization are explicit.
Not whether every NCR closes within one universal number, but whether you can show:
documented criteria for escalation and aging
risk-based prioritization
effective containment while the NCR is open
clear responsibility and due dates
traceable links to MRB, CAPA, supplier action, and rework or scrap decisions where applicable
evidence that overdue NCRs are reviewed, not ignored
So the short answer is: escalate based on risk and aging thresholds defined in your quality system, not on an industry myth that every aerospace NCR must close in a fixed number of days. If you do not already have formal thresholds, many organizations start with staged reviews at 7, 14, and 30 days, then tighten or relax by risk class and process maturity.
If your backlog is large, the safer response is usually not a full system replacement. In regulated aerospace settings, replacing QMS, MES, ERP, or MRB-related workflows outright often fails because of validation burden, qualification impact, downtime risk, integration complexity, and long equipment and process lifecycles. A more realistic path is to add aging rules, ownership checkpoints, and evidence links across existing systems first.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
