EUROCONTROL—Systemic Occurrence Analysis Methodology (SOAM)—A “Reason”-based organisational methodology for analysing incidents and accidents

https://doi.org/10.1016/j.ress.2006.08.010Get rights and content

Abstract

The Safety Occurrence Analysis Methodology (SOAM) developed for EUROCONTROL is an accident investigation methodology based on the Reason Model of organisational accidents. The purpose of a SOAM is to broaden the focus of an investigation from human involvement issues, also known as “active failures of operational personnel” under Reason's original model, to include analysis of the latent conditions deeper within the organisation that set the context for the event. Such an approach is consistent with the tenets of Just Culture in which people are encouraged to provide full and open information about how incidents occurred, and are not penalised for errors.

A truly systemic approach is not simply a means of transferring responsibility for a safety occurrence from front-line employees to senior managers. A consistent philosophy must be applied, where the investigation process seeks to correct deficiencies wherever they may be found, without attempting to apportion blame or liability.

Introduction

As a direct result of the runway incursion accident at Milan Linate airport (Italy in October 2001) and the mid-air collision near Überlingen (Germany in July 2002), EUROCONTROL1 established a High Level European Action Group for Air Traffic Management (ATM) Safety (AGAS) to examine existing procedures and standards. The objective was to propose enhancements in ATM safety within the States of the European Civil Aviation Conference (ECAC).

By gathering together experienced safety experts from across the industry to scrutinise all aspects of ATM safety, AGAS was able to identify the areas where most benefit will be gained by improving safety in the short term. As a consequence a Strategic Safety Action Plan was structured to provide quick implementation solutions for improving ATM safety throughout Eight High Priority Action Areas:

  • 1.

    Safety Related Human Resources in ATM.

  • 2.

    Incident Reporting and Data Sharing.

  • 3.

    Airborne Collision Avoidance System.

  • 4.

    Ground-Based Safety Nets.

  • 5.

    Runways and Runways Safety.

  • 6.

    Enforcement of ESARRs and monitoring of their implementation.

  • 7.

    Awareness of Safety Matters.

  • 8.

    Safety and Human Factors Research and Development.

The Safety Occurrence Analysis Methodology (SOAM) has been developed to support the objectives of AGAS Priority Area 2, Incident Reporting and Data Sharing, by:

  • Providing an investigation methodology that can be applied locally by a large number of trained users, across a wide variety of occurrences. Occurrence data collection would then be a dispersed rather than centralised and specialised activity, increasing the potential quantity of data analysed.

  • Establishing a dedicated investigation terminology, providing a common language for trained users that facilitates data exchange and understanding of safety lessons.

  • Supporting Just Culture principles, which are closely aligned with the philosophy underlying the investigation technique (EUROCONTROL, 2003 [3]). A comprehensive training program to roll out the new process would incorporate awareness and education on the benefits of a Just Culture and of open reporting.

  • Providing standardised principles for Air Navigation Service Providers (ANSPs), investigators and airspace users on generating valid, effective remedial actions once contributing factors are identified.

  • Providing additional structure and focus to the common taxonomy for reporting and investigating ATM safety occurrences.

Most importantly, SOAM will support one of the most critical Harmonisation2 objectives, by providing a common methodology for the identification of causal factors across the aviation industry. This has the potential to enhance Data Sharing and Lesson Dissemination by:

  • Providing a simple framework (based on principles drawn from the now widely disseminated and recognised Reason Model) for sharing safety information, covering in particular the contributing factors and remedial actions.

  • Standardising the way safety improvement actions are generated.

  • Making it simpler to summarise the outcome of real investigated occurrences for briefings and publication, for example in issues of Safety News.

Section snippets

Existing EUROCONTROL tools and techniques vs. SOAM

