How long should CAPAs remain open before escalation in aerospace programs?

There is no universal, standards-mandated number of days that a CAPA can remain open before escalation in aerospace. AS9100 and customer requirements focus on timeliness and effectiveness, not a fixed calendar limit. In practice, escalation thresholds are set by each organization (and sometimes by each program or customer) based on risk, complexity, and contractual expectations.

Typical timeframes used in aerospace CAPA systems

While numbers vary, many aerospace organizations use tiered age thresholds as internal triggers, for example:

• Low/medium risk CAPAs (no safety, airworthiness, or regulatory exposure):
  • Initial containment: 24 to 72 hours
  • Root cause defined and plan approved: 15 to 30 days
  • Corrective actions implemented: 30 to 60 days
  • Effectiveness verification and closeout: 60 to 90 days total
• High risk / safety / compliance-critical CAPAs:
  • Immediate containment: same shift to 24 hours
  • Root cause and action plan: typically within 7 to 14 days
  • Full implementation and verification: often targeted within 30 to 60 days, with tighter management review and more frequent checkpoints

Escalation is usually tied to these internal targets, for example:

• 30 days open: Escalate to area manager or functional lead.
• 60 days open: Escalate to quality director, program quality lead, or MRB chair.
• 90 days open: Escalate to executive review (e.g., QRB/MRB board, management review) with explicit decision to extend, re-scope, or split the CAPA.

These numbers are not requirements; they are examples of what experienced aerospace programs often adopt to stay defensible in audits and customer reviews.

What really drives your escalation thresholds

In aerospace programs, escalation timing should be driven by:

• Risk to safety and airworthiness: CAPAs addressing escape risk, potential field failures, or safety incidents should have much tighter timelines and earlier, automatic escalation (for example, immediate notification to the accountable executive or chief engineer).
• Regulatory and certification exposure: Issues that could impact compliance with EASA/FAA, military airworthiness authorities, or AS9100/AS9145 expectations need short clocks and documented oversight.
• Customer and contract requirements: Some primes or defense customers stipulate specific due dates or “days-to-close” metrics for CAPA or RCCA responses; these override generic internal targets.
• System and process maturity: Plants with immature CAPA processes or fragmented tools (separate QMS, MES, and manual trackers) often need shorter internal triggers just to ensure issues do not disappear in the gaps.
• Complexity and dependency on design authorities: CAPAs requiring design change, test campaigns, or authority approvals may legitimately run for many months, but should be formally reviewed and re-authorized at defined intervals.

Practical escalation model for aerospace CAPAs

A practical and defensible approach in aerospace programs is to define escalation based on age, risk, and stage of the CAPA:

1. Stage-based internal deadlines
   • Containment: Hours to a few days, depending on severity.
   • Root cause analysis: 7 to 30 days, with higher-risk issues on the short end.
   • Corrective actions implemented: 30 to 60 days for most manufacturing issues.
   • Verification and close: Within a defined period after implementation (for example, 30 days of stable performance data).
2. Escalation rules
   • If any stage deadline is exceeded without an approved extension, automatically escalate to the next management level.
   • If a high-risk CAPA is still open at 30 or 60 days, require senior quality/program review and a documented rationale for remaining risks during the open period.
   • For very long-running CAPAs (for example, design changes taking 6 to 12 months), require periodic management re-approval (for example, every 60 days) and clear evidence of progress.
3. Portfolio-level triggers
   • Escalate when the percentage of overdue CAPAs for a program exceeds a defined threshold (for example, 10 to 20 percent).
   • Escalate when the same root cause keeps reappearing, indicating that closed CAPAs have not been effective.

Brownfield and system coexistence considerations

In many aerospace environments, CAPAs are spread across a mix of systems: legacy QMS software, homegrown databases, MES, PLM change workflows, and spreadsheets. This reality affects escalation design:

• Do not rely on a single system clock if multiple tools hold CAPA tasks. Define a single system of record for CAPA status and due dates, even if execution tasks are in other tools.
• Use simple, robust triggers (for example, “days since CAPA opened” and “days since last status update”) that can be consistently calculated across legacy systems.
• Avoid full system replacement just to improve CAPA aging metrics. In regulated aerospace programs, large QMS/MES rip-and-replace efforts often fail due to validation burden, downtime risk, and integration complexity. Focus first on interfaces, reporting, and governance.
• Make sure escalation emails, dashboards, and review meetings work even when data comes from multiple systems; otherwise old CAPAs will be missed.

Governance, traceability, and defensibility

Whatever numbers you choose, auditors and customers will look at how you govern and justify CAPA aging, more than at any specific day count. To stay defensible:

• Document your CAPA procedure with stage timelines, roles, and escalation paths.
• Maintain audit trails showing who approved due dates, extensions, and scope changes, and why.
• Ensure that change control for process and documentation updates is linked to CAPAs, especially when MES routings, work instructions, or inspection plans are involved.
• Track overdue CAPAs and long-open items as part of management review and program reviews, not just in quality meetings.

Putting it together: a realistic starting point

For most aerospace programs without strong prior guidance, a reasonable starting policy is:

• Define stage targets (containment, root cause, implementation, verification) with 30/60/90 day outer limits for low/medium risk issues.
• Halve those limits for high-risk, safety, or regulatory-impact CAPAs, and require program or executive sign-off on any extension.
• Escalate at each missed stage deadline to the next management level, and at 90 days open (or earlier for high-risk) to an executive quality/program forum.
• Adjust thresholds as you gather data on actual cycle times, resource constraints, and integration with your existing QMS/MES/PLM stack.

This approach acknowledges aerospace program complexity and brownfield systems, while keeping CAPA aging under visible, documented control.