Legal Analysis and Recommendations Archives - Blakistons https://blakistons.co.uk/category/legal-analysis-and-recommendations/ Drone Law Mon, 06 Jul 2026 09:42:00 +0000 en-GB hourly 1 https://wordpress.org/?v=7.0.1 Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/ Mon, 06 Jul 2026 09:42:00 +0000 https://blakistons.co.uk/?p=2698 Drone Law | Counter-UAS | Defence AI | One-Way Effectors Summary: The Royal Navy’s launch of the British-built Nyan One-Way Effector from XV Patrick Blackett is more than a drone trial. It is a legal and operational marker in the UK’s transition towards a Hybrid Navy, raising issues of targeting law, weapons review, military airworthiness, […]

The post Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance appeared first on Blakistons.

]]>

Drone Law | Counter-UAS | Defence AI | One-Way Effectors

Summary: The Royal Navy’s launch of the British-built Nyan One-Way Effector from XV Patrick Blackett is more than a drone trial. It is a legal and operational marker in the UK’s transition towards a Hybrid Navy, raising issues of targeting law, weapons review, military airworthiness, counter-UAS defence, export controls and AI governance.

1. Why the Nyan Trial Matters

The Royal Navy and British Army have tested the Nyan One-Way Effector, designed and built by BAE Systems’ Callen-Lenz, for both maritime and land operations. The system has a 2.9-metre wingspan and is designed to provide a precision strike capability. It has now been launched from the Royal Navy’s experimentation ship XV Patrick Blackett as part of Project Vantage, the programme focused on accelerating maritime one-way effector capability.

Legally, the phrase “one-way effector” should not distract from the underlying classification problem. Nyan may simultaneously be an aircraft, a military UAS, a weapon system, a munition, a software-enabled targeting platform and an export-controlled defence article. Each classification carries its own compliance burden.

2. From Drone Novelty to Combat Mass

The trial reflects the UK’s move towards crewed-uncrewed teaming and the Royal Navy’s Hybrid Navy concept. One-way effectors are intended to provide affordable combat mass, allowing crewed platforms to extend reach, increase tempo and complicate an adversary’s defensive picture.

However, affordability does not dilute legal responsibility. The cheaper and more numerous the weapon, the more frequently it may be used. The more frequently it is used, the more important lawful targeting architecture becomes.

3. Autonomy: The Legal Question Is What the Machine Decides

The key legal question is not whether Nyan is a drone, but what functions are automated or autonomous. Autonomy in navigation is not the same as autonomy in target selection. A system may fly itself to a pre-programmed target without being authorised to decide who or what is attacked.

Commanders and lawyers should ask:

  • Does the system merely navigate to a human-selected target?
  • Does it detect, classify, prioritise or select targets?
  • Can it be retasked, recalled, aborted or terminated after launch?
  • What happens if GPS is jammed, spoofed or degraded?
  • What mission data and operator decisions are recorded?

Those questions determine whether the system can be used consistently with distinction, proportionality, precautions in attack and applicable rules of engagement.

4. Article 36 Weapons Review

A one-way effector requires a disciplined weapons review. That review should not be limited to the airframe or warhead. It should include the launcher, mission-planning software, navigation system, datalinks, communications architecture, abort logic, cyber resilience, payload effects and integration with intelligence or targeting systems.

The review must also examine foreseeable use cases. Launching from land against a fixed target is materially different from launching from a moving naval platform against a maritime or coastal target. The latter introduces neutral shipping, civilian infrastructure, allied aircraft, electromagnetic interference, airspace deconfliction and more complex proportionality assessments.

5. EU AI Act and UK AI Standards

The EU AI Act generally excludes AI systems used exclusively for military, defence or national-security purposes. However, its high-risk AI standards remain useful benchmarks for dual-use suppliers, defence contractors, procurement assurance and civilian spin-outs.

The UK does not currently have a single equivalent “UK AI Act”. Instead, the UK uses a sector-led, principles-based model. In defence, this is supplemented by Ministry of Defence AI principles, including human-centricity, responsibility, understanding, bias and harm mitigation, and reliability.

Governance Area EU AI Act Benchmark UK / MOD Equivalent Application to One-Way Effectors
Risk management Lifecycle risk management Safety, security and robustness Hazard logs for navigation failure, lost link, spoofing, target-data error and launch failure.
Technical documentation Technical file and system description Accountability and governance Configuration records for airframe, launcher, software, payload and mission-planning tools.
Record-keeping Automatic logging Transparency and explainability Mission logs, operator decisions, software versions, AI outputs and telemetry retention.
Human oversight Human control and intervention Human-centricity and responsibility Clear authority for launch, retask, abort, termination and post-strike review.
Cyber resilience Accuracy, robustness and cybersecurity Reliability and security Testing against jamming, spoofing, adversarial inputs, cyber compromise and degraded environments.

6. Maritime Launch Changes the Legal Burden

Launching from a ship is materially different from launching from a land range. The platform is moving. Weather and sea state affect launch reliability. The electromagnetic environment may be contested. The operating area may include neutral vessels, civil aircraft, allied aircraft, helicopters, missiles and other uncrewed systems.

