Aviation occurrence reporting, from the first report to closure.
Occurrence reporting is how an operator captures safety events, from small deviations to accidents, so each one is assessed and acted on. In eAviora every report moves through eleven stages, from triage and classification to risk, investigation, actions and closure, and each stage states what it still waits on.
- Overview
- Workflow
- Linked
- Discussion
- History
The module, on one sheet.
Four things, done on the record.
An occurrence, under investigation.
- Overview
- Workflow
- Linked
- Discussion
- History
- The linked investigation is complete, not yet
- Every challenged barrier is rated, 2 of 5 so far, not yet
No risk score without its reason.
- An occurrence cannot leave initial risk until someone writes why they chose that severity and probability.OccurrencesHolds
- Severity: Major, done
- Probability: Remote, done
- Why that severity and probability, in words, not yet
What it links to.
- From
- HAZ
- To
- OCC
- From
- INV
- To
- OCC
- From
- CAP
- To
- OCC
- From
- GOV
- To
- OCC
Short answers.
Yes. A reporter chooses identified, confidential or anonymous. For confidential and anonymous reports, contact details are stripped before the occurrence is written.
Yes. An occurrence exports as an E5X file, with its ECCAIRS codes mapped from the classification, and the export says when a mandatory attribute is still missing.
Yes. The eAviora app keeps the report on the device and sends it when the signal is back.
See Occurrences on your own records.
A walkthrough with the people who build eAviora.