Safety Management Systems and Quality Management Systems are often discussed in the same sentence — sometimes as if they are two names for the same thing. They are not. The overlap is real. But so is the gap between them, and that gap has been a contributing factor in aviation incidents where the formal quality records showed compliance while the operational reality showed something different.
EASA addressed this distinction in its European Plan for Aviation Safety (EPAS) 2026. The EPAS 2026 document notes explicitly that „competence of personnel is an important enabler for resilience and is therefore assigned an elevated priority ranking within the EPAS strategic priorities.“ The addendum to EPAS Volume I introduced workforce competency as a systemic priority, with the direct statement: „Addressing the shortage of competent aviation personnel is a priority topic for the Member States, and it has been recommended to be addressed as a matter of priority by the MAB.“ The 2024 EASA report on SMS compliance noted that „compliant SMS programs reduce incident rates by 20%.“ Understanding why EASA is framing workforce competency as a safety management issue — not just a training administration issue — requires understanding what each system is actually designed to do.
1. What a Quality Management System Is Designed to Do
A QMS is a process control framework. It defines how work is planned, executed, measured, and improved. It establishes procedures, documentation requirements, nonconformance management processes, and audit processes that verify the system is being followed.
A QMS is retrospective and prescriptive. It describes what the process should be and captures evidence that it was followed. It is optimized for compliance verification — the ability to demonstrate, through documented evidence, that required procedures were executed correctly.
The strength of a QMS is that it creates a structured, verifiable record of process execution. The limitation is that it captures what people documented, which is not always what they did, and documents what procedures required, which is not always what was operationally realistic under the conditions that existed at the time. EN 9100 Section 7.2 addresses competency requirements — but the standard addresses whether a procedure for competency assessment exists, not whether the organizational conditions allow competency gaps to surface and be addressed proactively.
2. What a Safety Management System Is Designed to Do
An SMS is a risk identification and communication framework. EASA defines SMS as seeking „to proactively identify hazards and to mitigate the related safety risks before they result in aviation accidents and incidents.“ It is designed to surface hazards before they become incidents — and critically, it depends on a reporting culture where personnel feel safe to raise concerns without consequence.
ICAO Annex 19 SMS Standards and Recommended Practices have been incorporated into each EASA aviation domain, including Part 145 (Continuing Airworthiness) and Part 21 (Design and Production). The EASA Management System Assessment Tool (MSAT) was developed to guide organizations through implementation and promote a common approach to management system assessment across aviation domains.
The core functional requirement of an SMS is voluntary hazard reporting. This means maintenance technicians, quality inspectors, and production personnel must be willing to identify and report conditions that are unsafe or sub-optimal — even when doing so might reveal errors they made or reflect poorly on their team. That willingness is a behavioral condition, not a procedural one. You cannot create it through a reporting form or a training module. You create it through years of organizational behavior that consistently demonstrates that reporting is safe and that reports lead to meaningful action. A 2023 study referenced by SMS compliance literature found that integrated SMS platforms reduce errors by 15% when they successfully improve data utilization and reporting consistency.
3. Where Confusing the Two Creates Risk
Organizations that treat their QMS as their safety system miss the behavioral dimension entirely. A nonconformance report captures what went wrong after it went wrong. It does not capture the organizational pressure that led someone to make a decision they knew was marginal — to accept a borderline measurement, to skip a verification step under schedule pressure, to install a part they were not completely certain about rather than delay the aircraft and face the operational consequence.
Those decisions happen in the gap between the formal QMS and the actual operational conditions. They are invisible to the QMS because they do not generate a nonconformance record — the part that was installed worked, or the marginal measurement did not produce a field failure in that specific instance. The risk accumulates in the system without appearing in the quality records.
EASA EPAS Volume III identifies „Lack of effectiveness of safety management system (SI-2026)“ as a specific safety issue within its Safety Risk Portfolio. The EPAS framework is explicit: „In most scenarios, these problems are related to human factors, human performance, competence of personnel, socio-economic factors or to deficiencies in organisational processes and procedures.“ A QMS that captures the technical cause of a nonconformance but does not examine the human factors conditions that produced it — fatigue, time pressure, unclear work instructions, inadequate supervision — is producing incomplete root cause analysis by EASA’s own framework.
4. The IA9100 Bridge
IA9100’s human factors root cause analysis requirement — one of the six named areas in the IAQG Key Change Summary — explicitly bridges QMS and SMS thinking. Organizations will be required to assess human factors as part of nonconformance root cause analysis. QT9 Software’s October 2025 analysis of IA9100 confirmed: „Leadership will be tasked with demonstrating commitment to a culture of quality through behavior and resources, including incorporating human factors, such as fatigue, into root cause investigations and providing employee well-being programs that support quality outcomes.“
A corrective action process that asks „what organizational conditions led the operator to make the decision they made?“ is applying SMS methodology to QMS problem-solving. Building that practice before IA9100 requires it produces better corrective actions now and a more mature organizational understanding of the relationship between the two systems ahead of the transition audit.
3 Concrete Actions
1. Audit your SMS reporting data — not just your QMS nonconformance data — for signals about quality-critical process conditions. If your SMS reports contain references to time pressure, uncertainty about procedure interpretation, or workload concerns in quality-critical roles, those reports are telling you something your QMS data is not. The absence of SMS reports in a quality-critical area is itself a signal worth investigating — it may reflect that reporting culture has not reached that area, not that the area is risk-free.
2. Review how your organization responds to SMS reports that describe marginal decisions that did not produce a nonconformance. If the response is „no action required — no nonconformance occurred,“ the organizational message is that reporting near-misses has no operational consequence. That message will reduce future voluntary reporting. The correct response is investigation of the conditions that produced the marginal decision — time pressure, unclear procedure, competency uncertainty — and action on those conditions.
3. For organizations preparing for IA9100 transition: begin incorporating human factors questions into your existing RCA process now. The question „what organizational conditions led the operator to make the decision they made?“ does not require IA9100 to be published before it produces value. It will produce better corrective actions immediately, and it will mean your team is practiced in the methodology before the first IA9100 transition audit expects to see it in your D5 root cause documentation.
👉 Request a Technical Consultation → www.skqc.org
Sources
- EASA — European Plan for Aviation Safety (EPAS) 2026, 15th Edition (December 18, 2025), easa.europa.eu
- EASA — European Plan for Aviation Safety (EPAS) Volume I Addendum: Workforce Competency Priority, easa.europa.eu
- EASA — Safety Management System and Management System: The Integrated Approach, easa.europa.eu
- EASA — EPAS Volume III Safety Risk Portfolios: SI-2026 Lack of Effectiveness of SMS, easa.europa.eu
- ICAO — Safety Management Manual (SMM), Document 9859, 4th Edition
- QT9 Software — IA9100 is Coming: Key Updates for Aerospace and Defense (October 23, 2025), qt9software.com
- IAQG — IA9100 Key Change Summary, iaqg.org
- EN 9100:2018 / AS9100 Rev D — Section 7.2: Competence
- SMS Pro / Aviation Safety Blog — How SMS Pro Facilitates EASA Compliance (September 10, 2025), aviationsafetyblog.asms-pro.com
#AviationSafety #SafetyCulture #QualityManagement #SMS #EASA #EPAS2026 #AerospaceQuality #IA9100 #SKQC