The legal architecture must therefore include target validation, positive identification, proportionality analysis, precautions in attack, air and maritime deconfliction, and auditability. The question is not simply whether Nyan can be launched from a ship. The question is whether the Navy can generate a repeatable, auditable and legally defensible kill chain from a ship.

7. The Counter-UAS Mirror

Every one-way effector creates a corresponding defence problem. If the UK can launch low-cost precision effectors from ships, adversaries and proxies can attempt similar effects. Counter-UAS law is therefore inseparable from OWE deployment.

Defending ships, ports, airbases and critical infrastructure requires layered capabilities: detection, identification, tracking, electronic warfare, cyber effects, kinetic interceptors, directed energy, decoys, hardening, dispersal and forensic recovery.

In armed conflict, commanders will operate under the law of armed conflict and rules of engagement. In peacetime or grey-zone conditions, counter-drone operations may engage aviation law, communications law, property rights, criminal law, public safety, port security and military aid to civil authorities.

8. Export Controls and Procurement Risk

Sovereign manufacture does not remove export-control obligations. Airframes, propulsion systems, launchers, datalinks, payloads, source code, mission-planning tools, technical assistance and software updates may all require careful classification and licensing analysis.

Rapid procurement also creates legal debt if safety cases, software changes, data rights, AI assurance, cyber resilience and operator training are not properly documented. The solution is not to slow innovation, but to embed lawyers, engineers, safety specialists, AI assurance teams and operators into the experimentation cycle from the start.

9. Bottom Line

The Nyan sea launch is a significant step towards a British Hybrid Navy. Its real importance lies in the legal system-of-systems problem it exposes. A one-way effector is not merely a drone with a warhead. It moves through air law, weapons law, targeting law, AI governance, export-control law, safety regulation, procurement governance and counter-UAS doctrine.

The future fleet will not be judged only by how many drones it can launch. It will be judged by whether it can launch them lawfully, safely, proportionately, responsibly and at scale.

About the Author

Richard Ryan is a barrister, Chartered Arbitrator and specialist in drone law, counter-UAS, defence procurement and AI governance. He advises government, defence and technology organisations on autonomous systems, military aviation, export controls, commercial contracts and regulatory compliance. Richard is also undertaking a PhD at Cranfield University researching the future legal framework for BVLOS operations, autonomous aviation and Unmanned Traffic Management.

This article is general legal commentary and does not constitute legal advice.

The post Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance appeared first on Blakistons.

]]> https://blakistons.co.uk/2673-2/ Wed, 03 Jun 2026 16:49:56 +0000 https://blakistons.co.uk/?p=2673 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 Status and method. This paper relies on primary and official sources, supplemented by reputable reporting for incident chronology. All facts are verified as […]

The post appeared first on Blakistons.

]]>

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

Status and method. This paper relies on primary and official sources, supplemented by reputable reporting for incident chronology. All facts are verified as at 2 June 2026. Battlefield figures drawn from active conflict reporting are attributed to their originating source and presented as attributed claims rather than judicially established fact. The paper contains no classified or privileged material. All footnote links are live.

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

2019 provision Current reality Assessment
Focus on the highest harm illegal use of small aerial drones in the UK. Concern now extends to defence sites, CNI in crisis or conflict, and state launched drones and missiles. Too narrow as a national frame.
Short planning horizon from 2019. Document is c. 6.6 years old; NPSA requires regular review because methods change quickly. Formally stale; refresh overdue.
Empower police and responders. MoD now seeks its own defeat powers at Defence sites because police only authorities are inadequate. Institutionally outdated.
Aerial drones only. New Defence policy extends to land and maritime uncrewed systems. Conceptually outdated.
Counter drone as a discrete problem. NATO now treats small UAS through hypersonic missiles as one integrated air and missile defence continuum.[16] The silo is no longer tenable.

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.

About the author. Mr Richard Ryan is a barrister of Blakiston’s Chambers..

