SAFETY SITREP Safety-Related Information and Resources from the Vertical Aviation Safety Team
WHEN DID YOUR SAFETY PROGRAM LAST TELL YOU NO?
Walk into almost any flight operation today and you will find some components of a safety management system. Safety policy is posted, risk assessments are completed, reports are filed, and safety meetings are scheduled. From the outside, it looks like an organization that takes safety seriously.
Having a safety program and actually using one effectively are not the same thing.
I have worked with operations throughout the aviation industry long enough to recognize the pattern. Ask whether safety findings have ever changed a decision that leadership did not want to change, and the room goes silent. Ask whether the safety program manager has ever walked out of a leadership meeting having pushed back hard enough to cause real discomfort. Ask whether a flight was ever delayed or denied because safety data drove the outcome rather than operational pressure. When the honest answer to these questions is rarely, or never, you are looking at a program with safety infrastructure, but without safety function.
Forms and checklists manage activity, but leadership decisions are what manage risk. In more complex operations, such as air medical transport, those decisions happen under conditions that will test any safety program’s actual strength. Crews routinely launch at night, in marginal weather to unfamiliar locations, into situations where time pressure and an organization’s culture can quietly override the judgment that the same safety program was supposed to support. Documenting risk in that environment is not the same as controlling it.
When aviation organizations operate without serious incidents or accidents for years, they tend to develop a confidence that works against them. Friction decreases and small deviations from standards accumulate without anyone noticing. After an accident, leaders may say: “this was not supposed to happen” or “this is not who we are.” While they may mean it, even the best intent does not survive an accident. What survives is the documented behavior that preceded it, such as what was tolerated, what was delayed, what was funded, and what was not. These organizations trust
their track record more than their own data, and those are very different foundations to build upon.
Listen to how your organization talks about close calls. If a totaled aircraft becomes a hard landing in conversation, if turndowns get questioned before they get examined, if the debrief after a difficult event focuses on the outcome rather than the conditions that produced it, none of that is neutral. It reveals how the organization has decided to interpret risk, and that interpretation shapes the next set of decisions made under pressure.
Effective safety programs change outcomes. A safety program manager who avoids conflict, defers to volume demands, and rarely brings findings that require a difficult conversation is not leading safety. A safety director once told me he preferred to lead safety from the shadows. He meant it as a feature. It was not. Staying out of the way is its own kind of decision, and over time it has consequences. Real safety influence means safety findings reach the accountable executive without being softened along the way, and that someone at the table has enough standing to hold a position when the room pushes back.
Your post-accident narrative is already written. It is being authored right now by the decisions your organization is making—or avoiding—under the ordinary pressure of daily operations. The only open question is what it says. A safety program that never creates tension does not function as a control, and what your program is tolerating today will be far more relevant after an accident than the best intentions.
Michael Benton, MAS, MBA, is president and CEO of VyClimb Consulting LLC. He serves on the boards of CAMTS and NEMSPA and brings nearly 30 years of helicopter operations experience to his work in aviation safety, with a focus on air medical transport.
18
July/Aug 2026
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84
