How much risk are you willing to accept?
This is one of the most critical questions that every aviation service provider needs to answer. The answer will influence every single risk management activity in the operator's aviation safety management system (SMS).
What is your risk appetite? Not surprisingly, our risk of appetite changes based on a variety of factors that require constant monitoring, including:
Commonly, we think about the "risk tolerance" question in terms of Acceptable Level of Safety (ALoS) or “as low as reasonably practicable” (ALARP). However, it may be less effective to address the issue of acceptability in terms of a concept (ALoS, ALARP) rather than as a question. This is because attacking risk permissibility from the point of view of ALoS or ALARP allows you to sidestep actually asking yourself the all-important question (), “How much risk are we willing to accept?” (HMRA)
The difference between ALoS/ALARP and HMRA is subtle but very important:
In other words, ALoS focuses on the amount of safety for a given type of concern, while asking HMRA focuses on the amount of risk being taken on for a given safety concern. Specifically asking how much risk you are willing to accept is a natural way of shifting your focus to what risks you are taking on and accepting, rather than the safety of the issue in question.
That being said, every aviation service provider should consider all three of the above points, but in a cycle.
ALOS, ALARP, and HMRA should all be established in your safety documentation and practices. However, they should be established in a particular order. It works like this:
This process should happen on a high level, such as in safety goals and objectives documentation. It should also exist on a micro level, such as during the risk management process of individual safety concerns.
This process is also a cycle, whereby reviewing ALoS goals should be reviewed by asking the HMRA question.
Assessing how much risk is being taken on is an important first step in establishing an acceptable level of safety and as low as reasonably practicable. By “taken on” we are talking about:
Taken-on is similar to “accepted.” It arises from the fact that absolute safety is unachievable. What this looks like is identifying aspects of a risk or hazard that:
In summary, taking on risk means addressing what potentialities remain after SMS mitigation efforts.
Asking and answering how much risk is being taken on is an essential part of segregating:
Establishing both elements is an essential part of risk mitigation effort, as it helps identify:
The main argument here is that mitigating risk is as much about understanding what you are mitigating as what you aren’t mitigating.
Taking on a certain amount of risk actually makes sense for organizations. It would be a poor and unmanageable use of resources to try and mitigate a particular risk “entirely.” Therefore:
Doing this assumes that your organization has already defined the line in your risk matrix that separates acceptability from non-acceptability.
For further information about defining acceptability and analyzing the risk that your company is taking on, these resources should prove valuable:
Last updated in June 2024.