White Paper

Beyond 2019

A New Counter Uncrewed Systems and Air Threat Resilience Strategy for the United Kingdom, After Ukraine and Iran

By Mr Richard Ryan, Barrister, Blakiston’s Chambers · June 2026

The United Kingdom’s published national counter drone policy; the UK Counter-Unmanned Aircraft Strategy, presented to Parliament as Command Paper 187 on 21 October 2019^[1]; is materially out of date as a strategic document. It remains the only published national strategy in the field for the whole of government, yet it is now approximately six years and seven months old, and roughly three and a half years beyond its own planning horizon.

The strategy was sound for its time. It identified the highest harm illegal uses of small drones; terrorism, smuggling into prisons, disruption of critical national infrastructure; and prescribed layered intervention, industry standards, responder powers and public education.^[2] But it was expressly confined to malicious and illegal use of small aerial drones, in a domestic policing and protective security frame. That frame has been overtaken by operational reality in Ukraine and the Iranian theatre: massed one way attack drones, combined drone and missile salvos, container and special forces launch, dense electronic warfare, fibre optic command links and AI assisted guidance now define the threat.

Subsequent UK documents do not update the 2019 strategy; they work around it. The Defence Drone Strategy (2024),^[3] the Strategic Defence Review 2025,^[4] NPSA’s site specific guidance,^[5] and the Ministry of Defence’s 2026 pursuit of new defeat powers at military sites^[6] together form a patchwork of sectoral adaptations laid over an unrevised core. This paper argues that the 2019 strategy should be retired as a standalone statement and replaced by an integrated Counter Uncrewed Systems and Air Threat Resilience Strategy, supported by a consolidated legal code for detection, disruption and defeat, and by an annual ministerial statement to Parliament.

1.  The threat has become a strategic mass system

The central lesson of 2024–2026 is not that drones have become more common but that they have become a strategic mass system — a consumable class of munition and sensor used for saturation, decoying, attrition of intelligence assets, target acquisition and the deliberate erosion of a defender’s cost exchange ratio. On the night of 2 June 2026, Ukraine’s air force reported that Russia had launched 656 drones and 73 missiles in a single overnight barrage, of which 602 drones and 40 missiles were downed or suppressed.^[7][8] Single salvos now routinely exceed several hundred drones.

Critical infrastructure has been directly affected. In February 2025 a Russian Geran-2 (Shahed type) drone struck the New Safe Confinement over Chornobyl’s reactor four;^[9] by December 2025 the International Atomic Energy Agency assessed that the structure had lost its primary safety functions, including confinement.^[10] In May 2026 a drone strike caused a fire at an electrical generator on the perimeter of the United Arab Emirates’ Barakah nuclear plant; a civilian reactor site; leaving one unit running on emergency diesel generators.^[11][12]

The homeland and deployed force dimension is now concrete for the United Kingdom. In early March 2026 a Shahed type drone struck a runway at RAF Akrotiri in Cyprus; a British Sovereign Base Area; causing limited damage,^[13] and the UK flew defensive sorties and, where requested, acted in the collective self defence of regional allies.^[14] Ukraine’s Operation Spider’s Web (June 2025) had already shown that 117 first person view drones launched from concealed truck borne containers could strike strategic bomber bases far from any front line, damaging more than 40 aircraft, with some guidance reportedly AI assisted.^[15]

A necessary qualification

Not every battlefield lesson maps to the British mainland. The most credible open analysis holds that long range Shahed type strikes on Great Britain would face high attrition because of geography and warning time, while shorter range drones launched from containers or by hostile special forces remain a credible risk to high value assets at home. The policy implication is to discriminate between vectors; not to import foreign assumptions wholesale, and not to dismiss the threat. A refreshed strategy should say so candidly.

2.  Why the 2019 strategy can no longer stand alone

The clearest institutional signal came in February 2026, when the Ministry of Defence reported 266 drone incidents near UK military sites during 2025 (up from 126 in 2024) and sought fresh statutory powers through the Armed Forces Bill; extending beyond aerial drones to land and maritime systems; to allow Defence personnel to defeat drones at their own sites without waiting for police intervention.^[6] When the armed forces must legislate around a framework built for policing to protect their own bases, that framework has expired.

