Log safety occurrences across fully configurable event types — each with its own reporting form — then conduct structured investigations and track findings through to closure, with automatic links to hazard log and corrective action workflows.
Every safety occurrence contains valuable information — but only if it's captured, investigated, and acted upon. AvioData's Event Report module provides a structured framework for doing exactly that, from the moment an occurrence is submitted to the point where all findings are closed.
Event types are fully configurable — your organisation defines which types of occurrences are reportable and designs a dedicated reporting form for each one. This means the form a crew member sees for a bird strike is different from the form for a ground damage event or a security occurrence, capturing exactly the fields that matter for that type without unnecessary clutter. Each form routes the submission to the appropriate investigator automatically.
Once an event is submitted, the investigation workflow guides the investigator through root cause analysis, contributing factor identification, and finding documentation. Each finding can be linked directly to a hazard log entry or used to raise a corrective action — closing the loop between occurrence and preventive action.
For operators subject to SAFA (Safety Assessment of Foreign Aircraft) ramp inspections, the module generates structured SAFA reports including SAFA 2 and SAFA 3 format outputs with corrective action due dates — providing the documentation format EU authorities expect when findings are raised during a ramp check.
Event reports can be filed directly from the AvioData EFB app on iPad and iPhone — even without a network connection. Photos taken at the scene and supporting file attachments can be added to the report in the app. Everything is queued locally and submitted automatically the moment connectivity is restored, ensuring no occurrence goes unreported due to poor signal at a remote stand or airfield.