Footnotes & sources (23)

  1. UK Counter-Unmanned Aircraft Strategy, CP 187, presented to Parliament 21 October 2019 (GOV.UK). https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy ↩
  2. UK Counter-Unmanned Aircraft Strategy (HTML version), GOV.UK, published 21 October 2019. https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy/table ↩
  3. Defence Drone Strategy — the UK’s approach to Defence Uncrewed Systems, GOV.UK, published 22 February 2024. https://www.gov.uk/government/publications/defence-drone-strategy-the-uks-approach-to-defence-uncrewed-systems/defence-drone-strategy-the-uks-approach-to-defence-uncrewed-systems ↩
  4. The Strategic Defence Review 2025 — Making Britain Safer, GOV.UK, published 2 June 2025. https://www.gov.uk/government/publications/the-strategic-defence-review-2025-making-britain-safer-secure-at-home-strong-abroad ↩
  5. NPSA, “Counter Uncrewed Aerial Systems (C-UAS)” specialised guidance. https://www.npsa.gov.uk/specialised-guidance/uncrewed-aerial-systems/counter-uncrewed-aerial-systems-c-uas ↩
  6. Ministry of Defence, “New powers for Defence personnel to defeat drones following doubling of incidents near bases” (266 incidents in 2025, up from 126), GOV.UK, 2 February 2026. https://www.gov.uk/government/news/new-powers-for-defence-personnel-to-defeat-drones-following-doubling-of-incidents-near-bases ↩
  7. “Russia launched 656 drones and 73 missiles” — figures attributed to the Ukrainian Air Force; CBS News, 2 June 2026. https://www.cbsnews.com/news/russia-ukraine-war-major-attacks-missile-drone-kill-several-wound-dozens/ ↩
  8. NPR, “Russian attack on Ukraine kills at least 14”, 2 June 2026 (corroborating launch and interception figures). https://www.npr.org/2026/06/02/nx-s1-5844071/russian-attack-ukraine ↩
  9. Chornobyl New Safe Confinement struck by a Geran-2 (Shahed type) drone, 14 February 2025: Greenpeace Ukraine mission report, 20 March 2025. https://www.greenpeace.org/ukraine/en/news/3504/fifty-percent-of-north-roof-structure-of-chornobyl-new-safe-confinement-shelter-severely-damaged/ ↩
  10. IAEA assessment (December 2025) that the New Safe Confinement had lost its primary safety functions, including confinement (reported via United24/Reuters). https://united24media.com/latest-news/iaea-chornobyls-new-safe-confinement-can-no-longer-contain-radiation-after-russian-drone-attack-14067 ↩
  11. Drone strike causing a generator fire at the UAE’s Barakah nuclear plant, 17 May 2026: Al Jazeera, 17 May 2026. https://www.aljazeera.com/news/2026/5/17/drone-strike-sparks-fire-at-uaes-barakah-nuclear-power-plant ↩
  12. NPR, “Drone strikes UAE nuclear plant”, 18 May 2026 (IAEA: one reactor on emergency diesel generators). https://www.npr.org/2026/05/18/g-s1-122534/drone-strikes-uae-nuclear-plant ↩
  13. Reuters, “Iranian-made drone hits British air base in Cyprus” (RAF Akrotiri runway strike, limited damage), 2 March 2026. https://www.aol.com/articles/iranian-made-drone-hits-british-121630466.html ↩
  14. Summary of the UK Government legal position: the legality of defensive action in respect of Iranian regional attacks, GOV.UK (10 Downing Street), March 2026. https://www.gov.uk/government/news/summary-of-the-uk-government-legal-position-the-legality-of-defensive-action-in-respect-of-iranian-regional-attacks ↩
  15. CSIS, “How Ukraine’s Operation Spider’s Web Redefines Asymmetric Warfare” (117 drones; 40+ aircraft struck; some AI assisted guidance). https://www.csis.org/analysis/how-ukraines-spider-web-operation-redefines-asymmetric-warfare ↩
  16. NATO Integrated Air and Missile Defence Policy, 13 February 2025 (threat spectrum “from small… UASs to all types of cruise and ballistic missiles, including hypersonic”). https://www.nato.int/cps/en/natohq/official_texts_233084.htm ↩
  17. Air Traffic Management and Unmanned Aircraft Act 2021 (c. 12), legislation.gov.uk. https://www.legislation.gov.uk/ukpga/2021/12/contents/enacted ↩
  18. Explanatory Notes to the Air Traffic Management and Unmanned Aircraft Act 2021 (kinetic/jamming measures may amount to unlawful interference; amendment of s. 93 Police Act 1997). https://www.legislation.gov.uk/ukpga/2021/12/pdfs/ukpgaen_20210012_en.pdf ↩
  19. UK Civil Aviation Authority, “Remote ID (RID)” — Direct RID in force from 1 January 2026 for UK1, UK2, UK3, UK5 and UK6 drones; extension from 1 January 2028. https://www.caa.co.uk/drones/regulations-consultations-and-policy-programmes/policy-programmes/remote-id-rid/ ↩
  20. Ofcom, “GPS jamming exercises” — operational use of a jammer is an offence under s. 68 Wireless Telegraphy Act 2006; Ofcom cannot authorise operational use. https://www.ofcom.org.uk/spectrum/frequencies/gps-jamming-exercises ↩
  21. DSIT, “Possession of radiofrequency jammers and the relevant legal framework” (call for evidence), GOV.UK, 2026. https://www.gov.uk/government/calls-for-evidence/possession-of-radiofrequency-jammers-and-the-relevant-legal-framework/possession-of-radiofrequency-jammers-and-the-relevant-legal-framework ↩
  22. ICRC, “FAQ: international humanitarian law and the use of drones in armed conflict” (distinction, proportionality, precaution). https://www.icrc.org/en/article/faq-international-humanitarian-law-drones-armed-conflict ↩
  23. NPSA, “Countering Threats from Uncrewed Aerial Systems — Making Your Site Ready”. https://www.npsa.gov.uk/resources/c-uas-making-your-site-ready ↩