3.  The legal framework: developed, but fragmented

Domestic powers have expanded since 2019 but remain complex. The Air Traffic Management and Unmanned Aircraft Act 2021 created bespoke constabulary powers to ground, stop, search, inspect and seize unmanned aircraft, and amended section 93 of the Police Act 1997 to facilitate authorisations for certain counter drone measures.^[17][18] In the civil regime, the Civil Aviation Authority’s Direct Remote ID requirements came into force on 1 January 2026 for UK1, UK2, UK3, UK5 and UK6 class drones, with extension to most drones carrying a camera from 1 January 2028.^[19]

Yet lawful defeat is markedly harder than detection. Operational use of a jammer is generally an offence under section 68 of the Wireless Telegraphy Act 2006, and Ofcom has no power to authorise operational use; only narrow trial and research licences in shielded conditions.^[20] Government is separately examining the enforcement framework around jammers.^[21] Kinetic or electronic interference may amount to unlawful property or wireless interference absent proper authorisation; the Act’s own explanatory notes acknowledge as much. Techniques that take over a drone by software may engage the Computer Misuse Act 1990 and the Investigatory Powers Act 2016, and sensing engages the Data Protection Act 2018, the UK GDPR and the Human Rights Act 1998, which requires the state both to protect life from foreseeable threats and to keep its sensing and defeat measures necessary and proportionate. A lawful defeat chain is a designed legal artefact, not an improvisation.

Overseas action sits within international law. The Government’s March 2026 legal position on Iranian regional attacks invoked the collective self defence of allies under Article 51 of the UN Charter, subject to necessity and proportionality and Security Council notification.^[14] Once in armed conflict, drones attract no special category: they are governed by the ordinary rules of distinction, proportionality and precaution applicable to all weapons.^[22]

4.  Recommendations

The Government should replace the 2019 strategy with a new instrument covering the whole of government. Five propositions should anchor it:

1. Integrate, do not append. A single Counter Uncrewed Systems and Air Threat Resilience Strategy spanning the Home Office, MoD, Cabinet Office resilience, CAA, Ofcom, NPSA, the intelligence community, prisons and CNI operators, aligned to NATO’s integrated air and missile defence framework.^[16]
2. Consolidate the law. A statutory code (or, at minimum, statutory guidance) defining who may detect, disrupt and defeat uncrewed systems, where, against which threat category, under what authorisation, with what recording and what review after an incident — differentiating urban areas, prisons, airports, defence sites and overseas operations.
3. Adopt a layered baseline that is alert to cost. Use NPSA’s site specific, threat informed model as the national spine,^[23] plugging into a wider air and missile defence architecture for higher end threats, and prioritising defeat options that are low in collateral, deep in magazine and economically rational. A missile fired at every cheap drone is not a strategy; it is a budgetary confession.
4. Treat industry and export control as readiness. Link procurement, export licensing, sanctions intelligence and sovereign industrial strategy, with secure by design and open architecture requirements across C-UAS procurement. A state that cannot source the components of its own counter drone systems is not strategically autonomous.
5. Compliance and oversight by design. Require a written legal basis, data minimisation, retention limits and human oversight for every C-UAS deployment by a public authority; subject identification by AI to documented necessity and a review of error rates; and provide Parliament an annual ministerial statement on C-UAS powers, deployments, tests, safety incidents, rights compliance and lessons learned, with NPSA and the ICO involved where domestic surveillance is concerned.

5.  Conclusion

None of this discards the 2019 strategy’s best inheritance; its insistence on layered intervention over an optimism founded on gadgets, an instinct NPSA’s later guidance has only reinforced.^[5] The task is not to repudiate 2019 but to lift its sound protective security spine into an architecture wide enough for the threat that now exists: a spectrum of low cost, autonomous and electronically contested uncrewed systems, ranging from nuisance to war. The 2019 strategy answered the question of its decade. It is time to ask the question of this one.

The post appeared first on Blakistons.

