These drivers act as the “why” behind the SMS, shaping how an organization prioritizes its investigative resources.
Regulatory Drivers
Modern regulators have shifted from prescriptive rules (did you do X?) to performance-based oversight (how well does X work?).
- This means investigations must now provide documented proof that the SMS is functioning as a closed-loop system.
- Furthermore, international standards like ICAO Annex 19 emphasize Just Culture protections, ensuring that the primary driver for an investigation is learning rather than legal prosecution.
Question – Does your current reporting system distinguish between “unintentional errors” and “gross negligence” as outlined in the Just Culture provisions of 376/2014?
Industry Drivers
Safety is increasingly collaborative. Industry bodies push for Data Sharing and Exchange, meaning your investigation must be compatible with industry taxonomies so that trends can be spotted across the entire sector. There is also a strong industry push toward
Resilience Engineering, where investigations look for “Safety-Plus” (why things go right) as much as they look for failures.
Business Drivers
From a commercial perspective, safety is a pillar of Operational Continuity. A major incident is a massive financial shock; therefore, business drivers demand investigations that find the “Permanent Corrective Action” to protect the brand and reduce insurance premiums.
- Increasingly, safety performance is a metric in ESG (Environmental, Social, and Governance) reporting, making high-quality investigations a requirement for investor confidence.
SMS Practical Investigation Skills
To meet the expectations of the drivers above, investigators require a specific set of practical competencies that move beyond simple technical troubleshooting.
The Interview: Seeking “Local Rationality”
The most critical skill is the ability to conduct non-punitive interviews. Instead of looking for where a person “failed,” the investigator looks for Local Rationality, understanding why the person’s actions made sense to them at the time given their tools, goals, and pressures.
Analytical Methodologies
Practical skill involves applying structured models to messy data. This includes:
- Barrier Analysis: Identifying which technical, administrative, or physical defenses failed or were missing.
- Root Cause Analysis (RCA): Using tools like the 5 Whys or Ishikawa (Fishbone) diagrams to dig past the immediate event to find the underlying organizational deficiencies.
Evidence Preservation and Digital Literacy
As systems become more complex, investigators must be skilled in capturing “soft” evidence, such as software logs, telemetry, and organizational surveys, alongside physical “bent metal” evidence.
- Understanding how to reconstruct a timeline from disparate digital sources is now a core practical requirement.
From Findings to Recommendations
The final practical skill is the ability to write Actionable Recommendations.
- A poor investigation ends in “remind staff to be careful.” A high-level SMS investigation results in tangible changes to design, hardware, or policy that eliminate the possibility of a repeat occurrence.
The Core Shift: From Performance to Constraints
In a traditional investigation, the human is the “variable” that failed. In an SME-focused SMS, the human is the “sensor” who reacted to a set of poorly managed constraints.
The Point of Interaction
When you focus on the individual, you are investigating Active Failures. These are the immediate triggers.
- We may assume the operator is competent and motivated to succeed. If they failed, the failure is a symptom, not the cause.
- The Problem: Focusing here provides a “false fix.” If you replace the person but leave the environment identical, the same accident is mathematically likely to happen again with a different name on the badge.
The Source of Energy
The Organizational Context represents the upstream decisions, budgeting, scheduling, equipment procurement, and procedure authoring. This is where the real “safety work” happens.
- We investigate Latest Conditions. These are the “resident pathogens” that exist in the system long before an incident occurs.
- The Analysis: We look for Objective Conflicts. Usually, an operator is forced to choose between “Safety” and “Efficiency.” When the Organizational prioritizes efficiency in its resource allocation, it creates a “trap” for the Point of Operational Contact.
Practical Application: The “Systemic” Investigation
When a specialist investigates a system, they typically look for three specific disconnects:
- Work-as-Imagined vs. Work-as-Done: (Management/Engineering) writes a procedure based on how they think the job works. The Sharp End (Operators) often has to “work around” those procedures because the tools or time provided are insufficient. An investigation must identify why these work-arounds became necessary.
- Safety Barriers vs. Safety Margins: A barrier is a specific check (e.g., a torque stripe). A margin is the “buffer” of time or resources available. Investigations often find that while the barrier was there, the margin had been eroded by business pressures, making the barrier impossible to use correctly.
- Normalization of Deviance: This is the most critical Blunt End finding. It is the process where a “shortcut” becomes the standard way of working because it has been successful in the past without consequence. The investigation must find where the organization stopped noticing the risk.
Regulatory Alignment: The 376/2014 Reality
For an SME, Regulation 376/2014 isn’t just about “being nice” to staff (Just Culture). It is a Data Reliability regulation.
- Take Away – If you focus on the Point of Operational Contact and punish people, you lose your data. If you lose your data, you lose your ability to see the Management System failures.
- 376/2014 forces the organization to treat an “Occurrence” as a System Diagnostic. The goal is to extract the maximum amount of technical and organizational intelligence from the event.
The Bottom Line
The shift to a system-focus means your investigation reports should rarely conclude with “Human Error.” Instead, they should conclude with a list of Upstream Deficiencies.
Important Take Away – If your recommendations do not require a change in how the business allocates resources, provides equipment, or writes policy, you most likely have not actually fixed the problem. you have just blamed the person who happened to be standing there when the system’s inherent flaws finally aligned.
Next Steps
Sofema Aviation and Sofema Aviation Services provide Classroom, Webinar & Online Training – with over 550 Online Courses, Packages & Diploma’s to choose from, Sofema Aviation is the ideal option to grow organisational or individual competence – Please see the websites or email [email protected]
Tags:
Human Factors, Root Cause Analysis, Safety Management systems, SMS, sasblogs, ICAO Annex 19, Sofema Online (SOL), Sofema Aviation Services (SAS), Regulation 376/2014
