Nothing Happened. That Was the Warning.
What aviation and healthcare learnt from near misses and why humanitarian organisations should stop waiting for harm
A near miss is easily mistaken for a successful outcome. In reality, it may reveal that plans and procedures failed and that only timing, improvisation or luck prevented serious harm. Other high-risk sectors learnt to treat such moments as valuable safety evidence. Humanitarian organisations can do the same.
In many organisations, a field movement that nearly went wrong is treated as a field movement that ended well.
A convoy returns safely after taking an unsuitable route. A team is released after an unexpectedly hostile checkpoint encounter. A communications failure occurs during a movement, but nobody needs assistance. There is relief, perhaps an informal conversation, and then work continues.
Nothing happened.
Aviation learnt to see these moments differently. A near miss was not evidence that the system had worked. It was evidence that the system had been tested, and that luck, individual improvisation or a last-minute intervention may have prevented a much more serious outcome.
The lesson was not simply to investigate accidents more thoroughly. It was to create ways of learning from the much larger number of events in which harm almost occurred.
Turning close calls into organisational learning
In 1975, the US Federal Aviation Administration established a voluntary safety-reporting programme and asked NASA to administer the system independently. The choice of NASA was deliberate: separating the collection and analysis of reports from the regulator’s enforcement role helped protect anonymity and encouraged the flow of information.
Today, the Aviation Safety Reporting System receives confidential reports from pilots, air traffic controllers, cabin crew, maintenance personnel, dispatchers and others. Reports are analysed and de-identified. The resulting information is used to identify system deficiencies, issue time-critical alerts, inform policy and share lessons across the aviation community.
Its protections are significant, but they are not unlimited. The system does not provide blanket immunity. Criminal conduct and accidents are excluded, and the waiver of sanctions is subject to conditions including that a violation was inadvertent rather than deliberate. Aviation’s approach is therefore more accurately described as a just culture than as a culture in which nobody can be held responsible.
The purpose of protection is not to excuse unacceptable conduct. It is to prevent fear of punishment from suppressing the information needed to make the system safer.
Confidential reporting was only one part of aviation’s improvement. Independent accident investigation, crew resource management, engineering advances, standardised procedures, simulation and stronger regulation all contributed. It would be misleading to attribute aviation’s safety record to a single programme. What reporting systems changed was the quantity and quality of information available: the industry no longer had to wait for wreckage before looking for weaknesses.
From the cockpit to the hospital
Healthcare began to draw more explicitly on these ideas as the scale of avoidable patient harm became harder to ignore. The influential 1999 report To Err Is Human helped shift attention away from the assumption that medical errors were primarily the result of careless individuals. Errors frequently emerged from combinations of workload, communication, equipment, hierarchy, procedures and organisational design.
One important bridge between aviation and medicine was created in Israel. Professor Amitai Ziv, a physician and former Israeli Air Force pilot and flight instructor, founded the Israel Center for Medical Simulation at Sheba Medical Center. The centre adapted aviation-style simulation and structured debriefing to clinical work, allowing medical teams to practise rare or dangerous situations, examine their decisions and learn without exposing patients to the consequences of an initial failure.
This was not the invention of a national “no-blame” investigation system for Israeli hospitals, as the story is sometimes simplified. Its importance lay in transferring a different way of thinking about professional performance: mistakes could be examined openly; teamwork and communication could be trained; and a difficult event could become material for structured reflection rather than humiliation.
Other healthcare systems developed more direct approaches to incident and close-call investigation. Within the US Veterans Health Administration, serious close calls could receive the same root-cause analysis as events in which patients were harmed. Aggregating information centrally also revealed patterns that individual hospitals could not see alone. Yet the greatest value remained local: teams used the review to change the way care was delivered.
A later near-miss reporting pilot supported by the US Agency for Healthcare Research and Quality recorded 770 events across seven primary-care practices during a twelve-month project. Staff continued reporting even after the formal reporting period and small incentives ended. The reports helped practices identify vulnerabilities and make meaningful changes to policy and daily work.
What actually changed?
The most important change was not the creation of another form. It was a change in what counted as useful safety information.
Near misses allowed organisations to examine failure before serious harm occurred. They exposed unsafe workarounds, confusing instructions, weak handovers, poorly designed equipment and power dynamics that made junior staff reluctant to challenge a decision. Simulation made difficult conversations and crisis coordination visible. Confidential reporting identified problems that staff would otherwise have kept to themselves.
But healthcare also demonstrated the limits of copying aviation superficially. Reporting systems can collect thousands of accounts without making anyone safer. If staff receive no feedback, if recommendations remain unimplemented or if managers use reports primarily to identify who should be disciplined, reporting declines or becomes defensive.
As the US Agency for Healthcare Research and Quality has observed, aviation tends to connect reporting with prompt investigation and action, while healthcare has sometimes placed greater emphasis on data collection. Learning occurs only when information is converted into changed practice and when those changes are tested to see whether they worked.
No blame is not the same as no accountability
The expression “no-blame culture” is attractive because it directly challenges the instinct to find a culprit. It is also incomplete. Organisations still have responsibilities to address deliberate misconduct, reckless disregard for safety, concealment and repeated conscious violations.
A just culture begins with a different sequence:
- First reconstruct what happened and what information was available at the time.
- Examine the operational pressures, competing priorities and system conditions that shaped the decisions.
- Establish whether rules, authority and expectations were clear, realistic and consistently applied.
- Only then decide whether the response requires system change, additional support, clearer expectations or individual accountability.
This does not weaken accountability. It makes accountability fairer and more credible. A review that begins with blame encourages self-protection. A review that does not consider how and why people acted can also lose the trust of those involved. The task is to preserve both learning and responsibility.
A no-fault review is a method for discovering how an event occurred. It is not a predetermined conclusion that nobody is accountable.
The humanitarian blind spot
Humanitarian organisations operate in unstable and uncertain environments where staff routinely adapt plans to changing conditions. Information is incomplete, communications fail, programme imperatives compete with security concerns and decisions may be distributed across headquarters, country management, partner organisations and individual staff members.
These are precisely the conditions in which near misses can provide valuable evidence. Yet many disappear from organisational memory.
A movement reaches its destination despite an unreported route change. A local colleague talks a team through a checkpoint encounter that could have escalated. A threat warning reaches one department but not the team planning missions. A staff member notices that an accommodation security measure has failed and quietly corrects it. Because nobody was injured, detained or abducted, the event may never be formally reviewed.
There are understandable reasons. Staff may fear being blamed for breaching procedure. Drivers or locally recruited colleagues may worry that reporting problems could jeopardize their employment. Managers may be concerned about reputational consequences or scrutiny of decisions made under pressure. Security staff may concentrate limited capacity on serious incidents. Country teams may see formal reporting as an administrative burden imposed by headquarters rather than a tool that will help them.
Time is another constraint. After a twelve-hour working day, including hours on the road, reporting a close call can feel like the start of another task rather than the end of a difficult day. Staff know that a report may lead to questions, meetings and a formal review, all while immediate life saving tasks are pending. A learning system that depends on exhausted staff finding additional time risks losing precisely the experiences it most needs to understand.
The result is that organisations investigate the small number of events in which harm occurred while losing the larger body of evidence showing where harm nearly occurred.
What a humanitarian learning system could look like
Humanitarian organisations do not need to reproduce aviation’s institutional machinery. A proportionate model could begin with six commitments:
- Create a protected reporting route. Staff and partners need a quick way to report close calls, including a confidential option where appropriate.
- Select events for their learning value. The absence of injury should not automatically make an event low priority.
- Reconstruct rather than prosecute. Initial questions should establish what people saw, knew, expected and tried to achieve.
- Look across the system. Reviews should examine information flow, workload, programme and donor pressure, equipment, procedures, authority, leadership and organisational culture, not just the final action of the person closest to the event.
- Separate learning from disciplinary decisions. Where possible, the learning review should be protected from automatic use as an employment or disciplinary investigation. Evidence of deliberate misconduct can and should still be referred through an appropriate and fair process.
- Close the loop. Actions need named owners, deadlines and follow-up. Those who report should be told what changed.
Not every report needs a formal review. A brief conversation may be enough to identify a useful change. Where a fuller review is needed, managers should make time for it within the workload, rather than expect staff to absorb it on top of existing duties.
Independent facilitation may be particularly useful for serious incidents, events involving senior decisions, or situations where staff do not trust internal processes. The objective is not to replace organisational ownership, but to create enough distance for assumptions and power relationships to be examined honestly.
Learning before the consequences become irreversible
Aviation did not become safer because people stopped being accountable. Healthcare did not improve merely by encouraging more incident reports. Progress came when organisations created conditions in which people could disclose weakness, examine decisions in context and turn what they learnt into practical change.
Humanitarian organisations already conduct after-action reviews, security assessments and incident investigations. The missing opportunity is often earlier: the journey that nearly failed, the warning that almost went unnoticed, the decision that worked only because an experienced colleague intervened.
When nobody has been harmed, organisations have a rare opportunity to learn without first paying the price of failure.
Nothing happened. That is precisely why there is still time to act.
Selected sources
- NASA Aviation Safety Reporting System, Program Briefing and Confidentiality and immunity policies.
- Barach, P. and Small, S.D. (2000), “Reporting and preventing medical mishaps: lessons from non-medical near miss reporting systems”, BMJ, 320:759–763.
- Macrae, C. (2016), “Errors and Near Misses: What Health Care Could Learn From Aviation”, AHRQ Patient Safety Network.
- Ziv, A. et al. (2003), “Simulation-based medical education: an ethical imperative”, Academic Medicine.
- Ziv, A. et al. (2006), “The Israel Center for Medical Simulation: a paradigm for cultural change in medical education”, Academic Medicine.
- Crane, S. et al., “Implementing Near-Miss Reporting and Improvement Tracking in Primary Care Practices: Lessons Learned”, Agency for Healthcare Research and Quality.
Join the conversation
What helps your team learn from a close call—and what gets in the way?