The newsletters keep landing in my inbox with their countdowns. The latest one fixes on 2 August; the date the AI Office acquires real teeth over general-purpose AI models. I read these updates the way a coastal town reads tide tables: not because every wave matters to me, but because I need to know which ones will reach the door. So let me work through what this particular tide actually touches, from the perspective of someone who spends their days arguing about machines that fly.

The autonomy problem nobody wants to define

Start with the thing that makes drones legally interesting in the first place: autonomy is a spectrum, and the law hates spectrums.

A consumer quadcopter holding position in a breeze is running control loops that would have been called “artificial intelligence” in a 1980s research paper. A military loitering munition selecting between candidate targets is doing something most people would unhesitatingly call AI, and find alarming. Between those two poles sits an enormous, messy middle; obstacle avoidance, automated return-to-home, “follow me” tracking, swarm coordination, automated target recognition that merely flags rather than decides. Where on that spectrum does a drone become an “AI system” in the meaning of Article 3?

This matters enormously and almost nobody asks it cleanly. The Act’s definition turns on a system that infers, from inputs, how to generate outputs that influence environments. Plenty of drone autonomy stacks meet that bar comfortably. Plenty of others; deterministic flight controllers executing fixed logic; arguably don’t. I have sat across the table from engineers who insist their navigation system is “just maths,” and they’re not entirely wrong, but “just maths” is also a fair description of every neural network ever trained. The line is not where intuition puts it.

Why the military carve-out is a trap, not a shield

Here is where I watch clients relax too early.

The AI Act contains an exclusion for systems used exclusively for military, defence or national security purposes. Counter-drone work, in particular, loves to shelter under this. The reasoning goes: we detect and defeat hostile UAS, this is inherently a security function, therefore the Act doesn’t reach us. Lovely. Except “exclusively” is doing ruthless work in that sentence, and the dual-use reality of this entire sector makes the exclusion far narrower than people want it to be.

The same RF-detection and optical-tracking stack that protects an airbase gets sold, with a different sticker, to protect a stadium, a prison, a private estate. The moment that system has a civilian commercial life; the moment it is placed on the EU market for protecting critical infrastructure rather than fighting a war; the exclusion frays. And critical infrastructure protection is precisely the kind of use the high-risk classification regime is built to capture. A counter-UAS platform that automatically classifies an incursion and cues a response near an airport is not obviously outside the high-risk net just because its cousin wears camouflage.

The targeted consultation on the high-risk classification guidelines, open until late June, is therefore not abstract bureaucracy to me. Those guidelines are where the boundary between “this is a security tool, leave it alone” and “this is a high-risk system, document everything” will actually get drawn through worked examples. Anyone in this sector who isn’t reading those drafts is choosing to be surprised later.

Article 50 and the drone you can’t see

Now the part that genuinely changes behaviour on the ground.

Article 50’s transparency obligations don’t care about risk tiers. They bite on situations; and one of those situations is biometric categorisation, another is emotion recognition, and another is content that interacts with or affects people. Picture the increasingly common deployment: a drone with a camera doing crowd monitoring, perimeter patrol, or event security. The instant that payload starts categorising people by biometric attributes, the deployer owes the exposed individuals notice. You cannot quietly run biometric categorisation from 120 metres up and treat the altitude as a privacy shield. The obligation attaches to what the system does, not to how far away the lens sits.

I find this is the provision that catches operators off guard, because it cuts against the entire instinct of aerial surveillance, which is to be unobtrusive. The law is, in effect, telling a category of drone operator that unobtrusiveness is now sometimes unlawful. That is a genuinely interesting collision between the technology’s reason for existing and the regulation’s reason for existing, and it is going to generate litigation.

The sandbox that slipped a year

There was a small piece of news in the recent updates that I suspect most readers skimmed: the establishment deadline for regulatory sandboxes has been pushed from August 2026 to August 2027.

For most industries that’s a footnote. For drones it’s meaningful, because the sandbox model is arguably better suited to unmanned aviation than to almost any other AI domain. We already have a mature culture of supervised, geographically-bounded testing; segregated airspace, specific operational risk assessments, temporary danger areas. A regulatory sandbox is conceptually just that culture extended from airworthiness into algorithmic compliance. The delay means the one mechanism that could let a counter-UAS startup test automated-response logic on real incursions, under supervision, with some shelter from fines, won’t materialise on the original timetable. The companies most in need of a structured way to prove their systems are safe will spend another year improvising compliance instead. Whether that protects the public or merely protects incumbents is the kind of question I find genuinely unresolved.

