When should an aerospace NCR be raised versus a simple process deviation note?

An NCR should be raised when actual or suspected nonconformance affects the product, material, records, or a required process outcome, or when you cannot objectively show that requirements were met. A simple process deviation note is only appropriate for a controlled and procedurally allowed departure from the normal process that does not create a product nonconformance and does not bypass required review.

In practice, if the event may affect fit, form, function, airworthiness-related requirements, traceability, configuration, required approvals, or the validity of inspection and test evidence, treat it as NCR territory until qualified personnel determine otherwise. If you already know the departure is minor, anticipated, within procedural limits, and explicitly covered by an approved deviation workflow, a deviation note may be sufficient.

Use an NCR when

• The part, assembly, or material does not meet drawing, specification, routing, traveler, or process requirements.
• A required operation was missed, performed out of sequence without approval, or performed with unapproved parameters.
• Inspection, test, calibration, or verification results are failed, missing, invalid, or not traceable.
• There is uncertainty about conformity and the product cannot be confidently accepted as-is.
• The issue may require segregation, MRB review, rework disposition, scrap decision, concession, or customer notification under your procedures.
• Required records were altered, incomplete, or not generated in a way that preserves objective evidence.

Use a process deviation note only when

• Your procedure explicitly allows that type of deviation and defines who can approve it.
• The deviation is documented before or at the time of execution, not after a failure is discovered.
• The departure does not change product requirements or invalidate required inspections, tests, or traceability.
• Risk has been assessed at the level your QMS requires, and the deviation remains within approved boundaries.
• The event is essentially procedural or administrative and does not create doubt about product conformity.

A common mistake is using a deviation note to avoid NCR volume or MRB workload. That is risky. If the note is being used after the fact to explain away a missed requirement, it is usually not a simple deviation anymore. It is evidence of nonconformance, or at minimum of uncertain conformity, and should be handled accordingly.

Decision rule that works in most plants

Ask one question first: can you still demonstrate conformance to approved requirements with complete and credible objective evidence?

• If no, or not yet, raise an NCR.
• If yes, and the departure is explicitly allowed by procedure and approved through the right channel, a deviation note may be enough.

That sounds simple, but the boundary is often site-specific. Different aerospace organizations define deviation, escape, concession, waiver, and NCR differently in their QMS and customer flowdowns. Some require formal nonconformance records for cases that another plant might log as controlled process deviations. The internal procedure, contract requirements, delegated authority limits, and MRB structure matter.

Brownfield system reality

In many aerospace environments, the practical problem is not the definition but the workflow. NCRs, deviations, concessions, and MRB actions may be split across MES, QMS, ERP, PLM, and paper or spreadsheet logs. That creates classification errors, duplicate records, and broken evidence trails. If systems are not well integrated, people often choose the path of least resistance rather than the path required by procedure.

For that reason, improving the decision logic usually matters more than trying to replace every legacy system. Full replacement often fails in regulated, long-lifecycle environments because of validation effort, qualification burden, downtime risk, integration complexity, and the need to preserve traceability across existing records. In many plants, the more realistic approach is to tighten routing rules, role-based approvals, and record linkage across the systems already in place.

What to define clearly in your procedure

• Examples of deviations that are allowed without NCR initiation.
• Triggers that require immediate NCR creation.
• Who can classify borderline cases and within what time window.
• Whether missing records alone trigger an NCR.
• How deviation notes link to travelers, lots, serial numbers, and equipment records.
• When customer or regulatory flowdowns override local practice.

If your teams repeatedly debate the same cases, that usually means the procedure is underspecified, the training is inconsistent, or the systems do not force the right branch. Those are process control issues, not just documentation issues.

So the short answer is: raise an NCR whenever conformity is not met or cannot be demonstrated. Use a simple process deviation note only for a pre-authorized, bounded departure that your QMS explicitly permits and that does not create product nonconformance or weaken traceability.