There is no single universal retention period for non-conformance documentation in aerospace. The correct answer for any given organization or program depends on a mix of regulatory, contractual, customer, and internal policy requirements.
Typical aerospace practices
In many aerospace environments, non-conformance records (including associated investigations, dispositions, and corrective actions) are retained:
- For at least the life of the product or aircraft type, often interpreted as the period from design release through end of support or decommissioning, and
- For an additional fixed period afterward (for example 7–30 years), driven by contract, liability, or customer expectations.
For safety-critical components and systems, it is common to align non-conformance record retention with overall configuration and airworthiness record retention, not with generic corporate document policies.
Key drivers of retention length
To determine how long you must retain non-conformance documentation, you typically need to consider:
- Customer and contract requirements: Many OEM and defense contracts explicitly specify record retention periods for quality and non-conformance data. These normally override generic internal rules.
- Regulatory and authority expectations: Aviation authorities and defense agencies often require that records relevant to continued airworthiness, safety, and conformity be kept as long as the product is in service. Non-conformance data usually falls into that category.
- Product lifecycle and support model: Aerospace platforms can remain in service for several decades. If non-conformance information is needed for major repairs, modifications, investigations, or life extension programs, it must remain available for that entire period.
- Liability and legal hold considerations: Corporate legal and risk teams may require retention for a defined number of years after product retirement to support potential claims or incident investigations.
- Customer-specific quality frameworks: Requirements from primes (for example, via quality clauses, supplier quality manuals, or purchasing terms) may define minimum periods and scope for quality records, including non-conformances.
What “non-conformance documentation” usually includes
When defining retention rules, it is important to be clear about which artifacts are in scope. In many aerospace organizations, non-conformance documentation includes:
- Non-conformance reports and defect records
- Concession or deviation permits and use-as-is dispositions
- Rework and repair dispositions and instructions
- Associated inspection and test results related to the non-conformance
- Root cause analysis and corrective/preventive action records linked to the non-conformance
- Approvals, signatures, and electronic workflow history where relevant to traceability
Your retention schedule should specify whether each type is retained for the same duration or whether some supporting materials can be retained for a shorter period, within regulatory and contractual limits.
Brownfield and systems coexistence considerations
In a typical aerospace brownfield environment, non-conformance data may be spread across multiple systems and formats:
- Legacy MES or mainframe systems
- PLM or PDM systems holding concessions, deviations, and engineering waivers
- QMS/CAPA tools and separate complaint handling systems
- File shares, scanned paper records, and email archives
Retention in this context is less about a single number of years and more about ensuring:
- Continuity of access when systems are replaced or upgraded
- Preservation of traceability links (for example, between non-conformance, part numbers, serial numbers, lots, and configuration baselines)
- Controlled migration or archiving when decommissioning legacy systems, under change control and validation where required
- That any data minimization or purging is documented, authorized, and consistent with contractual and regulatory retention obligations
Full replacement of legacy quality systems solely to improve recordkeeping can be difficult to justify if it risks breaking traceability chains or requires extensive revalidation. Many organizations instead introduce an archive or read-only layer that keeps historical non-conformance records accessible while new records are created in a newer system.
Practical approach to defining retention
A structured way to set retention requirements for non-conformance documentation is to:
- Inventory applicable obligations: Collect and review all relevant customer contracts, authority requirements, and internal policies that refer to quality or production records.
- Map obligations to record types: Classify your non-conformance-related artifacts and map each obligation to the affected record types.
- Define a conservative baseline: For safety-critical aerospace products, many organizations choose a baseline such as “product life plus X years” where X is large enough to cover liability and customer expectations.
- Align across systems: Ensure MES, QMS, PLM, ERP, and archival systems implement compatible retention rules so that related records are not purged at different times in ways that break traceability.
- Document in controlled procedures: Include retention rules in document control or records management procedures under change control, and ensure the rules are referenced in system validation or configuration documents where applicable.
- Plan for decommissioning: For any system holding non-conformance data, define how records will be exported, migrated, or archived before retirement, and test that approach.
Constraints and caveats
This guidance is descriptive of common aerospace practice and is not a legal, regulatory, or contractual interpretation. The appropriate retention period for your organization can only be set by reviewing your specific authority, customer, and contract requirements together with your legal, quality, and records management functions. Any change to retention practices should follow established change control and, where applicable, system validation processes.
