An aviation emergency response plan that deploys when you declare.
An emergency response plan sets out who does what when an accident or serious incident happens. In eAviora declaring a crisis deploys its checklist as a live task board, each task owned by a role on your crisis team, and the crisis stands down only on a written record that says where any open work went.
- Overview
- Workflow
- Linked
- Discussion
- History
The module, on one sheet.
Four things, done on the record.
- Secure the flight data and voice recorders, done
- Notify the authority, in progress, not yet
- Open the occurrence and the investigation, waits on the recorders, not yet
- Approve the holding statement, escalated to the commander, not yet
A crisis, while it runs.
- Overview
- Workflow
- Linked
- Discussion
- History
A crisis stands down only on a written record.
- Only the commander or an administrator can resolve it, naming a recovery owner, the control status, a handover plan and where any open mandatory task went.Emergency ResponseHolds
- A recovery owner, not yet
- The control status, not yet
- A handover plan, not yet
- Where any open mandatory task went, not yet
What it links to.
- From
- CAP
- To
- ERP
- From
- DMS
- To
- ERP
- From
- TRG
- To
- ERP
- From
- SPM
- To
- ERP
Short answers.
No. Accident and serious incident response checklists ship, built on ICAO Annex 13. You can copy one and bind its tasks to your departments.
The crisis commander, or an administrator recorded as an override. Either way the stand-down record goes on file, and the crisis takes no new work after it.
You write the debrief once the crisis stands down. From it you can assign training or publish a safety bulletin.
See Emergency Response on your own records.
A walkthrough with the people who build eAviora.