<?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>Drone Law - As the article provides legal insights specific to drone operations Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/drone-law-as-the-article-provides-legal-insights-specific-to-drone-operations/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/drone-law-as-the-article-provides-legal-insights-specific-to-drone-operations/</link>
	<description>Drone Law</description>
	<lastBuildDate>Thu, 11 Jun 2026 17:44:48 +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>UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots</title>
		<link>https://blakistons.co.uk/uk-drone-rules-from-1-january-2026-a-lawyers-practical-guide-for-pilots/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 11 Jun 2026 17:44:48 +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[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Drone Industry]]></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 Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></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]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[A1 category drones]]></category>
		<category><![CDATA[A2 CofC]]></category>
		<category><![CDATA[A3 category drones]]></category>
		<category><![CDATA[Air Navigation Order 2016]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA drone rules]]></category>
		<category><![CDATA[CAA regulations]]></category>
		<category><![CDATA[commercial drone operations]]></category>
		<category><![CDATA[drone airspace restrictions]]></category>
		<category><![CDATA[Drone Code]]></category>
		<category><![CDATA[drone compliance UK]]></category>
		<category><![CDATA[drone law UK]]></category>
		<category><![CDATA[Drone Lawyer]]></category>
		<category><![CDATA[drone legal advice]]></category>
		<category><![CDATA[drone registration UK]]></category>
		<category><![CDATA[drone regulations 2026]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[Flight Restriction Zones]]></category>
		<category><![CDATA[FPV drones UK]]></category>
		<category><![CDATA[FRZ drone rules]]></category>
		<category><![CDATA[recreational drone flying]]></category>
		<category><![CDATA[Remote ID UK]]></category>
		<category><![CDATA[UK drone pilots]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[UK drone rules]]></category>
		<category><![CDATA[Unmanned Aircraft Systems]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[Visual Line of Sight]]></category>
		<category><![CDATA[VLOS drones]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2685</guid>

					<description><![CDATA[<p>By Richard Ryan, Barrister and Drone Law Specialist From 1 January 2026, the UK drone regulatory framework enters a new phase. While the underlying legal structure remains based on the Air Navigation Order 2016 and UK UAS Regulations, several operational changes are being introduced. Understanding the distinction between legislation, Civil Aviation Authority guidance, and industry [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/uk-drone-rules-from-1-january-2026-a-lawyers-practical-guide-for-pilots/">UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>By Richard Ryan, Barrister and Drone Law Specialist</em></p>
<p>From 1 January 2026, the UK drone regulatory framework enters a new phase. While the underlying legal structure remains based on the Air Navigation Order 2016 and UK UAS Regulations, several operational changes are being introduced. Understanding the distinction between legislation, Civil Aviation Authority guidance, and industry practice is now essential.</p>
<p>This article provides a practical legal overview of the key changes affecting recreational and commercial drone operators flying within the Open Category in the United Kingdom.</p>
<h2>Law and Guidance Are Not the Same Thing</h2>
<p>One of the most common misunderstandings among drone operators is the assumption that everything in the Drone Code or CAA guidance is itself law.</p>
<p>The legal framework consists primarily of legislation, including the Air Navigation Order 2016 and UK UAS Regulations. These are the provisions under which enforcement action and prosecutions may occur.</p>
<p>The CAA also publishes guidance, including CAP 722, Acceptable Means of Compliance and the Drone Code. These materials are highly important, but they are generally guidance rather than legislation. Compliance with them will usually be persuasive evidence of safe and responsible operation.</p>
<p>A useful way to think about compliance is:</p>
<ul>
<li><strong>Green:</strong> operating within CAA guidance and published best practice.</li>
<li><strong>Amber:</strong> operating within the law but outside guidance.</li>
<li><strong>Red:</strong> operating outside the legal framework.</li>
</ul>
<p>Flying outside guidance may sometimes remain lawful, but operators must be ready to justify their decisions if challenged by the police, the CAA or a court.</p>
<h2>Registration Requirements</h2>
<p>Most drones with a camera and weighing more than 100 grams require registration under the Drone and Model Aircraft Registration and Education Scheme.</p>
<p>Operators will generally need both an Operator ID and a Flyer ID.</p>
<p>The Operator ID identifies the person responsible for the aircraft and must be displayed on the drone. The Flyer ID confirms that the pilot has passed the required competency test and remains valid for five years.</p>
<p>Importantly, it is the operator who is registered rather than the drone itself.</p>
<h2>Universal Rules for All Drone Flights</h2>
<h3>Maximum Altitude</h3>
<p>The maximum operating height remains 120 metres, or 400 feet, above the closest point of the earth’s surface. This matters particularly when flying near cliffs, hills, mountains or other changing terrain.</p>
<h3>Visual Line of Sight</h3>
<p>Visual Line of Sight remains a central requirement of UK drone regulation.</p>
<p>The pilot must be able to see the aircraft sufficiently to avoid collisions in the air and manage risks on the ground. Seeing only a small dot or relying solely on navigation lights is unlikely to be defensible if an incident occurs.</p>
<h3>First Person View Flying</h3>
<p>Where FPV goggles are used, a competent observer or spotter is generally required. The spotter should remain beside the pilot and maintain awareness of air and ground hazards while the pilot is focused on the video feed.</p>
<h2>Airspace Restrictions</h2>
<p>Many drone prosecutions arise from breaches of airspace restrictions rather than from technical flying errors.</p>
<p>Airspace should be checked before every flight using a reliable and current source of aeronautical information. The information should be refreshed immediately before launch.</p>
<p>Key restriction types include:</p>
<ul>
<li><strong>Flight Restriction Zones:</strong> permanent restricted areas around airports, prisons and protected sites.</li>
<li><strong>Temporary Restrictions:</strong> restrictions created for events, security operations and public safety purposes.</li>
<li><strong>NOTAMs:</strong> aviation notices which may affect drone operations.</li>
</ul>
<p>Operators should use modern airspace mapping tools and should not assume that yesterday’s airspace position remains correct today.</p>
<h2>A1, A2 and A3 Operational Categories</h2>
<h3>A1: Flying Over People</h3>
<p>The A1 category provides the greatest flexibility. Certain drones under 250 grams may be flown over uninvolved persons, although flight over crowds remains prohibited.</p>
<p>This category generally includes legacy drones under 250g, UK0 and UK1 aircraft, C0 aircraft and C1 aircraft subject to transitional provisions.</p>
<h3>A2: Flying Close to People</h3>
<p>A2 operations allow flight near uninvolved persons but generally prohibit flight directly over them. Operators normally require an A2 Certificate of Competency.</p>
<p>Certain UK2 and C2 aircraft may operate with reduced separation distances where the applicable requirements are met.</p>
<h3>A3: Flying Far from People</h3>
<p>A3 operations are intended for open areas away from uninvolved persons and built-up environments.</p>
<p>Operators must generally maintain 50 metres from uninvolved persons and 150 metres from residential, commercial, industrial and recreational areas.</p>
<h2>Article 16 Authorisations</h2>
<p>Members of recognised model aircraft and drone associations may benefit from Article 16 Authorisations. These permissions can provide greater operational flexibility, including reduced separation distances and access to some locations that would otherwise be more restricted under the Open Category framework.</p>
<h2>Ground Hazards and Article 241</h2>
<p>Even where all technical drone requirements are satisfied, operators remain subject to wider safety duties.</p>
<p>Article 241 of the Air Navigation Order provides that a person must not recklessly or negligently cause or permit an aircraft to endanger any person or property.</p>
<p>Ground hazards may include members of the public, vehicles, buildings, infrastructure, wildlife and protected environmental sites.</p>
<p>Particular care should be taken when operating near Sites of Special Scientific Interest and other environmentally protected areas.</p>
<h2>Remote ID Arrives in 2026</h2>
<p>One of the most significant developments is the introduction of Remote ID.</p>
<p>Remote ID creates an electronic identification system allowing drone operations to be identified through information transmitted by the aircraft.</p>
<p>Implementation is being phased in. New UK1, UK2 and UK3 drones released from 2026 will require Remote ID functionality. Existing aircraft will transition over a longer implementation period extending towards 2028.</p>
<p>Operators should monitor CAA updates closely as implementation progresses.</p>
<h2>Night Flying Requirements</h2>
<p>Night flying remains permissible within the Open Category.</p>
<p>From 2026, operators will generally require a green flashing light attached to the aircraft.</p>
<p>The purpose of the light is to assist people on the ground in recognising the aircraft as a drone. It should not be treated as a substitute for maintaining Visual Line of Sight.</p>
<h2>Insurance and Operational Responsibility</h2>
<p>Recreational operators are generally not legally required to carry insurance, although doing so is strongly recommended.</p>
<p>Commercial operators typically require specialist aviation insurance compliant with applicable regulatory requirements.</p>
<p>Pilots should also ensure they are fit to fly, avoid operating under the influence of alcohol or drugs, and remain alert to low-flying manned aircraft at all times.</p>
<h2>Conclusion</h2>
<p>The 2026 changes represent an evolution rather than a revolution in UK drone regulation.</p>
<p>The key principles remain unchanged: understand the law, check airspace before every flight, maintain Visual Line of Sight, operate safely and proportionately, and keep abreast of developments concerning Remote ID and future airspace integration.</p>
<p>For most operators, compliance remains straightforward. Those who understand the distinction between legislation and guidance, conduct appropriate pre-flight planning and adopt a risk-based approach should continue to fly safely and lawfully throughout 2026 and beyond.</p>
<p><strong>Disclaimer:</strong> This article is provided for general information only and does not constitute legal advice. Specific advice should be sought in relation to individual circumstances. </p>
<p>Richard Ryan is a practising barrister, Arbitrator , drone lawyer, and regulatory specialist with more than 20 years&#8217; experience in litigation, arbitration, aviation, defence, technology, construction, and commercial law. He advises drone operators, aerospace companies, government bodies, and technology businesses on complex regulatory, operational, and compliance issues relating to unmanned aircraft systems (UAS), counter-UAS technologies, urban air mobility, and emerging aviation regulation.</p>
<p>Richard is currently undertaking PhD research at Cranfield University examining the future regulatory framework for Beyond Visual Line of Sight (BVLOS) operations, Unmanned Traffic Management (UTM), and the integration of drones into shared airspace. He regularly writes on developments in drone law, aviation regulation, privacy, safety, and the future of autonomous flight.</p>
<p>The views expressed in this article are for general information purposes only and do not constitute legal advice.</p>
<p>The post <a href="https://blakistons.co.uk/uk-drone-rules-from-1-january-2026-a-lawyers-practical-guide-for-pilots/">UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots</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>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>When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports</title>
		<link>https://blakistons.co.uk/when-just-a-minute-becomes-bvlos-legal-lessons-for-drone-operators-from-chirps-september-2025-reports/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 27 Oct 2025 19:14:43 +0000</pubDate>
				<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Case Studies - Provides a real-world incident analysis for educational purposes in drone law and compliance]]></category>
		<category><![CDATA[Civil Aviation]]></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 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 Operators]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Government Reports]]></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 Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Urban Air Mobility]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[ANO 2016 Article 241]]></category>
		<category><![CDATA[battery settings]]></category>
		<category><![CDATA[BMFA]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CHIRP]]></category>
		<category><![CDATA[crowds]]></category>
		<category><![CDATA[DJI]]></category>
		<category><![CDATA[Drone and Model Aircraft Code]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[event safety]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[Mavic 4 Pro]]></category>
		<category><![CDATA[Mini 2]]></category>
		<category><![CDATA[Nottingham Carnival]]></category>
		<category><![CDATA[operations manual]]></category>
		<category><![CDATA[Operator ID]]></category>
		<category><![CDATA[powerlines]]></category>
		<category><![CDATA[RC2 controller]]></category>
		<category><![CDATA[Return to Home]]></category>
		<category><![CDATA[RTH altitude]]></category>
		<category><![CDATA[screen recording]]></category>
		<category><![CDATA[SWEETS]]></category>
		<category><![CDATA[UK CAA]]></category>
		<category><![CDATA[visual observer]]></category>
		<category><![CDATA[VLOS]]></category>
		<category><![CDATA[waypoint missions]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2590</guid>

					<description><![CDATA[<p>By Richard Ryan, Barrister &#038; Drone Lawyer &#8211; practical takeaways, not legal advice for your specific situation. Why this matters The incidents, in plain English &#8211; and what the law expects Unintentional BVLOS x3 (BMFA community) Nottingham Carnival injury (Mini 2) &#8220;My app froze&#8221; (Mavic 4 Pro + RC2) Fatigue and stress (power-line inspection) RTH [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/when-just-a-minute-becomes-bvlos-legal-lessons-for-drone-operators-from-chirps-september-2025-reports/">When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- ASCII-only HTML: no smart quotes, no en/em dashes, no non-breaking spaces --></p>
<article itemscope itemtype="https://schema.org/Article">
<p><em>By Richard Ryan, Barrister &#038; Drone Lawyer &#8211; practical takeaways, not legal advice for your specific situation.</em></p>
<nav aria-label="Table of contents">
<ul>
<li><a href="#why-this-matters">Why this matters</a></li>
<li><a href="#incidents">The incidents, in plain English &#8211; and what the law expects</a>
<ul>
<li><a href="#incident-bvlos">Unintentional BVLOS x3 (BMFA community)</a></li>
<li><a href="#incident-carnival">Nottingham Carnival injury (Mini 2)</a></li>
<li><a href="#incident-app-freeze">&#8220;My app froze&#8221; (Mavic 4 Pro + RC2)</a></li>
<li><a href="#incident-fatigue">Fatigue and stress (power-line inspection)</a></li>
<li><a href="#incident-rth-powerlines">RTH vs powerlines (mapping mission)</a></li>
</ul>
</li>
<li><a href="#pillars">Five legal pillars these cases keep hitting</a></li>
<li><a href="#playbook">Turn the lessons into a defensible playbook</a></li>
<li><a href="#bottom-line">Bottom line</a></li>
<li><a href="#sources">Credit and resources</a></li>
</ul>
</nav>
<section id="why-this-matters">
<h2>Why this matters</h2>
<p>
      CHIRP&#8217;s <strong>Drone/UAS FEEDBACK Edition 14 (September 2025)</strong> curates incidents that look ordinary until you view them through a law-and-liability lens:<br />
      three model-flying events that drifted into <strong>unintentional BVLOS</strong>, a Mini 2 injury at a carnival, a controller or app freeze mid-mission,<br />
      a fatigue-tinged flight that autolanded at 20 percent battery into a tree, and an RTH climb toward powerlines. Each contains avoidable legal exposure<br />
      that you can mitigate with better planning, clear roles, and a few settings changes.
    </p>
</section>
<section id="incidents">
<h2>The incidents, in plain English &#8211; and what the law expects</h2>
<section id="incident-bvlos">
<h3>1) Unintentional BVLOS x3 (BMFA community)</h3>
<ul>
<li><strong>What happened:</strong> One EDF jet lost power from a poor solder joint after a user modification; two other flights went BVLOS when sea fog or thermal lift arrived faster than forecast.</li>
<li><strong>Legal frame (UK):</strong> The Drone and Model Aircraft Code requires <strong>direct VLOS</strong> and the ability to determine <strong>orientation</strong> at all times. If you cannot do that, the flight is non-compliant.</li>
<li><strong>Practical fix:</strong> Treat post-purchase alterations as airworthiness-significant and inspect them before each flight. Use BMFA&#8217;s <strong>SWEETS</strong> pre-flight. Adopt a simple &#8220;radial scan&#8221; habit: eyes out (aircraft and airspace) then quick glance down (controller or map) then eyes out again.</li>
</ul>
</section>
<section id="incident-carnival">
<h3>2) Nottingham Carnival injury (Mini 2)</h3>
<ul>
<li><strong>What happened:</strong> A minor pressed &#8220;land&#8221; while the supervising adult was distracted; the drone struck another child who was sitting on someone&#8217;s shoulders. Police confiscated the aircraft. No Operator ID was displayed and it was flown over a crowd.</li>
<li><strong>Legal frame (UK):</strong> <strong>Never fly over crowds or assemblies of people</strong>. Label the aircraft with a visible <strong>Operator ID</strong>. Where injury occurs, expect scrutiny under general endangerment provisions.</li>
<li><strong>Practical fix:</strong> Establish a safe <strong>TOLA</strong> (take-off and landing area) away from the crowd. Use aviation-style handover phraseology: &#8220;You have control&#8221; / &#8220;I have control&#8221;. Keep controller audio alerts audible. Supervision of minors must be active and informed by the Code.</li>
</ul>
</section>
<section id="incident-app-freeze">
<h3>3) &#8220;My app froze&#8221; (Mavic 4 Pro + RC2; 87-waypoint mission)</h3>
<ul>
<li><strong>What happened:</strong> Switching to Map View mid-mission froze the Fly app. The pilot used the hardware <strong>RTH</strong> button to recover the aircraft. Possible overload from running a large waypoint mission while screen-recording.</li>
<li><strong>Legal frame:</strong> You remain responsible for safe operation even when the UI hiccups. The defensible question is whether your procedures anticipated foreseeable failures, such as hardware RTH muscle memory, function checks, and reboot-on-the-ground policies.</li>
<li><strong>Practical fix:</strong> For long waypoint jobs, test the profile without screen-recording first. Pre-brief the hardware RTH action. Use a <strong>visual observer</strong> if you will be heads-down.</li>
</ul>
</section>
<section id="incident-fatigue">
<h3>4) Fatigue and stress (power-line inspection)</h3>
<ul>
<li><strong>What happened:</strong> The pilot became disoriented, lost VLOS about 1,700 ft from home, hit 20 percent battery, and, unaware that &#8220;land at 20 percent&#8221; was set, descended into a tree despite pressing RTH.</li>
<li><strong>Practical fix:</strong> Know and brief your <strong>low-battery action</strong> (RTH vs auto-land vs hover) in the <strong>Operations Manual</strong>. Use two-crew where terrain or workload increases disorientation risk. Remember UK requirements to maintain VLOS and orientation at all times.</li>
</ul>
</section>
<section id="incident-rth-powerlines">
<h3>5) RTH vs powerlines (mapping mission)</h3>
<ul>
<li><strong>What happened:</strong> An automated flight went off-nominal. On RTH, the aircraft likely contacted an obstacle while climbing. CHIRP notes the perception trap of judging wire clearance at range and reminds that wires sag mid-span.</li>
<li><strong>Practical fix:</strong> Set <strong>RTH altitude</strong> locally before each flight, above towers, tree lines, cranes, and powerlines. Do not rely on obstacle avoidance to detect thin wires. Pre-flight, measure line heights relative to the home point and add margin for sag and wind.</li>
</ul>
</section>
</section>
<section id="pillars">
<h2>Five legal pillars these cases keep hitting</h2>
<ol>
<li><strong>VLOS is non-negotiable.</strong> Keep the aircraft in direct sight and be able to tell its orientation, with a full view of surrounding airspace.</li>
<li><strong>Crowds are out of bounds.</strong> &#8220;Assemblies of people&#8221; are defined by the inability to disperse quickly, not by a headcount.</li>
<li><strong>Operator ID labelling is strict.</strong> Visible, legible, on the airframe. Sub-250 g camera drones typically still require an Operator ID.</li>
<li><strong>Endangerment provisions are broad.</strong> If someone is endangered or injured, regulators may consider reckless or negligent operation.</li>
<li><strong>Automation is not absolution.</strong> You own the outcomes of RTH, low-battery actions, waypointing, and controller limits.</li>
</ol>
</section>
<section id="playbook">
<h2>Turn the lessons into a defensible playbook</h2>
<h3>A. Pre-flight and design for failure</h3>
<ul>
<li><strong>Modified anything?</strong> Treat user soldering, adapters, and third-party leads as risk-relevant. Inspect that joint every flight until replaced with a proven assembly. Log the check.</li>
<li><strong>Weather is slippery.</strong> Do not rely on one app. Triangulate forecasts. Identify <strong>abort gates</strong> if visibility closes in (fog, showers, glare). Use <strong>SWEETS</strong> at the field.</li>
<li><strong>Controller workload.</strong> For heavy waypoint missions, disable screen-recording unless proven stable. Rehearse <strong>hardware RTH</strong> and app-independent control.</li>
</ul>
<h3>B. RTH and battery settings you can defend</h3>
<ul>
<li><strong>Set RTH altitude locally, every time.</strong> Clear known obstacles and powerlines. Consider Advanced RTH where available.</li>
<li><strong>Know low-battery behavior.</strong> Document thresholds in the Operations Manual, brief them to the crew, and confirm on the controller before take-off.</li>
</ul>
<h3>C. People, roles, and sterile cockpit</h3>
<ul>
<li><strong>Observer next to you</strong> for heads-down tasks, with real-time verbal coordination.</li>
<li><strong>Minors at the sticks?</strong> Only with active oversight, formal handovers, and never within or over a crowd.</li>
<li><strong>Events and assemblies.</strong> Create buffer zones and safe <strong>TOLA</strong> sites. If a client insists on crowd-proximate shots, the safest and most defensible answer is often no without appropriate authorization and controls.</li>
</ul>
<h3>D. Evidence and reporting (preserve the facts)</h3>
<ul>
<li>After any occurrence, preserve flight logs, app caches, screen recordings, controller settings, and note battery and RTH configuration.</li>
<li>Consider confidential safety reporting to <strong>CHIRP</strong> in the UK (and NASA ASRS in the U.S.) to help the community learn without blame.</li>
</ul>
</section>
<section id="bottom-line">
<h2>Bottom line</h2>
<p>
      The risk here is ordinary: a conversation at the wrong moment, fog rolling in, a buried setting, an RTH altitude that did not clear wires,<br />
      or a controller pushed too hard. The Code&#8217;s core duties &#8211; <strong>VLOS</strong>, <strong>no crowds</strong>, <strong>proper ID labelling</strong>,<br />
      <strong>know your automation</strong>, and <strong>keep records</strong> &#8211; are your best legal shield when something goes wrong.</p>
