Docked drones and drone security patrols in the UK: what the rules allow and what a site needs

A docked drone, often sold as drone-in-a-box, is a drone paired with a ground station that shelters it, charges it and launches it. Flights are planned in advance and repeated: a patrol route after dark, a weekly thermal pass over a substation, a look at a perimeter fence when an alarm triggers. The drone returns to the dock to land and charge. It is an outdoor tool for large open sites such as compounds, solar farms, tank farms, rail and utility assets and industrial estates. It is not built for indoor or confined spaces.

The drone in a dock is normally a compact integrated unit carrying a combined visual and thermal camera sized to the dock. Heavier specialist payloads, such as contact thickness probes or cooled gas-imaging cameras, usually need a larger system or a crewed flight.

No. The CAA's guidance on unmanned aircraft operations, CAP 722, states that "all UAS must be under the command of a remote pilot". It also says there are currently no unmanned aircraft systems that meet its definition of autonomous. A docked system that launches on a schedule is automated: it follows pre-programmed instructions while a remote pilot remains responsible and able to intervene. That pilot can be in a remote operations centre rather than on site, and CAP 722 allows one pilot to supervise more than one aircraft where the human factors are shown to be addressed.

So "no pilot on site" is achievable; "no pilot" is not. Budget and plan for the remote pilot, their training and their shift pattern as part of the system.

It depends on how and where it flies. The Open category covers simple flights within the pilot's direct sight, below 120 metres and away from people and built-up areas; the CAA's Drone Code says flying closer to residential, commercial, industrial or recreational areas than its distances allow needs CAA authorisation. Most useful docked operations fall outside the Open category.

The Specific category needs an operational authorisation from the CAA before any flight. There are two routes. PDRA01, the only pre-defined risk assessment currently available, covers flights within the pilot's visual line of sight and within 500 metres of them, which does not suit a dock whose drone flies out of sight. Anything outside PDRA01, including flights beyond visual line of sight, goes through the UK SORA risk assessment. The CAA is explicit: "You must never carry out BVLOS flying unless you have an Operational Authorisation from the CAA that authorises you to carry out BVLOS operations."

Two developments help inspection and security use near structures. The CAA's atypical air environment policy recognises that close to ground infrastructure there are fewer conventionally piloted aircraft, and gives a route for beyond-sight flights there, still under an authorisation. And the CAA's BVLOS roadmap states its goal of routine BVLOS operations in the UK by 2027. Until then, treat the authorisation as a project workstream with its own timeline, specific to the operation it describes.

There is a UK precedent. Network Rail said on 3 June 2026 that it had secured CAA approval to operate drones beyond the operator's line of sight at Gloucester and Romford, using automated drone-in-a-box systems flown by pilots at a remote operations centre, for infrastructure monitoring, incident response and security. That is Network Rail's own statement about its own operation, not a template any site can assume.

The 2026 changes to the general rules apply too. Since 1 January 2026 a Flyer ID is needed for any drone of 100 g or more, new drones placed on the market must carry a UK class mark, and Remote ID applies now to drones in the UK1, UK2 and UK3 classes and, from 1 January 2028, to other camera-carrying drones of 100 g or more. Third-party insurance is compulsory for flying that is not purely recreational.

Data protection

A drone that films people processes personal data under UK GDPR. The ICO's guidance on drones says a data protection impact assessment should consider the risks of recording at altitude, that "unless you have a strong justification for doing so, and it is necessary and proportionate, recording should not be continuous", and that drones have the potential for "collateral intrusion" by recording other people unnecessarily. Privacy information still has to be given, which is harder from the air. Plan when the camera records, what it keeps, for how long, and who can see it, before the first patrol.

The Surveillance Camera Code

The Surveillance Camera Code of Practice binds only relevant authorities in England and Wales, such as local authorities and police. Other operators do not have to have regard to it, but the Code describes following it as best practice. The Protection of Freedoms Act 2012 defines surveillance camera systems broadly, including "any other systems for recording or viewing visual images for surveillance purposes", although the Code itself does not name drones.

SIA licensing

The SIA says you still need a licence even if the CCTV footage you are viewing comes from a camera on a drone. A person working under a contract for services who watches drone footage to guard premises or people needs a public space surveillance (CCTV) licence. Someone who watches the footage only in order to pilot the drone does not. Decide who watches what before choosing the staffing model.

Most docked systems report into their maker's own software. A security team watches a video management system or incident log; a maintenance team works from an asset or maintenance system. If a drone's alerts sit in a separate app, someone has to notice them and re-key them, and that is where drone programmes stall.

Forge Anvil, the integration software we are developing, is built to talk to as many robots as possible, drones included, and pass what they find into the systems you already run. For a docked drone that means an alarm or schedule trigger in, and a located event, clip or reading out, landing in the system the right team already watches: the control room for a security event, the maintenance system for an inspection finding. What the drone system exports and what your systems accept decide exactly which connections a site gets, which we confirm in the integration review. The four ways integration can be done are compared in integrating a robot with the software you already run.

Separate the questions. A first phase flown within sight, with a pilot on site, tests whether the drone sees what you need in your weather and light, without waiting for a beyond-sight authorisation. The authorisation work runs alongside it. Only then does a docked, remotely piloted phase test the operation you actually want. Agree the measures before the first flight:

Write the exit criteria down too. That is how we structure a pilot programme. For security patrols we work with our security partner, Macaw Security Solutions, which already uses drones in its security work. For patrols on the ground rather than in the air, see robot security patrols; the four drone categories are compared on our industrial drones page.