Compliance

Compliance that comes out of the flying

Audits are usually a binder built the week before. In AutrikOS, every flight records its own evidence: who flew, what was checked, what happened in the air. The audit pack is an export.

Isometric scene of a pilot with a signed checklist, the flight, and a sealed flight record
Before the flight

Nothing launches unchecked

Signed checklists and briefings

On every launch path: take-off, mission dispatch and arming. Signed by tap, attendees listed, a reason for every open item.

Pilot logbook and currency

Licences, ratings and recency per aircraft model, computed from the flights themselves, with expiry warnings.

Aircraft and batteries fit to fly

Battery register with cycle limits and cell checks, approved firmware, maintenance releases and a test flight after updates.

A gate before arming

The server checks it all before the aircraft arms. Soft findings need a reason, hard ones an admin who is not the pilot.

One gate before arming
BEFORE THE FLIGHTchecklist signedbriefed todaypilot current on modelbatteries fitreason givenfirmware approvedGATEon the serversoft: a reasonhard: admin, not the pilotSIGNEDapprovalTAKE-OFFMISSION DISPATCHARMaircraft armsno approval, no arming
Take-off, mission dispatch or arming: every launch path meets the same gate. A soft finding needs a reason, a hard one an admin who is not the pilot, and the aircraft arms only with the signed approval.
During and after

The record writes itself

In-flight monitors

Link loss, route deviation, reserve, range and health warnings are watched and kept with the flight.

Occurrences

Serious events open an occurrence automatically; the safety officer investigates and closes it, and the lesson reaches the fleet.

Sealed flight records

Each flight is sealed with its logs in a hash chain. A later change shows as a change.

One flight, recorded as it happens
TAKE-OFFLANDINGlink lossroute deviationMONITORS · reserve, range, health: watched all alongOCCURRENCE→ safety officerSEALED RECORDS#1041hash#1042hash#1043hasha later change shows as a change
Monitors mark what happened while it happened; a serious event opens an occurrence for the safety officer; after landing the flight is sealed with its logs into the chain.
Frameworks

One record, a mapping per framework

BARS today, SORA next

The evidence is collected once. Each framework is a mapping on top of it, with the report its audience expects.
  • BARS RPASControls mapped one by one to live evidence, an audit pack and the annual client report as exports, and a read-only view for your client.
  • SORA 2.5The operational volume (flight geography, contingency volume, ground risk buffer) computed from the plan and exported for eSORA or the authority. The full SORA, PDRA and STS path is next.
  • Your own rulesOperations manuals, ORAs, emergency plans, documents and training records live next to the flights they govern.
Collected once, reported many ways
ONE RECORDflightspilots + logbookschecklistsaircraft + batteriesoccurrencesdocumentsMAPPINGSBARS RPAScontrol by controlSORA 2.5operational volumefull path: nextYOUR RULESORA · ERP · manualsREPORTSaudit pack (ZIP)annual client reportclient's read-only vieweSORA volume exportSORA · PDRA · STS: nextbeside the flights
The evidence is collected once. Each framework is a mapping on top of it with the report its audience expects: BARS today, SORA's operational volume today and the full path next.
Where this stands today

BARS shipped, SORA in development

BARS RPAS is in the product end to end: the records, signed checklists on every launch path, the launch gate, in-flight monitors and occurrences, the per-framework report and the client share, and sealed flight records.

EU risk applications ship their short paths — Open category, STS and PDRA — in the operation wizard. The full SORA 2.5 assessment (the ten steps, SAIL, OSOs) is being built on the same operation record, and a framework of your own rules comes after it. Where this page says SORA, read it as the direction of the build.

Bring your last audit

Show us the findings, and we show you where each one lives in AutrikOS.

Talk to us→