Checklists, personnel, occurrences, SORA · AutrikOS

LUC readiness

Ready for a LUC: the evidence, from the flights

A Light UAS operator Certificate lets an organisation authorise its own specific-category operations. In return it has to show, at any time, that procedures are followed, people are current, aircraft are fit and every event is followed up. AutrikOS records most of that evidence as the flights happen. The certificate is still the authority’s decision, and the organisation behind it is yours.

Line illustration of checklists, a launch gate and sealed flight records
Checklist

What a LUC asks for, and where it comes from

The evidence an applicant or holder is asked for, and what AutrikOS keeps for it today.

Procedures that are provably followed

Signed checklists and briefings; a gate before arming that refuses a launch with open items

Personnel qualified for what they fly

Licences and ratings with expiry, recency per aircraft model, all from the pilot logbook

Aircraft and batteries fit to fly

Aircraft, battery and firmware state checked at the gate; maintenance kept per device

Occurrence reporting and follow-up

Serious events open an occurrence; the safety officer investigates and closes it

Complete, tamper-evident records

Each flight sealed with its logs in a hash chain; exports for audits

Risk assessment per operation

Operation wizard: Open, STS, PDRA, then SORA 2.5 with SAIL, OSOs and the volume on the map

Manuals and documents

Operations manuals, ORAs, emergency plans and training records stored next to the flights

Your organisation

Yours: the safety management system, the accountable manager, compliance monitoring and the LUC manual itself

Procedures

Nothing launches with an open item

About the launch gate→
  • Signed, not tickedChecklists and briefings are signed by the people who did them, with attendees.
  • A reason for every exceptionA soft finding needs a written reason; a hard one needs 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.
People and aircraft

Currency and fitness, from the logbook

About personnel and currency→
  • Recency per aircraft modelCounted from the flights, not typed in; licences and ratings show their days to expiry.
  • Aircraft and batteriesBattery packs on the checklist, the aircraft’s health and firmware checked before arming.
Collected once, reported many ways
ONE RECORDflightspilots + logbookschecklistsaircraft + batteriesoccurrencesdocumentsMAPPINGSBARS RPAScontrol by controlSORA 2.5iGRC · ARC · SAIL · OSOsvolume on the mapYOUR RULESORA · ERP · manualsREPORTSaudit pack (ZIP)annual client reportclient's read-only viewSORA application packOSO evidence packbeside the flights
The evidence is collected once. Each framework is a mapping on top of it with the report its audience expects: the BARS audit pack and client report, the SORA 2.5 assessment on the operation.
Records

Records an inspector can trust

AutrikOS runs in our EU cloud, in your own cloud or on your premises, for organisations whose records must stay under their control.
  • Sealed flight recordsEach flight is sealed with its logs in a hash chain; a later change shows as a change.
  • Occurrences with an ownerOpened automatically for serious events, investigated and closed by the safety officer.
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.

Applying for a LUC, or holding one?

Tell us your operations and where you are with the authority. We will walk through which evidence AutrikOS produces for you and what stays with your organisation.