Sofema Online (SOL) examines the role of Just Culture related to effective MEDA analysis.

 

Introduction: What “Just Culture” Means in Day-to-Day Maintenance

•  Fairness + learning: Separate how we learn from the event from how we handle accountability.

•  Intent before outcome: Judge intent and context first (error vs at-risk vs reckless), not just the size of the consequence.

•  System first: Look for conditions and barriers that set people up to fail before considering individual remedies.

Anticipated Results: People are more willing to report and speak frankly in MEDA interviews; investigators get usable detail; actions target system fixes.

 

Why Just Culture Increases Reporting (& Quality of Data)

•   Trust lowers personal risk: When staff believe honest mistakes won’t trigger punishment, self-reports rise and narratives are richer.

•   Clarity reduces ambiguity: A visible decision pathway (console → coach → discipline for rare reckless acts) removes fear of arbitrary outcomes.

•   Feedback sustains participation by reporting earlier with fewer minor issues.

 

Operational Mechanics That Make it Real - Policy & Definitions (Put in the SMS/MEDA SOP)

•  Define error (unintentional) and violation (intentional) plainly.

•  State: “We investigate events to learn about the system; accountability decisions follow after context is established.”

•   Specify immunity boundaries: good-faith reporting of errors and at-risk acts is protected; reckless acts are not.

 

Decision Pathway (Simple and Visible)

•   Honest mistake (not on purpose): We support you, give coaching, and fix the work setup so it’s harder to repeat.

•   Shortcut (done on purpose but due to habits or pressure): We coach, remove rewards or pressures that encourage the shortcut, and redesign the process.

•   Reckless act (rare- knowingly taking a significant, unjustified risk): We start formal discipline, and we also review our processes to see if pressure or drift played a role.

 

How Just Culture Strengthens MEDA 

 

Before the Interview

•   Use neutral event statements (“During re-rigging, actuator installed reversed; leak discovered post-release”).

•   Brief the participant on purpose, protections, and process (we’re fixing the system).

During the Interview

•   Explore intent and context early; avoid outcome bias.

•   Probe latent conditions (info, tools, environment, supervision, KPIs).

•   Ask for fix ideas-local expertise is gold.

After the Interview

•   Classify behaviour (error/violation) and contributors; write barrier-changing actions with owners/dates/verification.

•   Route themes to the risk register and the Safety Action Group; escalate resource needs to the Safety Review Board.

 

Leadership Behaviours That Make or Break Just Culture

 

Watch your words: Say “Let’s understand the conditions” instead of “Who missed the step?”

Don’t punish just because the result was bad: A significant outcome doesn’t turn an honest mistake into a rule break.

Be consistent: Use the same decision rules on every shift and at every site.

Be transparent about real fixes: In briefings, talk about how we changed the system (process, tools, info) —not just “we retrained people.”

 

Next Steps

Sofema Aviation Services and Sofema Online deliver Maintenance Error Management System (MEMS) and Maintenance Event Decision Aid (MEDA) training as Classroom, Webinar and Online training. For details, please see the websites or email team@sassofia.com.