The post appeared first on Blakistons.

]]> The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft https://blakistons.co.uk/the-drone-in-the-room-what-the-ai-acts-august-deadline-actually-means-for-unmanned-aircraft/ Mon, 01 Jun 2026 11:14:30 +0000 https://blakistons.co.uk/?p=2661 There’s a particular kind of frustration that comes from practising in a field that everyone assumes is covered by a law that, on close reading, barely mentions it. Drone law is one of those fields. People hear “AI Act” and “drones” in the same breath and assume the two slot neatly together; that the great […]

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

]]> There’s a particular kind of frustration that comes from practising in a field that everyone assumes is covered by a law that, on close reading, barely mentions it. Drone law is one of those fields. People hear “AI Act” and “drones” in the same breath and assume the two slot neatly together; that the great European regulatory machine has, somewhere in its 113 articles, a tidy chapter telling me when my client’s counter-UAS system crosses a line. It doesn’t. And the gap between what people assume and what the text actually says is where most of my work now lives.

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.

]]> How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/ Thu, 06 Nov 2025 18:28:20 +0000 https://blakistons.co.uk/?p=2624 By Richard Ryan, barrister and drone lawyer How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft — and what the defence carve-outs really mean. In Brief… Purely military AI systems are out of scope of the EU AI Act. If an AI system is developed or used exclusively for military/defence or national-security […]

The post How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean appeared first on Blakistons.

]]>

By Richard Ryan, barrister and drone lawyer

How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft — and what the defence carve-outs really mean.

In Brief…

  • Purely military AI systems are out of scope of the EU AI Act. If an AI system is developed or used exclusively for military/defence or national-security purposes, the Act does not apply. (EUR-Lex)
  • Dual-use is different. If the same autonomy stack, sensors or models are marketed or used for civilian purposes in the EU (for example, civil UAS, border or law-enforcement tasks), the Act can apply — with stringent duties for “high-risk” systems. (EUR-Lex)
  • Real-world testing is regulated. Pre-market R&D is generally excluded, but real-world testing isn’t — it requires specific safeguards and registration. (EUR-Lex)
  • Foundation models (GPAI) have their own rules from 2 Aug 2025; the defence carve-out in the Act is written for AI systems, not explicitly for models. If a model is placed on the EU market generally, the provider’s GPAI obligations can still bite. (EUR-Lex)

Context: sUAS News reports that GA-ASI is showcasing its autonomous fighter portfolio (for example, YFQ-42A CCA, MQ-20 Avenger) at the International Fighter Conference in Rome, 4–6 Nov 2025. This post overlays that scenario with the EU AI Act’s rules.

1) First principles: When does the EU AI Act apply?

The Act has extraterritorial reach. It covers (i) providers and deployers in the EU, (ii) providers placing on the EU market or putting systems into service in the EU — even if they are not established here — and (iii) providers/deployers in third countries where the AI system’s output is used in the EU. (EUR-Lex)

However, Article 2(3) draws a bright line: the Act does not apply to AI systems used exclusively for military, defence or national security. It also does not apply where a system is not placed on the EU market but its output is used in the EU exclusively for those purposes. Recital 24 reiterates this and clarifies that non-defence use falls back under the Act. (EUR-Lex)

What this means in Rome:

  • A closed, defence-only showcase for European militaries: out of scope.
  • A civil-use pitch, civil flight trials, or plans to sell autonomy modules to EU civilian buyers: in scope (see the high-risk section below). (EUR-Lex)

2) The key defence carve-outs (and their limits)

Carve-out #1 — Defence/military:

“This Regulation shall not apply to AI systems … used exclusively for military, defence or national security purposes.” (Article 2(3))

Two important nuances:

  • Exclusivity matters. The moment an autonomy stack or sensor suite is also marketed or used for civilian or law-enforcement tasks, the defence exclusion no longer shields those non-defence uses. (EUR-Lex)
  • Models vs systems. The text explicitly excludes AI systems for defence; it does not create an explicit defence exclusion for general-purpose AI models. If a GPAI model is placed on the EU market, Chapter V obligations for model providers can still apply — even if one downstream customer is a defence user. (More on GPAI below.) (EUR-Lex)

Carve-out #2 — Pre-market R&D:
R&D before placing on the market is generally outside scope, but real-world testing is not. Testing in real-world conditions triggers a dedicated regime (for example, registration, time limits, informed consent or special conditions for law enforcement, incident reporting). (EUR-Lex)

Carve-out #3 — Emergency derogations (non-defence):
For exceptional public-security reasons (or imminent threats to life/health), market surveillance authorities can authorise temporary use of a high-risk AI system before full conformity assessment — subject to strict conditions. Law-enforcement or civil-protection bodies can also use in urgent cases, then seek authorisation without undue delay. This is not a defence-specific carve-out, but it explains emergency deployments outside the military context. (EUR-Lex)

3) If the defence exclusion doesn’t apply, would autonomous fighters tech be “high-risk”?

