<?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>UTM (Unmanned Aircraft System Traffic Management) Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/utm-unmanned-aircraft-system-traffic-management/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/utm-unmanned-aircraft-system-traffic-management/</link>
	<description>Drone Law</description>
	<lastBuildDate>Mon, 06 Jul 2026 09:53:17 +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>Navigating UK SORA: A Drone Lawyer’s Guide to CAA Decision No. 60</title>
		<link>https://blakistons.co.uk/navigating-uk-sora-a-drone-lawyers-guide-to-caa-decision-no-60/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 06 Jul 2026 09:53:17 +0000</pubDate>
				<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA) Policies]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Industry Challenges]]></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 Regulations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[International Drone Policies]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></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 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[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[Aerospace Law]]></category>
		<category><![CDATA[AI Governance]]></category>
		<category><![CDATA[Air Risk]]></category>
		<category><![CDATA[artificial intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[aviation safety]]></category>
		<category><![CDATA[Beyond Visual Line of Sight]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA Decision No. 60]]></category>
		<category><![CDATA[Civil Aviation Authority]]></category>
		<category><![CDATA[Commercial Drones]]></category>
		<category><![CDATA[Containment]]></category>
		<category><![CDATA[Detect and Avoid]]></category>
		<category><![CDATA[Drone Compliance]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Evidence Retention]]></category>
		<category><![CDATA[Flight Safety]]></category>
		<category><![CDATA[Flight Termination System]]></category>
		<category><![CDATA[Geo-caging]]></category>
		<category><![CDATA[Ground Risk]]></category>
		<category><![CDATA[Kinetic Energy]]></category>
		<category><![CDATA[Operational Authorisation]]></category>
		<category><![CDATA[Operational Safety Objectives]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[SAIL]]></category>
		<category><![CDATA[Specific Category]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UAV]]></category>
		<category><![CDATA[UK AI Framework]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[UK SORA]]></category>
		<category><![CDATA[Uncrewed Aircraft Systems]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2703</guid>

					<description><![CDATA[<p>Drone Law &#124; UK SORA &#124; CAA Regulation &#124; AI Governance Summary: CAA Decision No. 60 marks a significant development in the regulation of Specific category drone operations in the UK. Coming into force on 1 October 2026, it updates the UK SORA framework and introduces clearer expectations around compliance evidence, ground-risk mitigation, containment, kinetic [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/navigating-uk-sora-a-drone-lawyers-guide-to-caa-decision-no-60/">Navigating UK SORA: A Drone Lawyer’s Guide to CAA Decision No. 60</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="drone-law-blog">
<p><strong>Drone Law | UK SORA | CAA Regulation | AI Governance</strong></p>
<p><strong>Summary:</strong> CAA Decision No. 60 marks a significant development in the regulation of Specific category drone operations in the UK. Coming into force on 1 October 2026, it updates the UK SORA framework and introduces clearer expectations around compliance evidence, ground-risk mitigation, containment, kinetic energy analysis and evidence retention. For operators, the message is clear: compliance is no longer just a narrative safety case. It must be evidenced, retained and auditable.</p>
<h2>1. Why Decision No. 60 Matters</h2>
<p>The UK’s lower airspace is becoming increasingly complex. Beyond Visual Line of Sight operations, drone delivery, infrastructure inspection, emergency services use, autonomous routing and higher-risk commercial UAS activity all require a more mature regulatory framework.</p>
<p>CAA Decision No. 60 updates the Acceptable Means of Compliance and Guidance Material for UK Regulation (EU) 2019/947. In practical terms, it strengthens the UK Specific Operation Risk Assessment, or UK SORA, for operators seeking authorisation in the Specific category.</p>
<p>The legal significance is that UK SORA is becoming a structured assurance methodology. Operators must not merely state that an operation is safe. They must demonstrate that the aircraft, procedures, people, operational volume, ground environment, airspace risks, mitigations and emergency arrangements meet the required level of safety.</p>
<h2>2. UK SORA Is Not a Box-Ticking Exercise</h2>
<p>UK SORA exists to support the operational risk assessment required for Specific category operations. It considers both ground risk and air risk, then applies mitigations and operational safety objectives according to the Specific Assurance and Integrity Level, or SAIL.</p>
<p>The updated framework is particularly important because it clarifies how operators must gather, present and retain compliance evidence. This is a move away from generalised operational assertions and towards aviation-grade documentation.</p>
<h2>3. The Three Compliance Pathways</h2>
<p>Decision No. 60 identifies three broad routes for demonstrating compliance.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Pathway</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">What It Means</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Legal Significance</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Declarative approach</td>
<td style="border: 1px solid #000; padding: 8px;">The operator declares that it meets the relevant acceptable means of compliance.</td>
<td style="border: 1px solid #000; padding: 8px;">Suitable for lower-risk requirements, but the declaration must still be accurate and supportable.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Agreed compliance basis</td>
<td style="border: 1px solid #000; padding: 8px;">The operator and CAA agree in advance how compliance will be demonstrated.</td>
<td style="border: 1px solid #000; padding: 8px;">Useful for novel or complex operations where evidence may include testing, analysis or design appraisal.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Compliance evidence approach</td>
<td style="border: 1px solid #000; padding: 8px;">The operator submits both the compliance basis and the underlying evidence to the CAA.</td>
<td style="border: 1px solid #000; padding: 8px;">The most rigorous route, likely to be required for higher-risk or technically complex operations.</td>
</tr>
</tbody>
</table>
<p>Operators must also retain compliance evidence for the duration of the operational authorisation and for three years after operations under that authorisation cease. That evidence may become critical in a CAA audit, incident investigation, insurance dispute or civil claim.</p>
<h2>4. Ground Risk: What Happens If the Drone Falls?</h2>
<p>Ground risk is central to UK SORA. The law is concerned not only with whether the drone can fly, but with what happens if it fails. Decision No. 60 provides more detailed guidance on how operators may reduce ground risk.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Mitigation</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Description</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Key Legal Risk</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">M1A: Sheltering</td>
<td style="border: 1px solid #000; padding: 8px;">Relying on people being inside structures.</td>
<td style="border: 1px solid #000; padding: 8px;">The aircraft must not be capable of penetrating the relevant structures.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">M1B: Operational restrictions</td>
<td style="border: 1px solid #000; padding: 8px;">Operating at times or in areas where fewer uninvolved people are present.</td>
<td style="border: 1px solid #000; padding: 8px;">Population assumptions must be evidenced and realistic.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">M1C: Ground observation</td>
<td style="border: 1px solid #000; padding: 8px;">Using observers or technical systems to detect uninvolved people.</td>
<td style="border: 1px solid #000; padding: 8px;">Detection capability, observer competence and response procedures must be credible.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">M2: Impact mitigation</td>
<td style="border: 1px solid #000; padding: 8px;">Reducing impact energy through parachutes, flight termination or design features.</td>
<td style="border: 1px solid #000; padding: 8px;">Deployment reliability, minimum altitude, failure modes and secondary hazards must be addressed.</td>
</tr>
</tbody>
</table>
<h2>5. Kinetic Energy and Penetration Risk</h2>
<p>Decision No. 60 gives particular importance to kinetic energy. This matters because it converts safety claims into measurable injury-risk analysis.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Kinetic Energy</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Risk Category</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Operator Requirement</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Up to 175 joules</td>
<td style="border: 1px solid #000; padding: 8px;">Lower hazard</td>
<td style="border: 1px solid #000; padding: 8px;">Generally less demanding penetration analysis, subject to the operational context.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">175 to 7,000 joules</td>
<td style="border: 1px solid #000; padding: 8px;">Medium hazard</td>
<td style="border: 1px solid #000; padding: 8px;">Penetration analysis should be conducted against representative structures.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Over 7,000 joules</td>
<td style="border: 1px solid #000; padding: 8px;">High hazard</td>
<td style="border: 1px solid #000; padding: 8px;">More rigorous evidence is required, potentially including crashworthiness analysis and structural modelling.</td>
</tr>
</tbody>
</table>
<p>Operators should not rely on generic manufacturer statements. They need platform-specific evidence: mass, velocity, terminal impact behaviour, parachute performance, battery fire risk and representative structural analysis.</p>
<h2>6. Containment and Fly-Away Risk</h2>
<p>Containment is a central pillar of the updated UK SORA framework. It asks whether the unmanned aircraft can be kept within its operational volume and ground risk buffer, even after failure or loss of control.</p>
<p>For lower-risk operations, containment may be assessed qualitatively through design appraisal and procedural evidence. For higher-risk operations, the CAA may expect quantitative probability targets, such as demonstrating that the probability of exiting the relevant volume or buffer is below specified thresholds per flight hour.</p>
<p>Containment evidence may include geo-caging, tethering, independent flight termination systems, lost-link logic, command-and-control resilience, navigation integrity, power-system independence and emergency procedures.</p>
<h2>7. EU AI Act and UK AI Standards</h2>
<p>Decision No. 60 is not an AI regulation. However, many modern drone operations increasingly rely on AI-enabled functions, including detect-and-avoid, automated route planning, computer vision, landing assistance, ground-person detection, predictive maintenance and autonomous contingency management.</p>
<p>The EU AI Act is relevant as a benchmark for risk management, technical documentation, record-keeping, transparency, human oversight, robustness and cybersecurity. The UK does not currently have a single equivalent UK AI Act. Instead, it follows a sector-led, principles-based model based on safety, security and robustness; transparency and explainability; fairness; accountability and governance; and contestability and redress.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">UK SORA Issue</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">AI Governance Standard</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Practical Evidence</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Operational risk assessment</td>
<td style="border: 1px solid #000; padding: 8px;">Lifecycle risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Hazard log, AI failure-mode analysis, operating design domain and residual-risk register.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Compliance evidence</td>
<td style="border: 1px solid #000; padding: 8px;">Technical documentation</td>
<td style="border: 1px solid #000; padding: 8px;">Version-controlled technical file, test reports, software release notes and design appraisals.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Ground observation</td>
<td style="border: 1px solid #000; padding: 8px;">Accuracy and human oversight</td>
<td style="border: 1px solid #000; padding: 8px;">Detection metrics, false-negative analysis, lighting limits and observer escalation procedures.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Containment</td>
<td style="border: 1px solid #000; padding: 8px;">Robustness and cybersecurity</td>
<td style="border: 1px solid #000; padding: 8px;">Geo-cage testing, lost-link logic, GNSS spoofing assessment and command-link resilience.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Evidence retention</td>
<td style="border: 1px solid #000; padding: 8px;">Record-keeping and auditability</td>
<td style="border: 1px solid #000; padding: 8px;">Flight logs, telemetry, AI outputs, incident reviews and corrective actions.</td>
</tr>
</tbody>
</table>
<h2>8. Data Protection and Surveillance Risk</h2>
<p>Many Specific category operations involve cameras, thermal imaging, mapping payloads or AI-enabled object recognition. UK SORA primarily addresses safety, but operators must also consider privacy, data protection and surveillance risk.</p>
<p>If cameras or AI systems detect uninvolved persons, personal data may be captured, stored or analysed. Operators may need a data protection impact assessment, retention limits, access controls, privacy notices and clear rules on secondary use.</p>
<h2>9. What Operators Should Do Before 1 October 2026</h2>
<p>Operators should review their safety cases and evidence packs now. In particular, they should check:</p>
<ul>
<li>Aircraft mass, speed, kinetic energy and terminal velocity;</li>
<li>Ground-risk assumptions and population-density evidence;</li>
<li>Sheltering, operational restriction and observation claims;</li>
<li>Parachute, flight termination and impact mitigation evidence;</li>
<li>Containment evidence, including geo-caging and lost-link logic;</li>
<li>AI-enabled functions, including detect-and-avoid and automated decision-support tools;</li>
<li>Evidence retention systems;</li>
<li>Supplier contracts for access to technical data.</li>
</ul>
<h2>10. Bottom Line</h2>
<p>CAA Decision No. 60 marks a shift from descriptive drone safety cases to structured assurance. Operators must now be able to prove their safety claims through coherent, retained and auditable evidence.</p>
<p>The most important development is the convergence between aviation safety and AI governance. UK SORA asks whether the drone operation is safe. The EU AI Act and UK AI principles ask whether automated systems are risk-managed, documented, robust, explainable, secure and subject to human oversight. For modern drone operations, those are increasingly the same question.</p>
<p>Compliance is not what the operator says it does. Compliance is what the operator can prove.</p>
<hr />
<h2>About the Author</h2>
<p><strong>Richard Ryan</strong> is a barrister, Chartered Arbitrator and specialist in drone law, aviation regulation and artificial intelligence. He advises operators, manufacturers and public bodies on UK CAA regulation, UK SORA, BVLOS operations, AI governance and commercial drone operations. He is currently undertaking a PhD at Cranfield University researching the legal framework for autonomous aviation and future airspace integration.</p>
<p><em>This article is general legal commentary and does not constitute legal advice.</em></p>
</div>
<p>The post <a href="https://blakistons.co.uk/navigating-uk-sora-a-drone-lawyers-guide-to-caa-decision-no-60/">Navigating UK SORA: A Drone Lawyer’s Guide to CAA Decision No. 60</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>Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities</title>
		<link>https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 28 Oct 2025 08:05:36 +0000</pubDate>
				<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Partnerships and Collaborations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[Case Studies - Provides a real-world incident analysis for educational purposes in drone law and compliance]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Drone Delivery Companies]]></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 Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Technology]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Insurance and Liability]]></category>
		<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[International Drone Policies]]></category>
		<category><![CDATA[International Drone Regulations]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Compliance Strategies]]></category>
		<category><![CDATA[Regulatory Oversight]]></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[Technology and Innovation]]></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[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[Urban Air Mobility]]></category>
		<category><![CDATA[Urban Drone Delivery]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[Atypical Air Environment]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[Blakiston’s Chambers]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA]]></category>
		<category><![CDATA[drone authorisation]]></category>
		<category><![CDATA[Drone Compliance]]></category>
		<category><![CDATA[drone industry UK]]></category>
		<category><![CDATA[drone insurance]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[drone lawyer UK]]></category>
		<category><![CDATA[drone legal advice]]></category>
		<category><![CDATA[drone pilots]]></category>
		<category><![CDATA[legal risk management]]></category>
		<category><![CDATA[PwC drone report]]></category>
		<category><![CDATA[Richard Ryan]]></category>
		<category><![CDATA[SORA]]></category>
		<category><![CDATA[UK drone regulation]]></category>
		<category><![CDATA[unmanned aviation]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2597</guid>

					<description><![CDATA[<p>&#8220;`By Richard Ryan, barrister and drone lawyer What the paper actually shows (evidence you can cite) Insurers say risk is intrinsically low; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11) UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it has delayed [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/">Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities</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/10/251027_PWC-report-2025-300x300.png" alt="" width="300" height="300" class="alignnone size-medium wp-image-2601" srcset="https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-300x300.png 300w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-150x150.png 150w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-768x768.png 768w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-600x600.png 600w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-100x100.png 100w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025.png 1024w" sizes="(max-width: 300px) 100vw, 300px" />&#8220;`By Richard Ryan, barrister and drone lawyer</p>
<article>
<section>
<h2>What the paper actually shows (evidence you can cite)</h2>
<ul>
<li><strong>Insurers say risk is intrinsically low</strong>; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11)</li>
<li><strong>UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies</strong> than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it <strong>has delayed progress</strong>. (pp. 12–13)</li>
<li><strong>Net-risk lens:</strong> drones <strong>remove</strong> more risk than they introduce (e.g., falls from height, confined spaces, helicopter exposure). (pp. 14–18)</li>
<li><strong>BVLOS doesn’t materially increase risk</strong> where well-managed; biggest predictors are location and safety management. (pp. 10–11, 19–22)</li>
<li><strong>Incident data 2022–24:</strong> commercial operations show <strong>zero fatalities</strong> across UK, US, EU, Canada, Singapore; only a handful of serious injuries. (Appendix + country sections, pp. 55–61)</li>
<li><strong>SORA friction/cost:</strong> UK SORA application at SAIL II is <strong>£3,495</strong>; mitigations/AMC still qualitative ? “OSC-style” uncertainty persists. (p. 35)</li>
<li><strong>“Picking winners”:</strong> five BVLOS priorities (emergency response, powerlines, maritime SAR, rail, crop spraying). (pp. 6, 25–33)</li>
<li><strong>Policy levers:</strong> shift to <strong>digital PDRAs</strong> for repeatable, low-risk scenarios; reuse prior approvals; model on EU PDRAs/Canada’s lower-risk BVLOS. (pp. 36–37; Appendix 1)</li>
<li><strong>Emergency services gap:</strong> the old standing exemption (E4506) lapsed; routine BVLOS now hard to get—BTP resorted to <strong>State Aircraft</strong> rules. (p. 27)</li>
<li><strong>Comparative table</strong> (risk models, UTM status, Remote ID, scale-up reality) explains why the UK feels “high-friction”. (p. 52)</li>
</ul>
</section>
<section>
<h2>Regulatory &amp; enforcement issues to flag (and build matters around)</h2>
<ol>
<li><strong>Incoherent risk calibration:</strong> the UK treats many Specific-category ops as high-risk despite cross-market low incident severity and strong insurer data. (pp. 9–13, 55–57)</li>
<li><strong>Process opacity &amp; cost-burden:</strong> SORA mitigations/AMC are qualitative ? inconsistent asks; <strong>high fees</strong> despite narrow temporal/spatial grants. (p. 35)</li>
<li><strong>Emergency-services capability gap:</strong> loss of E4506 creates avoidable delay/risk; forces <strong>work-arounds</strong> (State Aircraft) rather than transparent PDRA. (p. 27)</li>
<li><strong>AAE not yet a permissioning tool:</strong> policy concept ? scalable authorisation path (contrast EU PDRA-G03 for linear infrastructure). (pp. 28–31, 36)</li>
<li><strong>Net-risk inversions:</strong> requirements like “observer in a boat” for coastal EVLOS can <strong>increase</strong> system risk and cost vs. sensor-driven shore control. (p. 21)</li>
<li><strong>Data transparency:</strong> the UK has many “record-only” entries; EU public access is patchy; hard for operators/insurers to benchmark safety cases publicly. (pp. 54–61)</li>
</ol>
</section>
<section>
<h2>Practical exposure points for stakeholders</h2>
<ul>
<li><strong>Insurers:</strong> common declinature trip-wires—ops outside the authorisation envelope; poor log preservation; weak maintenance/firmware governance. (pp. 9–11, 35–36)</li>
<li><strong>Operators/pilots:</strong> SORA drift, local land-use limitations, and fragmented permissions across linear corridors; evidence-pack discipline needed. (pp. 28–31, 35–36, 56–57)</li>
<li><strong>Associations/community:</strong> need bilingual templates/FAQs and incident learning loops; emphasise the <strong>airspace vs land-use</strong> distinction to reduce friction. (inferred)</li>
<li><strong>Public bodies (blue-light, MCA, NR, utilities):</strong> proven benefits blocked by bespoke approvals—strong case for <strong>sector PDRA playbooks</strong>. (pp. 26–33, 36)</li>
</ul>
</section>
<p>  <!-- NOTE: The previous section titled “Where you can add legal value (service lines you can sell now)” has been intentionally removed and will be addressed separately as part of practice growth content. --></p>
<section>
<h2>What this means for drone pilots, operators, and companies</h2>
<p>As a drone lawyer, my reading of the PwC paper is that the safety record increasingly supports <strong>predictable, rules-based authorisations</strong>, but the UK still applies bespoke processes that create delay, cost and legal uncertainty. The winners will be those who treat compliance as an operational capability, not a paperwork chore.</p>
<h3>Implications for Drone Pilots</h3>
<ul>
<li><strong>Documentation is defence:</strong> retain native telemetry, app/controller logs, and pre-flight risk assessments. These are crucial in insurer claims and any CAA inquiry.</li>
<li><strong>VLOS/BVLOS discipline:</strong> be explicit about how VLOS was maintained (or the BVLOS mitigations used). Ambiguity here is a common enforcement and insurance pain point.</li>
<li><strong>Privacy on site:</strong> where people are identifiable, prepare a simple lawful-basis note and signage plan; it reduces complaint/escalation risk significantly.</li>
</ul>
<h3>Implications for Operators</h3>
<ul>
<li><strong>Align your OA/ops manual with SORA and AAE logic:</strong> show how mitigations reduce <em>both</em> air and ground risk. Clear mapping cuts questions and accelerates approvals.</li>
<li><strong>Design for repeatability:</strong> build PDRA-ready evidence packs for your most common jobs (e.g., rail/powerline corridors) so each new mission is a variation, not a reinvention.</li>
<li><strong>Insurance resilience:</strong> standardise maintenance/firmware baselines and battery care logs; many declinatures stem from gaps here, not from the incident itself.</li>
<li><strong>Contracts that reflect reality:</strong> flowing down responsibilities to subcontractors (airworthiness, data protection, incident reporting) reduces exposure and smooths procurement.</li>
</ul>
<h3>Implications for Drone Companies &amp; Enterprise Users</h3>
<ul>
<li><strong>Board-level accountability:</strong> appoint a named senior responsible owner (SRO) for UAS operations with decision logs—critical if decisions are later examined in court or by regulators.</li>
<li><strong>Data governance as an asset:</strong> implement DPIAs where warranted, role-based access to imagery, retention/deletion schedules, and breach protocols. This increases tender scores and reduces enforcement risk.</li>
<li><strong>Public value narrative:</strong> quantify how drone tasks remove traditional risks (work at height, road possessions, helicopter hours). This “net-risk” case supports proportional, scalable permissions.</li>
</ul>
<h3>Where legal support helps, assists, and mitigates</h3>
<ul>
<li><strong>Approvals &amp; permissions:</strong> structuring SORA/AAE applications with proportional mitigations, re-using prior evidence, and narrowing scope to reduce fees and conditions.</li>
<li><strong>Policy &amp; appeals:</strong> challenging irrational or net-risk-increasing conditions; seeking clarifications; and preparing proportionate alternatives that the regulator can accept.</li>
<li><strong>Privacy &amp; data:</strong> lawful-basis memos, DPIAs, signage/LLN templates, and response playbooks for complaints or subject access requests.</li>
<li><strong>Insurance &amp; claims:</strong> coverage mapping, notification strategy, and evidence preservation to avoid declinature; subrogation prospects where third parties contributed to loss.</li>
<li><strong>Contracts:</strong> allocating risk cleanly across clients, operators and subcontractors (indemnities, limitation, IP/data ownership, incident reporting).</li>
</ul>
<p><em>Bottom line:</em> the sector is safe and maturing. Those who can <strong>demonstrate</strong> their risk controls, <strong>evidence</strong> compliance, and <strong>standardise</strong> approvals will grow fastest—with fewer legal shocks along the way.</p>
</section>
<section>
<h2>Talking points for meetings &amp; panels</h2>
<ul>
<li><strong>Same safety, slower UK growth:</strong> insurers and incident data show low intrinsic risk—authorisations should be <strong>predictable and prescriptive</strong>, not bespoke. (pp. 9–13, 36–37)</li>
<li><strong>Digital PDRAs now:</strong> for repeatable BVLOS (powerlines/rail/SAR/maritime/agri)—reuse evidence from prior OSCs; mirror EU PDRA/Canada logic. (pp. 25–33, 36)</li>
<li><strong>Emergency drones need an emergency rulebook:</strong> the E4506 gap is pushing forces into State Aircraft work-arounds. (p. 27)</li>
<li><strong>Incident reality:</strong> zero fatalities in 2022–24 across major markets; claims are mainly minor property/equipment—calibrate conditions accordingly. (pp. 55–61; pp. 9–11)</li>
</ul>
</section>
<hr />
<footer>
<section>
<h2>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>
<p><em></em></p>
</section>
</footer>
</article>
<p>&#8220;`</p>
<p>The post <a href="https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/">Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities</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>Legal Framework of UTM for UAS &#8211; 2020 Digital Avionics Systems Conference</title>
		<link>https://blakistons.co.uk/legal-framework-of-utm-for-uas/</link>
		
		<dc:creator><![CDATA[zeroabove]]></dc:creator>
		<pubDate>Wed, 23 Dec 2020 13:07:52 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[Air Traffic Management]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Traffic Management]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[FAA]]></category>
		<category><![CDATA[ICAO]]></category>
		<category><![CDATA[legal challenges]]></category>
		<category><![CDATA[Legal Framework]]></category>
		<category><![CDATA[Policy Development]]></category>
		<category><![CDATA[regulatory challenges]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UAV]]></category>
		<category><![CDATA[UTM]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2295</guid>

					<description><![CDATA[<p>2020 Digital Avionics Systems Conference UTM Operational Concept The legal framework for UTM (Unmanned aircraft system Traffic Management) will need to develop as regulators grapple with issues that relate to legal responsibility and accountability as the proliferation of drones increases. Unmanned Aircraft System (UAS) Traffic Management (UTM) Enabling Civilian Low-altitude Airspace and Unmanned Aircraft System [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/legal-framework-of-utm-for-uas/">Legal Framework of UTM for UAS &#8211; 2020 Digital Avionics Systems Conference</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>2020 Digital Avionics Systems Conference</h2>
<p><strong>UTM Operational Concept</strong></p>
<p>The legal framework for UTM (Unmanned aircraft system Traffic Management) will need to develop as regulators grapple with issues that relate to legal responsibility and accountability as the proliferation of drones increases.</p>
<p class="p1">Unmanned Aircraft System (UAS) Traffic Management (UTM) Enabling Civilian Low-altitude Airspace and Unmanned Aircraft System Operations.</p>
<p class="p1"><strong>What is the problem?</strong></p>
<p class="p2">Many beneficial civilian applications of the UAS have been proposed, that include goods delivery, medical deliveries, infrastructure surveillance, search and rescue and agricultural monitoring. Currently, there is <span class="s1">no </span>established UTM infrastructure to enable and safely manage <span class="s2">the </span>widespread use of BVLOS low-altitude airspace and UAS operations, regardless of the type of UAS.</p>
<p>To read the full article <a href="https://blakistons.co.uk/wp-content/uploads/2020/12/200910_1112_Presentation_The-Legal-Framework-of-UTM-for-UAS.pdf" target="_blank" rel="noopener">click here</a>.</p>
<p>&nbsp;</p>
<p>The post <a href="https://blakistons.co.uk/legal-framework-of-utm-for-uas/">Legal Framework of UTM for UAS &#8211; 2020 Digital Avionics Systems Conference</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The Legal Framework of UTM for UAS</title>
		<link>https://blakistons.co.uk/developing-legal-frameworks-for-utm-addressing-legal-challenges-in-drone-traffic-management/</link>
		
		<dc:creator><![CDATA[zeroabove]]></dc:creator>
		<pubDate>Wed, 23 Dec 2020 13:00:59 +0000</pubDate>
				<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Technology]]></category>
		<category><![CDATA[Legal Frameworks]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[Air Traffic Management]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Traffic Management]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[FAA]]></category>
		<category><![CDATA[ICAO]]></category>
		<category><![CDATA[legal challenges]]></category>
		<category><![CDATA[Legal Framework]]></category>
		<category><![CDATA[Policy Development]]></category>
		<category><![CDATA[regulatory challenges]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UAV]]></category>
		<category><![CDATA[UTM]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2290</guid>

					<description><![CDATA[<p>Abstract— It is very apparent that the legal framework for Unmanned aircraft system Traffic Management (UTM) needs to be developed as regulators grapple with issues that relate to legal responsibility and accountability for each UTM stakeholder as the proliferation of drones increases. There is a considerable ‘legal lacuna’ that exists creating much uncertainty within the [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/developing-legal-frameworks-for-utm-addressing-legal-challenges-in-drone-traffic-management/">The Legal Framework of UTM for UAS</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="p2"><strong><i>Abstract</i></strong>— It is very apparent that the legal framework for Unmanned aircraft system Traffic Management (UTM) needs to be developed as regulators grapple with issues that relate to legal responsibility and accountability for each UTM stakeholder as the proliferation of drones increases. There is a considerable ‘legal lacuna’ that exists creating much uncertainty within the industry with respect to investment and the direction of innovation. Drones are being utilised today under controlled conditions as technology and ability develops, but with this accelerated pace of technological development, existing regulations soon become limited to address new capabilities and thus become out of date.</p>
<p class="p2">Policy has become law in many jurisdictions, but policy needs to be developed further to keep pace with demand because safety is paramount. This paper investigates and highlights legal aspects that a regulator and UTM stakeholders have to consider in developing good drone law. It is essential that a properly considered legal framework is developed for many reasons including, but not limited to, increased positive public perception, proliferation of innovation of use cases for Unmanned Aerial Systems, improved environmental impact and improved safety.</p>
<p class="p2">This paper describes the fundamentals that a well designed and considered legal framework for a UTM system should address, in order to provide much needed certainty that can guide all stakeholders to a regulatory path that leads to safe maximized utility of drones in shared airspace.</p>
<p><a href="https://blakistons.co.uk/wp-content/uploads/2020/12/200811_DASC_Paper-Submission_Legal-Framework-of-UTM-for-UAS_Richard-Ryan_Cranfield-University.pdf" target="_blank" rel="noopener">Click here</a> to read the full article.</p>
<p>The post <a href="https://blakistons.co.uk/developing-legal-frameworks-for-utm-addressing-legal-challenges-in-drone-traffic-management/">The Legal Framework of UTM for UAS</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
