An aerospace non-conformance report (NCR, NCMR, NCD, DR, QN, etc.) must contain enough structured information to fully identify the part, describe the defect, assess risk, and support traceable disposition and corrective action. Field names and layouts will vary by customer, site, and system, but the required content is broadly consistent.
1. Identification and traceability
At minimum the NCR must allow someone outside the immediate team (auditor, customer, investigator) to uniquely identify the event and link it to the affected product and records:
- NCR identifier: unique NCR / DR number, revision, and status.
- Date/time: when the non-conformance was detected and recorded.
- Reporter: name/ID and organization (e.g., inspector, operator, supplier, customer).
- Location: facility, building, line/cell, station, and operation/inspection step.
- Customer link: customer program/aircraft/platform, contract/SOW, and any customer defect report ID if applicable.
2. Part, configuration, and documentation data
Aerospace non-conformance records must allow reconstruction of the exact configuration involved. Typical required fields:
- Part identification: part number, description, dash level or variant, and configuration if applicable.
- Serial/lot/heat/batch: serial numbers, lot numbers, heat numbers, cast numbers, or other unique identifiers for all affected units.
- Quantity: total quantity affected, and used/scrapped/quarantined quantities.
- Revision and configuration: drawing revision, model revision, planning revision, software/hardware revision as applicable.
- Process routing: operation number, work order/traveler number, router/planning ID, and revision under which work was performed.
- Referenced documents: drawing numbers, specifications, work instructions, special process instructions, and any deviation/concession already applicable.
3. Detection details (how and when it was found)
Auditors and customers will look for evidence that your detection and inspection system is functioning. The NCR should record:
- Detection point: in-process inspection, final inspection, receiving, test, field/service, customer site, or supplier.
- Detection method: visual, dimensional, NDT, functional test, software verification, torque check, leak test, etc.
- Inspection tools/equipment: gauge or test equipment ID, calibration status reference, automated test system ID if relevant.
- Trigger: routine inspection, sampling, SPC alarm, operator observation, customer complaint, or escape report.
4. Detailed description of the non-conformance
The defect description needs to be specific enough that another engineer could understand it without access to the part. Aerospace customers and standards typically expect:
- Requirement violated: clear reference to the requirement not met, such as drawing dimension and tolerance, spec paragraph, procedure step, process limit, or software requirement ID.
- As-found condition: factual description of what is wrong, avoiding interpretation or blame (e.g., “Ø12.000 mm feature measured Ø12.065 mm; tolerance 12.000 ±0.020 mm”).
- Defect category and code: standardized defect type or code (e.g., dimensional, surface defect, documentation error, process escape, material non-conformance).
- Location of defect: feature ID, station, face, hole number, zone, frame-stringer location, rib number, or coordinate system location as appropriate.
- Extent and pattern: number of occurrences per part, which serials are affected, and whether the issue is isolated or systemic.
- Visual/test evidence: references to photos, test results, CMM reports, NDT results, or measurement records stored elsewhere.
5. Risk and impact assessment
Regulated aerospace environments require a structured evaluation of impact on safety, airworthiness, performance, and compliance. The NCR should capture:
- Application/use: where and how the part is used (primary/secondary structure, flight control, engine, cabin, ground test only, tooling).
- Safety/airworthiness impact: preliminary assessment of potential safety impact, including whether the issue is potentially safety-critical or reportable.
- Functional impact: potential impact on performance, reliability, maintainability, or interoperability.
- Regulatory/contractual impact: potential effect on certification basis, customer requirements, or regulatory commitments.
- Escape status: whether non-conforming product has shipped, been installed, or entered service, and how that was determined.
6. Containment and immediate actions
Containment steps must be recorded clearly for traceability and to demonstrate control of non-conforming material:
- Quarantine details: where affected items are physically located (MRB area, quarantine cage, bond room) and how they are segregated.
- Inventory check: scope of stock search and results (WIP, finished goods, in-transit, at supplier, at customer).
- Production impact: whether operations were stopped, slowed, or allowed to continue under temporary controls.
- Temporary controls: additional inspections, holds, tags, or process changes applied pending disposition.
7. Disposition and approvals
Formal, documented dispositions are essential in aerospace due to airworthiness and contractual requirements. Depending on your procedures and customer rules, the NCR should include:
- Disposition type: scrap, rework to drawing, repair (non-standard), use-as-is, return to supplier, re-grade (for material), reclassify to non-flight or ground test use.
- Repair/rework instructions: clear, approved instructions tied to engineering authority, including new drawings or sketches, process steps, and any additional inspections or tests required.
- Authority reference: MRB authority numbers, engineering concessions/deviations, customer-approved permits, or controlled repair procedures.
- Affected documentation: any updates or notes required on travelers, as-built records, configuration management systems, or digital models.
- Validation requirements: additional proof tests, analysis, or inspections needed to justify the disposition and confirm conformity after action.
- Approvals: signatures or electronic approvals for quality, MRB engineer, design authority, program/customer representative when required, and date/time stamps.
8. Root cause and corrective / preventive action (as applicable)
In many aerospace organizations, the non-conformance record also serves as the entry point to CAPA or problem-solving processes. At a minimum, the NCR should link to these records, and in some systems it will contain them:
- Cause analysis reference: 5-Whys, fishbone, fault tree, or other analysis used, and where that record is stored.
- Verified root cause(s): distinct identification of direct cause, contributing factors, systemic/root causes as determined.
- Corrective actions: actions to prevent recurrence for the same part/location (e.g., fixture correction, updated tool, clarified work instruction).
- Preventive/systemic actions: broader actions that prevent similar escapes elsewhere (e.g., training, changes to design rules, FMEA updates, additional poka-yoke).
- Effectiveness checks: how and when you will verify that actions worked, metrics to monitor, and responsible owner.
9. System integration and brownfield considerations
In real aerospace plants, NCR information is often spread across multiple systems (MES, QMS, PLM, ERP, supplier portals). To avoid gaps and inconsistencies:
- Ensure identifiers: the NCR should carry or reference the IDs used in upstream and downstream systems (work orders, as-built records, supplier lots, customer notifications).
- Link, do not duplicate: where possible, link to source records (CMM reports, NDT logs, test data, concessions) rather than copying data that will get out of sync.
- Respect long lifecycle: avoid designs where changing NCR formats requires revalidating large portions of the MES/QMS stack unless you have a strong justification and a migration plan.
- Change control: treat NCR schema and workflow changes as controlled changes, with traceability, training, and, where relevant, revalidation.
10. Dependencies and variability
The exact information you must include is constrained by:
- Customer and regulatory requirements: prime OEMs and authorities often define mandatory fields, codes, and workflows in contracts, quality clauses, or supplier manuals.
- Internal procedures: your QMS, MRB procedures, and engineering authority processes may add requirements beyond typical industry practice.
- System capabilities: legacy QMS/MES solutions may not support every desirable field; in those cases, you will need controlled workarounds (attachments, linked records, or upgraded systems) and careful validation.
- Product type and risk: safety-critical and flight hardware usually demand more detailed risk, analysis, and approval data than ground equipment or test rigs.
Because of this variability, you should treat the list above as a reference checklist, then map it to your actual forms, electronic workflows, customer requirements, and validation constraints rather than adopting it blindly.
