Emergency Response Plan (ERP): Be Ready for the Day You Hope Never Comes
- Margrét Hrefna Pétursdóttir
- Nov 5
- 2 min read
Every operator hopes the Emergency Response Plan (ERP) is something that never has to be used. But that doesn’t mean it should be left to gather dust on a shelf.
An ERP must be simple, practical, and tailored to your operation. When a crisis hits, clarity matters more than complexity.

Keep It Simple — Start Small and Build
Too many operators make the mistake of starting with a massive, copy-pasted plan from another organization. But your ERP isn’t a generic document, it needs to describe your process, your resources, and your response structure, including your response contracts.
Keep it short and usable. Start with the essentials, then build on experience.
In an emergency, you don’t have time to search through 150 pages. You need to know who does what, and when.
Be Prepared — Not Caught Off Guard
When the unexpected happens, confusion is your worst enemy. A well-designed ERP gives structure when the pressure is highest.
It’s not just about reacting, it’s about maintaining control, knowing your communication lines, and continuing operations where possible.
Even though it might sound cold, business continuity is part of emergency response. Not everyone needs to be involved in the ERP activation, some must focus on keeping the rest of the operation going safely.
Train for Reality
Training is what turns a written plan into a living process.
Start with theoretical training when personnel are first nominated for ERP roles, but don’t stop there. The real training happens during practice.
Whether the ERP is owned by the Safety Department, Operations Control Center (OCC), or any other department, the Safety team should ensure that regular ERP drills are conducted. Treat these exercises as both training and audit, a chance to test whether the plan actually works under pressure.
Because the worst time to discover flaws is during a real event.
Make Emergency Response Plan Part of Everyday Operations
Some operators use elements of their ERP regularly, for example, during adverse weather, airport diversions, or ATC strikes.
That’s actually a positive sign. When parts of the ERP are used in daily operations, the plan stays fresh and functional. It may grow in size, but it also grows in strength, tested, refined, and adapted to reality.
Final Thought
You can’t predict when an emergency will strike. But you can decide how prepared you’ll be when it does. A good ERP isn’t about bureaucracy, it’s about readiness. Keep it simple. Keep it real. And keep it alive through training and practice.




Comments