Built to answer the questions your risk team will ask.
Autonomy only works in public service if people stay in charge and every action can be accounted for. These are the commitments ORCA is built around.
Six commitments.
A person confirms before anything happens to a find.
Likely finds come to your team with an image, a location and the reason. Nothing is acted on until someone confirms it, and dismissals are logged with their reason.
Drones can’t leave the area you set.
A hard boundary and height limit sit above every task, checked separately from the software that plans the work. Whatever the job, the fleet is designed never to cross it.
Every aircraft keeps its own failsafes.
Each drone can land or return home without ORCA, if its battery runs low, a part fails or it loses contact.
A person can stop the whole fleet at any time.
A qualified pilot is always in command. The operator can pause, recall or take control of any drone, or every drone at once.
Aviation rules are checked before launch.
Each mission is checked against the limits you load, such as range, height, no-fly areas and hours. If it breaks one, it doesn’t launch, and ORCA says why.
Every command is recorded.
Every instruction, override and safety event is logged and can be replayed, for your own review, an audit or an incident report.
The safety design doesn’t depend on ORCA.
Three layers sit under every task, and each one works on its own.
- 01 · Aircraft
Failsafes on every drone
Low battery, lost contact or a fault: the drone lands or comes home on its own.
- 02 · Boundary
A hard geofence above every task
Checked separately from planning. A command that would cross it is blocked before it reaches the drone.
- 03 · People
A pilot in command, a stop for everything
A qualified pilot can stop or take over any drone, or the whole fleet, at any time.
Within the rules, wherever it flies.
Drone operations are regulated, and what a fleet can do depends on how and where it flies: by day or at night, within sight or beyond it, over open country or near people.
For a trial, Komneon carries the regulatory path: the safety case, the evidence and the approvals. Where an operation needs a certified operator, that work runs with one while the safety case is built.
| Type of operation | Requirement |
|---|---|
| Daylight, within line of sight | Standard rules, with their conditions met |
| Night | Additional approval from the regulator |
| Beyond line of sight | Additional approval from the regulator |
| Over people or private land | Consent or approval, depending on the rules |
General information, not legal advice. Each operation is planned against the current rules where it flies.
Your data stays yours.
Imagery of land, homes and culturally significant sites is sensitive. How it is handled is agreed with you before any work starts.
You own your imagery and records
Outright. Export everything at any time, in standard formats.
Agreed before work starts
Data handling, including private land and cultural interests, is agreed with you first.
Every access on the record
Who saw what, and what left the system, is logged like everything else.
- 05:12:00ORCAMission checked: boundary, height, hours. Cleared to launch.
- 05:16:48ORCAD-02 at 20%. D-04 launched to take its place.
- 05:28:10RangerConfirmed find: possible stoat, north shore. D-05 holding watch.
- 05:28:12ORCAIncident opened. Images and location sent to the ranger team.
- 05:41:30PilotPaused D-05 for 30 s while a boat passed under.
Bring your risk team.
We’ll walk your risk, legal and operations people through the safety case, the rules and the record, using your own scenario.