SMS That Works: Revisiting the 6 Components for Real-World Performance (6/6)
Part 6: Emergency Response Planning — The Stress Test
Over the past five weeks, we have explored:
Safety Management Plan
Documentation
Safety Oversight
Quality Assurance
Training & Safety Promotion
This week, we conclude the series with what may be one of the most misunderstood components of a Safety Management System:
Emergency Response Planning (ERP).
Not because organizations don't recognize its importance.
But because many organizations struggle to understand how it connects to the rest of their SMS.
Too often, the ERP is treated as a standalone document—a plan that sits on a shelf until it is needed.
Yet Emergency Response Planning is not separate from SMS.
It is an essential part of it.
Why Is Emergency Response Planning Part of SMS?
When reviewing Advisory Circular 107-001, the connection between ERP and SMS is not always immediately obvious.
To understand it, we need to return to the foundation of SMS itself.
Transport Canada defines a Safety Management System as:
A documented process for managing risks that integrates operations and technical systems with the management of financial and human resources to ensure aviation safety or the safety of the public.
Notice what the definition does not say.
It does not say that SMS eliminates risk.
It says that SMS manages risk.
Throughout this series, we've discussed how organizations:
Identify hazards
Assess risk
Implement mitigations
Monitor effectiveness
Continuously improve
All of these activities reduce risk.
But they do not eliminate it.
There is always residual risk.
And because residual risk remains:
Incidents, emergencies, and crises can still occur.
Emergency Response Planning is the organization's acknowledgement of that reality.
Managing What Happens When Risk Becomes Reality
A functioning SMS recognizes two important truths:
We should do everything reasonably possible to prevent incidents.
We must be prepared when incidents occur anyway.
This is where Emergency Response Planning becomes critical.
ERP is about:
Responding effectively
Protecting lives
Reducing impacts
Recovering operations
Learning from events
In other words:
ERP is how the organization manages risk after an incident occurs.
The Objective of an ERP
ICAO Doc 9859 states that the objective of an Emergency Response Plan is:
The safe continuation of operations and the return to normal operations as soon as possible.
That objective is often overlooked.
Many people think ERP is primarily about emergency response.
But it is equally about:
Business continuity
Recovery
Organizational resilience
Learning and improvement
Responding is only the beginning.
What matters is how effectively the organization recovers and what it learns afterward.
The ERP Is a Stress Test of the SMS
If the Safety Management System is truly a system, then every component should support Emergency Response Planning.
An emergency is often the ultimate test of whether those components are functioning as intended.
When an incident occurs:
Are responsibilities understood?
Are resources available?
Are personnel trained?
Are procedures accessible?
Are communications effective?
Can leadership make informed decisions?
These questions extend far beyond the ERP itself.
They involve every component of the SMS.
How the Other Components Connect to ERP
🔹 Safety Management Plan
The Safety Management Plan establishes:
Roles
Responsibilities
Authorities
Accountabilities
During an emergency, these become critical.
If responsibilities are unclear during normal operations, they will be even less clear during a crisis.
🔹 Documentation
The ERP itself is documentation.
But so are:
Contact lists
Checklists
Procedures
Resource inventories
Notification protocols
Without effective document management, response effectiveness suffers.
🔹 Safety Oversight
Safety Oversight helps organizations understand:
Hazard trends
Emerging risks
Areas of concern
This information should influence:
Exercise planning
Emergency scenarios
Resource allocation
Preparedness activities
🔹 Quality Assurance
Quality Assurance verifies that:
ERP reviews occur
Exercises are conducted
Corrective actions are completed
Lessons learned are implemented
Without QA, organizations often repeat the same mistakes exercise after exercise.
🔹 Training & Safety Promotion
An ERP is only effective if people understand their roles.
Training ensures personnel:
Know what to do
Understand expectations
Can perform under pressure
Safety Promotion ensures those lessons remain visible between exercises and real-world events.
What Good Looks Like
Organizations with mature Emergency Response Planning programs typically:
Integrate ERP into SMS activities
Conduct meaningful exercises
Train personnel regularly
Track lessons learned
Implement corrective actions
Review plans periodically
Allocate appropriate resources
Involve leadership in preparedness activities
Most importantly:
They treat emergency preparedness as an ongoing process—not a compliance exercise.
What Bad Looks Like
Organizations often struggle when:
The ERP is reviewed only before an audit
Contact information is outdated
Exercises are conducted only to satisfy requirements
Corrective actions remain open indefinitely
Personnel are unfamiliar with their roles
Lessons learned are documented but never implemented
The ERP operates independently from the SMS
In these environments, the organization may appear prepared on paper while remaining vulnerable in practice.
Questions for Executives
If you're a senior leader, ask:
What are the most credible emergency scenarios facing our organization?
When was our last exercise?
What did we learn?
What changed as a result?
Are corrective actions complete?
Do we have the resources required to respond effectively?
Could we safely recover operations if a significant event occurred tomorrow?
These questions often reveal more about organizational preparedness than the ERP document itself.
Quick Wins
If you're looking to strengthen Emergency Response Planning, start here:
🔹 Review your last exercise report
What recommendations were made?
🔹 Identify one outstanding corrective action
Why is it still open?
🔹 Verify emergency contact information
Outdated contact lists remain one of the most common ERP weaknesses.
🔹 Confirm leadership responsibilities
Could everyone explain their role during an emergency?
🔹 Connect lessons learned to your SMS
Ensure findings feed into:
Risk management
Documentation updates
Training activities
Quality Assurance reviews
Bringing the Series Together
Over the past six weeks, we've discussed six components.
But the most important lesson is this:
They are not six separate components.
They are one interconnected system.
The Safety Management Plan defines the system.
Documentation supports it.
Safety Oversight monitors it.
Quality Assurance verifies it.
Training & Safety Promotion enable it.
Emergency Response Planning stress-tests it.
When all six work together, organizations move beyond compliance and toward meaningful safety performance.
That is what a functioning Safety Management System looks like.
Work With Us
At Acclivix, we help aviation organizations build Safety Management Systems that work in the real world.
Whether you need support with:
Emergency Response Planning
Exercise design and facilitation
Safety Risk Management
Internal audits and Quality Assurance
Training and competency development
SMS implementation and continuous improvement
Or tools like Wombat Safety Software to strengthen visibility, accountability, and performance
—we can help.
If you're unsure how well your ERP is connected to your SMS—or whether your SMS is truly functioning as a system—we'd be pleased to start that conversation.
Because when emergencies occur, the goal isn't simply to respond.
It's to respond effectively, recover quickly, learn from the experience, and emerge stronger than before.