Built for regulated drone operations

UK CAA-aligned workflows now. EASA support coming soon.

Compliance isn’t optional. It’s part of professional delivery

Meticulous record-keeping is integral

In the UK, compliance documentation is a formal requirement for Specific Category operations — not optional admin.

The UK Civil Aviation Authority (UK CAA) expects operators to develop and maintain an Operations Manual, maintain records, and keep an aircraft technical logbook as part of ongoing oversight.

These records must be kept up to date and retained for three years.

heliguy.io supports documentation workflows that help teams stay consistent, structured, and review-ready.

Compliance is proof

What you can’t show becomes exposure

When oversight or scrutiny occurs, compliance documentation is your first and strongest line of defence.

That includes maintaining clear records such as:

Flight date, time, and duration.

Remote pilot and aircraft details.

Inspections, maintenance, and defects.

Risk assessments and supporting documents.

It’s not about producing more paperwork. It’s about having the right proof, ready when needed.

Foster a culture of safety and professionalism

Scale your operations with accountability, operational excellence, and trust

Robust compliance reflects how professional operators demonstrate control, discipline, and safe delivery.

When documentation is consistent, current, and review-ready, it supports:

A stronger safety culture.

Clearer accountability across the team.

Higher operational professionalism.

Greater client confidence and trust.

Compliance isn’t separate from operations — it’s part of how mature teams deliver.

What the UK CAA says on compliance

Why it matters: UK Regulation (EU) 2019/947

Up-to-date record of information - Flight data
“This would assist with demonstration of regulatory compliance during the CAA audit process, to demonstrate that UAS Operations have been conducted within the conditions and limits of the Operational Authorisation….”
— GM1 UAS.SPEC.050(1)(g)(iii) Responsibilities of the UAS Operator
Remote Pilot Competence - Currency
“RPs are expected to maintain a logbook of flying activity, which may be used to demonstrate currency. This should be stored electronically, in order that it can be easily submitted to the CAA for oversight purposes ”
— AMC1 UAS.SPEC.050(1)(d)(i), (ii) and (iii) Responsibilities of the UAS Operator
Access
“For the purpose of demonstrating compliance…a UAS operator shall grant to any person authorised by the CAA access to any facility, UAS, document, records, data, procedures or to any other material relevant to its activity, which is subject to operational authorisation… ”
— GM1 UAS.SPEC.060(3)(e) Responsibilities of the Remote Pilot

Oversight and enforcement

Be ready to provide evidence quickly and clearly

The UK CAA can conduct targeted oversight during the validity period of an Operational Authorisation.

Operators may be required to demonstrate that records are being maintained and that operations remain within approved conditions and limits.

In practice, this means documentation needs to be easy to retrieve, consistent, and defensible — without chasing files across folders, spreadsheets, or message threads.

Failure to provide evidence — including flight logs — can result in suspension of your Operational Authorisation.

UK SORA

Evidence matters as risk increases

For teams operating under UK SORA-based approvals, documentation becomes even more important.

Higher-risk operations require clear evidence that controls are in place, processes are followed, and records exist to support assurance and accountability.

A robust portfolio of documented flight logs can be crucial for UK SORA applications, providing proof of operational safety and competence for more advanced missions.

heliguy.io supports workflows that help teams build that evidence through consistent documentation and structured operational capture.

EU regulation (EASA) — Phase 2

EASA-aligned workflows are planned for Phase 2 of heliguy.io