<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Regulations and Compliance Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/regulations-and-compliance/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/regulations-and-compliance/</link>
	<description>Drone Law</description>
	<lastBuildDate>Mon, 06 Jul 2026 09:42:00 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</title>
		<link>https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 06 Jul 2026 09:42:00 +0000</pubDate>
				<category><![CDATA[AI and Drone Technology]]></category>
		<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[AI Technology]]></category>
		<category><![CDATA[Airspace Legislation]]></category>
		<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA) Policies]]></category>
		<category><![CDATA[Counter-Drone Technology]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Defence Procurement]]></category>
		<category><![CDATA[Defence Technology]]></category>
		<category><![CDATA[Defense Innovation]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[International Drone Policies]]></category>
		<category><![CDATA[International Drone Regulations]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[Technology and Warfare]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Defence Policy]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Aerospace Law]]></category>
		<category><![CDATA[Airworthiness]]></category>
		<category><![CDATA[Article 36]]></category>
		<category><![CDATA[artificial intelligence]]></category>
		<category><![CDATA[BAE Systems]]></category>
		<category><![CDATA[British Army]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[Callen-Lenz]]></category>
		<category><![CDATA[Counter Drone]]></category>
		<category><![CDATA[counter-UAS]]></category>
		<category><![CDATA[Defence AI]]></category>
		<category><![CDATA[defence technology]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[drone regulation]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Export Controls]]></category>
		<category><![CDATA[Hybrid Navy]]></category>
		<category><![CDATA[Law of Armed Conflict]]></category>
		<category><![CDATA[Maritime Operations]]></category>
		<category><![CDATA[Maritime Security]]></category>
		<category><![CDATA[Military Aviation]]></category>
		<category><![CDATA[military drones]]></category>
		<category><![CDATA[Military Innovation]]></category>
		<category><![CDATA[NATO]]></category>
		<category><![CDATA[Naval Aviation]]></category>
		<category><![CDATA[Nyan]]></category>
		<category><![CDATA[One-Way Effectors]]></category>
		<category><![CDATA[Project Vantage]]></category>
		<category><![CDATA[Royal Navy]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UAV]]></category>
		<category><![CDATA[UK AI]]></category>
		<category><![CDATA[UK defence]]></category>
		<category><![CDATA[Uncrewed Aircraft Systems]]></category>
		<category><![CDATA[Weapons Review]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2698</guid>

					<description><![CDATA[<p>Drone Law &#124; Counter-UAS &#124; Defence AI &#124; 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, [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/">Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="drone-law-blog">
<p><strong>Drone Law | Counter-UAS | Defence AI | One-Way Effectors</strong></p>
<p><strong>Summary:</strong> 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.</p>
<h2>1. Why the Nyan Trial Matters</h2>
<p>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.</p>
<p>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.</p>
<h2>2. From Drone Novelty to Combat Mass</h2>
<p>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.</p>
<p>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.</p>
<h2>3. Autonomy: The Legal Question Is What the Machine Decides</h2>
<p>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.</p>
<p>Commanders and lawyers should ask:</p>
<ul>
<li>Does the system merely navigate to a human-selected target?</li>
<li>Does it detect, classify, prioritise or select targets?</li>
<li>Can it be retasked, recalled, aborted or terminated after launch?</li>
<li>What happens if GPS is jammed, spoofed or degraded?</li>
<li>What mission data and operator decisions are recorded?</li>
</ul>
<p>Those questions determine whether the system can be used consistently with distinction, proportionality, precautions in attack and applicable rules of engagement.</p>
<h2>4. Article 36 Weapons Review</h2>
<p>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.</p>
<p>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.</p>
<h2>5. EU AI Act and UK AI Standards</h2>
<p>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.</p>
<p>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.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Governance Area</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">EU AI Act Benchmark</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">UK / MOD Equivalent</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Application to One-Way Effectors</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Lifecycle risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Safety, security and robustness</td>
<td style="border: 1px solid #000; padding: 8px;">Hazard logs for navigation failure, lost link, spoofing, target-data error and launch failure.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Technical documentation</td>
<td style="border: 1px solid #000; padding: 8px;">Technical file and system description</td>
<td style="border: 1px solid #000; padding: 8px;">Accountability and governance</td>
<td style="border: 1px solid #000; padding: 8px;">Configuration records for airframe, launcher, software, payload and mission-planning tools.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Record-keeping</td>
<td style="border: 1px solid #000; padding: 8px;">Automatic logging</td>
<td style="border: 1px solid #000; padding: 8px;">Transparency and explainability</td>
<td style="border: 1px solid #000; padding: 8px;">Mission logs, operator decisions, software versions, AI outputs and telemetry retention.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Human oversight</td>
<td style="border: 1px solid #000; padding: 8px;">Human control and intervention</td>
<td style="border: 1px solid #000; padding: 8px;">Human-centricity and responsibility</td>
<td style="border: 1px solid #000; padding: 8px;">Clear authority for launch, retask, abort, termination and post-strike review.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Cyber resilience</td>
<td style="border: 1px solid #000; padding: 8px;">Accuracy, robustness and cybersecurity</td>
<td style="border: 1px solid #000; padding: 8px;">Reliability and security</td>
<td style="border: 1px solid #000; padding: 8px;">Testing against jamming, spoofing, adversarial inputs, cyber compromise and degraded environments.</td>
</tr>
</tbody>
</table>
<h2>6. Maritime Launch Changes the Legal Burden</h2>
<p>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.</p>
<p>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.</p>
<h2>7. The Counter-UAS Mirror</h2>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h2>8. Export Controls and Procurement Risk</h2>
<p>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.</p>
<p>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.</p>
<h2>9. Bottom Line</h2>
<p>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.</p>
<p>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.</p>
<hr />
<h2>About the Author</h2>
<p><strong>Richard Ryan</strong> 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.</p>
<p><em>This article is general legal commentary and does not constitute legal advice.</em></p>
</div>
<p>The post <a href="https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/">Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title></title>
		<link>https://blakistons.co.uk/2673-2/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Wed, 03 Jun 2026 16:49:56 +0000</pubDate>
				<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Autonomous Systems in Aviation]]></category>
		<category><![CDATA[Aviation Innovation]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Counter-Drone Technology]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Defence Technology]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Future Trends]]></category>
		<category><![CDATA[Government Reports]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Legal Cases]]></category>
		<category><![CDATA[Legal Challenges]]></category>
		<category><![CDATA[Legal Challenges in Drone Operations]]></category>
		<category><![CDATA[Legal Compliance]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Legal Investigations]]></category>
		<category><![CDATA[Local Government Policies]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[operational guidelines]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Compliance - Focuses on the importance of adherence to regulatory guidelines and consequences of violations.]]></category>
		<category><![CDATA[Regulatory Compliance - Includes insights on compliance with FAA]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Defence Policy]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[Wireless Telegraphy Act]]></category>
		<category><![CDATA[air and missile defence]]></category>
		<category><![CDATA[Air Traffic Management and Unmanned Aircraft Act 2021]]></category>
		<category><![CDATA[Article 51 self defence]]></category>
		<category><![CDATA[Barakah nuclear plant]]></category>
		<category><![CDATA[Blakiston’s Chambers]]></category>
		<category><![CDATA[C-UAS]]></category>
		<category><![CDATA[Chornobyl drone strike]]></category>
		<category><![CDATA[counter drone policy]]></category>
		<category><![CDATA[counter uncrewed systems]]></category>
		<category><![CDATA[Counter-Unmanned Aircraft Strategy 2019]]></category>
		<category><![CDATA[critical national infrastructure]]></category>
		<category><![CDATA[Defence Drone Strategy]]></category>
		<category><![CDATA[drone defence]]></category>
		<category><![CDATA[drone jamming law]]></category>
		<category><![CDATA[Iran drone attacks]]></category>
		<category><![CDATA[NATO integrated air and missile defence]]></category>
		<category><![CDATA[NPSA]]></category>
		<category><![CDATA[Operation Spider's Web]]></category>
		<category><![CDATA[RAF Akrotiri]]></category>
		<category><![CDATA[Richard Ryan barrister]]></category>
		<category><![CDATA[Strategic Defence Review 2025]]></category>
		<category><![CDATA[UK counter drone strategy]]></category>
		<category><![CDATA[UK defence policy]]></category>
		<category><![CDATA[Ukraine drone warfare]]></category>
		<category><![CDATA[Wireless Telegraphy Act 2006]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2673</guid>

					<description><![CDATA[<p>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&#8217;s Chambers &#183; 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 [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/2673-2/"></a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="cuas-whitepaper">
<style>
.cuas-whitepaper{max-width:820px;margin:0 auto;font-family:Georgia,"Times New Roman",serif;color:#1a1a2e;line-height:1.6;}
.cuas-whitepaper .wp-kicker{color:#b23a48;font-weight:bold;letter-spacing:.08em;font-size:.8rem;text-transform:uppercase;font-family:Arial,Helvetica,sans-serif;}
.cuas-whitepaper h1{font-size:2.4rem;color:#14213d;margin:.1em 0 .15em;}
.cuas-whitepaper .wp-sub{font-style:italic;font-size:1.25rem;color:#444;border-bottom:3px solid #14213d;padding-bottom:.5em;margin-bottom:1em;}
.cuas-whitepaper .wp-meta{color:#666;font-size:.95rem;margin-bottom:1.2em;}
.cuas-whitepaper .wp-note{background:#f4f6fa;border-left:6px solid #14213d;padding:.8em 1em;font-style:italic;font-size:.95rem;margin:1.2em 0;}
.cuas-whitepaper .wp-authornote{background:#fbfbfd;border:1px solid #d8dde8;border-radius:8px;padding:.8em 1em;font-size:.92rem;margin:2em 0 1em;color:#333;}
.cuas-whitepaper h2{font-size:1.45rem;color:#14213d;margin-top:1.6em;}
.cuas-whitepaper h3{font-size:1.15rem;color:#14213d;font-style:italic;margin-top:1.2em;}
.cuas-whitepaper table{border-collapse:collapse;width:100%;margin:1.2em 0;font-size:.95rem;}
.cuas-whitepaper th{background:#14213d;color:#fff;text-align:left;padding:.55em .7em;border:1px solid #bbb;}
.cuas-whitepaper td{padding:.55em .7em;border:1px solid #bbb;vertical-align:top;}
.cuas-whitepaper tbody tr:nth-child(odd){background:#eef1f6;}
.cuas-whitepaper sup a{color:#14213d;text-decoration:none;font-weight:bold;}
.cuas-whitepaper ol{padding-left:1.3em;}
.cuas-whitepaper ol li{margin-bottom:.7em;}
.cuas-whitepaper .wp-footnotes{margin-top:2em;border-top:1px solid #ccc;padding-top:1em;font-size:.82rem;line-height:1.45;color:#333;}
.cuas-whitepaper .wp-footnotes ol{padding-left:1.4em;}
.cuas-whitepaper .wp-footnotes li{margin-bottom:.5em;word-break:break-word;}
.cuas-whitepaper .wp-footnotes a{color:#1f5fa8;}
</style>
<p class="wp-kicker">White Paper</p>
<h1>Beyond 2019</h1>
<p class="wp-sub">A New Counter Uncrewed Systems and Air Threat Resilience Strategy for the United Kingdom, After Ukraine and Iran</p>
<p class="wp-meta">By Mr Richard Ryan, Barrister, Blakiston&rsquo;s Chambers &middot; June 2026</p>
<div class="wp-note"><strong>Status and method.</strong> This paper relies on primary and official sources, supplemented by reputable reporting for incident chronology. All facts are verified as at 2&nbsp;June&nbsp;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.</div>
<p><strong>The United Kingdom&rsquo;s published national counter drone policy; the <em>UK Counter-Unmanned Aircraft Strategy</em>, presented to Parliament as Command Paper 187 on 21&nbsp;October&nbsp;2019<sup id="fnref-1"><a href="#fn-1">[1]</a></sup>; is materially out of date as a strategic document.</strong> 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.</p>
<p>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.<sup id="fnref-2"><a href="#fn-2">[2]</a></sup> 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.</p>
<p>Subsequent UK documents do not update the 2019 strategy; they work around it. The Defence Drone Strategy (2024),<sup id="fnref-3"><a href="#fn-3">[3]</a></sup> the Strategic Defence Review 2025,<sup id="fnref-4"><a href="#fn-4">[4]</a></sup> NPSA&rsquo;s site specific guidance,<sup id="fnref-5"><a href="#fn-5">[5]</a></sup> and the Ministry of Defence&rsquo;s 2026 pursuit of new defeat powers at military sites<sup id="fnref-6"><a href="#fn-6">[6]</a></sup> 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 <strong>Counter Uncrewed Systems and Air Threat Resilience Strategy</strong>, supported by a consolidated legal code for detection, disruption and defeat, and by an annual ministerial statement to Parliament.</p>
<h2>1.&nbsp;&nbsp;The threat has become a strategic mass system</h2>
<p>The central lesson of 2024&ndash;2026 is not that drones have become more common but that they have become a strategic mass system &mdash; a consumable class of munition and sensor used for saturation, decoying, attrition of intelligence assets, target acquisition and the deliberate erosion of a defender&rsquo;s cost exchange ratio. On the night of 2&nbsp;June&nbsp;2026, Ukraine&rsquo;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.<sup id="fnref-7"><a href="#fn-7">[7]</a></sup><sup id="fnref-8"><a href="#fn-8">[8]</a></sup> Single salvos now routinely exceed several hundred drones.</p>
<p>Critical infrastructure has been directly affected. In February&nbsp;2025 a Russian Geran-2 (Shahed type) drone struck the New Safe Confinement over Chornobyl&rsquo;s reactor four;<sup id="fnref-9"><a href="#fn-9">[9]</a></sup> by December&nbsp;2025 the International Atomic Energy Agency assessed that the structure had lost its primary safety functions, including confinement.<sup id="fnref-10"><a href="#fn-10">[10]</a></sup> In May&nbsp;2026 a drone strike caused a fire at an electrical generator on the perimeter of the United Arab Emirates&rsquo; Barakah nuclear plant; a civilian reactor site; leaving one unit running on emergency diesel generators.<sup id="fnref-11"><a href="#fn-11">[11]</a></sup><sup id="fnref-12"><a href="#fn-12">[12]</a></sup></p>
<p>The homeland and deployed force dimension is now concrete for the United Kingdom. In early March&nbsp;2026 a Shahed type drone struck a runway at RAF&nbsp;Akrotiri in Cyprus; a British Sovereign Base Area; causing limited damage,<sup id="fnref-13"><a href="#fn-13">[13]</a></sup> and the UK flew defensive sorties and, where requested, acted in the collective self defence of regional allies.<sup id="fnref-14"><a href="#fn-14">[14]</a></sup> Ukraine&rsquo;s Operation Spider&rsquo;s Web (June&nbsp;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.<sup id="fnref-15"><a href="#fn-15">[15]</a></sup></p>
<h3>A necessary qualification</h3>
<p>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.</p>
<h2>2.&nbsp;&nbsp;Why the 2019 strategy can no longer stand alone</h2>
<table>
<thead>
<tr>
<th>2019 provision</th>
<th>Current reality</th>
<th>Assessment</th>
</tr>
</thead>
<tbody>
<tr>
<td>Focus on the highest harm illegal use of small aerial drones in the UK.</td>
<td>Concern now extends to defence sites, CNI in crisis or conflict, and state launched drones and missiles.</td>
<td>Too narrow as a national frame.</td>
</tr>
<tr>
<td>Short planning horizon from 2019.</td>
<td>Document is c.&nbsp;6.6 years old; NPSA requires regular review because methods change quickly.</td>
<td>Formally stale; refresh overdue.</td>
</tr>
<tr>
<td>Empower police and responders.</td>
<td>MoD now seeks its own defeat powers at Defence sites because police only authorities are inadequate.</td>
<td>Institutionally outdated.</td>
</tr>
<tr>
<td>Aerial drones only.</td>
<td>New Defence policy extends to land and maritime uncrewed systems.</td>
<td>Conceptually outdated.</td>
</tr>
<tr>
<td>Counter drone as a discrete problem.</td>
<td>NATO now treats small UAS through hypersonic missiles as one integrated air and missile defence continuum.<sup id="fnref-16"><a href="#fn-16">[16]</a></sup></td>
<td>The silo is no longer tenable.</td>
</tr>
</tbody>
</table>
<p>The clearest institutional signal came in February&nbsp;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.<sup id="fnref-6"><a href="#fn-6">[6]</a></sup> When the armed forces must legislate around a framework built for policing to protect their own bases, that framework has expired.</p>
<h2>3.&nbsp;&nbsp;The legal framework: developed, but fragmented</h2>
<p>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&nbsp;93 of the Police Act 1997 to facilitate authorisations for certain counter drone measures.<sup id="fnref-17"><a href="#fn-17">[17]</a></sup><sup id="fnref-18"><a href="#fn-18">[18]</a></sup> In the civil regime, the Civil Aviation Authority&rsquo;s Direct Remote&nbsp;ID requirements came into force on 1&nbsp;January&nbsp;2026 for UK1, UK2, UK3, UK5 and UK6 class drones, with extension to most drones carrying a camera from 1&nbsp;January&nbsp;2028.<sup id="fnref-19"><a href="#fn-19">[19]</a></sup></p>
<p>Yet lawful defeat is markedly harder than detection. Operational use of a jammer is generally an offence under section&nbsp;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.<sup id="fnref-20"><a href="#fn-20">[20]</a></sup> Government is separately examining the enforcement framework around jammers.<sup id="fnref-21"><a href="#fn-21">[21]</a></sup> Kinetic or electronic interference may amount to unlawful property or wireless interference absent proper authorisation; the Act&rsquo;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.</p>
<p>Overseas action sits within international law. The Government&rsquo;s March&nbsp;2026 legal position on Iranian regional attacks invoked the collective self defence of allies under Article&nbsp;51 of the UN Charter, subject to necessity and proportionality and Security Council notification.<sup id="fnref-14"><a href="#fn-14">[14]</a></sup> 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.<sup id="fnref-22"><a href="#fn-22">[22]</a></sup></p>
<h2>4.&nbsp;&nbsp;Recommendations</h2>
<p>The Government should replace the 2019 strategy with a new instrument covering the whole of government. Five propositions should anchor it:</p>
<ol>
<li><strong>Integrate, do not append.</strong> 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&rsquo;s integrated air and missile defence framework.<sup id="fnref-16"><a href="#fn-16">[16]</a></sup></li>
<li><strong>Consolidate the law.</strong> 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 &mdash; differentiating urban areas, prisons, airports, defence sites and overseas operations.</li>
<li><strong>Adopt a layered baseline that is alert to cost.</strong> Use NPSA&rsquo;s site specific, threat informed model as the national spine,<sup id="fnref-23"><a href="#fn-23">[23]</a></sup> 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.</li>
<li><strong>Treat industry and export control as readiness.</strong> 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.</li>
<li><strong>Compliance and oversight by design.</strong> 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.</li>
</ol>
<h2>5.&nbsp;&nbsp;Conclusion</h2>
<p>None of this discards the 2019 strategy&rsquo;s best inheritance; its insistence on layered intervention over an optimism founded on gadgets, an instinct NPSA&rsquo;s later guidance has only reinforced.<sup id="fnref-5"><a href="#fn-5">[5]</a></sup> 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.</p>
<div class="wp-authornote"><strong>About the author.</strong> Mr Richard Ryan is a barrister of Blakiston&rsquo;s Chambers..</div>
<div class="wp-footnotes">
<h2 style="font-size:1.15rem;">Footnotes &amp; sources (23)</h2>
<ol>
<li id="fn-1">UK Counter-Unmanned Aircraft Strategy, CP 187, presented to Parliament 21 October 2019 (GOV.UK). <a href="https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy" target="_blank" rel="noopener noreferrer">https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy</a> <a href="#fnref-1" aria-label="Back to text">&#8617;</a></li>
<li id="fn-2">UK Counter-Unmanned Aircraft Strategy (HTML version), GOV.UK, published 21 October 2019. <a href="https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy/table" target="_blank" rel="noopener noreferrer">https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy/table</a> <a href="#fnref-2" aria-label="Back to text">&#8617;</a></li>
<li id="fn-3">Defence Drone Strategy — the UK’s approach to Defence Uncrewed Systems, GOV.UK, published 22 February 2024. <a href="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" target="_blank" rel="noopener noreferrer">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</a> <a href="#fnref-3" aria-label="Back to text">&#8617;</a></li>
<li id="fn-4">The Strategic Defence Review 2025 — Making Britain Safer, GOV.UK, published 2 June 2025. <a href="https://www.gov.uk/government/publications/the-strategic-defence-review-2025-making-britain-safer-secure-at-home-strong-abroad" target="_blank" rel="noopener noreferrer">https://www.gov.uk/government/publications/the-strategic-defence-review-2025-making-britain-safer-secure-at-home-strong-abroad</a> <a href="#fnref-4" aria-label="Back to text">&#8617;</a></li>
<li id="fn-5">NPSA, “Counter Uncrewed Aerial Systems (C-UAS)” specialised guidance. <a href="https://www.npsa.gov.uk/specialised-guidance/uncrewed-aerial-systems/counter-uncrewed-aerial-systems-c-uas" target="_blank" rel="noopener noreferrer">https://www.npsa.gov.uk/specialised-guidance/uncrewed-aerial-systems/counter-uncrewed-aerial-systems-c-uas</a> <a href="#fnref-5" aria-label="Back to text">&#8617;</a></li>
<li id="fn-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. <a href="https://www.gov.uk/government/news/new-powers-for-defence-personnel-to-defeat-drones-following-doubling-of-incidents-near-bases" target="_blank" rel="noopener noreferrer">https://www.gov.uk/government/news/new-powers-for-defence-personnel-to-defeat-drones-following-doubling-of-incidents-near-bases</a> <a href="#fnref-6" aria-label="Back to text">&#8617;</a></li>
<li id="fn-7">“Russia launched 656 drones and 73 missiles” — figures attributed to the Ukrainian Air Force; CBS News, 2 June 2026. <a href="https://www.cbsnews.com/news/russia-ukraine-war-major-attacks-missile-drone-kill-several-wound-dozens/" target="_blank" rel="noopener noreferrer">https://www.cbsnews.com/news/russia-ukraine-war-major-attacks-missile-drone-kill-several-wound-dozens/</a> <a href="#fnref-7" aria-label="Back to text">&#8617;</a></li>
<li id="fn-8">NPR, “Russian attack on Ukraine kills at least 14”, 2 June 2026 (corroborating launch and interception figures). <a href="https://www.npr.org/2026/06/02/nx-s1-5844071/russian-attack-ukraine" target="_blank" rel="noopener noreferrer">https://www.npr.org/2026/06/02/nx-s1-5844071/russian-attack-ukraine</a> <a href="#fnref-8" aria-label="Back to text">&#8617;</a></li>
<li id="fn-9">Chornobyl New Safe Confinement struck by a Geran-2 (Shahed type) drone, 14 February 2025: Greenpeace Ukraine mission report, 20 March 2025. <a href="https://www.greenpeace.org/ukraine/en/news/3504/fifty-percent-of-north-roof-structure-of-chornobyl-new-safe-confinement-shelter-severely-damaged/" target="_blank" rel="noopener noreferrer">https://www.greenpeace.org/ukraine/en/news/3504/fifty-percent-of-north-roof-structure-of-chornobyl-new-safe-confinement-shelter-severely-damaged/</a> <a href="#fnref-9" aria-label="Back to text">&#8617;</a></li>
<li id="fn-10">IAEA assessment (December 2025) that the New Safe Confinement had lost its primary safety functions, including confinement (reported via United24/Reuters). <a href="https://united24media.com/latest-news/iaea-chornobyls-new-safe-confinement-can-no-longer-contain-radiation-after-russian-drone-attack-14067" target="_blank" rel="noopener noreferrer">https://united24media.com/latest-news/iaea-chornobyls-new-safe-confinement-can-no-longer-contain-radiation-after-russian-drone-attack-14067</a> <a href="#fnref-10" aria-label="Back to text">&#8617;</a></li>
<li id="fn-11">Drone strike causing a generator fire at the UAE’s Barakah nuclear plant, 17 May 2026: Al Jazeera, 17 May 2026. <a href="https://www.aljazeera.com/news/2026/5/17/drone-strike-sparks-fire-at-uaes-barakah-nuclear-power-plant" target="_blank" rel="noopener noreferrer">https://www.aljazeera.com/news/2026/5/17/drone-strike-sparks-fire-at-uaes-barakah-nuclear-power-plant</a> <a href="#fnref-11" aria-label="Back to text">&#8617;</a></li>
<li id="fn-12">NPR, “Drone strikes UAE nuclear plant”, 18 May 2026 (IAEA: one reactor on emergency diesel generators). <a href="https://www.npr.org/2026/05/18/g-s1-122534/drone-strikes-uae-nuclear-plant" target="_blank" rel="noopener noreferrer">https://www.npr.org/2026/05/18/g-s1-122534/drone-strikes-uae-nuclear-plant</a> <a href="#fnref-12" aria-label="Back to text">&#8617;</a></li>
<li id="fn-13">Reuters, “Iranian-made drone hits British air base in Cyprus” (RAF Akrotiri runway strike, limited damage), 2 March 2026. <a href="https://www.aol.com/articles/iranian-made-drone-hits-british-121630466.html" target="_blank" rel="noopener noreferrer">https://www.aol.com/articles/iranian-made-drone-hits-british-121630466.html</a> <a href="#fnref-13" aria-label="Back to text">&#8617;</a></li>
<li id="fn-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. <a href="https://www.gov.uk/government/news/summary-of-the-uk-government-legal-position-the-legality-of-defensive-action-in-respect-of-iranian-regional-attacks" target="_blank" rel="noopener noreferrer">https://www.gov.uk/government/news/summary-of-the-uk-government-legal-position-the-legality-of-defensive-action-in-respect-of-iranian-regional-attacks</a> <a href="#fnref-14" aria-label="Back to text">&#8617;</a></li>
<li id="fn-15">CSIS, “How Ukraine’s Operation Spider’s Web Redefines Asymmetric Warfare” (117 drones; 40+ aircraft struck; some AI assisted guidance). <a href="https://www.csis.org/analysis/how-ukraines-spider-web-operation-redefines-asymmetric-warfare" target="_blank" rel="noopener noreferrer">https://www.csis.org/analysis/how-ukraines-spider-web-operation-redefines-asymmetric-warfare</a> <a href="#fnref-15" aria-label="Back to text">&#8617;</a></li>
<li id="fn-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”). <a href="https://www.nato.int/cps/en/natohq/official_texts_233084.htm" target="_blank" rel="noopener noreferrer">https://www.nato.int/cps/en/natohq/official_texts_233084.htm</a> <a href="#fnref-16" aria-label="Back to text">&#8617;</a></li>
<li id="fn-17">Air Traffic Management and Unmanned Aircraft Act 2021 (c. 12), legislation.gov.uk. <a href="https://www.legislation.gov.uk/ukpga/2021/12/contents/enacted" target="_blank" rel="noopener noreferrer">https://www.legislation.gov.uk/ukpga/2021/12/contents/enacted</a> <a href="#fnref-17" aria-label="Back to text">&#8617;</a></li>
<li id="fn-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). <a href="https://www.legislation.gov.uk/ukpga/2021/12/pdfs/ukpgaen_20210012_en.pdf" target="_blank" rel="noopener noreferrer">https://www.legislation.gov.uk/ukpga/2021/12/pdfs/ukpgaen_20210012_en.pdf</a> <a href="#fnref-18" aria-label="Back to text">&#8617;</a></li>
<li id="fn-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. <a href="https://www.caa.co.uk/drones/regulations-consultations-and-policy-programmes/policy-programmes/remote-id-rid/" target="_blank" rel="noopener noreferrer">https://www.caa.co.uk/drones/regulations-consultations-and-policy-programmes/policy-programmes/remote-id-rid/</a> <a href="#fnref-19" aria-label="Back to text">&#8617;</a></li>
<li id="fn-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. <a href="https://www.ofcom.org.uk/spectrum/frequencies/gps-jamming-exercises" target="_blank" rel="noopener noreferrer">https://www.ofcom.org.uk/spectrum/frequencies/gps-jamming-exercises</a> <a href="#fnref-20" aria-label="Back to text">&#8617;</a></li>
<li id="fn-21">DSIT, “Possession of radiofrequency jammers and the relevant legal framework” (call for evidence), GOV.UK, 2026. <a href="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" target="_blank" rel="noopener noreferrer">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</a> <a href="#fnref-21" aria-label="Back to text">&#8617;</a></li>
<li id="fn-22">ICRC, “FAQ: international humanitarian law and the use of drones in armed conflict” (distinction, proportionality, precaution). <a href="https://www.icrc.org/en/article/faq-international-humanitarian-law-drones-armed-conflict" target="_blank" rel="noopener noreferrer">https://www.icrc.org/en/article/faq-international-humanitarian-law-drones-armed-conflict</a> <a href="#fnref-22" aria-label="Back to text">&#8617;</a></li>
<li id="fn-23">NPSA, “Countering Threats from Uncrewed Aerial Systems — Making Your Site Ready”. <a href="https://www.npsa.gov.uk/resources/c-uas-making-your-site-ready" target="_blank" rel="noopener noreferrer">https://www.npsa.gov.uk/resources/c-uas-making-your-site-ready</a> <a href="#fnref-23" aria-label="Back to text">&#8617;</a></li>
</ol>
</div>
</div>
<p>The post <a href="https://blakistons.co.uk/2673-2/"></a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft</title>
		<link>https://blakistons.co.uk/the-drone-in-the-room-what-the-ai-acts-august-deadline-actually-means-for-unmanned-aircraft/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 01 Jun 2026 11:14:30 +0000</pubDate>
				<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[AI Technology]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[Counter-Drone Technology]]></category>
		<category><![CDATA[Data Privacy]]></category>
		<category><![CDATA[Data Protection and Privacy]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Defence Procurement]]></category>
		<category><![CDATA[Defence Technology]]></category>
		<category><![CDATA[Defense Innovation]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Ethical Considerations in AI]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[European Union Policy Updates]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Future Trends]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Legal Compliance]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Legal Issues in Technology]]></category>
		<category><![CDATA[Legal Updates]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[Tech Law and Regulation]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[AI compliance]]></category>
		<category><![CDATA[Article 50]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[biometric categorisation]]></category>
		<category><![CDATA[counter-UAS]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[drone regulation]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[high-risk AI systems]]></category>
		<category><![CDATA[regulatory sandboxes]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[Unmanned Aircraft]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2661</guid>

					<description><![CDATA[<p>There&#8217;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 &#8220;AI Act&#8221; and &#8220;drones&#8221; in the same breath and assume the two slot neatly together; that the great [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/the-drone-in-the-room-what-the-ai-acts-august-deadline-actually-means-for-unmanned-aircraft/">The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>There&rsquo;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 &ldquo;AI Act&rdquo; and &ldquo;drones&rdquo; 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&rsquo;s counter-UAS system crosses a line. It doesn&rsquo;t. And the gap between what people assume and what the text actually says is where most of my work now lives.</p>
<p>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.</p>
<h2>The autonomy problem nobody wants to define</h2>
<p>Start with the thing that makes drones legally interesting in the first place: autonomy is a spectrum, and the law hates spectrums.</p>
<p>A consumer quadcopter holding position in a breeze is running control loops that would have been called &ldquo;artificial intelligence&rdquo; 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, &ldquo;follow me&rdquo; tracking, swarm coordination, automated target recognition that merely flags rather than decides. Where on that spectrum does a drone become an &ldquo;AI system&rdquo; in the meaning of Article 3?</p>
<p>This matters enormously and almost nobody asks it cleanly. The Act&rsquo;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&rsquo;t. I have sat across the table from engineers who insist their navigation system is &ldquo;just maths,&rdquo; and they&rsquo;re not entirely wrong, but &ldquo;just maths&rdquo; is also a fair description of every neural network ever trained. The line is not where intuition puts it.</p>
<h2>Why the military carve-out is a trap, not a shield</h2>
<p>Here is where I watch clients relax too early.</p>
<p>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&rsquo;t reach us. Lovely. Except &ldquo;exclusively&rdquo; 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.</p>
<p>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.</p>
<p>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 &ldquo;this is a security tool, leave it alone&rdquo; and &ldquo;this is a high-risk system, document everything&rdquo; will actually get drawn through worked examples. Anyone in this sector who isn&rsquo;t reading those drafts is choosing to be surprised later.</p>
<h2>Article 50 and the drone you can&rsquo;t see</h2>
<p>Now the part that genuinely changes behaviour on the ground.</p>
<p>Article 50&rsquo;s transparency obligations don&rsquo;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.</p>
<p>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&rsquo;s reason for existing and the regulation&rsquo;s reason for existing, and it is going to generate litigation.</p>
<h2>The sandbox that slipped a year</h2>
<p>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.</p>
<p>For most industries that&rsquo;s a footnote. For drones it&rsquo;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&rsquo;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.</p>
<h2>What I&rsquo;m telling clients</h2>
<p>The honest summary I give, stripped of comfort, runs roughly like this. The August date isn&rsquo;t your date; it&rsquo;s aimed at the makers of large general-purpose models, and most drone autonomy doesn&rsquo;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&rsquo;t wait for enforcement to tell you which side of the line you&rsquo;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.</p>
<p>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&rsquo;s abstractions get tested against physical reality. I&rsquo;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.</p>
<hr>
<p><em>This is not legal advice; if you&rsquo;re making compliance decisions about a specific system, get advice tailored to it.</em></p>
<p>About the author<br />
Richard Ryan is a Direct Access Barrister at Blakiston&#8217;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.</p>
<p>The post <a href="https://blakistons.co.uk/the-drone-in-the-room-what-the-ai-acts-august-deadline-actually-means-for-unmanned-aircraft/">The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean</title>
		<link>https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 06 Nov 2025 18:28:20 +0000</pubDate>
				<category><![CDATA[AI and Drone Technology]]></category>
		<category><![CDATA[AI Governance and Ethics]]></category>
		<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[AI Technology]]></category>
		<category><![CDATA[Airspace Legislation]]></category>
		<category><![CDATA[Airspace Management]]></category>
		<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Autonomous Systems in Aviation]]></category>
		<category><![CDATA[Aviation Innovation]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Aviation Security]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Defence Procurement]]></category>
		<category><![CDATA[Defence Technology]]></category>
		<category><![CDATA[Defense Innovation]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[Emerging Technologies]]></category>
		<category><![CDATA[Emerging Technologies in Logistics]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[European Union Policy Updates]]></category>
		<category><![CDATA[Future Trends]]></category>
		<category><![CDATA[Government Reports]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[Law Enforcement]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Legal Challenges]]></category>
		<category><![CDATA[Legal Conflicts]]></category>
		<category><![CDATA[Legal Frameworks]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Legal Updates]]></category>
		<category><![CDATA[Local Government Policies]]></category>
		<category><![CDATA[Local Government Policy]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Public Safety]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance Strategies]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[Risk Assessment & Mitigation]]></category>
		<category><![CDATA[Risk Management and Insurance]]></category>
		<category><![CDATA[Safety and Risk Management - Emphasizes safety protocols]]></category>
		<category><![CDATA[Safety and Security in Aviation]]></category>
		<category><![CDATA[Tech Law and Regulation]]></category>
		<category><![CDATA[Technological Innovations in Drones]]></category>
		<category><![CDATA[Technology and Innovation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Defence Policy]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[autonomous fighters]]></category>
		<category><![CDATA[biometric identification]]></category>
		<category><![CDATA[CE marking]]></category>
		<category><![CDATA[defence law]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[EU aviation law]]></category>
		<category><![CDATA[GA-ASI]]></category>
		<category><![CDATA[GPAI]]></category>
		<category><![CDATA[high-risk AI]]></category>
		<category><![CDATA[International Fighter Conference]]></category>
		<category><![CDATA[manned-unmanned teaming]]></category>
		<category><![CDATA[real-world testing]]></category>
		<category><![CDATA[Rome]]></category>
		<category><![CDATA[UAS]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2624</guid>

					<description><![CDATA[<p>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&#8230; 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 [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/">How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Begin blog content (no title; WordPress provides its own) --></p>
<div>
By Richard Ryan, barrister and drone lawyer </p>
<p><em>How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft — and what the defence carve-outs really mean.</em></p>
<hr />
<h3>In Brief&#8230;</h3>
<ul>
<li><strong>Purely military AI systems are out of scope</strong> of the EU AI Act. If an AI system is <strong>developed or used exclusively for military/defence or national-security purposes</strong>, the Act does not apply. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Dual-use is different.</strong> If the same autonomy stack, sensors or models are marketed or used for <strong>civilian</strong> purposes in the EU (for example, civil UAS, border or law-enforcement tasks), the Act can apply — with stringent duties for “high-risk” systems. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Real-world testing is regulated.</strong> Pre-market R&amp;D is generally excluded, <strong>but real-world testing isn’t</strong> — it requires specific safeguards and registration. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Foundation models (GPAI)</strong> have their own rules from <strong>2 Aug 2025</strong>; the defence carve-out in the Act is written for <strong>AI systems</strong>, not explicitly for <strong>models</strong>. If a model is placed on the EU market generally, the provider’s GPAI obligations can still bite. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<blockquote>
<p><strong>Context:</strong> 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.</p>
</blockquote>
<hr />
<h2>1) First principles: When does the EU AI Act apply?</h2>
<p>The Act has <strong>extraterritorial reach</strong>. 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 <strong>where the AI system’s output is used in the EU</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<p>However, <strong>Article 2(3)</strong> draws a bright line: the Act <strong>does not apply</strong> to <strong>AI systems used exclusively</strong> for <strong>military, defence or national security</strong>. It also does not apply where a system is <strong>not</strong> placed on the EU market but its <strong>output is used in the EU exclusively</strong> for those purposes. Recital 24 reiterates this and clarifies that <strong>non-defence use falls back under the Act</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<p><strong>What this means in Rome:</strong></p>
<ul>
<li>A <strong>closed, defence-only</strong> showcase for European militaries: <strong>out of scope</strong>.</li>
<li>A <strong>civil-use pitch</strong>, civil flight trials, or plans to sell autonomy modules to <strong>EU civilian buyers</strong>: <strong>in scope</strong> (see the high-risk section below). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>2) The key defence carve-outs (and their limits)</h2>
<p><strong>Carve-out #1 — Defence/military:</strong></p>
<blockquote>
<p>“This Regulation shall not apply to AI systems … used exclusively for military, defence or national security purposes.” (Article 2(3))</p>
</blockquote>
<p>Two important nuances:</p>
<ul>
<li><strong>Exclusivity matters.</strong> The moment an autonomy stack or sensor suite is also <strong>marketed or used for civilian</strong> or law-enforcement tasks, the <strong>defence exclusion no longer shields those non-defence uses</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Models vs systems.</strong> The text explicitly excludes <strong>AI systems</strong> for defence; it <strong>does not create an explicit defence exclusion for general-purpose AI models</strong>. If a <strong>GPAI model</strong> is <strong>placed on the EU market</strong>, Chapter V obligations for model providers can still apply — even if one downstream customer is a defence user. (More on GPAI below.) (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>Carve-out #2 — Pre-market R&amp;D:</strong><br />
  R&amp;D <strong>before</strong> placing on the market is generally outside scope, <strong>but real-world testing is not</strong>. Testing in real-world conditions triggers a dedicated regime (for example, registration, time limits, informed consent or special conditions for law enforcement, incident reporting). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<p><strong>Carve-out #3 — Emergency derogations (non-defence):</strong><br />
  For <strong>exceptional public-security reasons</strong> (or imminent threats to life/health), <strong>market surveillance authorities</strong> can authorise <strong>temporary use</strong> of a high-risk AI system <strong>before</strong> 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 <strong>not</strong> a defence-specific carve-out, but it explains emergency deployments outside the military context. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>3) If the defence exclusion doesn’t apply, would autonomous fighters tech be “high-risk”?</h2>
<p>Very likely <strong>yes</strong> — for <strong>civil</strong> variants or dual-use spin-outs:</p>
<ul>
<li><strong>Annex I (product-safety route).</strong> AI that is a <strong>safety component</strong> of products covered by sectoral EU safety laws is <strong>high-risk</strong> where those products need <strong>third-party conformity assessment</strong>. That list <strong>explicitly includes EU civil aviation law (Reg. 2018/1139)</strong> — covering <strong>unmanned aircraft</strong> and their remotely controllable equipment. In a civil-UAS configuration, an autonomy stack acting as a safety component would be regulated as <strong>high-risk</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Annex III (stand-alone uses).</strong> Separate “high-risk” buckets also capture, for example, <strong>remote biometric identification</strong> and other sensitive functions (if and where permitted by Union/national law), <strong>critical infrastructure</strong> safety components, and more. If a fighter-born sensing suite were repurposed for <strong>civil border surveillance</strong> or <strong>public-space identification</strong>, you quickly hit these Annex III categories. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>What “high-risk” demands in practice</strong><br />
  Providers must implement a <strong>risk-management system</strong>, <strong>data governance</strong>, <strong>technical documentation</strong>, <strong>logging</strong>, <strong>transparency/instructions</strong>, <strong>human oversight</strong>, and <strong>accuracy/robustness/cybersecurity</strong> — then pass <strong>conformity assessment</strong>, issue an <strong>EU Declaration of Conformity</strong>, and affix <strong>CE marking</strong>. Deployers also carry duties (for example, monitoring, data relevance, user notification in some cases). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>4) Sensors on show: what about face recognition and other “red lines”?</h2>
<p>The <strong>EU bans</strong> several AI practices outright (from <strong>2 Feb 2025</strong>), including:</p>
<ul>
<li><strong>Untargeted scraping</strong> of facial images to build recognition databases.</li>
<li><strong>Biometric categorisation</strong> inferring sensitive traits (for example, race, political opinions, religion).</li>
<li><strong>Emotion recognition</strong> in workplaces or schools (with narrow safety/medical exceptions).</li>
<li><strong>Predictive “risk assessments”</strong> of criminality based solely on personality traits/profiling.</li>
<li><strong>Real-time remote biometric identification (RBI) in public spaces for law enforcement</strong> — <strong>unless</strong> 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. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>Implication for a trade-show demo:</strong> training a camera on attendees to test <strong>real-time RBI</strong> in a public venue would <strong>likely be unlawful</strong> unless those strict law-enforcement exceptions and procedural safeguards apply — which they typically <strong>will not</strong> at a commercial defence conference. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>5) Real-world testing in the EU (civil or dual-use variants)</h2>
<p>If a provider runs <strong>real-world flight tests</strong> in the EU (outside the defence exclusion), the Act requires — among other things — <strong>registration</strong>, an EU-established entity or <strong>EU legal representative</strong>, limits on <strong>duration</strong> (normally up to six months, extendable once), rules on <strong>informed consent</strong> (with special handling for law-enforcement tests), <strong>qualified oversight</strong>, and the ability to <strong>reverse/ignore</strong> the system’s outputs. <strong>Serious incidents</strong> must be reported promptly. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>6) Foundation models (GPAI): obligations can still attach</h2>
<p>From <strong>2 Aug 2025</strong>, <strong>Chapter V</strong> sets <strong>baseline transparency and copyright-policy duties</strong> for <strong>providers of general-purpose AI models</strong> (with extra obligations if the model presents <strong>systemic risks</strong>). The defence exclusion in Article 2(3) is framed for <strong>AI systems</strong>, not <strong>models</strong>. So, if a foundation model is <strong>placed on the EU market</strong>, the <strong>model provider</strong> can have obligations even if a downstream customer is a defence prime. (Open-source specifics and systemic-risk thresholds also apply.) (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>7) Timelines you need in Rome (as of 6 Nov 2025)</h2>
<ul>
<li><strong>Entry into force:</strong> 1 Aug 2024 (20 days after OJ publication).</li>
<li><strong>Prohibited practices + core chapters (I–II):</strong> apply from <strong>2 Feb 2025</strong>.</li>
<li><strong>GPAI rules (Chapter V), plus other chapters (III §4, VII, XII, and Article 78):</strong> apply from <strong>2 Aug 2025</strong>.</li>
<li><strong>General application:</strong> <strong>2 Aug 2026</strong> (high-risk regime starts to bite broadly).</li>
<li><strong>Article 6(1) Annex III classification trigger &amp; related obligations:</strong> <strong>2 Aug 2027</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>8) Enforcement and penalties</h2>
<ul>
<li>Violating <strong>prohibited practices</strong> (Article 5) can draw fines up to <strong>€35m or 7%</strong> of worldwide annual turnover, whichever is higher.</li>
<li>Other operator obligations can reach <strong>€15m or 3%</strong>; supplying <strong>misleading information</strong> can reach <strong>€7.5m or 1%</strong> (SMEs benefit from caps). Separate fine scales apply to EU institutions. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>9) Practical playbook for IFC attendees</h2>
<p><strong>If you are a defence OEM showing autonomy stacks:</strong></p>
<ol>
<li><strong>Map uses</strong>: Defence-only (excluded) vs <strong>any civil or law-enforcement</strong> pathways (potentially in scope). Document the <strong>exclusivity</strong> of defence deployments if you rely on the carve-out. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>GPAI suppliers</strong>: If you place a <strong>foundation model</strong> on the EU market, expect <strong>Chapter V</strong> duties regardless of defence customers. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>No RBI demos</strong> on the show floor. Those prohibitions already apply in 2025. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Planning EU flight tests</strong> for civil variants? Prepare for <strong>real-world testing</strong> conditions (registration, oversight, incident reporting). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li>For <strong>civil UAS commercialisation</strong>, treat your autonomy as <strong>high-risk</strong> (EASA product-safety route), budget time for <strong>conformity assessment</strong> and <strong>CE marking</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ol>
<p><strong>If you are a European ministry or agency:</strong></p>
<ul>
<li>Distinguish <strong>military operations</strong> (out of scope) from <strong>law-enforcement or border</strong> uses (in scope; watch <strong>RBI</strong> limits and high-risk duties). Consider <strong>Article 46</strong> emergency derogations only in <strong>exceptional</strong> and <strong>documented</strong> cases. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>If you are a civil UAS integrator:</strong></p>
<ul>
<li>Expect the full <strong>high-risk</strong> package (risk management, data governance, human oversight, cybersecurity, logs, conformity assessment, CE). Build compliance into your <strong>system architecture</strong>, <strong>ML pipelines</strong>, <strong>safety cases</strong>, and <strong>ops manuals</strong> from day one. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>10) Quick decision pathway</h2>
<ol>
<li><strong>Is the use exclusively defence or national security?</strong><br />
      Yes: AI <strong>system</strong> is <strong>out of scope</strong>.<br />
      No: continue. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
<li><strong>Is it a civil product or law-enforcement/border use?</strong><br />
      Civil product with safety function (for example, civil UAS): <strong>High-risk</strong> via <strong>Annex I</strong> ? conformity assessment + CE. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)<br />
      Stand-alone sensitive use (for example, RBI, critical infrastructure): <strong>Annex III</strong> high-risk or <strong>Article 5</strong> prohibition applies. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
<li><strong>Is there a GPAI model being placed on the EU market?</strong><br />
      Yes: <strong>Chapter V</strong> duties for <strong>model providers</strong> from <strong>2 Aug 2025</strong>, separate from the defence carve-out for systems. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
<li><strong>Is this pre-market testing?</strong><br />
      <strong>Real-world testing</strong> rules apply (registration, oversight, incident reporting). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
</ol>
<hr />
<h3>Bottom line for “Autonomous Fighters in Rome”</h3>
<ul>
<li>A <strong>military-only</strong> display of GA-ASI’s autonomous fighters is <strong>outside</strong> the AI Act.</li>
<li>Any <strong>civil</strong> spin-off (cargo drones, civil surveillance, airport ops) or <strong>law-enforcement</strong> application in the EU will trigger the Act — often at the <strong>high-risk</strong> level — together with <strong>tight prohibitions</strong> around biometric uses in public spaces. Plan your <strong>compliance architecture</strong> accordingly. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><em>This article is informational and not legal advice. Citations are to the Official Journal text of the <strong>Artificial Intelligence Act (Regulation (EU) 2024/1689)</strong> 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).</em></p>
<hr />
<section aria-label="Author bio">
<p><strong>About the author — Richard Ryan</strong></p>
<p>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.</p>
</section>
</div>
<p><!-- End blog content --></p>
<p>The post <a href="https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/">How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</title>
		<link>https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 06 Nov 2025 17:53:49 +0000</pubDate>
				<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Drone Accidents & Case Studies]]></category>
		<category><![CDATA[Drone Incidents]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Industry Challenges]]></category>
		<category><![CDATA[Drone Industry Concerns]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Drone Innovation and Trends]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Insurance and Liability]]></category>
		<category><![CDATA[Law Enforcement]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Legal Cases]]></category>
		<category><![CDATA[Legal Challenges]]></category>
		<category><![CDATA[Legal Challenges in Drone Operations]]></category>
		<category><![CDATA[Legal Compliance]]></category>
		<category><![CDATA[Legal Conflicts]]></category>
		<category><![CDATA[Legal Frameworks]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Legal Investigations]]></category>
		<category><![CDATA[Legal Updates]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Compliance - Focuses on the importance of adherence to regulatory guidelines and consequences of violations.]]></category>
		<category><![CDATA[Regulatory Compliance - Includes insights on compliance with FAA]]></category>
		<category><![CDATA[Risk Assessment & Mitigation]]></category>
		<category><![CDATA[Safety and Security in Aviation]]></category>
		<category><![CDATA[Technological Innovations in Drones]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2615</guid>

					<description><![CDATA[<p>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 [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/">A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Begin WordPress post content (no H1 included; WordPress will supply the title) --></p>
<p>By Richard Ryan, barrister and drone lawyer</p>
<p><strong>Constructive outcome, practical lessons.</strong> 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.</p>
<section aria-labelledby="outcome">
<h2 id="outcome">Outcome at a glance</h2>
<ul>
<li><strong>Count 1 (conviction):</strong> Operating an unmanned aircraft close to the site of an ongoing emergency response — <strong>Air Navigation Order 2016</strong> Articles <strong>265B(3)</strong>, <strong>265B(5)(j)</strong> and <strong>265F(3)(c)</strong> (reflecting <strong>UAS.OPEN.060(3)</strong>).</li>
<li><strong>Count 2 (dismissed):</strong> Obstructing or hindering emergency workers — <strong>Emergency Workers (Obstruction) Act 2006</strong>, sections <strong>1</strong> and <strong>4</strong> — no case to answer.</li>
<li><strong>Sentence:</strong> <strong>£300</strong> (reduced from <strong>£2,500</strong>). <strong>Deprivation order refused</strong> — the client’s equipment will be returned.</li>
</ul>
<p></strong>.</p>
</section>
<section aria-labelledby="background">
<h2 id="background">Competence, cooperation and public interest flying</h2>
<p>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.</p>
</section>
<section aria-labelledby="lesson-telemetry">
<h2 id="lesson-telemetry">Lesson 1: Telemetry clarity</h2>
<p>When presenting flight data, clarity matters. Plot the flight path with a <strong>thin, precise line</strong> so the <strong>base map remains legible</strong>, including fences, road edges, cordons and measured standoffs. A thick line can obscure the very features that prove separation.</p>
<ul>
<li>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.</li>
<li>Use a thin line that clearly shows accurate telemetry when placed on a map, not a thick line that obscures part of the map.</li>
</ul>
<p>  <!-- Optional image placeholder:
  

<figure>
    <img decoding="async" src="telemetry-thin-vs-thick.png" alt="Thin flight path line keeps the base map legible; thick line obscures fences, roads and standoffs." loading="lazy" />
    
 
<figcaption>Thin versus thick telemetry overlays (illustrative).</figcaption>
 

  </figure>


  --><br />
</section>
<section aria-labelledby="lesson-dat">
<h2 id="lesson-dat">Lesson 2: Plan for seizure and understand where DJI DAT lives</h2>
<p>High fidelity <strong>DJI DAT</strong> logs are stored on the aircraft and typically require <strong>connecting the drone to a computer</strong> to extract. If a drone is seized by police, immediate access to those DAT files is difficult.</p>
<ul>
<li>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.</li>
<li>For sensitive assignments, consider periodic DAT offloads in advance.</li>
</ul>
</section>
<section aria-labelledby="commitments">
<h2 id="commitments">Five straightforward commitments</h2>
<ol>
<li>Thin line telemetry as the default for mapping outputs.</li>
<li>Evidence resilience: dual path logging (logs plus screen capture) and periodic DAT offloads.</li>
<li>Proportionate communications near emergency activity where appropriate.</li>
<li>A simple one page ops note on every job covering airspace, standoffs and abort triggers.</li>
<li>Calm, courteous engagement with officers, with a record of powers used and a property schedule if equipment is seized.</li>
</ol>
</section>
<section aria-labelledby="tech-ref">
<h2 id="tech-ref">Technical reference: cross motorway separation</h2>
<p>To contextualise the judge’s description (opposite side of a six lane motorway plus hard shoulder plus verge), the following uses standard UK dimensions.</p>
<h3>Assumptions from UK highway standards</h3>
<ul>
<li><strong>Lane width (motorways):</strong> 3.65 m per lane (DMRB CD 127). <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">[1]</a></li>
<li><strong>Hard shoulder width:</strong> 3.3 m (National Highways). <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">[2]</a></li>
<li><strong>Central reservation (median):</strong> assume about 3.0 m (DMRB derived guidance). <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">[3]</a></li>
<li><strong>Verge:</strong> varies by site; on trunk roads, about 3.0 m is common. Use 2.0 to 3.0 m to bracket reality. <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">[4]</a></li>
</ul>
<h3>Baseline components</h3>
<ul>
<li>Six lanes = 6 x 3.65 = <strong>21.90 m</strong>. <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">[1]</a></li>
<li>Two hard shoulders = <strong>6.60 m</strong>. <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">[2]</a></li>
<li>Central reservation (median) about <strong>3.00 m</strong>. <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">[3]</a></li>
<li>Verge per side about <strong>2.0 to 3.0 m</strong>. <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">[4]</a></li>
</ul>
<h3>Real world lateral separation (verge to verge)</h3>
<p><code>Distance = 6 lanes + 2 x hard shoulder + 2 x verge + median</code></p>
<ul>
<li>With 2.0 m verges (conservative): <strong>21.90 + 6.60 + 4.00 + 3.00 = 35.50 m</strong></li>
<li>With 3.0 m verges (typical): <strong>21.90 + 6.60 + 6.00 + 3.00 = 37.50 m</strong></li>
</ul>
<p><strong>Figure to use:</strong> about <strong>37.5 m</strong> horizontal separation verge to verge (typical). <strong>Lower bound:</strong> about <strong>35.5 m</strong> if verges are unusually narrow.</p>
<h3>Lean reading (narrow phrasing)</h3>
<p>Six lanes plus one hard shoulder plus one verge (omitting the median and the opposite side shoulder and verge):</p>
<p><code>21.90 + 3.30 + (2.0 to 3.0) = 27.2 to 28.2 m</code></p>
<p>This underestimates the physical cross section that most operators and engineers would use.</p>
<h3>Add altitude for slant distance</h3>
<p>If height is h, the slant range is <code>sqrt(lateral^2 + h^2)</code>.</p>
<ul>
<li>With 37.5 m lateral: <strong>48.0 m</strong> at 30 m AGL, <strong>70.8 m</strong> at 60 m, <strong>125.7 m</strong> at 120 m.</li>
<li>With 35.5 m lateral: <strong>46.5 m</strong> at 30 m, <strong>69.2 m</strong> at 60 m, <strong>124.2 m</strong> at 120 m.</li>
</ul>
<p><strong>Practical effect:</strong> 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.</p>
<p>Standards: <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">DMRB CD 127</a>, <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">National Highways</a>, <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">TII DN GEO 03036</a>, <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">Transport Scotland</a>.</p>
</section>
<section aria-labelledby="closing">
<h2 id="closing">Bottom line</h2>
<p>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.</p>
</section>
<hr />
<section aria-labelledby="bio">
<h2 id="bio">About the author</h2>
<p><strong>Richard Ryan</strong> 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.</p>
</section>
<p><em>This post is for general information only and is not legal advice.</em></p>
<p><!-- End WordPress post content --></p>
<p>The post <a href="https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/">A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Trespass by Drones: Is Section 76 Civil Aviation Act 1982 Fit for Purpose?</title>
		<link>https://blakistons.co.uk/trespass-by-drones-is-section-76-civil-aviation-act-1982-fit-for-purpose/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 30 Sep 2025 09:51:14 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Industry Concerns]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Legal Cases]]></category>
		<category><![CDATA[Legal Challenges]]></category>
		<category><![CDATA[Legal Challenges in Drone Operations]]></category>
		<category><![CDATA[Legal Compliance]]></category>
		<category><![CDATA[Legal Conflicts]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Compliance Strategies]]></category>
		<category><![CDATA[Trespass Law]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[airspace rights UK]]></category>
		<category><![CDATA[Blakiston’s Chambers]]></category>
		<category><![CDATA[Civil Aviation Act 1982]]></category>
		<category><![CDATA[drone compliance UK]]></category>
		<category><![CDATA[drone law UK]]></category>
		<category><![CDATA[drone nuisance claims]]></category>
		<category><![CDATA[drone operators legal issues]]></category>
		<category><![CDATA[Drone Trespass]]></category>
		<category><![CDATA[Section 76 drones]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2571</guid>

					<description><![CDATA[<p>Blakiston’s Chambers – Insight for Drone Operators • 30th September 2025 Why this matters for drone companies The question of whether a drone operator can be sued for trespass when flying over private land is no longer a theoretical debate. With drones now routinely used for surveying, deliveries, inspections, and filming, landowners are increasingly asking [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/trespass-by-drones-is-section-76-civil-aviation-act-1982-fit-for-purpose/">Trespass by Drones: Is Section 76 Civil Aviation Act 1982 Fit for Purpose?</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Blakiston's Chambers | Drone Trespass Article (uniform text colour) --></p>
<section id="bc-drone-article" lang="en-GB">
<style>
    /* Scoped, theme-safe styles */
    #bc-drone-article {
      --content-width: min(900px, 92vw);
      --pad: max(16px, 6vw);
      --text: #222222; /* consistent text colour */
    }
    #bc-drone-article, #bc-drone-article * {
      box-sizing: border-box;
      color: var(--text) !important;
      font-family: Georgia, "Times New Roman", serif;
    }
    #bc-drone-article .bc-wrap {
      width: var(--content-width);
      margin: 0 auto;
      padding: 0 var(--pad);
    }
    #bc-drone-article .bc-meta {
      margin: .25rem auto 1.5rem;
      font-size: .95rem;
      opacity: .95;
    }
    #bc-drone-article article {
      line-height: 1.6;
      padding: 0 0 2.5rem;
    }
    #bc-drone-article h2 {
      margin-top: 2rem;
      font-size: 1.55rem;
      line-height: 1.35;
    }
    #bc-drone-article h3 {
      margin-top: 1.1rem;
      font-size: 1.2rem;
    }
    #bc-drone-article p { margin: .85rem 0; }
    #bc-drone-article ul,
    #bc-drone-article ol { margin: .6rem 0 1rem 1.25rem; }
    #bc-drone-article li { margin: .35rem 0; }
    #bc-drone-article .bc-callout {
      border-left: 4px solid var(--text);
      background: #f7f7f7;
      padding: .9rem 1rem;
      margin: 1.5rem 0;
    }
    #bc-drone-article .bc-foot {
      border-top: 1px solid #e6e6e6;
      padding: 1rem 0 2rem;
      font-size: .9rem;
      text-align: center;
      opacity: .9;
    }
  </style>
