What constitutes a nonconformity, and what is the standard flow from detection to closure in AMQS?

• A. A nonconformity is a deviation from requirements; flow: detect, document, assess impact, contain if needed, determine root cause, implement corrective action, verify effectiveness, close when resolved and documented.
• B. A nonconformity is a delay in maintenance; flow: schedule, perform, log, close.
• C. A nonconformity is only documentation gaps; flow: fix, ignore, archive.
• D. A nonconformity is when supplier quality changes; flow: confront supplier, demand action, close.

Answer: (A)

In AMQS, a nonconformity is a deviation from requirements or standards that applies to the product, process, or service. When such a deviation is detected, the normal flow is to capture it in a record, assess its potential impact on safety, airworthiness, and overall compliance, and apply containment if needed to prevent further use or spread of the issue. Next, you identify the root cause so you know why the deviation occurred. Based on that analysis, you implement corrective actions to fix the problem and prevent recurrence, then verify that these actions are effective. The issue is considered closed only when the problem is resolved and all steps, including verification, are properly documented and traceable.

This approach aligns with the disciplined CAPA-style process used in AMQS: detection, documentation, impact assessment, containment, root cause analysis, corrective action, verification of effectiveness, and formal closure with records. The other options miss essential elements (for example, defining a nonconformity narrowly as a maintenance delay, or focusing only on documentation gaps or supplier changes) and do not provide the complete, structured flow from detection through closure.