Very likely yes — for civil variants or dual-use spin-outs:

  • Annex I (product-safety route). AI that is a safety component of products covered by sectoral EU safety laws is high-risk where those products need third-party conformity assessment. That list explicitly includes EU civil aviation law (Reg. 2018/1139) — covering unmanned aircraft and their remotely controllable equipment. In a civil-UAS configuration, an autonomy stack acting as a safety component would be regulated as high-risk. (EUR-Lex)
  • Annex III (stand-alone uses). Separate “high-risk” buckets also capture, for example, remote biometric identification and other sensitive functions (if and where permitted by Union/national law), critical infrastructure safety components, and more. If a fighter-born sensing suite were repurposed for civil border surveillance or public-space identification, you quickly hit these Annex III categories. (EUR-Lex)

What “high-risk” demands in practice
Providers must implement a risk-management system, data governance, technical documentation, logging, transparency/instructions, human oversight, and accuracy/robustness/cybersecurity — then pass conformity assessment, issue an EU Declaration of Conformity, and affix CE marking. Deployers also carry duties (for example, monitoring, data relevance, user notification in some cases). (EUR-Lex)

4) Sensors on show: what about face recognition and other “red lines”?

The EU bans several AI practices outright (from 2 Feb 2025), including:

  • Untargeted scraping of facial images to build recognition databases.
  • Biometric categorisation inferring sensitive traits (for example, race, political opinions, religion).
  • Emotion recognition in workplaces or schools (with narrow safety/medical exceptions).
  • Predictive “risk assessments” of criminality based solely on personality traits/profiling.
  • Real-time remote biometric identification (RBI) in public spaces for law enforcement — unless strictly authorised and necessary for narrowly defined objectives (for example, locating a specific suspect in serious crimes, preventing a specific imminent threat, finding missing persons), with prior judicial/independent approval and registration. (EUR-Lex)

Implication for a trade-show demo: training a camera on attendees to test real-time RBI in a public venue would likely be unlawful unless those strict law-enforcement exceptions and procedural safeguards apply — which they typically will not at a commercial defence conference. (EUR-Lex)

5) Real-world testing in the EU (civil or dual-use variants)

If a provider runs real-world flight tests in the EU (outside the defence exclusion), the Act requires — among other things — registration, an EU-established entity or EU legal representative, limits on duration (normally up to six months, extendable once), rules on informed consent (with special handling for law-enforcement tests), qualified oversight, and the ability to reverse/ignore the system’s outputs. Serious incidents must be reported promptly. (EUR-Lex)

6) Foundation models (GPAI): obligations can still attach

From 2 Aug 2025, Chapter V sets baseline transparency and copyright-policy duties for providers of general-purpose AI models (with extra obligations if the model presents systemic risks). The defence exclusion in Article 2(3) is framed for AI systems, not models. So, if a foundation model is placed on the EU market, the model provider can have obligations even if a downstream customer is a defence prime. (Open-source specifics and systemic-risk thresholds also apply.) (EUR-Lex)

7) Timelines you need in Rome (as of 6 Nov 2025)

  • Entry into force: 1 Aug 2024 (20 days after OJ publication).
  • Prohibited practices + core chapters (I–II): apply from 2 Feb 2025.
  • GPAI rules (Chapter V), plus other chapters (III §4, VII, XII, and Article 78): apply from 2 Aug 2025.
  • General application: 2 Aug 2026 (high-risk regime starts to bite broadly).
  • Article 6(1) Annex III classification trigger & related obligations: 2 Aug 2027. (EUR-Lex)

8) Enforcement and penalties

  • Violating prohibited practices (Article 5) can draw fines up to €35m or 7% of worldwide annual turnover, whichever is higher.
  • Other operator obligations can reach €15m or 3%; supplying misleading information can reach €7.5m or 1% (SMEs benefit from caps). Separate fine scales apply to EU institutions. (EUR-Lex)

9) Practical playbook for IFC attendees

If you are a defence OEM showing autonomy stacks:

  1. Map uses: Defence-only (excluded) vs any civil or law-enforcement pathways (potentially in scope). Document the exclusivity of defence deployments if you rely on the carve-out. (EUR-Lex)
  2. GPAI suppliers: If you place a foundation model on the EU market, expect Chapter V duties regardless of defence customers. (EUR-Lex)
  3. No RBI demos on the show floor. Those prohibitions already apply in 2025. (EUR-Lex)
  4. Planning EU flight tests for civil variants? Prepare for real-world testing conditions (registration, oversight, incident reporting). (EUR-Lex)
  5. For civil UAS commercialisation, treat your autonomy as high-risk (EASA product-safety route), budget time for conformity assessment and CE marking. (EUR-Lex)

If you are a European ministry or agency:

  • Distinguish military operations (out of scope) from law-enforcement or border uses (in scope; watch RBI limits and high-risk duties). Consider Article 46 emergency derogations only in exceptional and documented cases. (EUR-Lex)

If you are a civil UAS integrator:

  • Expect the full high-risk package (risk management, data governance, human oversight, cybersecurity, logs, conformity assessment, CE). Build compliance into your system architecture, ML pipelines, safety cases, and ops manuals from day one. (EUR-Lex)