<p>  <!-- Meta line only (title handled by WordPress theme) --></p>
<div class="bc-wrap bc-meta">
    <span>Blakiston’s Chambers – Insight for Drone Operators</span> •<br />
    <time datetime="2025-09-30">30th September 2025</time>
  </div>
<p>  <!-- Article body --></p>
<article class="bc-wrap" role="article">
<section id="why-this-matters">
<h2>Why this matters for drone companies</h2>
<p>The question of whether a drone operator can be sued for trespass when flying over private land is no longer a theoretical debate. With drones now routinely used for surveying, deliveries, inspections, and filming, landowners are increasingly asking whether they can stop flights above their property.</p>
<p>At the heart of this issue lies <strong>section 76 of the Civil Aviation Act 1982</strong>. Originally drafted for manned aviation, it has never been fully adapted to the realities of drones flying close to the ground, often well below 400 feet.</p>
<p>Recent High Court cases – <em>Anglo-International Upholland Ltd v Wainwright</em> (2023) and <em>MBR Acres Ltd v Curtin</em> (2025) – have thrown the law into sharper focus. For drone operators, the practical question is whether your drone can legally enter the airspace above a neighbour’s land without risking an injunction or damages claim.</p>
</section>
<section id="trespass-basics">
<h2>Trespass: the basic position</h2>
<p>Trespass is normally straightforward: step onto someone’s land without permission, and you’re liable – even if you cause no harm. Landowners don’t need to prove loss; mere entry is enough.</p>
<p>But what about airspace? Does a landowner “own the sky” above their property? Historically, English law used the maxim <em>cujus est solum, ejus est usque ad coelum</em> – whoever owns the soil owns all the way up to the heavens. Courts have long since rejected that absolute view. Instead, the law recognises ownership only of the airspace “necessary for the reasonable enjoyment of the land”.</p>
<p>For manned aircraft, Parliament drew a compromise in section 76(1): flights at a “reasonable height” cannot be challenged as trespass or nuisance. But what is a “reasonable height” when drones are often flown at 50 metres, 20 metres, or even lower?</p>
</section>
<section id="bernstein">
<h2>Bernstein and the buffer zone</h2>
<p>In <em>Bernstein v Skyviews</em> (1978), a landowner sued after an aircraft flew hundreds of feet above his estate to take photographs. The court held that this was not trespass, because the aircraft was too high to interfere with the landowner’s use of his land.</p>
<p>That decision gave us a rough principle: landowners control only the slice of airspace that matters to their ordinary use of land. The problem is that drones now operate in precisely that slice – near buildings, gardens, roads, and industrial sites – where interference with land use is most likely.</p>
</section>
<section id="new-drone-cases">
<h2>The new drone cases</h2>
<h3>1. Anglo-International (2023)</h3>
<p>Drone flights over a derelict college were used to capture images which encouraged trespassers to enter the site. The judge treated the flights as mischievous and granted an injunction, holding that section 76 did not protect the operators.</p>
<p>The ruling was short and did not carefully analyse airspace ownership or flight height, but it showed courts are willing to act against drone flights if their purpose is seen as facilitating trespass or mischief.</p>
<h3>2. MBR Acres (2025)</h3>
<p>Animal rights campaigners used drones to film over a research facility. Some drones were flown as low as the height of a single-storey building, but evidence on height and operators was inconsistent.</p>
<p>The judge refused to grant an injunction. He accepted that flights at <strong>50 metres or more</strong> did not interfere with the use of the land. Importantly, he suggested that other legal remedies – nuisance, harassment, or data protection – might be more appropriate than trespass.</p>
</section>
<section id="what-it-means">
<h2>What this means for drone operators</h2>
<ol>
<li><strong>Trespass claims are harder to make stick than many landowners think.</strong> Courts are reluctant to find trespass unless flights interfere with the actual use of land (e.g. disrupting activity on site, flying extremely low, or endangering people).</li>
<li><strong>Section 76 may be becoming redundant.</strong> Both <em>Bernstein</em> and <em>MBR Acres</em> suggest that unless a flight interferes with land use, there is no trespass at all – making section 76’s “reasonable height” defence almost irrelevant.</li>
<li><strong>Purpose of flight matters – at least sometimes.</strong> In <em>Anglo-International</em>, mischievous use of drones was enough to justify an injunction. Operators engaged in legitimate commercial activity (surveying, deliveries, inspections) are on stronger ground.</li>
<li><strong>Evidence is critical.</strong> Landowners will struggle to obtain injunctions unless they can prove height, frequency, and impact of flights. For operators, maintaining robust flight logs and compliance records (as required by the UK drone regulations) is the best defence.</li>
<li><strong>Regulatory compliance is non-negotiable.</strong> Section 76 only protects operators if flights are lawful. Breach of drone regulations (flying beyond visual line of sight, too close to people, or over congested areas without permissions) will undermine any defence.</li>
</ol>
</section>
<section id="looking-ahead">
<h2>Looking ahead</h2>
<p>The law remains unsettled. Drone operators should assume:</p>
<ul>
<li>Routine overflights at safe, documented altitudes are unlikely to amount to trespass, provided they don’t interfere with land use.</li>
<li>Low-level flights directly over private land remain risky, particularly if they appear intrusive, harassing, or unsafe.</li>
<li>Other causes of action are emerging – nuisance, data protection, and harassment are likely to be more powerful tools for landowners than trespass.</li>
</ul>
<p>For commercial operators, the key is to plan flight paths with landowner sensitivities in mind, document compliance, and keep up with evolving case law. What remains unclear is whether Parliament will modernise section 76 to deal explicitly with drones – or whether the courts will continue to adapt 20th-century law to 21st-century technology.</p>
<div class="bc-callout">
<p><strong>Blakiston’s Chambers</strong> advises drone operators, manufacturers, and service providers on all aspects of UK drone law, including airspace rights, regulatory compliance, and litigation risk. If your business is concerned about trespass or overflight liability, our team can help.</p>
</p></div>
</section>
</article>
<div class="bc-wrap bc-foot">&copy; 2025 Blakiston’s Chambers. All rights reserved.</div>
</section>
<p>The post <a href="https://blakistons.co.uk/trespass-by-drones-is-section-76-civil-aviation-act-1982-fit-for-purpose/">Trespass by Drones: Is Section 76 Civil Aviation Act 1982 Fit for Purpose?</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Airprox 2024294 – What Actually Happened at RAF Lakenheath?</title>
		<link>https://blakistons.co.uk/airprox-2024294-ec135-mistakes-f-15-for-drone-in-uk-night-operation/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Fri, 27 Jun 2025 13:41:37 +0000</pubDate>
				<category><![CDATA[Airprox Reports]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Aviation Security]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Drone Accidents & Case Studies]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Risk Assessment & Mitigation]]></category>
		<category><![CDATA[Safety and Security in Aviation]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Airprox 2024294]]></category>
		<category><![CDATA[airspace coordination]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS)]]></category>
		<category><![CDATA[Class G airspace]]></category>
		<category><![CDATA[drone misidentification]]></category>
		<category><![CDATA[drone regulation UK]]></category>
		<category><![CDATA[EC135]]></category>
		<category><![CDATA[F-15]]></category>
		<category><![CDATA[NPAS]]></category>
		<category><![CDATA[public perception of drones]]></category>
		<category><![CDATA[RAF Lakenheath]]></category>
		<category><![CDATA[TCAS limitations]]></category>
		<category><![CDATA[UK Drone Law]]></category>
		<category><![CDATA[USAFE]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2561</guid>

					<description><![CDATA[<p>Airprox 2024294 – What Actually Happened? On the night of 22 November 2024 at 21:51 UTC, a National Police Air Service (NPAS) EC135 helicopter operating near RAF Lakenheath reported multiple “drones” manoeuvring around it. In reality, the objects were USAF F15 fighters engaged in authorised night training in Class G airspace (surface–FL150), coordinated by Lakenheath [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/airprox-2024294-ec135-mistakes-f-15-for-drone-in-uk-night-operation/">Airprox 2024294 – What Actually Happened at RAF Lakenheath?</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img fetchpriority="high" decoding="async" src="https://blakistons.co.uk/wp-content/uploads/2025/06/250627_airpox-blog-300x200.png" alt="" width="300" height="200" class="size-medium wp-image-2562" srcset="https://blakistons.co.uk/wp-content/uploads/2025/06/250627_airpox-blog-300x200.png 300w, https://blakistons.co.uk/wp-content/uploads/2025/06/250627_airpox-blog-1024x683.png 1024w, https://blakistons.co.uk/wp-content/uploads/2025/06/250627_airpox-blog-768x512.png 768w, https://blakistons.co.uk/wp-content/uploads/2025/06/250627_airpox-blog-600x400.png 600w, https://blakistons.co.uk/wp-content/uploads/2025/06/250627_airpox-blog.png 1536w" sizes="(max-width: 300px) 100vw, 300px" /> </p>
<h2>Airprox 2024294 – What Actually Happened?</h2>
<p>On the night of <strong>22 November 2024 at 21:51 UTC</strong>, a National Police Air Service (NPAS) <strong>EC135 helicopter</strong> operating near RAF Lakenheath reported multiple “drones” manoeuvring around it. In reality, the objects were <strong>USAF F15 fighters</strong> engaged in authorised night training in Class G airspace (surface–FL150), coordinated by Lakenheath Approach (&#8220;Overlord&#8221;).</p>
<h3>Summary of Key Facts:</h3>
<ul>
<li><strong>Closest Point of Approach (CPA):</strong> 1 NM horizontal / 1900 ft vertical separation (recorded).</li>
<li><strong>ATC Services:</strong>
<ul>
<li>EC135 – Basic Service (no traffic information guaranteed).</li>
<li>F-15s – Traffic Service (received information about the EC135).</li>
</ul>
</li>
<li><strong>Misidentification Factors:</strong>
<ul>
<li>EC135’s TCAS did <strong>not display the F-15s</strong>.</li>
<li>F-15 lighting did <strong>not resemble standard civil aircraft lighting</strong>.</li>
<li>The crew believed the lights were drones due to their apparent behaviour and lack of TCAS confirmation.</li>
</ul>
</li>
</ul>
<p>The <strong>UK Airprox Board (UKAB)</strong> concluded that there was <strong>no risk of collision</strong> (Risk Category E) and attributed the report to <strong>misidentification and situational awareness breakdown</strong> rather than unsafe flying.</p>
<hr>
<h2>Why This Matters to Drone Operators</h2>
<h3>1. Misidentification Risk</h3>
<p>Even experienced police aircrew using EO/IR cameras mistook military jets for drones. This shows how easily drone operators can be blamed for aerial events they weren’t involved in.</p>
<h3>2. Electronic Conspicuity Limitations</h3>
<p>The EC135’s TCAS did not detect the F-15s despite them squawking Modes A and C. This highlights the ongoing limitations of EC systems in complex or mixed-use airspace, particularly at night.</p>
<h3>3. ATC Service Levels – Know the Difference</h3>
<p>Under a <strong>Basic Service</strong>, ATC is <strong>not required</strong> to provide traffic information. Drone operators should consider requesting a <strong>Traffic Service</strong> or <strong>Deconfliction Service</strong> for BVLOS, urban, or sensitive operations.</p>
<hr>
<h2>Public Perception: A Persistent Challenge</h2>
<ul>
<li><strong>“Drone blame” is the default:</strong> Unidentified lights in the sky are often assumed to be drones, fuelling public concern and regulatory overreaction.</li>
<li><strong>Poor understanding of airspace rules:</strong> The public often assumes ATC sees and controls everything — which is untrue in Class G.</li>
<li><strong>Coordination gaps:</strong> The police helicopter tasking was not pre-notified to the USAF. This shows the need for better operational coordination.</li>
</ul>
<hr>
<h2>Risk Assessment for UK Drone Operations</h2>
<h3>Potential Scenarios and Risk Levels:</h3>
<ul>
<li><strong>Misidentification by other aircraft:</strong>
<ul>
<li>Likelihood: Medium</li>
<li>Severity: Low to Medium</li>
<li>Risk Level: Moderate overall, but High reputationally</li>
</ul>
</li>
<li><strong>No traffic info under Basic Service:</strong>
<ul>
<li>Likelihood: Medium</li>
<li>Severity: Medium</li>
<li>Risk Level: Moderate</li>
</ul>
</li>
<li><strong>Public/media backlash from perceived near-miss:</strong>
<ul>
<li>Likelihood: High</li>
<li>Severity: High</li>
<li>Risk Level: High (especially for commercial operators)</li>
</ul>
</li>
</ul>
<h3>Key Mitigations for Drone Operators:</h3>
<ul>
<li>Use <strong>dual EC systems</strong> (ADS-B OUT and ground-based detect-and-avoid).</li>
<li>Maintain a <strong>telemetry and flight log archive</strong> for every operation.</li>
<li><strong>Pre-notify military ATC</strong> when operating near MOD airspace.</li>
<li>File <strong>CANPs, NOTAMs, or Temporary Danger Areas</strong> when applicable.</li>
<li>Train pilots to request an <strong>upgrade to Traffic Service</strong> where required.</li>
</ul>
<hr>
<h2>Legal and Regulatory Observations</h2>
<ul>
<li><strong>SERA.3205</strong> and <strong>ANO Article 239</strong> set the standard for proximity liability. Keep compliance well-documented.</li>
<li>Expect growing pressure for <strong>mandatory electronic conspicuity</strong>, with incidents like this cited in policy.</li>
<li>If blamed in media or police statements without evidence, drone operators may have grounds for <strong>defamation or economic loss claims</strong>. Get legal advice promptly.</li>
</ul>
<hr>
<h2>Final Thoughts</h2>
<blockquote><p><strong>This wasn’t a drone incident — but it could have been perceived as one.</strong></p></blockquote>
<p>The lesson? <strong>Control the narrative by controlling the data.</strong><br />
Record everything. Secure it. Share it when necessary. With the right evidence, drone operators can protect themselves from false blame and help improve UK airspace safety.</p>
<hr>
<h3>About the Author</h3>
<p><strong>Richard Ryan</strong> is a UK barrister and aviation lawyer specialising in drone regulation, UAS integration, and counter-drone law. A Fellow of the Chartered Institute of Arbitrators, he advises police forces, government bodies, and commercial operators on airspace compliance and emerging UTM frameworks. He is also completing a PhD on airspace integration and unmanned traffic management at Cranfield University.</p>
<p>The post <a href="https://blakistons.co.uk/airprox-2024294-ec135-mistakes-f-15-for-drone-in-uk-night-operation/">Airprox 2024294 – What Actually Happened at RAF Lakenheath?</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</title>
		<link>https://blakistons.co.uk/military-drones-and-ai-regulation-a-uk-drone-lawyers-perspective/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 07 Jan 2025 13:29:44 +0000</pubDate>
				<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[International Drone Regulations]]></category>
		<category><![CDATA[International Humanitarian Law]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[UK Defence Policy]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[AI Ethics]]></category>
		<category><![CDATA[AI regulation]]></category>
		<category><![CDATA[artificial intelligence]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Faculty AI]]></category>
		<category><![CDATA[frontier AI]]></category>
		<category><![CDATA[lethal autonomous weapons]]></category>
		<category><![CDATA[military drones]]></category>
		<category><![CDATA[UK drone lawyer]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2540</guid>

					<description><![CDATA[<p>Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective By Richard Ryan, UK Drone Lawyer On 7 January 2025, The Guardian published an article highlighting the British AI consultancy Faculty AI’s involvement in the development of drone technology for defence clients, prompting renewed questions about where legal, ethical, and regulatory boundaries should lie for [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/military-drones-and-ai-regulation-a-uk-drone-lawyers-perspective/">Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" src="https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-300x300.webp" alt="" width="300" height="300" class="alignnone size-medium wp-image-2541" srcset="https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-300x300.webp 300w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-150x150.webp 150w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-768x768.webp 768w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-600x600.webp 600w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-100x100.webp 100w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_.webp 1024w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</strong></p>
<p><strong>By Richard Ryan, UK Drone Lawyer</strong></p>
<p>On 7 January 2025, The Guardian published an article highlighting the British AI consultancy Faculty AI’s involvement in the development of drone technology for defence clients, prompting renewed questions about where legal, ethical, and regulatory boundaries should lie for AI-driven military applications.<br />
Faculty AI, already prominent for its work with various UK government departments (including the NHS and the Department for Education) and advisory services for the AI Safety Institute (AISI), has reportedly developed and deployed AI models on unmanned aerial vehicles (UAVs) for military purposes. Although it remains unclear whether these drones are intended for lethal operations, the revelations have amplified concerns about how best to regulate or restrict the use of AI in weapon systems.<br />
Below, I explore the key legal issues and examine how the recently adopted <strong>EU AI Act</strong>—as well as the evolving UK regulatory framework—may shape the future of this sector.<br />
________________________________________<br />
<strong>1. Faculty AI’s Defence Work: A Brief Overview</strong><br />
<strong>1.1 Government and Public Sector Ties</strong><br />
Faculty AI, known for its work with the Vote Leave campaign in 2016, was later engaged by Dominic Cummings to provide data analytics during the pandemic. Since then, it has won multiple government contracts worth at least £26.6m, extending its work into healthcare (via the NHS), education, and policy consulting with the AISI on frontier AI safety.<br />
<strong>1.2 UAV Development</strong><br />
The Guardian reports that Faculty AI has experience in deploying AI models on UAVs. Its partner firm, Hadean, indicated that the two companies collaborated on subject identification, tracking objects in movement, and exploring swarm deployment. While Faculty states that it aims to create “safer, more robust solutions”, details on whether these drones might be capable of lethal autonomous targeting remain undisclosed.<br />
________________________________________<br />
<strong>2. The EU AI Act: A New Regulatory Milestone</strong><br />
<strong>2.1 Status of the EU AI Act</strong><br />
Introduced by the European Commission in 2021 as a proposed regulation, the EU AI Act has since been adopted via the EU’s legislative process. As of early 2025, it is recognised as a binding regulation designed to harmonise AI rules across all EU Member States. Although the UK is no longer part of the EU, any UK-based company offering AI products or services within the EU must ensure compliance with the regulation’s requirements.<br />
<strong>2.2 Risk-Tiered Framework</strong><br />
The EU AI Act operates on a tiered risk basis:<br />
•	<strong>Unacceptable risk</strong>: Certain AI applications (e.g., social scoring) are outright banned.<br />
•	<strong>High risk</strong>: This category includes critical infrastructure, healthcare, and—potentially—defence-related AI systems that could significantly affect people’s safety or fundamental rights. Such systems must meet strict transparency, oversight, and data governance requirements.<br />
•	<strong>Limited or minimal risk</strong>: These uses are subject to fewer obligations, generally focused on transparency (e.g., disclosing AI usage to end users).<br />
For <strong>high-risk</strong> AI in military contexts, the EU AI Act demands robust <strong>human oversight</strong>, thorough documentation, and strict compliance obligations, particularly around accountability and the prevention of harm.<br />
<strong>2.3 Potential Impact on Military Drones</strong><br />
While national security and defence largely remain the prerogative of individual EU Member States, the EU AI Act’s principles can still influence how companies and governments view the development of autonomous or semi-autonomous drones. Key considerations include:<br />
•	<strong>Transparent Data and Design</strong>: Documenting data sets, development processes, and operational parameters.<br />
•	<strong>Human in the Loop</strong>: Ensuring a human operator is always able to override or intervene in the AI’s decision-making. Other terms such as Human on the Loop and Human outside the Loop are also referred to.<br />
•	<strong>Liability and Penalties</strong>: Breaches can incur hefty fines—up to 6% of global turnover—thus acting as a significant deterrent against unethical or unlawful AI deployment.<br />
________________________________________<br />
<strong>3. The UK’s Approach to AI Regulation and Military Drones</strong><br />
<strong>3.1 Divergence from the EU?</strong><br />
Post-Brexit, the UK has chosen a “pro-innovation” approach to AI regulation. Rather than adopting a single, all-encompassing statute akin to the EU AI Act, the UK is implementing a sector-by-sector and risk-based strategy, guided by existing regulators such as the Information Commissioner’s Office and the Competition and Markets Authority.<br />
<strong>3.2 AI Safety Institute (AISI)</strong><br />
Established under former Prime Minister Rishi Sunak in 2023, the AISI focuses on frontier AI safety research. Faculty AI’s role in testing large language models and advising the AISI on threats like disinformation and system security places the company in a key position to influence UK policy. Critics argue that this may create potential conflicts of interest if the same organisation is also developing AI for military use.<br />
<strong>3.3 House of Lords Recommendations</strong><br />
In 2023, a House of Lords committee urged the UK Government to clarify the application of International Humanitarian Law (IHL) to lethal drone strikes and to work towards an international agreement limiting or banning fully autonomous weapons systems. The Government response acknowledged the importance of maintaining “human control” in critical decisions but did not enact binding legislation banning lethal autonomous drones outright.<br />
________________________________________<br />
<strong>4. Legal and Ethical Concerns for AI-Enabled Drones</strong><br />
<strong>4.1 International Humanitarian Law (IHL)</strong><br />
IHL principles—<strong>distinction</strong> (separating combatants from civilians) and <strong>proportionality</strong> (limiting harm relative to military objectives)—are central to discussions on AI-driven drones. Fully autonomous UAVs, capable of selecting and engaging targets without human intervention, raise profound legal questions on accountability, particularly if biases or system errors result in wrongful casualties.<br />
<strong>4.2 Allocation of Liability</strong><br />
Traditionally, accountability in military operations lies with commanders and operators. With increasingly autonomous systems, however, liability could extend to technology developers, programmers, or even the purchaser of the system. Clarifying how legal responsibilities are distributed may become a focal point for future litigation and regulatory reform.<br />
<strong>4.3 Export Controls</strong><br />
Companies like Faculty AI must also comply with arms-export rules when providing AI-targeting systems or related software to foreign entities. In the UK, export licences for military-grade technology are subject to domestic legislation and international protocols, such as the Wassenaar Arrangement on dual-use goods.<br />
________________________________________<br />
<strong>5. Looking Ahead: Balancing Innovation, Safety, and Accountability</strong><br />
<strong>5.1	Stronger National Frameworks</strong><br />
Although the UK favours a pro-innovation stance, there is growing pressure from Parliament and civil society for more rigorous, enforceable rules on potentially lethal AI applications. The EU AI Act may serve as a reference point for the UK to consider stricter domestic regulations.<br />
<strong>5.2	International Collaboration</strong><br />
Calls for global agreements—treaties or non-binding accords—to prohibit fully autonomous weapons continue to gain momentum. The House of Lords committee specifically recommended international engagement to ensure that lethal force remains under human control.<br />
<strong>5.3	Corporate Accountability</strong><br />
Organisations operating at the intersection of commercial defence contracts and government policy—such as Faculty AI—need transparent internal processes and robust ethics boards to mitigate conflicts of interest. Demonstrating genuine corporate responsibility will be vital for maintaining public trust.<br />
<strong>5.4	Ethical and Safety Audits</strong><br />
As AI becomes more embedded in defence, mandatory ethical and safety audits may become standard practice. These would scrutinise algorithmic fairness, training data, and how effectively systems can identify and mitigate unintended harms.<br />
________________________________________<br />
<strong>6. Conclusion</strong><br />
Faculty AI’s role in developing AI for military drones underscores how high the stakes are when cutting-edge technology meets defence applications. With the EU AI Act now in force as a binding regulation, Europe has provided a blueprint for tighter control over “high-risk” AI systems. In contrast, the UK’s approach still offers substantial flexibility for companies, potentially raising both legal and ethical concerns around autonomy, accountability, and conflicts of interest.<br />
From an IHL standpoint, keeping a human responsible for any life-and-death decision is imperative. As a UK drone lawyer, I urge policymakers, regulators, and industry stakeholders to keep asking: <strong>Where do we draw the line between legitimate defensive innovation and an unacceptable risk to civilians?</strong> Only by establishing clear, enforceable legal standards—anchored in international law and ethical scrutiny—can we ensure AI-powered drones serve to protect rather than endanger fundamental human values.</p>
<p><strong>Bio – Richard Ryan, UK Drone Lawyer</strong></p>
<p>Richard Ryan is a UK-based drone lawyer specialising in the regulatory, ethical, and commercial aspects of unmanned aerial vehicles (UAVs) and artificial intelligence (AI). Through a series of blogs, Richard Ryan has explored critical issues such as the EU AI Act, the UK’s evolving “pro-innovation” regulatory landscape, and the legal considerations surrounding military drones and lethal autonomous weapons systems.</p>
<p>Drawing on extensive experience in advising government bodies, technology companies, and public institutions, Richard Ryan brings a deep understanding of how international humanitarian law (IHL), export controls, and data protection obligations intersect in modern drone operations. Their writing emphasises the importance of maintaining human oversight in AI-driven systems, championing ethical development and transparent accountability mechanisms.</p>
<p>A trusted voice in the field, Richard Ryan regularly comments on emerging case law, parliamentary recommendations, and global discussions around frontier AI safety. The mission is to help stakeholders—from hobbyist drone operators to established aerospace firms—navigate the complexities of regulation, risk management, and innovation.</p>
<p>The post <a href="https://blakistons.co.uk/military-drones-and-ai-regulation-a-uk-drone-lawyers-perspective/">Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Navigating the Skies: Legal Perspectives on the UK&#8217;s Drone Revolution</title>
		<link>https://blakistons.co.uk/navigating-the-skies-legal-perspectives-on-the-uks-drone-revolution/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Wed, 13 Nov 2024 11:50:26 +0000</pubDate>
				<category><![CDATA[Airspace Management]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Environmental and Wildlife Considerations]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Infrastructure and Utility Inspections]]></category>
		<category><![CDATA[Insurance and Liability]]></category>
		<category><![CDATA[International Drone Policies]]></category>
		<category><![CDATA[Privacy and Data Protection]]></category>
		<category><![CDATA[Public Perception and Community Engagement]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Security and Counter-UAS]]></category>
		<category><![CDATA[Technological Innovations in Drones]]></category>
		<category><![CDATA[Workforce Development and Training]]></category>
		<category><![CDATA[Air Navigation Order]]></category>
		<category><![CDATA[airspace integration]]></category>
		<category><![CDATA[airspace management]]></category>
		<category><![CDATA[CAA regulations]]></category>
		<category><![CDATA[drone applications]]></category>
		<category><![CDATA[drone innovation]]></category>
		<category><![CDATA[drone insurance]]></category>
		<category><![CDATA[Drone Lawyer]]></category>
		<category><![CDATA[drone regulation]]></category>
		<category><![CDATA[drone technology]]></category>
		<category><![CDATA[drone workforce]]></category>
		<category><![CDATA[emergency response]]></category>
		<category><![CDATA[environmental impact]]></category>
		<category><![CDATA[ethical drone use]]></category>
		<category><![CDATA[GDPR compliance]]></category>
		<category><![CDATA[infrastructure inspection]]></category>
		<category><![CDATA[legal challenges]]></category>
		<category><![CDATA[legal perspectives]]></category>
		<category><![CDATA[privacy and data protection]]></category>
		<category><![CDATA[public perception]]></category>
		<category><![CDATA[regulatory compliance]]></category>
		<category><![CDATA[safety assessments]]></category>
		<category><![CDATA[security and counter-UAS]]></category>
		<category><![CDATA[sustainable drone growth]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK drone industry]]></category>
		<category><![CDATA[unmanned aerial systems]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2494</guid>

					<description><![CDATA[<p>Navigating the Skies: Legal Perspectives on the UK&#8217;s Drone Revolution By Richard Ryan November 2024 As an experienced drone lawyer in the UK with two decades of immersion in this rapidly evolving field, I&#8217;ve witnessed firsthand the transformative impact drones have across various industries. The recent ARPAS report &#8220;Drones In Action&#8221; (November 2024) showcases a [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/navigating-the-skies-legal-perspectives-on-the-uks-drone-revolution/">Navigating the Skies: Legal Perspectives on the UK&#8217;s Drone Revolution</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" src="https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution-300x171.webp" alt="" width="300" height="171" class="alignnone size-medium wp-image-2495" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution-300x171.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution-1024x585.webp 1024w, https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution-768x439.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution-1536x878.webp 1536w, https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution-600x343.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/241112_Navigating-the-Skies-Legal-Perspectives-on-the-UKs-Drone-Revolution.webp 1792w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Navigating the Skies: Legal Perspectives on the UK&#8217;s Drone Revolution<br />
By Richard Ryan<br />
November 2024</strong><br />
As an experienced drone lawyer in the UK with two decades of immersion in this rapidly evolving field, I&#8217;ve witnessed firsthand the transformative impact drones have across various industries. The recent ARPAS report &#8220;Drones In Action&#8221; (November 2024) showcases a spectrum of innovative applications, from housing inspections to emergency response. While these use cases highlight significant benefits—such as cost savings, improved safety, and enhanced efficiency—they also surface critical legal considerations that must be addressed to foster sustainable growth in the drone industry.<br />
In this blog, I will analyse the legal issues arising from these drone applications, provide recommendations for regulators to facilitate industry development, and identify unresolved legal challenges.<br />
________________________________________<br />
<strong>Legal Issues Arising from Drone Use Cases</strong></p>
<p>1. Airspace Regulation and Flight Permissions<br />
Many of the use cases involve operations in complex airspace or beyond visual line of sight (BVLOS), such as:<br />
•	Decommissioning Nuclear Sites (Sellafield Ltd): BVLOS flights over sensitive areas.<br />
•	Train Track Inspection (Network Rail): Flights over live tracks without service interruption.<br />
•	Electric Grid Tower Inspections (National Grid): Operations near critical infrastructure.<br />
•	Live Flare Stack Offshore Inspections: BVLOS flights over the North Sea platforms.</p>
<p>Legal Considerations:<br />
•	Air Navigation Order 2016 (ANO 2016) and CAA Regulations require specific permissions for BVLOS operations and flights near congested areas or critical infrastructure.<br />
•	Safety Assessments: Operators must conduct rigorous safety cases and obtain Operational Authorisations from the CAA.<br />
•	Compliance with Flight Restriction Zones (FRZs): Especially near nuclear sites, railways, and power grids.</p>
<p>2. Data Protection and Privacy<br />
Use cases involving data capture, such as:<br />
•	Housing Inspections: Capturing images of residential properties.<br />
•	University of Exeter’s Gutter Cleaning: Collecting extensive imagery over campus buildings.<br />
•	Site Security Management: Continuous surveillance operations.</p>
<p>Legal Considerations:<br />
•	General Data Protection Regulation (GDPR): Operators must ensure compliance when processing personal data.<br />
•	Privacy Impact Assessments: Necessary to evaluate risks to individuals&#8217; privacy.<br />
•	Transparency and Consent: Informing affected individuals when feasible.</p>
<p>3. Environmental and Wildlife Impact<br />
Operations in sensitive environmental areas:<br />
•	Peatland Restoration: Drone seeding over ecologically sensitive peatlands.<br />
•	Emergency Response: Drones used in flood monitoring by the Environment Agency.</p>
<p>Legal Considerations:<br />
•	Wildlife and Countryside Act 1981: Protects certain wildlife from disturbance.<br />
•	Environmental Impact Assessments: May be required for operations affecting protected areas.</p>
<p>4. Security and Counter-UAS Measures<br />
Use cases involving critical infrastructure and potential security risks:<br />
•	Nuclear Sites: Potential for drones to be perceived as security threats.<br />
•	Emergency Services: Need to deconflict airspace during emergencies.</p>
<p>Legal Considerations:<br />
•	Security Regulations: Operators must coordinate with authorities to prevent misunderstandings.<br />
•	Counter-Unmanned Aircraft Systems (C-UAS): Awareness of anti-drone measures that could impact legitimate operations.</p>
<p>5. Insurance and Liability<br />
All commercial drone operations must consider:<br />
•	Mandatory Insurance: Compliance with EC Regulation 785/2004 on insurance requirements.<br />
•	Liability for Damages: Clear understanding of responsibility in case of accidents or data breaches.<br />
________________________________________<br />
<strong>Pathways for Regulatory Enhancement</strong></p>
<p>To facilitate easier business operations and industry development, regulators can consider the following recommendations:</p>
<p>1. Streamlining Permissions for BVLOS Operations<br />
•	Develop Standard Scenarios: Create predefined conditions under which BVLOS operations can be conducted without lengthy approval processes.<br />
•	Risk-Based Approaches: Adopt flexible frameworks that assess risk based on the operation&#8217;s specifics rather than a one-size-fits-all model.</p>
<p>2. Enhancing Regulatory Clarity and Guidance<br />
•	Clear Guidelines on Data Protection: Issue specific guidance on GDPR compliance for drone operators.<br />
•	Environmental Operation Protocols: Provide clear procedures for operations in or near protected areas to prevent ecological disturbances.</p>
<p>3. Facilitating Technological Advancements<br />
•	Support for UTM Systems: Implement unmanned traffic management systems to safely integrate drones into UK airspace.<br />
•	Encourage Innovation: Provide sandbox environments where companies can test new technologies under regulatory supervision.</p>
<p>4. Harmonizing Security Measures<br />
•	Establish Communication Channels: Create protocols for operators to notify authorities of intended flights near sensitive sites.<br />
•	Standardise C-UAS Policies: Ensure that anti-drone measures do not inadvertently disrupt lawful operations.</p>
<p>5. Simplifying Insurance Processes<br />
•	Unified Insurance Platforms: Work with the insurance industry to develop products tailored for drone operations.<br />
•	Liability Caps: Consider legislative caps on liability to reduce barriers for smaller operators.<br />
________________________________________<br />
<strong>Legal Issues Needing Resolution</strong></p>
<p>1. Airspace Integration and Management<br />
•	National Airspace Policy for Drones: There is a pressing need for a comprehensive policy that integrates drones into the national airspace, balancing innovation with safety.</p>
<p>2. Privacy Laws Adaptation<br />
•	Modernising Legislation: Current privacy laws may not adequately address the nuances of drone surveillance. Legislation needs updating to reflect technological capabilities.</p>
<p>3. Standardisation of Training and Certification<br />
•	Pilot Competency: Establish standardized training programs and certifications to ensure all operators meet safety and competency requirements.</p>
<p>4. Addressing Environmental Concerns<br />
•	Environmental Regulations: Clear regulations are needed to manage the environmental impact of drones, particularly in wildlife areas.</p>
<p>5. International Coordination<br />
•	Cross-Border Operations: With companies operating internationally, harmonization with EU and international regulations is essential to facilitate operations and maintain competitiveness.<br />
________________________________________<br />
<strong>Other Relevant Issues</strong><br />
1. Public Perception and Acceptance<br />
•	Community Engagement: Efforts should be made to educate the public on the benefits of drones to alleviate concerns over privacy and safety.</p>
<p>2. Workforce Development<br />
•	Skill Shortages: Addressing the need for skilled professionals in the drone industry through education and training initiatives.</p>
<p>3. Ethical Considerations<br />
•	Responsible Use: Establishing ethical guidelines to govern the use of drones, particularly in sensitive contexts like surveillance and data collection.</p>
<p>4. Infrastructure Investment<br />
•	Support Facilities: Investment in infrastructure such as drone ports and charging stations to support the growing industry.</p>
<p>5. Encouraging SME Participation<br />
•	Reducing Barriers to Entry: Simplify regulatory processes to encourage small and medium-sized enterprises to enter the market, fostering innovation and competition.<br />
________________________________________<br />
<strong>Conclusion</strong></p>
<p>The &#8220;Drones In Action&#8221; report highlights the immense potential of drone technology to revolutionize various sectors in the UK. However, to fully realize these benefits, it is imperative to address the legal challenges that accompany such technological advancements. Regulators play a crucial role in shaping a conducive environment that balances innovation with safety, privacy, and environmental stewardship.</p>
<p>By streamlining regulatory processes, updating legal frameworks, and fostering open communication between stakeholders, the UK can position itself at the forefront of the global drone industry. As we navigate this exciting frontier, collaboration between industry players, regulators, and legal professionals will be key to unlocking the full potential of drones while safeguarding public interests.<br />
________________________________________<br />
<strong>Author: Richard Ryan, an experienced drone lawyer specialising in UK aviation law, with 20 years of expertise in navigating the legal landscapes of unmanned aerial systems.</strong></p>
<p>The post <a href="https://blakistons.co.uk/navigating-the-skies-legal-perspectives-on-the-uks-drone-revolution/">Navigating the Skies: Legal Perspectives on the UK&#8217;s Drone Revolution</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