A common approach to the reporting and assessment of ATM safety occurrences is specified within EUROCONTROL Safety Regulatory Requirement 2—ESARR 2. In the past years EUROCONTROL has progressively developed and distributed a set of valuable tools and guidance materials in support of this requirement. Despite these activities, some shortcomings have been observed in the extent to which the key objectives of ESARR 2 are currently being achieved in practice.

When developing SOAM a thorough review

SOAM approach

The investigation philosophy on which the SOAM approach is based is adapted from ICAO Annex 13, as follows: “The fundamental purpose of safety investigation is the prevention of further occurrences. It is not our task to apportion blame or liability”.3

Safety occurrences are by definition

Summary

It is axiomatic that the goal of improved system safety will be served by conducting some level of investigation into all occurrences. Achieving this goal will be substantially assisted by the availability of a simple, systemic analysis methodology that can be applied reliably to all levels of occurrence.

While highly competent investigators will always be required for complex, high level investigations, SOAM is suitable for use with all levels of occurrence, and is particularly suitable for use

Acknowledgements

The authors are grateful to Emeritus Professor James Reason for his review, helpful comments and inspiration for this work.

References (9)

There are more references available in the full text version of this article.

Cited by (28)

  • A method to identify investigative blind spots (MIBS): Addressing blunt-end factors of ultra-safe organizations’ investigation-work-as-done

    2022, Safety Science
    Citation Excerpt :

    As a starting point in assessing and the describing the performance of safety management systems we can view them as other organizations that want to safeguard against (dangerous) failure. Modern investigative processes (Licu et al., 2007) usually involve a defense-in-depth approach (Reason, 1997). Going upwards in the organization from the accident (rather than simply back in time from individual actions), barriers and situational conditions are examined.

  • A day when (Almost) nothing happened

    2022, Safety Science
    Citation Excerpt :

    As a result, the system broke down for the third time. The organisation analysed the event using the Systemic Occurrence Analysis Methodology (SOAM), an accident investigation methodology developed for Eurocontrol and based on James Reason’s model of organisational accidents (Licu et al., 2007). The aim of SOAM is to go beyond the “active failures of operational personnel” by including an analysis of the latent conditions within the organisation that in many ways determine the context for the event.

  • Learning from accidents: Interactions between human factors, technology and organisations as a central element to validate risk studies

    2017, Safety Science
    Citation Excerpt :

    Many risk management approaches derive from the multi-barrier concept developed by Reason, believing that the underlying mechanisms causing organisational accidents can be correctly identified and properly managed. Human reliability approaches such as Human Factors Analysis and Classification System – HFACS (Shappell et al., 2007), Systematic Occurrence Analysis Methodology – SOAM (Licu et al., 2007) and the Sequentially Outlining and Follow-up Integrated Analysis – SOFIA (Blajev, 2002), and accident causation analysis methods such as Bow-Tie (Zuijderduijn, 2000) and Cause-Consequence Diagrams (Nielsen, 1971) are examples, to name but a few, of risk assessment techniques deeply aligned with Reason’s approach. Contemporary approaches on accidents causality models try to apply systems theory and system thinking (e.g. Leveson, 2011) to disclose deeper factors contributing to accidents, by adding higher hierarchical levels beyond immediate events and analysing the interactions among factors and broader circumstances.

  • System dynamics approach for modelling the variation of organizational factors for risk control in automatic metro

    2017, Safety Science
    Citation Excerpt :

    Based on this, many methods of risk analysis were proposed to analyse the roles of humans and organizations. These methods include the following: Human Factors Analysis and Classification System (HFACS; Shappell and Wiegmann, 2000), Safety Occurrence Analysis Methodology (SOAM; Licu et al., 2007), Accident Analysis for Humans and Organizations (AcciMap; Svedung and Rasmussen, 2002), and Events and Causal Factors (ECF; Buys and Clark, 1995). These methods categorize the organizational factors to identify the types of errors, problems, or incorrect decisions and discuss the influence of organizational factors on the actions of humans and the equipment operation.

View all citing articles on Scopus
View full text