IRELAND · Emergency Response Plan
ERP and Emergency Procedures for Drone Operators
An ERP translates emergency procedures into immediate actions during and after an incident. The document must be concise enough for use under pressure and simultaneously align with the operational manual, notification obligations, and internal responsibilities.
Start with universal priorities
Protect persons, stabilize or end the flight as safely as possible, secure the location, and prevent further damage. Record time, position, altitude, and relevant system information when it is safe to do so.
Develop scenarios separately
Use action cards for lost link, fly-away, crash/damage, injury, fire/battery, airspace conflict, and other realistically relevant scenarios. Outline decision points, role distribution, communication, and registration.
Make reporting routes conditional
Not every incident requires the same notification. Include decision trees for emergency services, aviation authority, client, insurer, and privacy/data leak assessment. Avoid absolute yes/no assumptions before facts are known.
Exercise and improve
IAA points out that operators must demonstrate the suitability of contingency and emergency procedures under PDRA or SORA. Register scenario, participants, outcome, shortcomings, owner, and closure date of improvement actions.
Frequently asked questions
Should 'stop the flight' always be the first action?
Not blindly. The first priority is to protect persons and safely stabilize or end the flight. The appropriate action depends on the scenario and remaining control.
What is a Pocket ERP?
A compact emergency card for mobile or print use containing key contacts and first actions, used alongside the full ERP version.