10) Quick decision pathway

  1. Is the use exclusively defence or national security?
    Yes: AI system is out of scope.
    No: continue. (EUR-Lex)
  2. Is it a civil product or law-enforcement/border use?
    Civil product with safety function (for example, civil UAS): High-risk via Annex I ? conformity assessment + CE. (EUR-Lex)
    Stand-alone sensitive use (for example, RBI, critical infrastructure): Annex III high-risk or Article 5 prohibition applies. (EUR-Lex)
  3. Is there a GPAI model being placed on the EU market?
    Yes: Chapter V duties for model providers from 2 Aug 2025, separate from the defence carve-out for systems. (EUR-Lex)
  4. Is this pre-market testing?
    Real-world testing rules apply (registration, oversight, incident reporting). (EUR-Lex)

Bottom line for “Autonomous Fighters in Rome”

  • A military-only display of GA-ASI’s autonomous fighters is outside the AI Act.
  • Any civil spin-off (cargo drones, civil surveillance, airport ops) or law-enforcement application in the EU will trigger the Act — often at the high-risk level — together with tight prohibitions around biometric uses in public spaces. Plan your compliance architecture accordingly. (EUR-Lex)

This article is informational and not legal advice. Citations are to the Official Journal text of the Artificial Intelligence Act (Regulation (EU) 2024/1689) for scope (Art. 2), prohibitions (Art. 5), high-risk regime (Ch. III), real-world testing (Arts. 57–61), GPAI (Ch. V incl. Art. 53), timelines (Art. 113), and penalties (Art. 99–101).

About the author — Richard Ryan

Richard Ryan is a UK barrister (Direct Access), mediator and Chartered Arbitrator (FCIArb), and a Bencher of Gray’s Inn. He practises across defence, aerospace, construction, engineering and commodities, with a leading specialism in drone and counter-drone law, unmanned aviation regulation, and AI-enabled safety and compliance. Richard advises government, primes and operators on EU/UK UAS frameworks, BVLOS, U-space/UTM and the EU AI Act. He leads Blakiston’s Chambers and contributes regularly to industry guidance and policy consultations.

The post How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean appeared first on Blakistons.

]]> A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/ Thu, 06 Nov 2025 17:53:49 +0000 https://blakistons.co.uk/?p=2615 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. Outcome at a glance Count 1 (conviction): Operating an unmanned aircraft close to the site of an ongoing […]

The post A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots 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.

Outcome at a glance

  • Count 1 (conviction): Operating an unmanned aircraft close to the site of an ongoing emergency response — Air Navigation Order 2016 Articles 265B(3), 265B(5)(j) and 265F(3)(c) (reflecting UAS.OPEN.060(3)).
  • Count 2 (dismissed): Obstructing or hindering emergency workers — Emergency Workers (Obstruction) Act 2006, sections 1 and 4 — no case to answer.
  • Sentence: £300 (reduced from £2,500). Deprivation order refused — the client’s equipment will be returned.

.

Competence, cooperation and public interest flying

The client is an experienced operator with hundreds of hours and thousands of flights, combining sound aviation literacy with routine work around public interest incidents. On the day in question, the client used aircraft tracking tools and air band monitoring, maintained a conservative standoff where no formal cordon existed, and landed promptly when requested by police. This was a measured and safety first response in a dynamic setting.

Lesson 1: Telemetry clarity

When presenting flight data, clarity matters. Plot the flight path with a thin, precise line so the base map remains legible, including fences, road edges, cordons and measured standoffs. A thick line can obscure the very features that prove separation.

  • Keep a clean thin line map and a forensic overlay with timestamps for take off, orbit points, return to home and landing, plus measured distances to fixed features.
  • Use a thin line that clearly shows accurate telemetry when placed on a map, not a thick line that obscures part of the map.


Lesson 2: Plan for seizure and understand where DJI DAT lives

High fidelity DJI DAT logs are stored on the aircraft and typically require connecting the drone to a computer to extract. If a drone is seized by police, immediate access to those DAT files is difficult.

  • Build redundancy: back up app and controller logs after each flight, use screen recordings of the flight user interface, and capture independent stills or video.
  • For sensitive assignments, consider periodic DAT offloads in advance.

Five straightforward commitments

  1. Thin line telemetry as the default for mapping outputs.
  2. Evidence resilience: dual path logging (logs plus screen capture) and periodic DAT offloads.
  3. Proportionate communications near emergency activity where appropriate.
  4. A simple one page ops note on every job covering airspace, standoffs and abort triggers.
  5. Calm, courteous engagement with officers, with a record of powers used and a property schedule if equipment is seized.

Technical reference: cross motorway separation

To contextualise the judge’s description (opposite side of a six lane motorway plus hard shoulder plus verge), the following uses standard UK dimensions.

Assumptions from UK highway standards

  • Lane width (motorways): 3.65 m per lane (DMRB CD 127). [1]
  • Hard shoulder width: 3.3 m (National Highways). [2]
  • Central reservation (median): assume about 3.0 m (DMRB derived guidance). [3]
  • Verge: varies by site; on trunk roads, about 3.0 m is common. Use 2.0 to 3.0 m to bracket reality. [4]

