Sofema Aviation Services (SAS) considers the challenges when building an HSE into an Aviation Domain.

Introduction

Aviation Leaders set the Cultural Tone. If leaders treat safety as “how we work,” people copy it. If leaders treat safety as a box to tick, people copy that too.

Important Note: Do not treat HSE and your core management activities as separate. Use your business knowledge to design simple, practical safety steps that people will actually use. That keeps operations safe, steady, and efficient.

Safety competence in aviation leadership should be built into daily work, not added on. Leaders set the tone: when they make health and safety part of every plan, handover, and review, people copy that. The most significant risks hide at the joins- between teams, shifts, and contractors, so simple, shared ways of working matter: short briefs and debriefs, clear escalation (stop if a concern is raised twice), standard handovers, one source of truth for documents, and visible controls at the point of work.

The Main Challenges

• Competing goals: Hitting deadlines and cutting costs can push people to take shortcuts.

• Mixed messages: One manager says “safety first,” another says “get it out the door.”

• Silent risks: People see hazards but stay quiet because they fear blame or think “not my job.”

• Patchy skills: New leaders know the rules but not how to apply them under time pressure.

• Poor handovers: Mistakes often happen at the joins- between teams, shifts, and contractors.

• Paper vs practice: Procedures exist, but everyday work drifts away from them.

• Weak learning loop: Incidents repeat because lessons aren’t captured or shared well.

Best Practices: How to Set-Up for Success

• Make safety part of daily work, not a separate thing. Ask about risk and controls in every planning meeting.

• Use short, structured briefs and debriefs. Before: “What are we doing? What could bite us? What will we do about it?” After: “What surprised us? What will we change tomorrow?”

• Invite challenge. Set a simple rule: if someone raises a safety concern twice, the task stops until a leader decides.

• Standardize handovers (what, who, when), keep one “source of truth” for documents, and publish clear escalation paths.

• Recognise good behaviour, not just bad outcomes. Praise people who slow down to check, who help another team, and who report weak signals.

• Keep controls visible. Simple checklists, hazard cue cards, and “red flag” lists at the point of work.

• Learn fast from small misses. Treat near-miss reports like gold- review weekly, share one takeaway, and close the loop.

• Lead by walking around. Short floor walks with two questions: “What could go wrong here?” and “What do you need from me to make this safer?”

 

Development Methodologies: Building Competence

What leaders are accountable for:

• Set direction: Safety is “how we work,” not a project. Write it down in 3 lines: what we value, what we will not accept, and who decides what.

• Provide means: People get time, tools, and training to work safely. If not, work pauses.

• Check reality: What is written matches what is done. If not, fix the gap fast.

• Learn and improve: Small signals (near-miss, delay, rework) trigger action before harm.

 Core Oversight Moves (Works in Ops, MX, Ground, Flight)

• One page per high-risk task: What can go wrong, key controls, who can stop work.

• Short, standard brief & debrief:
   >> Before: Task, biggest risk, control, who calls stop.
   >> After: What surprised us, what we’ll change tomorrow.

• Clear escalation ladder: If a concern is raised twice, stop and escalate—no penalties.

• Tidy interfaces: Standard handovers (what, who, when), single source of truth for documents.

• Visible controls: Checklists and “red flag” cues at the point of work, not hidden in a folder.

• Leaders in the field: Regular short walks: What could hurt us here? What do you need from me?

Building Competence

• Simple skill steps: Learn → Observe → Do (supervised) → Do (with standby) → Do (solo).

• Fast “what-if” drills: Situation → Risk → Options → Recommendation → Decision by when.

What Leaders Review

• Daily (duty/shift): Top 3 risks today, one action owner, one check item.

• Weekly: One interface defect fixed; one near-miss closed with a lesson shared.

• Monthly: Time-to-competence trend, overdue actions burn-down, top repeat issues.

• Quarterly: Independent check that “paper = practice” on 2–3 high-risk activities.

Measures That Matter (Few, Clear, Cross-Domain)

 Leading (before harm):

• % shifts with brief/debrief done

• Near-misses reported, and closed on time

• Interface defects found/fixed

• Time-to-competence for key roles

Lagging (after harm):

• Rework/delays linked to safety controls not used

• Tool/FOD, equipment damage, ground/ramp events

• Repeat findings from audits/occurrence reports

Behaviour Check:

• People felt safe to challenge

• Stop-work is used when needed- and backed by leaders

Final Comments  

Competence grows through small, frequent practices:

• Learn → observe → do with supervision → do with a standby → do solo.

• Reinforced by quick “what-if” drills.

• Oversight is rhythmic and practical, daily top-three risks, weekly near-miss learning, monthly time-to-competence, and quarterly checks that paper matches practice.

• Measure a few things that drive behaviour (brief/debrief completion, near-miss closure, interface defects fixed, time-to-competence) and back people who pause work when unsure.

Next Steps  

Sofema Aviation Services (SAS) provides a First Aid in the Part-145 Workplace (Base and Line) – 2 Day training as a Classroom and Webinar. Please see our online website, Sofema Online (SOL), or email team@sassofia.com.