A drone service that works at one site may be costly to expand if every location requires an entirely separate operating case. Yet two facilities that look similar can differ in the risks that matter. Scaling needs a defensible way to distinguish a repeatable operation from a materially different one.
The UK Civil Aviation Authority's fourth edition of CAP3040 adds Annex G on equivalent operations across multiple sites. The publication page is dated September 29; the document's revision history gives September 28. The guidance concerns beyond-visual-line-of-sight operations in an atypical air environment and remains a policy concept supporting authorization. Primary source.
Equivalence is the central question
Annex G describes a potential route for an organization with an existing authorization to add equivalent sites within defined parameters. The operation must remain consistent with the underlying safety case. The document calls for early engagement with the CAA and does not remove authorization conditions or other applicable requirements.
For an operator, the analytical work is deciding which site characteristics could invalidate an assumption. A repeatable template is useful only if it can detect the exceptions. Treating every new facility as equivalent by default would defeat the purpose of defining a boundary.
A scalable process needs change control
An organization considering expansion could create a traceable record of why each proposed site fits its operating envelope. That record should make differences and unresolved questions visible to the responsible team, rather than turn a checklist into a substitute for judgment.
The same logic applies after a site has entered service. Changes to infrastructure or operating conditions can make an earlier comparison less reliable. A scalable process needs a way to notice those changes and reconsider the assumptions that supported the operation.
Make equivalence auditable
The practical value of a multi-site approach depends on how an organization records its reasoning. A site checklist can be useful, but a checked box should point to evidence rather than conceal an assumption. An operator could maintain a structured comparison showing the relevant characteristics of each location and the basis for treating them as equivalent. That would make the process easier to review and easier to update when a change affects an earlier conclusion.
Responsibility for that comparison should also be explicit. Expanding a commercial service may involve different teams handling operations, facilities and customer relationships. Each can hold information relevant to the site's conditions. A consistent process would specify how those inputs reach the person responsible for the operating case. Otherwise, a technically sound template could still fail because the organization did not notice that a new location differed in a way the template was meant to detect.
Do not confuse a category with an empty sky
The policy's focus on a particular environment does not mean that all other activity can be ignored. The central editorial implication is that reduced exposure and absence of exposure are different propositions. A site assessment needs to preserve the assumptions that support the proposed operation and identify what would make them unreliable. That is a general interpretation of why an operating envelope matters, not a replacement for the regulator's detailed guidance or an assessment of any reader's proposed flight.
Scaling also creates a documentation challenge after authorization. A local team may alter a facility while the central operations team continues to rely on an older record. Organizations can design change reporting around the assumptions that matter to the operation, rather than collect every possible site detail indiscriminately. The purpose is to ensure that a relevant change prompts review before a previous equivalence conclusion is treated as permanently valid.
For buyers of drone services, a useful question is what the provider means by being ready to expand. Equipment availability, a repeatable operating process and applicable authorization are separate dependencies. A credible proposal should identify which have been established and which remain subject to review. That would allow commercial planning to proceed with clearer milestones, while avoiding the mistaken impression that a published policy concept automatically permits the same service at any facility that looks superficially similar.
The potential benefit is more consistent expansion without losing the reasoning behind the safety case. The evidence to watch is how operators and the regulator apply the pathway in practice, including which differences require further review. The policy concept itself is not a grant of permission to fly.
Source organization: UK Civil Aviation Authority. Source statements are attributed; operational implications and suggested evaluation criteria are editorial analysis.
Questions, news tips or corrections? Contact [email protected].
