We continuously improve AvioData based on operator feedback and evolving regulatory requirements. Here's what's new.
AvioData now integrates with GitHub via Claude Code, enabling AI-assisted code reviews and development tasks directly from pull requests and issues. This is an internal tooling improvement that accelerates the pace of feature development and quality improvements for the platform.
This release brings AvioData up to the latest versions of both its backend and frontend frameworks. The upgrade delivers meaningful improvements to performance, security, and long-term supportability:
The Risk report now includes a dedicated definitions chapter. This provides readers — including auditors and oversight bodies — with a clear reference for the terms and criteria used in the risk assessment, improving the document's usefulness as a standalone report.
Initial support for AI integration has been introduced, laying the foundation for AI-assisted features within the platform. This is the first step toward intelligent assistance in areas such as report drafting, data analysis, and workflow guidance.
A new Management of Change module has been introduced (AD-17). This module allows organisations to formally track and manage changes to processes, procedures, equipment, and organisational structures — a key requirement in modern aviation safety management systems. Features include:
A new editor has been added for managing global type definitions used in impact analysis. Parent/child relationships between types can now be configured directly in the interface, giving administrators more control over the risk and impact taxonomy used across modules.
Tasks can now be created and linked directly to hazard records. This closes the loop between hazard identification and the corrective or preventive actions needed to manage them.
The legal compliance print output has been refined: the CCL print now excludes GM (Guidance Material) entries, and only manuals that are explicitly referenced are included. This produces cleaner, more focused compliance documentation.
The Aviation Safety Report (ASR) module received a series of improvements across this period:
The interface for approving action extensions has been improved. Approvers now have a cleaner view of pending extension requests, making the process faster and less error-prone.
The platform's file storage backend has been migrated from Azure to Scaleway S3. This is an infrastructure change with no impact on how users upload, view, or download documents — files remain fully accessible as before.
AvioData now supports passkey authentication. Users can register a passkey on their device — using Face ID, Touch ID, Windows Hello, or a hardware security key — and use it to log in without a password. This provides a significantly more secure and convenient login experience, especially on mobile and tablet devices.
Passkey registration and management is available from the account settings. Existing username/password login continues to work alongside passkeys.
Several improvements have been made to the Legal compliance module, improving how regulations and associated manuals are presented and printed.
A bug has been fixed where selecting the 1st of January for an audit schedule date did not behave correctly.
When requesting an extension on an action, users are now required to provide a new proposed due date. This makes extension requests more structured and gives managers better information when deciding whether to approve. Extension approval notification emails have also been fixed to ensure the right people are informed.
SAFA 2 and SAFA 3 reports now include the due date for linked corrective actions. This makes SAFA reporting more complete and reduces the need for manual cross-referencing.
A new company-level setting has been added to enable or disable the automatic mailing of open (overdue) actions. Organisations that prefer to manage this communication manually can now turn off the automated reminder.
The audit report has been updated with improved structure and content, addressing several formatting and completeness issues raised during field use.
Documents in the Library module can now be flagged as visible on EFB (Electronic Flight Bag). This makes it straightforward to identify and manage which documents are published to flight crew devices, without changing how the documents are stored or managed in the back office.
An edge case has been fixed where actions due on today's date were incorrectly flagged as overdue. Actions are now correctly treated as on time when the due date equals the current date.
The reference number field in safety reports has been extended from its previous limit to 120 characters, accommodating organisations with longer reference numbering schemes.
A fix has been applied to the audit checklist that prevented certain items from saving correctly. A new weekly mailing has also been introduced to keep compliance managers informed of outstanding audit items on a regular schedule.
Risk mitigations are now sorted alphabetically by title in the risk record view, making it easier to scan and compare mitigation measures in risk assessments with multiple entries.
Several fixes have been applied to improve the login and registration experience on iOS and iPadOS devices, including better handling of device registration and QR code flows.
A new Escalation list has been added to the Actions module. This provides an overview of actions that have escalated — either due to missed deadlines, repeated extensions, or other escalation triggers — giving compliance managers a single place to monitor at-risk items.
The Escalation list is also reflected in the Evaluation report, so it is included in formal audit and compliance documentation.
A bug has been fixed where actions that were overdue could incorrectly block other workflow steps. The overdue state is now correctly handled without affecting downstream processes.
A missing regulatory reference — AMC1 ORO.GEN.110(a) — has been restored in the compliance regulation set.
The Audit Schedule module now lets you designate a compliance manager for each scheduled audit directly from the scheduling interface. This makes ownership and accountability clearer, especially in larger organisations where audit responsibilities are spread across teams.
Risk level descriptions have been updated for clarity and consistency throughout the application. If you work with risk assessments regularly, you will notice more precise wording that better reflects aviation safety conventions.
Login error handling has been improved. Users who encounter authentication issues will now receive more descriptive feedback, making it easier to diagnose and resolve access problems.
Closed actions in the Actions module can now be reopened. This is useful when new information comes to light after an action was marked complete, or when a corrective measure needs to be revisited. The reopening is tracked in the audit trail.
The Actions module received several improvements to its extension mechanism, which allows actions to be linked to other modules such as IP Administration. A bug in the extension approval workflow for IP administrators has been fixed, and the extension interface has been refined for better usability.
Email notifications sent from the system now include clearer function names in the message body, making it easier to understand the context and source of automated messages.
Application icons have been refreshed. Unnecessary debug logging that was visible in certain environments has been removed, resulting in a cleaner experience.
User sessions are now managed with improved reliability. Sessions persist for up to 4 hours of inactivity before requiring re-authentication, reducing disruption during longer working sessions. The iOS mobile login flow has also been improved with automatic login support.
PDF reports generated in the application — such as audit reports and ASR printouts — are now delivered as file attachments rather than opening inline in the browser. This makes it easier to save and share documents.
A file upload size limit was set to prevent oversized files from causing errors when attaching documents to records.
AvioData's user interface has been rebuilt on the latest version of front-end frameworks. The update brings a more consistent visual design, better responsiveness, and improved behaviour on mobile and tablet devices. Key improvements include:
This release also marks the removal of legacy UI components that had been carried forward from earlier versions of the platform, resulting in a faster and cleaner interface.
The Library module — used for managing documents, manuals, and regulated references — received significant stability improvements, including better handling of document uploads and more reliable test coverage to prevent regressions.
Files can now be uploaded and downloaded directly within the Actions module. This removes the need to manage supporting documents separately and keeps all relevant information in one place.
The Minutes module (used for Flight Operations and other meeting records) received fixes and expanded test coverage. Event recommendation handling was also corrected.
Initial automated test coverage has been added for the Hazard Log, improving confidence in the reliability of this safety-critical module.
Account Managers now have an improved interface for handling action extensions. The extension panel can be collapsed to reduce visual clutter when not in use.
A dedicated file download component has been introduced across modules, providing a consistent way to retrieve attached documents and reports.
The "Compliance" module has been renamed to Corrective Action Request (CAR), better reflecting its purpose in the safety management workflow. The underlying logic for creating and managing corrective actions has been improved alongside this rename.
The platform now tracks build versions automatically during the release process, making it easier to identify exactly which version is running in a given environment.
Users with access to multiple environments can now filter views by environment, making it easier to work in organisations that operate across separate operational contexts.
Single sign-on (SSO) authentication is now fully operational, enabling organisations to integrate AvioData login with their existing identity provider.
The application navigation has been redesigned. The new menu reads permissions dynamically from the security layer, meaning users only see the modules and sections they are authorised to access. The menu state is preserved across navigation, reducing unnecessary reloading.
Risk reporting has been significantly improved:
Emails received on iOS devices are now better formatted, with improved rendering and handling of file attachments.
Several fixes were made to the ASR (Aviation Safety Report) manual workflow:
The Notices module — used for communicating regulatory and operational notices to accounts — received extensive improvements:
The Audit Schedule now supports filtering by audit date, making it easier to find upcoming or past audits within a large schedule.
Several fixes were made to file attachment behaviour, including correct handling of file deletions and improved reliability when fetching file lists from records.
Meeting minutes can now be printed directly from the application using a structured print layout.
The Risk module received its most significant update to date. The underlying data model was modernised with new risk tables, and the user interface was brought in line with the rest of the application. Key additions include:
The new Actions module — introduced earlier in 2023 — is now used consistently throughout the application. Records from other modules that previously triggered separate workflows now route through Actions, giving a unified view of all outstanding corrective and preventive actions.
The Aviation Safety Report module received several rounds of fixes and refinements:
The Legal module received substantial improvements throughout this period:
The admin panel has been improved with a clearer permissions and roles interface. Administrators now have finer control over what each role can access, and the UI makes permission configuration more transparent.
ASR form development continued with additional fields, improved layout, and stability fixes. The ASR print output has been extended.
Graphical charting has been integrated into the application, enabling data visualisation in reports and dashboards.
The Actions module matured significantly with the introduction of a formal approval and escalation workflow:
The audit report has been updated with improved layout and content. Law paragraph deletion from reports is now supported.
The law compliance report has been improved, with better handling of linked paragraphs and decisions.
Session caching has been added to reduce load and improve login performance. Login flow is quicker and more reliable.
Audit closure reports have been redesigned and renewed. The new layout gives a clearer overview of audit findings, actions taken, and the final status at closure.
The compliance list mailing now includes the Audit Schedule, giving compliance managers a more complete picture of upcoming and outstanding compliance obligations in each automated update.
The Actions module continued to grow, with improved workflows, better form submission handling, and more stable background processing.
A file upload issue affecting several modules has been fixed, improving reliability when attaching documents to records.
A new Compliance module was introduced in this release. The module provides a structured framework for managing regulatory compliance, covering:
The Actions module was introduced — a central place to create, assign, and track corrective and preventive actions across all areas of the safety management system. Early features included:
Security method-level security was added to the backend, tightening access control at the service layer. File storage migration was completed. Several security hardening measures were applied.
The Legal module received a series of refinements at the start of 2023:
Audit schedule change type support was added, allowing schedules to be typed and categorised more precisely.
Improvements were made to support the iOS companion app, including better handling of app registration and data synchronisation.
Risk fields were added and the Risk service was improved with better data handling and service-layer improvements.
A dedicated Manuals module was introduced, providing a structured place to manage company manuals separately from the broader Library. Features include:
Notices can now require recipient confirmation. Once a notice is sent, recipients confirm receipt within the application. Features include:
A dedicated admin interface for accounts and crew has been introduced, including:
The Legal module continued to grow, with legal references, improved applicable field handling, keyboard shortcuts, and state saving for manual views.
"Practical Drift" has been added as a contributing factor option in safety reports, in line with modern human factors taxonomy.
The Notices module received significant work over this period:
Initial Real User Monitoring support has been integrated, providing operational insight into how the application is being used and where performance bottlenecks occur.
The file storage backend was migrated to a new provider, improving compatibility, reliability, and maintainability of the object storage layer.
Risk records can now be saved with new actions directly from the risk management module, closing the loop between identified risks and the actions taken to mitigate them.
The Legal module was introduced in this period, providing initial support for managing applicable regulations and linking them to operational documents. iOS synchronisation of legal data was also started.
The Notices module saw extensive refinement:
The web server was updated and security vulnerabilities were addressed across platform dependencies.
A full Audit Checklist module was introduced, providing structured checklists that can be created from templates and used during audits. Key features:
A Law Decision Analyser was introduced to help compliance teams analyse regulatory decisions and their impact on applicable procedures and manuals.
The Library module received a redesigned layout and restructuring. Improvements include:
Print output across modules was improved, with better table formatting, page break support, and retry mechanisms for print generation.
The print and PDF generation engine was upgraded to a modern renderer, providing better layout fidelity and more reliable print output across all modules.
Tasks are now automatically invalidated after 4 hours of inactivity, reducing stale task data and improving system responsiveness.