What I’m telling clients

The honest summary I give, stripped of comfort, runs roughly like this. The August date isn’t your date; it’s aimed at the makers of large general-purpose models, and most drone autonomy doesn’t live there. But the regime those powers belong to is the same regime whose high-risk rules and Article 50 duties absolutely will reach you, and the classification guidelines being drafted right now are where your fate gets decided. Don’t wait for enforcement to tell you which side of the line you’re on. The structured dialogue the AI Office favours means the first contact is likely to be a request for documentation, not a fine; which means the clients who survive comfortably are simply the ones who wrote the documentation before anyone asked.

Drones made autonomy visible; something you can point at in the sky. That visibility is exactly why this sector will be among the first places the AI Act’s abstractions get tested against physical reality. I’d rather my clients be the test case that wins than the cautionary one. The tide tables are right there in my inbox. The only real choice is whether to read them.

This is not legal advice; if you’re making compliance decisions about a specific system, get advice tailored to it.

About the author
Richard Ryan is a Direct Access Barrister at Blakiston’s Chambers, and a chartered arbitrator and accredited mediator, specialising in drone and counter-drone law. He advises operators, manufacturers, UTM providers, insurers and public bodies across the full UAS spectrum — regulatory permissions and BVLOS approvals, C-UAS deployment at airports, prisons and critical infrastructure, data and privacy, liability and high-value disputes. Instruct him directly or through solicitors.

The post The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft appeared first on Blakistons.

By Richard Ryan, barrister and drone lawyer

Constructive outcome, practical lessons. A technical proximity breach was confirmed, a more serious allegation was dismissed, and there are clear takeaways that raise standards on evidence, cooperation and public safety.

This post is for general information only and is not legal advice.

The post A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots appeared first on Blakistons.