<section id="bmfa-sweets">
<h2>BMFA SWEETS: a quick pre-flight check</h2>
<ul>
<li><strong>S — Sun:</strong> position now and later; glare; keep VLOS; avoid flying through the sun.</li>
<li><strong>W — Wind:</strong> direction/strength/turbulence; safe areas for forced or dead-stick landings.</li>
<li><strong>E — Environment:</strong> visibility (rain, mist, fog, fading light), people nearby, RF risks, space to fly a full circuit.</li>
<li><strong>E — Emergencies:</strong> plan what you will do if there is a malfunction or airspace incursion; confirm failsafes.</li>
<li><strong>T — Transmitter control:</strong> local Tx control and frequencies; correct model; trims/rates; Tx power/voltage.</li>
<li><strong>S — Site rules:</strong> club rules, local byelaws, no-fly zones, height and airspace limits.</li>
</ul>
<p><em>Note: some older guides use &#8220;Eventualities&#8221; for the first E. Meaning is the same: think ahead about what could happen and how you will handle it.</em></p>
</section>
<p><em>This article is general information, not legal advice. If an incident has occurred, speak to counsel at Blakiston&#8217;s Chambers before making statements to third parties and preserve all electronic evidence immediately.</em></p>
</section>
<section id="sources">
<h2>Credit and resources</h2>
<ul>
<li>Based on incidents and analysis in <strong>CHIRP Drone/UAS FEEDBACK Edition 14 (September 2025)</strong>.</li>
<li>BMFA pre-flight mnemonic SWEETS: <a href="https://handbook.bmfa.uk/13-general-model-safety" rel="noopener">handbook.bmfa.uk/13-general-model-safety</a></li>
<li>UK Drone and Model Aircraft Code: <a href="https://register-drones.caa.co.uk" rel="noopener">register-drones.caa.co.uk</a></li>
<li>Report a safety concern to CHIRP (confidential): <a href="https://www.chirp.co.uk/aviation/submit-a-report" rel="noopener">chirp.co.uk/aviation/submit-a-report</a></li>
</ul>
</section>
</article>
<p>The post <a href="https://blakistons.co.uk/when-just-a-minute-becomes-bvlos-legal-lessons-for-drone-operators-from-chirps-september-2025-reports/">When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5</title>
		<link>https://blakistons.co.uk/what-the-uk-drone-industry-can-learn-from-easas-adoption-of-sora-2-5/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 30 Sep 2025 10:57:46 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></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[Drones]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[European Union Policy Updates]]></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[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[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[UAS (Unmanned Aircraft Systems)]]></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 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]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[bvlos uk]]></category>
		<category><![CDATA[drone law barrister]]></category>
		<category><![CDATA[drone operators compliance]]></category>
		<category><![CDATA[Drone Regulations UK]]></category>
		<category><![CDATA[easa drone rules]]></category>
		<category><![CDATA[osc applications]]></category>
		<category><![CDATA[sora 2.5]]></category>
		<category><![CDATA[specific operations risk assessment]]></category>
		<category><![CDATA[uk caa drones]]></category>
		<category><![CDATA[UK Drone Law]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2580</guid>

					<description><![CDATA[<p>By Richard Ryan, Barrister &#038; Drone Lawyer • 30th September 2025 Introduction On 29 September 2025, the European Union Aviation Safety Agency (EASA) published ED Decision 2025/018/R, updating the Acceptable Means of Compliance (AMC) and Guidance Material (GM) to Implementing Regulation (EU) 2019/947. This update introduces the European version of the Specific Operations Risk Assessment [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/what-the-uk-drone-industry-can-learn-from-easas-adoption-of-sora-2-5/">What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Blakiston's Chambers | SORA 2.5 Article --></p>
<section id="bc-sora-article" lang="en-GB">
<style>
    #bc-sora-article {
      --content-width: min(900px, 92vw);
      --pad: max(16px, 6vw);
      --text: #222222;
    }
    #bc-sora-article, #bc-sora-article * {
      box-sizing: border-box;
      color: var(--text) !important;
      font-family: Georgia, "Times New Roman", serif;
    }
    #bc-sora-article .bc-wrap {
      width: var(--content-width);
      margin: 0 auto;
      padding: 0 var(--pad);
    }
    #bc-sora-article .bc-meta {
      margin: .25rem auto 1.5rem;
      font-size: .95rem;
      opacity: .95;
    }
    #bc-sora-article article {
      line-height: 1.6;
      padding: 0 0 2.5rem;
    }
    #bc-sora-article h2 {
      margin-top: 2rem;
      font-size: 1.55rem;
      line-height: 1.35;
    }
    #bc-sora-article h3 {
      margin-top: 1.1rem;
      font-size: 1.2rem;
    }
    #bc-sora-article p { margin: .85rem 0; }
    #bc-sora-article ul,
    #bc-sora-article ol { margin: .6rem 0 1rem 1.25rem; }
    #bc-sora-article li { margin: .35rem 0; }
    #bc-sora-article .bc-callout {
      border-left: 4px solid var(--text);
      background: #f7f7f7;
      padding: .9rem 1rem;
      margin: 1.5rem 0;
    }
    #bc-sora-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 --></p>