Baseline components

  • Six lanes = 6 x 3.65 = 21.90 m. [1]
  • Two hard shoulders = 6.60 m. [2]
  • Central reservation (median) about 3.00 m. [3]
  • Verge per side about 2.0 to 3.0 m. [4]

Real world lateral separation (verge to verge)

Distance = 6 lanes + 2 x hard shoulder + 2 x verge + median

  • With 2.0 m verges (conservative): 21.90 + 6.60 + 4.00 + 3.00 = 35.50 m
  • With 3.0 m verges (typical): 21.90 + 6.60 + 6.00 + 3.00 = 37.50 m

Figure to use: about 37.5 m horizontal separation verge to verge (typical). Lower bound: about 35.5 m if verges are unusually narrow.

Lean reading (narrow phrasing)

Six lanes plus one hard shoulder plus one verge (omitting the median and the opposite side shoulder and verge):

21.90 + 3.30 + (2.0 to 3.0) = 27.2 to 28.2 m

This underestimates the physical cross section that most operators and engineers would use.

Add altitude for slant distance

If height is h, the slant range is sqrt(lateral^2 + h^2).

  • With 37.5 m lateral: 48.0 m at 30 m AGL, 70.8 m at 60 m, 125.7 m at 120 m.
  • With 35.5 m lateral: 46.5 m at 30 m, 69.2 m at 60 m, 124.2 m at 120 m.

Practical effect: even before adding any field offset inside the field beyond the verge, cross motorway separation is around 36 to 38 m. Any field offset adds to that figure. Slant range increases further with altitude.

Standards: DMRB CD 127, National Highways, TII DN GEO 03036, Transport Scotland.

Bottom line

This is a constructive outcome. The most serious allegation fell away, the fine is modest, and the client retains their equipment. More importantly, the experience is being used to lead on best practice: clearer telemetry, stronger data resilience and exemplary on scene conduct, supporting emergency services, informing the public and keeping UK skies safe.

About the author

