How do you distinguish between a minor and major non-conformance in aerospace?

There is no single industry-wide legal definition of “minor” vs “major” non-conformance in aerospace. The distinction is set by each organization’s Quality Management System (QMS), customer contracts, and applicable regulations (for example, AS9100, EASA/FAA requirements, and individual OEM specs).

Core principles that usually define a major non-conformance

Most aerospace OEMs and primes treat a non-conformance as major if any of the following apply:

• Potential safety or airworthiness impact: Any realistic path to affecting structural integrity, system performance, reliability, or continued airworthiness, even if the immediate risk seems low.
• Impact on fit, form, or function: The part, assembly, or software no longer meets design intent or approved configuration without engineering disposition.
• Violation of regulatory, type design, or certification baseline: Deviation from approved design data, type certificate data, or mandatory regulatory requirements (e.g., ADs, CS/FAR requirements).
• Escape to customer or field: Non-conformance discovered after shipment, at the MRO, or in service, especially if multiple units or serial numbers may be affected.
• Systemic or recurring issue: Evidence that the issue is not isolated (e.g., repeated similar NCRs, process drift, gage failure, programming error, or documentation error impacting many orders).
• Suspected counterfeit, unapproved, or wrong material: Incorrect specification, missing certifications, or traceability gaps on critical characteristics or safety-related parts.
• Configuration or traceability break: Inability to demonstrate full as-built traceability, required inspection records, or conformity to the controlled configuration.
• Extensive rework or redesign required: Correction requires significant rework, re-qualification, engineering change, or re-certification activity.

Major non-conformances in this sense usually require:

• Formal engineering disposition (MRB, concession, or deviation).
• Stronger containment, risk assessment, and sometimes stop-ship or stop-use decisions.
• Structured root cause and corrective action (e.g., 8D / RCCA or CAPA), often with customer involvement.

Characteristics of a minor non-conformance

A non-conformance is often classified as minor when all of the following are true (subject to your QMS and customer rules):

• No impact on safety, airworthiness, or function: Deviation is clearly limited to cosmetic or non-critical requirements and is demonstrably outside any safety or certification boundary.
• Limited scope and well-contained: Single part, operation, or lot; no evidence of systemic process failure.
• Simple, defined rework: Can be corrected by a standard, previously approved rework instruction that restores full compliance to the existing design without engineering change.
• No breach of regulatory, type design, or mandatory customer requirement: The condition does not contradict an airworthiness requirement, critical characteristic, or contractual requirement flagged as critical or key.
• Documentation issues with recoverable evidence: Missing signatures, dates, or incomplete entries, where objective evidence exists and a documented, controlled correction process (with traceability) is allowed.

Even minor non-conformances still require proper documentation, disposition, and trend analysis. In many aerospace environments, repeated minor issues can trigger reclassification as a more serious systemic problem.

Contract and customer-specific definitions

Many aerospace customers define severity levels directly in their specs or quality clauses (for example, critical/major/minor or Class 1/2/3 defects). Typical patterns include:

• Critical/major/minor defect codes tied to product characteristics (dimensions, materials, processes, documentation, labeling, etc.).
• Critical characteristics and key characteristics where any deviation is automatically treated at least as major.
• Supplier quality requirements that specify when a concession, deviation, or customer approval is mandatory.

In practice, your classification must align with:

• Your AS9100-compliant QMS procedures and risk criteria.
• Customer, OEM, or airframer-specific quality manuals and SQARs/SQMs.
• Regulatory constraints applicable to your role (production, repair station, design organization, etc.).

If internal criteria conflict with a customer requirement, the stricter requirement usually governs in aerospace supply chains.

Process and system considerations in brownfield environments

In mixed legacy environments (paper travelers, older MES/QMS, and multiple customer portals), consistent severity classification depends heavily on:

• Clear, accessible criteria: Documented decision trees or matrices stored under document control and visible at point of use (digital or paper).
• Role-based training: Planners, inspectors, operators, and MRB members must interpret severity the same way across product lines and shifts.
• Integrated NCR workflows: Where MES, QMS, and customer portals are not fully integrated, ensure that severity codes and dispositions are mapped correctly to avoid misalignment (for example, a “minor” in your system auto-mapping to “major” or “unknown” in a customer portal).
• Change control: Updates to criteria, risk thresholds, or defect coding must go through formal change control and validation where required, especially when embedded into MES/QMS rules or automated routing.

Full replacement of existing QMS/MES/NCR systems solely to “fix” severity classification is rarely justified in aerospace due to qualification and validation burden, downtime risk, and integration complexity. Incremental improvements (for example, harmonized defect codes, better decision support in NCR forms, or digital work instructions that embed the classification logic) are usually lower risk and easier to validate.

Practical steps to distinguish and apply minor vs major consistently

To make the distinction defensible and repeatable:

1. Use a documented decision tree
   For example: Does it affect safety or airworthiness? Does it affect fit/form/function? Is a critical characteristic involved? Is the issue already at the customer or in service? Use yes/no logic to drive to major vs minor.
2. Define characteristic criticality up front
   Classify characteristics (critical, major, minor) in design and planning so that inspectors and MRB have clear context when an NCR is raised.
3. Standardize codes across systems
   Align severity levels and defect codes between ERP, MES, QMS, and customer portals as far as contracts allow. Where they differ, maintain a controlled mapping and document it.
4. Require MRB review for ambiguous cases
   If there is any doubt about potential safety, airworthiness, or systemic risk, treat the non-conformance as major or escalate to MRB / engineering.
5. Trend and re-evaluate
   Review NCR data periodically. Repeated “minor” issues related to the same process, supplier, or program may indicate that your criteria or controls need adjustment.

Constraints and limitations

This explanation does not override your AS9100 QMS, OEM specifications, repair station manuals, or regulatory approvals. Final authority on minor vs major classification comes from your approved procedures, customer contracts, and applicable regulators. Always follow those governing documents and use change control to adjust your criteria.