<div class="bc-wrap bc-meta">
    <span>By Richard Ryan, Barrister &#038; Drone Lawyer</span> •<br />
    <time datetime="2025-09-30">30th September 2025</time>
  </div>
<p>  <!-- Article body --></p>
<article class="bc-wrap" role="article">
<section id="intro">
<h2>Introduction</h2>
<p>On 29 September 2025, the European Union Aviation Safety Agency (EASA) published <strong>ED Decision 2025/018/R</strong>, updating the Acceptable Means of Compliance (AMC) and Guidance Material (GM) to Implementing Regulation (EU) 2019/947. This update introduces the European version of the <strong>Specific Operations Risk Assessment (SORA) 2.5</strong>, developed by the Joint Authorities for Rulemaking on Unmanned Systems (JARUS).</p>
<p>Although the UK has left the EU regulatory framework, these developments are highly relevant. UK operators, manufacturers, and regulators can learn much from how EASA is simplifying compliance, clarifying roles, and promoting harmonisation across Member States.</p>
</section>
<section id="changes">
<h2>What Changed under SORA 2.5?</h2>
<ul>
<li><strong>Simplification of procedures:</strong> Ambiguities from earlier SORA versions have been removed, making it easier for operators and authorities to understand their obligations.</li>
<li><strong>Clarity of roles:</strong> Responsibilities are now more clearly divided between operators, designers, and manufacturers. For example, design verification reports (DVRs) from EASA are required at SAIL IV, and type certification is required at SAIL V and VI.</li>
<li><strong>Terminology alignment:</strong> EU-specific terms replace JARUS wording. For instance, “EVLOS” has been dropped in favour of “BVLOS with airspace observer”.</li>
<li><strong>Containment requirements:</strong> Refined criteria for ground risk buffers and adjacent ground areas, particularly relevant for BVLOS and urban operations.</li>
<li><strong>Flexibility for competent authorities:</strong> NAAs can use direct assessment, recognised entities, or qualified entities to review compliance.</li>
<li><strong>Removal of weak cybersecurity rules:</strong> EASA stripped out JARUS’s cybersecurity provisions, deeming them disproportionate, but stressed that vulnerability assessments remain best practice.</li>
</ul>
</section>
<section id="lessons">
<h2>Lessons for the UK CAA</h2>
<ol>
<li><strong>Consistency and clarity –</strong> EASA has responded to industry feedback by clarifying operator versus manufacturer responsibilities. The UK’s guidance could benefit from similar precision, particularly in BVLOS authorisations.</li>
<li><strong>Streamlining approvals –</strong> The two-phase SORA process (Phase 1 for risk identification, Phase 2 for compliance evidence) allows operators to obtain early regulatory feedback. This approach could make the UK’s OSC process faster and more predictable.</li>
<li><strong>Population density mapping –</strong> EASA now recommends more accurate, dynamic maps to avoid over- or under-estimating risk in commercial and recreational areas. The UK could adopt a similar model, especially for urban drone delivery corridors.</li>
<li><strong>Terminology alignment –</strong> Dropping “EVLOS” in favour of “BVLOS with AO” reflects operational reality and removes confusion. The UK should consider whether maintaining unique terminology helps or hinders international harmonisation.</li>
<li><strong>Cybersecurity gap –</strong> By removing JARUS’s rules but encouraging vulnerability assessments, EASA has left space for proportionate, risk-based security. The CAA could similarly mandate cybersecurity risk assessments in line with wider aviation resilience standards.</li>
</ol>
</section>
<section id="best-practice">
<h2>Best Practice for UK Drone Pilots and Operators</h2>
<ul>
<li><strong>Adopt SORA 2.5 methodology voluntarily –</strong> Even though the UK hasn’t formally adopted it, operators preparing risk assessments will benefit from aligning with European standards, especially if seeking approvals abroad.</li>
<li><strong>Keep clear records –</strong> Maintain compliance matrices and comprehensive safety portfolios (CSPs) as outlined in SORA 2.5. This not only supports OSC applications but also protects operators in audits and insurance claims.</li>
<li><strong>Use accurate population data –</strong> Don’t rely solely on outdated maps; supplement with local knowledge, real-time data, or site surveys to avoid underestimating risk.</li>
<li><strong>Plan robust contingency procedures –</strong> Ensure abnormal and emergency procedures are well defined, tested, and rehearsed with crew. The new focus on containment means that “fly-away” risks must be demonstrably controlled.</li>
<li><strong>Stay ahead on cybersecurity –</strong> Even though not mandated, conduct vulnerability assessments for command-and-control links and data storage. Cyber weaknesses could undermine insurance and liability cover.</li>
</ul>
</section>
<section id="conclusion">
<h2>Conclusion</h2>
<p>EASA’s adoption of SORA 2.5 is a significant step towards regulatory clarity and harmonisation across Europe. The UK CAA should take note: simplifying authorisations, clarifying roles, and embracing proportionate risk-based approaches would strengthen the UK’s position as a leader in drone regulation.</p>
<p>For operators and pilots, the message is clear: best practice means anticipating international standards, not just meeting the minimum domestic requirement.</p>
<div class="bc-callout">
<p>At <strong>Blakiston’s Chambers</strong> we advise 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/what-the-uk-drone-industry-can-learn-from-easas-adoption-of-sora-2-5/">What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5</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>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 fetchpriority="high" 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>
	</channel>
</rss>
