Safety and compliance approach
Support the system of control. Keep authority where it belongs.
AirKo helps an organisation apply its own controlled workflows, preserve evidence and make responsibility visible. It does not confer regulatory standing or guarantee compliance.
Operating principles
Safety starts with honest boundaries.
The platform is designed to make dependencies, exceptions and decisions easier to see without obscuring the legal and operational responsibility of the UASOC holder.
- 01
Authority
Decision support, not decision substitution
AirKo surfaces checks, blockers and evidence. It does not automate a regulatory decision or replace the authorised human responsible for flight release.
- 02
Meaning
No single compliance score
Regulatory records, Internal Safety Stage, Job Safety Stage, residual mission risk and UASOC authorization remain separate in data, interface and logic.
- 03
Traceability
Evidence the decision that was made
A release records the authorised user, role and authority, time, conditions, decision and exact flight-pack version considered.
- 04
Change control
Approval does not drift across versions
Material operational changes preserve the authorised version, invalidate its authorization and create a new proposed version for review.
Control framework
Designed for least privilege and reviewable evidence.
Security, privacy and auditability are treated as platform requirements. They still require organisation-specific configuration, testing and legal or regulatory review before production use.
- Scoped access
- Access follows explicit UASOC, Team and user scopes. Role checks and tenant boundaries are enforced on the server and in database policies.
- Private evidence
- Pilot, aircraft, flight-pack and safety evidence is held in private storage with record ownership, tenant scope and short-lived access controls.
- Data minimisation
- Operational status is separated from sensitive source documents so a user receives only the detail needed for their work.
- Audit history
- Important changes, reviews, assignments, stage assessments and decisions produce append-only events with actor, action, time and affected record.
- Privacy readiness
- POPIA readiness informs the design, but retention periods, notices, data-subject processes and operator/responsible-party roles require formal legal review before production.
- Accessible status
- Current, warning and blocked states use text and structure in addition to colour. Internal stages always display both stage number and label.
Authorization boundary
Human review remains the final gate.
Every release attaches authority and conditions to one exact version. A material change cannot silently carry the earlier decision forward.
AirKo does not claim to be SACAA-approved and does not replace the applicable Operations Manual, Operations Specifications, accountable personnel or regulatory obligations.
See AirKo in context
Test the control path, not just the interface.
Use a demonstration to examine AirKo’s role boundaries, version controls and evidence trail against your own documented procedures.
Request a demonstration