“`

The post Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities appeared first on Blakistons.

The post What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5 appeared first on Blakistons.

The post Trespass by Drones: Is Section 76 Civil Aviation Act 1982 Fit for Purpose? appeared first on Blakistons.

Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations

By Richard Ryan, Drone Lawyer

As a UK drone lawyer, I’ve seen firsthand how tricky it can be to navigate the ever-changing skies of unmanned aviation regulation. The Civil Aviation Authority’s (CAA) “Unmanned Aircraft Operations in an Atypical Air Environment (AAE): Policy Concept” (CAP 3040) is no exception. After the initial excitement of the First Edition, many in the drone community were eagerly awaiting the Second Edition, hoping for clarifications, improvements, and a more future-focused framework.

What’s New?
At a glance, the changes between the First and Second Editions might seem minimal—just a tweak to the reference for ADS-B (Automatic Dependent Surveillance-Broadcast) equipment, rolling back from RTCA DO-282C to the older DO-282B standard. But that’s not a small footnote. If you’ve been prepping your drone gear to meet DO-282C standards, you may now be left wondering why the rug’s been pulled from under you.

The Tech Twist:
DO-282B is an earlier standard for ADS-B performance, while DO-282C was supposed to reflect newer technology and real-world lessons learned. Reverting to an older standard could mean extra work or unexpected costs if you’ve already made purchases or adapted your systems for DO-282C. It also raises questions about whether the policy is truly forward-looking, or inadvertently stifling progress at a critical time in UK drone innovation.

Still Flying Through Foggy Regulations:
The Second Edition still leaves operators wrestling with a few nagging uncertainties:
1. Defining ‘Atypical Air Environment’: The document still lacks a crystal-clear definition of AAE. Without a firm legal baseline, you might struggle to know if your flight qualifies—adding confusion to your operations and potentially slowing down approvals.
2. Single Site Limitations: The CAA’s recommended approach of applying for just one site per Operational Authorisation (OA) remains. This can create unnecessary hurdles for those looking to scale up and serve multiple clients or routes.
3. Extra Admin, Less Innovation: Requirements like routine NOTAM submissions or intricate Electronic Conspicuity (EC) licensing haven’t been simplified. For many operators, these processes feel more bureaucratic than beneficial, potentially discouraging new entrants and curbing the industry’s growth.

How to Navigate This Airspace Turbulence:
• Stay Agile: Keep tabs on CAA communications and industry forums. If the CAA shifts requirements again, you’ll want to pivot quickly.
• Ask for Clarity: Don’t hesitate to reach out to uavenquiries@caa.co.uk for guidance, especially if you’ve already invested in tech aligned with DO-282C.
• Industry Collaboration: Connect with fellow operators, manufacturers, and drone associations. Shared experiences help identify practical solutions and give your concerns more weight when approaching regulators.
• Professional Advice: A drone-focused legal expert can help you interpret the Second Edition’s nuances, reduce compliance guesswork, and ensure you’re not sinking costs into the wrong standards.

Charting a Better Flight Path: While the Second Edition’s updates may feel like a step back, there’s still hope. The CAA emphasizes that CAP 3040 is an evolving concept. By voicing concerns, sharing data, and staying engaged, the drone community can help steer policy revisions that balance safety, innovation, and economic growth.

The Bottom Line:
The CAP 3040 Second Edition is a reminder that regulatory frameworks are works in progress. This can be frustrating, yes—but it’s also an opportunity. Operators willing to adapt, learn, and advocate for sensible changes can help shape the UK’s drone landscape into one that truly welcomes innovation. Keep your engines running, your channels of communication open, and your ambitions high. Together, we can ensure that tomorrow’s regulations are as cutting-edge and future friendly as the drone technology they’re meant to guide.

About the Author
Richard Ryan is a direct access barrister at Blakiston’s Chambers, specialising in drone law and unmanned aircraft regulation. Leveraging extensive knowledge of emerging aviation technologies and the UK’s complex regulatory landscape, Richard Ryan provides pragmatic guidance that empowers clients to navigate compliance challenges, secure operational approvals, and seize opportunities in the rapidly evolving drone sector. Known for translating intricate legal frameworks into actionable strategies, Richard Ryan is dedicated to shaping the policies that will define the future of unmanned aviation in the UK.

The post Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations appeared first on Blakistons.

Analysis and Recommendations on CAP 3040 | First Edition

1. Executive Summary

The CAA’s policy concept aims to enable Beyond Visual Line of Sight (BVLOS) operations for Unmanned Aircraft Systems (UAS) within an Atypical Air Environment (AAE). While the initiative is commendable for promoting innovation, the policy, as currently drafted, presents several challenges:
– Ambiguity in Definitions: The lack of precise definitions for key terms like AAE may lead to inconsistent application and legal uncertainty.
– Operational Burdens: Requirements such as pre-flight notifications, electronic conspicuity, and high-intensity lighting may impose significant burdens on operators, especially small and medium enterprises (SMEs).
– Potential Stifling of Innovation: The cumulative effect of stringent requirements may deter new entrants and hinder technological advancement.
– Legal Efficacy: For the policy to have legal effect, certain elements need to be codified into law or regulations.

2. Issues for Drone Operators

a. Ambiguity in Definition of Atypical Air Environment (AAE)
– Lack of Clarity: The document does not provide a clear, legal definition of an AAE, leading to potential inconsistencies in interpretation.
– Examples vs. Definitions: Providing examples (e.g., within 100ft of a building) without a firm definition creates uncertainty for operators attempting to comply.

b. Operational Requirements
– Pre-Tactical Flight Route Notification:
– Administrative Burden: Requiring Notices to Airmen (NOTAMs) for each operation may be impractical for frequent or short-duration flights.
– Coordination Complexity: Mandatory coordination with multiple stakeholders (e.g., military, emergency services) increases complexity.

– Electronic Conspicuity (EC):
– Equipment Availability: ADS-B equipment operating on 978 MHz UAT is not widely used in the UK, making compliance challenging.
– Licensing Issues: Reliance on OFCOM’s Innovation and Trial licensing procedures adds uncertainty and administrative hurdles and no doubt costs.

– High-Intensity Anti-Collision Lighting:
– Technical Challenges: The requirement may not be feasible for small UAS due to weight and power constraints.
– Cost Implications: Additional equipment increases operational costs, affecting profitability and competitiveness.

– Containment Solutions:
– Technical Barriers: Implementing robust geo-caging or equivalent systems may be technologically and financially prohibitive for some operators.

c. Application Process Limitations
– Single Site Per Submission:
– Operational Inefficiency: Limiting applications to one site may slow down deployment and increase administrative overhead.

d. Evolving Policy and Regulatory Uncertainty
– Continuous Review:
– Investment Risk: Operators may be hesitant to invest in compliance if policies are subject to change.
– Lack of Legal Certainty:
– Enforceability Issues: As a policy concept rather than law, operators may face legal ambiguities in enforcement and compliance.

3. Potential Impacts on the Drone Industry

a. Stifling Innovation and Market Entry
– Barrier to Entry: Stringent requirements may discourage startups and SMEs from entering the market.
– Reduced Experimentation: High compliance costs limit the ability to test new technologies and operational models.

b. Competitive Disadvantages
– Favoring Large Operators: Well-resourced companies are better equipped to meet the requirements, potentially leading to market monopolisation.

c. International Disparities
– Inconsistency with Global Standards: Reliance on U.S. standards (e.g., RTCA DO-282C) may create conflicts with other international regulations, affecting operators engaged in cross-border activities.

4. Recommendations for Amendments

a. Clarify Definitions and Parameters
– Precise Definition of AAE:
– Legal Clarity: Provide a clear, legally binding definition of AAE to reduce ambiguity.
– Criteria Establishment: Set specific parameters (e.g., exact distances, types of infrastructure) to qualify as an AAE.

b. Proportionality in Operational Requirements
– Risk-Based Approach:
– Scaled Requirements: Tailor operational requirements based on the risk profile of the UAS operation (e.g., size, weight, location).
– Exemptions for Low-Risk Operations:
– Simplify Compliance: Allow for exemptions or reduced requirements for operations posing minimal risk.

c. Streamline Application Process
– Multiple Sites Per Application:
– Administrative Efficiency: Permit applications covering multiple sites where appropriate, reducing bureaucratic hurdles.
– Standardised Procedures:
– Transparency: Develop clear guidelines and timelines for application processing.

d. Address Electronic Conspicuity Challenges
– Equipment Standardisation:
– Market Availability: Collaborate with manufacturers to ensure ADS-B equipment is accessible and affordable.
– Licensing Simplification:
– Permanent Licensing Arrangements: Work with OFCOM to establish permanent, streamlined licensing procedures for 978 MHz UAT.

e. Provide Flexibility in Mitigation Measures
– Alternative Solutions:
– Innovation Encouragement: Allow operators to propose alternative methods to achieve safety outcomes.
– Technology Neutrality:
– Avoid Prescriptive Requirements: Focus on performance outcomes rather than prescribing specific technologies.

f. Enhance Stakeholder Engagement
– Consultation Processes:
– Inclusive Policy Development: Engage with a broad range of stakeholders, including SMEs and industry groups.
– Support and Guidance:
– Educational Resources: Provide operators with clear guidance and training materials to aid compliance.

g. Align with UK Standards
– Develop Domestic Standards:
– Consistency: Establish UK-specific standards for technical requirements like anti-collision lighting.
– International Harmonisation:
– Global Compatibility: Ensure new standards are compatible with international regulations to facilitate cross-border operations.

5. Legal Requirements for Effective Implementation

a. Codification into Law
– Regulatory Framework:
– Statutory Instruments: Incorporate key policy elements into UK aviation law to provide legal enforceability.
– Amendments to Existing Regulations:
– Regulation (EU) 2019/947 Adaptation: Modify existing regulations to accommodate AAE operations and associated requirements.

b. Legal Certainty and Enforcement
– Clear Obligations:
– Operator Compliance: Define legal obligations clearly to ensure operators understand requirements.
– Enforcement Mechanisms:
– Penalties and Sanctions: Establish clear enforcement protocols for non-compliance to uphold safety standards.

6. Additional Relevant Points for the CAA

a. Balancing Safety with Innovation
– Proportional Regulation:
– Innovation Friendly: Ensure that safety regulations do not unnecessarily hinder technological advancement.
– Risk Management:
– Data-Driven Policies: Use empirical data to inform policy adjustments, maintaining safety without over-regulation.

b. Data Privacy and Confidentiality
– Data Handling Policies:
– Privacy Protection: Develop clear guidelines on data usage, storage, and sharing to protect operators’ proprietary information.

c. Future-Proofing Regulations
– Adaptive Frameworks:
– Technological Evolution: Design policies flexible enough to accommodate future technological developments.
– Regular Reviews:
– Stakeholder Feedback: Implement mechanisms for ongoing consultation and policy refinement.

d. International Cooperation
– Global Best Practices:
– Information Sharing: Engage with international aviation authorities to align policies and share lessons learned.
– Cross-Border Operations:
– Harmonized Regulations: Facilitate international drone operations by harmonizing standards where possible.

7. Conclusion

The CAA’s initiative to introduce the concept of Atypical Air Environment for BVLOS operations is a progressive step towards integrating UAS into the national airspace. However, without careful consideration and amendments, the policy may inadvertently stifle innovation and impose undue burdens on operators.
By clarifying definitions, scaling operational requirements appropriately, streamlining processes, and codifying necessary elements into law, the CAA can foster a regulatory environment that promotes both safety and innovation. Collaboration with industry stakeholders, legal experts, and technology providers will be crucial in refining the policy to achieve its intended objectives.

Recommendations Summary:

1. Clarify Definitions: Provide precise legal definitions for AAE and other key terms.
2. Proportional Requirements: Scale operational requirements based on risk assessments.
3. Streamline Processes: Allow multiple sites per application and simplify procedures.
4. Address EC Challenges: Ensure equipment availability and simplify licensing.
5. Flexibility in Mitigations: Permit alternative safety solutions and avoid prescriptive technologies.
6. Stakeholder Engagement: Enhance consultation and provide guidance resources.
7. Align Standards: Develop UK-specific technical standards and harmonise internationally.
8. Legal Codification: Incorporate essential policy elements into law for enforceability.
9. Balance Safety and Innovation: Maintain safety without hindering technological progress.
10. Protect Data Privacy: Establish clear data handling and confidentiality policies.
By implementing these recommendations, the CAA can create a robust regulatory framework that ensures safety while encouraging the growth and innovation of the UK’s drone industry.

8. Comparison with EASA PDRA03 and Lessons for the UK
Comparing the CAA’s position with the European Union Aviation Safety Agency’s (EASA) Pre-Defined Risk Assessment number 03 (PDRA03) reveals both opportunities and challenges for UK drone regulation. EASA’s PDRA03 offers a structured, risk-based framework that allows operators to self-declare compliance with specific conditions, reducing administrative burdens and accelerating operational approvals. This approach supports drone operators by providing clear guidelines while fostering innovation through flexibility in operations such as autonomous flights, multi-UAV control, and operations beyond visual line of sight (BVLOS) under certain conditions. In contrast, the CAA’s policy concept imposes more prescriptive requirements, such as mandatory NOTAM submissions for each operation and specific technical equipment like ADS-B transceivers, which may be unnecessary and bureaucratic for certain low-risk operations. The UK drone industry could benefit from adopting elements of the EASA PDRA03 by implementing a more proportionate, risk-based regulatory framework that emphasises operator declarations and standardised procedures. This would streamline the approval process, reduce administrative overheads, and encourage innovation while maintaining safety. Learning from the EU’s experience, the CAA can enhance its policies to better support the growth of the UK drone industry by embracing flexibility, reducing unnecessary bureaucratic requirements, and aligning more closely with international best practices.

Richard Ryan is an experienced drone lawyer specialising in unmanned aircraft systems (UAS) and aviation law. He provides expert legal guidance on regulatory compliance, licensing, and operational issues to clients navigating the complexities of drone technology.
Disclaimer: This blog is for informational purposes only and does not constitute legal advice. For legal counsel regarding specific situations, please consult a qualified drone lawyer.

The post Analysis and Recommendations on CAP 3040 | First Edition appeared first on Blakistons.