Richard Ryan is a Barrister (Direct Access), Mediator and Chartered Arbitrator based in the UK, specialising in drone and counter-drone law, aviation regulation, and complex commercial disputes. He advises operators, insurers and public bodies on SORA/AAE approvals, BVLOS programmes, privacy/data governance, and risk allocation across the drone ecosystem.

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.

]]> Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/ Tue, 28 Oct 2025 08:05:36 +0000 https://blakistons.co.uk/?p=2597 “`By Richard Ryan, barrister and drone lawyer What the paper actually shows (evidence you can cite) Insurers say risk is intrinsically low; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11) UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it has delayed […]

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

]]> “`By Richard Ryan, barrister and drone lawyer

What the paper actually shows (evidence you can cite)

  • Insurers say risk is intrinsically low; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11)
  • UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it has delayed progress. (pp. 12–13)
  • Net-risk lens: drones remove more risk than they introduce (e.g., falls from height, confined spaces, helicopter exposure). (pp. 14–18)
  • BVLOS doesn’t materially increase risk where well-managed; biggest predictors are location and safety management. (pp. 10–11, 19–22)
  • Incident data 2022–24: commercial operations show zero fatalities across UK, US, EU, Canada, Singapore; only a handful of serious injuries. (Appendix + country sections, pp. 55–61)
  • SORA friction/cost: UK SORA application at SAIL II is £3,495; mitigations/AMC still qualitative ? “OSC-style” uncertainty persists. (p. 35)
  • “Picking winners”: five BVLOS priorities (emergency response, powerlines, maritime SAR, rail, crop spraying). (pp. 6, 25–33)
  • Policy levers: shift to digital PDRAs for repeatable, low-risk scenarios; reuse prior approvals; model on EU PDRAs/Canada’s lower-risk BVLOS. (pp. 36–37; Appendix 1)
  • Emergency services gap: the old standing exemption (E4506) lapsed; routine BVLOS now hard to get—BTP resorted to State Aircraft rules. (p. 27)
  • Comparative table (risk models, UTM status, Remote ID, scale-up reality) explains why the UK feels “high-friction”. (p. 52)

Regulatory & enforcement issues to flag (and build matters around)

  1. Incoherent risk calibration: the UK treats many Specific-category ops as high-risk despite cross-market low incident severity and strong insurer data. (pp. 9–13, 55–57)
  2. Process opacity & cost-burden: SORA mitigations/AMC are qualitative ? inconsistent asks; high fees despite narrow temporal/spatial grants. (p. 35)
  3. Emergency-services capability gap: loss of E4506 creates avoidable delay/risk; forces work-arounds (State Aircraft) rather than transparent PDRA. (p. 27)
  4. AAE not yet a permissioning tool: policy concept ? scalable authorisation path (contrast EU PDRA-G03 for linear infrastructure). (pp. 28–31, 36)
  5. Net-risk inversions: requirements like “observer in a boat” for coastal EVLOS can increase system risk and cost vs. sensor-driven shore control. (p. 21)
  6. Data transparency: the UK has many “record-only” entries; EU public access is patchy; hard for operators/insurers to benchmark safety cases publicly. (pp. 54–61)

Practical exposure points for stakeholders

  • Insurers: common declinature trip-wires—ops outside the authorisation envelope; poor log preservation; weak maintenance/firmware governance. (pp. 9–11, 35–36)
  • Operators/pilots: SORA drift, local land-use limitations, and fragmented permissions across linear corridors; evidence-pack discipline needed. (pp. 28–31, 35–36, 56–57)
  • Associations/community: need bilingual templates/FAQs and incident learning loops; emphasise the airspace vs land-use distinction to reduce friction. (inferred)
  • Public bodies (blue-light, MCA, NR, utilities): proven benefits blocked by bespoke approvals—strong case for sector PDRA playbooks. (pp. 26–33, 36)

What this means for drone pilots, operators, and companies

As a drone lawyer, my reading of the PwC paper is that the safety record increasingly supports predictable, rules-based authorisations, but the UK still applies bespoke processes that create delay, cost and legal uncertainty. The winners will be those who treat compliance as an operational capability, not a paperwork chore.

Implications for Drone Pilots

  • Documentation is defence: retain native telemetry, app/controller logs, and pre-flight risk assessments. These are crucial in insurer claims and any CAA inquiry.
  • VLOS/BVLOS discipline: be explicit about how VLOS was maintained (or the BVLOS mitigations used). Ambiguity here is a common enforcement and insurance pain point.
  • Privacy on site: where people are identifiable, prepare a simple lawful-basis note and signage plan; it reduces complaint/escalation risk significantly.

Implications for Operators

  • Align your OA/ops manual with SORA and AAE logic: show how mitigations reduce both air and ground risk. Clear mapping cuts questions and accelerates approvals.
  • Design for repeatability: build PDRA-ready evidence packs for your most common jobs (e.g., rail/powerline corridors) so each new mission is a variation, not a reinvention.
  • Insurance resilience: standardise maintenance/firmware baselines and battery care logs; many declinatures stem from gaps here, not from the incident itself.
  • Contracts that reflect reality: flowing down responsibilities to subcontractors (airworthiness, data protection, incident reporting) reduces exposure and smooths procurement.

Implications for Drone Companies & Enterprise Users

  • Board-level accountability: appoint a named senior responsible owner (SRO) for UAS operations with decision logs—critical if decisions are later examined in court or by regulators.
  • Data governance as an asset: implement DPIAs where warranted, role-based access to imagery, retention/deletion schedules, and breach protocols. This increases tender scores and reduces enforcement risk.
  • Public value narrative: quantify how drone tasks remove traditional risks (work at height, road possessions, helicopter hours). This “net-risk” case supports proportional, scalable permissions.

Where legal support helps, assists, and mitigates

  • Approvals & permissions: structuring SORA/AAE applications with proportional mitigations, re-using prior evidence, and narrowing scope to reduce fees and conditions.
  • Policy & appeals: challenging irrational or net-risk-increasing conditions; seeking clarifications; and preparing proportionate alternatives that the regulator can accept.
  • Privacy & data: lawful-basis memos, DPIAs, signage/LLN templates, and response playbooks for complaints or subject access requests.
  • Insurance & claims: coverage mapping, notification strategy, and evidence preservation to avoid declinature; subrogation prospects where third parties contributed to loss.
  • Contracts: allocating risk cleanly across clients, operators and subcontractors (indemnities, limitation, IP/data ownership, incident reporting).

Bottom line: the sector is safe and maturing. Those who can demonstrate their risk controls, evidence compliance, and standardise approvals will grow fastest—with fewer legal shocks along the way.

Talking points for meetings & panels

  • Same safety, slower UK growth: insurers and incident data show low intrinsic risk—authorisations should be predictable and prescriptive, not bespoke. (pp. 9–13, 36–37)
  • Digital PDRAs now: for repeatable BVLOS (powerlines/rail/SAR/maritime/agri)—reuse evidence from prior OSCs; mirror EU PDRA/Canada logic. (pp. 25–33, 36)
  • Emergency drones need an emergency rulebook: the E4506 gap is pushing forces into State Aircraft work-arounds. (p. 27)
  • Incident reality: zero fatalities in 2022–24 across major markets; claims are mainly minor property/equipment—calibrate conditions accordingly. (pp. 55–61; pp. 9–11)

About the Author

Richard Ryan is a Barrister (Direct Access), Mediator and Chartered Arbitrator based in the UK, specialising in drone and counter-drone law, aviation regulation, and complex commercial disputes. He advises operators, insurers and public bodies on SORA/AAE approvals, BVLOS programmes, privacy/data governance, and risk allocation across the drone ecosystem.

“`

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

]]> Analysis and Recommendations on CAP 3040 | First Edition https://blakistons.co.uk/analysis-and-recommendations-on-cap-3040-first-edition/ Wed, 06 Nov 2024 13:38:21 +0000 https://blakistons.co.uk/?p=2476 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 […]

The post Analysis and Recommendations on CAP 3040 | First Edition 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.

]]>