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

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

					<description><![CDATA[<p>Drone Law &#124; Counter-UAS &#124; Defence AI &#124; One-Way Effectors Summary: The Royal Navy’s launch of the British-built Nyan One-Way Effector from XV Patrick Blackett is more than a drone trial. It is a legal and operational marker in the UK’s transition towards a Hybrid Navy, raising issues of targeting law, weapons review, military airworthiness, [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/">Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="drone-law-blog">
<p><strong>Drone Law | Counter-UAS | Defence AI | One-Way Effectors</strong></p>
<p><strong>Summary:</strong> The Royal Navy’s launch of the British-built Nyan One-Way Effector from XV Patrick Blackett is more than a drone trial. It is a legal and operational marker in the UK’s transition towards a Hybrid Navy, raising issues of targeting law, weapons review, military airworthiness, counter-UAS defence, export controls and AI governance.</p>
<h2>1. Why the Nyan Trial Matters</h2>
<p>The Royal Navy and British Army have tested the Nyan One-Way Effector, designed and built by BAE Systems’ Callen-Lenz, for both maritime and land operations. The system has a 2.9-metre wingspan and is designed to provide a precision strike capability. It has now been launched from the Royal Navy’s experimentation ship XV Patrick Blackett as part of Project Vantage, the programme focused on accelerating maritime one-way effector capability.</p>
<p>Legally, the phrase “one-way effector” should not distract from the underlying classification problem. Nyan may simultaneously be an aircraft, a military UAS, a weapon system, a munition, a software-enabled targeting platform and an export-controlled defence article. Each classification carries its own compliance burden.</p>
<h2>2. From Drone Novelty to Combat Mass</h2>
<p>The trial reflects the UK’s move towards crewed-uncrewed teaming and the Royal Navy’s Hybrid Navy concept. One-way effectors are intended to provide affordable combat mass, allowing crewed platforms to extend reach, increase tempo and complicate an adversary’s defensive picture.</p>
<p>However, affordability does not dilute legal responsibility. The cheaper and more numerous the weapon, the more frequently it may be used. The more frequently it is used, the more important lawful targeting architecture becomes.</p>
<h2>3. Autonomy: The Legal Question Is What the Machine Decides</h2>
<p>The key legal question is not whether Nyan is a drone, but what functions are automated or autonomous. Autonomy in navigation is not the same as autonomy in target selection. A system may fly itself to a pre-programmed target without being authorised to decide who or what is attacked.</p>
<p>Commanders and lawyers should ask:</p>
<ul>
<li>Does the system merely navigate to a human-selected target?</li>
<li>Does it detect, classify, prioritise or select targets?</li>
<li>Can it be retasked, recalled, aborted or terminated after launch?</li>
<li>What happens if GPS is jammed, spoofed or degraded?</li>
<li>What mission data and operator decisions are recorded?</li>
</ul>
<p>Those questions determine whether the system can be used consistently with distinction, proportionality, precautions in attack and applicable rules of engagement.</p>
<h2>4. Article 36 Weapons Review</h2>
<p>A one-way effector requires a disciplined weapons review. That review should not be limited to the airframe or warhead. It should include the launcher, mission-planning software, navigation system, datalinks, communications architecture, abort logic, cyber resilience, payload effects and integration with intelligence or targeting systems.</p>
<p>The review must also examine foreseeable use cases. Launching from land against a fixed target is materially different from launching from a moving naval platform against a maritime or coastal target. The latter introduces neutral shipping, civilian infrastructure, allied aircraft, electromagnetic interference, airspace deconfliction and more complex proportionality assessments.</p>
<h2>5. EU AI Act and UK AI Standards</h2>
<p>The EU AI Act generally excludes AI systems used exclusively for military, defence or national-security purposes. However, its high-risk AI standards remain useful benchmarks for dual-use suppliers, defence contractors, procurement assurance and civilian spin-outs.</p>
<p>The UK does not currently have a single equivalent “UK AI Act”. Instead, the UK uses a sector-led, principles-based model. In defence, this is supplemented by Ministry of Defence AI principles, including human-centricity, responsibility, understanding, bias and harm mitigation, and reliability.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Governance Area</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">EU AI Act Benchmark</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">UK / MOD Equivalent</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Application to One-Way Effectors</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Lifecycle risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Safety, security and robustness</td>
<td style="border: 1px solid #000; padding: 8px;">Hazard logs for navigation failure, lost link, spoofing, target-data error and launch failure.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Technical documentation</td>
<td style="border: 1px solid #000; padding: 8px;">Technical file and system description</td>
<td style="border: 1px solid #000; padding: 8px;">Accountability and governance</td>
<td style="border: 1px solid #000; padding: 8px;">Configuration records for airframe, launcher, software, payload and mission-planning tools.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Record-keeping</td>
<td style="border: 1px solid #000; padding: 8px;">Automatic logging</td>
<td style="border: 1px solid #000; padding: 8px;">Transparency and explainability</td>
<td style="border: 1px solid #000; padding: 8px;">Mission logs, operator decisions, software versions, AI outputs and telemetry retention.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Human oversight</td>
<td style="border: 1px solid #000; padding: 8px;">Human control and intervention</td>
<td style="border: 1px solid #000; padding: 8px;">Human-centricity and responsibility</td>
<td style="border: 1px solid #000; padding: 8px;">Clear authority for launch, retask, abort, termination and post-strike review.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Cyber resilience</td>
<td style="border: 1px solid #000; padding: 8px;">Accuracy, robustness and cybersecurity</td>
<td style="border: 1px solid #000; padding: 8px;">Reliability and security</td>
<td style="border: 1px solid #000; padding: 8px;">Testing against jamming, spoofing, adversarial inputs, cyber compromise and degraded environments.</td>
</tr>
</tbody>
</table>
<h2>6. Maritime Launch Changes the Legal Burden</h2>
<p>Launching from a ship is materially different from launching from a land range. The platform is moving. Weather and sea state affect launch reliability. The electromagnetic environment may be contested. The operating area may include neutral vessels, civil aircraft, allied aircraft, helicopters, missiles and other uncrewed systems.</p>
<p>The legal architecture must therefore include target validation, positive identification, proportionality analysis, precautions in attack, air and maritime deconfliction, and auditability. The question is not simply whether Nyan can be launched from a ship. The question is whether the Navy can generate a repeatable, auditable and legally defensible kill chain from a ship.</p>
<h2>7. The Counter-UAS Mirror</h2>
<p>Every one-way effector creates a corresponding defence problem. If the UK can launch low-cost precision effectors from ships, adversaries and proxies can attempt similar effects. Counter-UAS law is therefore inseparable from OWE deployment.</p>
<p>Defending ships, ports, airbases and critical infrastructure requires layered capabilities: detection, identification, tracking, electronic warfare, cyber effects, kinetic interceptors, directed energy, decoys, hardening, dispersal and forensic recovery.</p>
<p>In armed conflict, commanders will operate under the law of armed conflict and rules of engagement. In peacetime or grey-zone conditions, counter-drone operations may engage aviation law, communications law, property rights, criminal law, public safety, port security and military aid to civil authorities.</p>
<h2>8. Export Controls and Procurement Risk</h2>
<p>Sovereign manufacture does not remove export-control obligations. Airframes, propulsion systems, launchers, datalinks, payloads, source code, mission-planning tools, technical assistance and software updates may all require careful classification and licensing analysis.</p>
<p>Rapid procurement also creates legal debt if safety cases, software changes, data rights, AI assurance, cyber resilience and operator training are not properly documented. The solution is not to slow innovation, but to embed lawyers, engineers, safety specialists, AI assurance teams and operators into the experimentation cycle from the start.</p>
<h2>9. Bottom Line</h2>
<p>The Nyan sea launch is a significant step towards a British Hybrid Navy. Its real importance lies in the legal system-of-systems problem it exposes. A one-way effector is not merely a drone with a warhead. It moves through air law, weapons law, targeting law, AI governance, export-control law, safety regulation, procurement governance and counter-UAS doctrine.</p>
<p>The future fleet will not be judged only by how many drones it can launch. It will be judged by whether it can launch them lawfully, safely, proportionately, responsibly and at scale.</p>
<hr />
<h2>About the Author</h2>
<p><strong>Richard Ryan</strong> is a barrister, Chartered Arbitrator and specialist in drone law, counter-UAS, defence procurement and AI governance. He advises government, defence and technology organisations on autonomous systems, military aviation, export controls, commercial contracts and regulatory compliance. Richard is also undertaking a PhD at Cranfield University researching the future legal framework for BVLOS operations, autonomous aviation and Unmanned Traffic Management.</p>
<p><em>This article is general legal commentary and does not constitute legal advice.</em></p>
</div>
<p>The post <a href="https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/">Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots</title>
		<link>https://blakistons.co.uk/uk-drone-rules-from-1-january-2026-a-lawyers-practical-guide-for-pilots/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 11 Jun 2026 17:44:48 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[A1 category drones]]></category>
		<category><![CDATA[A2 CofC]]></category>
		<category><![CDATA[A3 category drones]]></category>
		<category><![CDATA[Air Navigation Order 2016]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA drone rules]]></category>
		<category><![CDATA[CAA regulations]]></category>
		<category><![CDATA[commercial drone operations]]></category>
		<category><![CDATA[drone airspace restrictions]]></category>
		<category><![CDATA[Drone Code]]></category>
		<category><![CDATA[drone compliance UK]]></category>
		<category><![CDATA[drone law UK]]></category>
		<category><![CDATA[Drone Lawyer]]></category>
		<category><![CDATA[drone legal advice]]></category>
		<category><![CDATA[drone registration UK]]></category>
		<category><![CDATA[drone regulations 2026]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[Flight Restriction Zones]]></category>
		<category><![CDATA[FPV drones UK]]></category>
		<category><![CDATA[FRZ drone rules]]></category>
		<category><![CDATA[recreational drone flying]]></category>
		<category><![CDATA[Remote ID UK]]></category>
		<category><![CDATA[UK drone pilots]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[UK drone rules]]></category>
		<category><![CDATA[Unmanned Aircraft Systems]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[Visual Line of Sight]]></category>
		<category><![CDATA[VLOS drones]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2685</guid>

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

					<description><![CDATA[<p>By Richard Ryan, barrister and drone lawyer Constructive outcome, practical lessons. A technical proximity breach was confirmed, a more serious allegation was dismissed, and there are clear takeaways that raise standards on evidence, cooperation and public safety. Outcome at a glance Count 1 (conviction): Operating an unmanned aircraft close to the site of an ongoing [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/">A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Begin WordPress post content (no H1 included; WordPress will supply the title) --></p>
<p>By Richard Ryan, barrister and drone lawyer</p>
<p><strong>Constructive outcome, practical lessons.</strong> A technical proximity breach was confirmed, a more serious allegation was dismissed, and there are clear takeaways that raise standards on evidence, cooperation and public safety.</p>
<section aria-labelledby="outcome">
<h2 id="outcome">Outcome at a glance</h2>
<ul>
<li><strong>Count 1 (conviction):</strong> Operating an unmanned aircraft close to the site of an ongoing emergency response — <strong>Air Navigation Order 2016</strong> Articles <strong>265B(3)</strong>, <strong>265B(5)(j)</strong> and <strong>265F(3)(c)</strong> (reflecting <strong>UAS.OPEN.060(3)</strong>).</li>
<li><strong>Count 2 (dismissed):</strong> Obstructing or hindering emergency workers — <strong>Emergency Workers (Obstruction) Act 2006</strong>, sections <strong>1</strong> and <strong>4</strong> — no case to answer.</li>
<li><strong>Sentence:</strong> <strong>£300</strong> (reduced from <strong>£2,500</strong>). <strong>Deprivation order refused</strong> — the client’s equipment will be returned.</li>
</ul>
<p></strong>.</p>
</section>
<section aria-labelledby="background">
<h2 id="background">Competence, cooperation and public interest flying</h2>
<p>The client is an experienced operator with hundreds of hours and thousands of flights, combining sound aviation literacy with routine work around public interest incidents. On the day in question, the client used aircraft tracking tools and air band monitoring, maintained a conservative standoff where no formal cordon existed, and landed promptly when requested by police. This was a measured and safety first response in a dynamic setting.</p>
</section>
<section aria-labelledby="lesson-telemetry">
<h2 id="lesson-telemetry">Lesson 1: Telemetry clarity</h2>
<p>When presenting flight data, clarity matters. Plot the flight path with a <strong>thin, precise line</strong> so the <strong>base map remains legible</strong>, including fences, road edges, cordons and measured standoffs. A thick line can obscure the very features that prove separation.</p>
<ul>
<li>Keep a clean thin line map and a forensic overlay with timestamps for take off, orbit points, return to home and landing, plus measured distances to fixed features.</li>
<li>Use a thin line that clearly shows accurate telemetry when placed on a map, not a thick line that obscures part of the map.</li>
</ul>
<p>  <!-- Optional image placeholder:
  

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

  </figure>


  --><br />
</section>
<section aria-labelledby="lesson-dat">
<h2 id="lesson-dat">Lesson 2: Plan for seizure and understand where DJI DAT lives</h2>
<p>High fidelity <strong>DJI DAT</strong> logs are stored on the aircraft and typically require <strong>connecting the drone to a computer</strong> to extract. If a drone is seized by police, immediate access to those DAT files is difficult.</p>
<ul>
<li>Build redundancy: back up app and controller logs after each flight, use screen recordings of the flight user interface, and capture independent stills or video.</li>
<li>For sensitive assignments, consider periodic DAT offloads in advance.</li>
</ul>
</section>
<section aria-labelledby="commitments">
<h2 id="commitments">Five straightforward commitments</h2>
<ol>
<li>Thin line telemetry as the default for mapping outputs.</li>
<li>Evidence resilience: dual path logging (logs plus screen capture) and periodic DAT offloads.</li>
<li>Proportionate communications near emergency activity where appropriate.</li>
<li>A simple one page ops note on every job covering airspace, standoffs and abort triggers.</li>
<li>Calm, courteous engagement with officers, with a record of powers used and a property schedule if equipment is seized.</li>
</ol>
</section>
<section aria-labelledby="tech-ref">
<h2 id="tech-ref">Technical reference: cross motorway separation</h2>
<p>To contextualise the judge’s description (opposite side of a six lane motorway plus hard shoulder plus verge), the following uses standard UK dimensions.</p>
<h3>Assumptions from UK highway standards</h3>
<ul>
<li><strong>Lane width (motorways):</strong> 3.65 m per lane (DMRB CD 127). <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">[1]</a></li>
<li><strong>Hard shoulder width:</strong> 3.3 m (National Highways). <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">[2]</a></li>
<li><strong>Central reservation (median):</strong> assume about 3.0 m (DMRB derived guidance). <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">[3]</a></li>
<li><strong>Verge:</strong> varies by site; on trunk roads, about 3.0 m is common. Use 2.0 to 3.0 m to bracket reality. <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">[4]</a></li>
</ul>
<h3>Baseline components</h3>
<ul>
<li>Six lanes = 6 x 3.65 = <strong>21.90 m</strong>. <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">[1]</a></li>
<li>Two hard shoulders = <strong>6.60 m</strong>. <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">[2]</a></li>
<li>Central reservation (median) about <strong>3.00 m</strong>. <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">[3]</a></li>
<li>Verge per side about <strong>2.0 to 3.0 m</strong>. <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">[4]</a></li>
</ul>
<h3>Real world lateral separation (verge to verge)</h3>
<p><code>Distance = 6 lanes + 2 x hard shoulder + 2 x verge + median</code></p>
<ul>
<li>With 2.0 m verges (conservative): <strong>21.90 + 6.60 + 4.00 + 3.00 = 35.50 m</strong></li>
<li>With 3.0 m verges (typical): <strong>21.90 + 6.60 + 6.00 + 3.00 = 37.50 m</strong></li>
</ul>
<p><strong>Figure to use:</strong> about <strong>37.5 m</strong> horizontal separation verge to verge (typical). <strong>Lower bound:</strong> about <strong>35.5 m</strong> if verges are unusually narrow.</p>
<h3>Lean reading (narrow phrasing)</h3>
<p>Six lanes plus one hard shoulder plus one verge (omitting the median and the opposite side shoulder and verge):</p>
<p><code>21.90 + 3.30 + (2.0 to 3.0) = 27.2 to 28.2 m</code></p>
<p>This underestimates the physical cross section that most operators and engineers would use.</p>
<h3>Add altitude for slant distance</h3>
<p>If height is h, the slant range is <code>sqrt(lateral^2 + h^2)</code>.</p>
<ul>
<li>With 37.5 m lateral: <strong>48.0 m</strong> at 30 m AGL, <strong>70.8 m</strong> at 60 m, <strong>125.7 m</strong> at 120 m.</li>
<li>With 35.5 m lateral: <strong>46.5 m</strong> at 30 m, <strong>69.2 m</strong> at 60 m, <strong>124.2 m</strong> at 120 m.</li>
</ul>
<p><strong>Practical effect:</strong> even before adding any field offset inside the field beyond the verge, cross motorway separation is around 36 to 38 m. Any field offset adds to that figure. Slant range increases further with altitude.</p>
<p>Standards: <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">DMRB CD 127</a>, <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">National Highways</a>, <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">TII DN GEO 03036</a>, <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">Transport Scotland</a>.</p>
</section>
<section aria-labelledby="closing">
<h2 id="closing">Bottom line</h2>
<p>This is a constructive outcome. The most serious allegation fell away, the fine is modest, and the client retains their equipment. More importantly, the experience is being used to lead on best practice: clearer telemetry, stronger data resilience and exemplary on scene conduct, supporting emergency services, informing the public and keeping UK skies safe.</p>
</section>
<hr />
<section aria-labelledby="bio">
<h2 id="bio">About the author</h2>
<p><strong>Richard Ryan</strong> is a Barrister (Direct Access), Mediator and Chartered Arbitrator based in the UK, specialising in drone and counter-drone law, aviation regulation, and complex commercial disputes. He advises operators, insurers and public bodies on SORA/AAE approvals, BVLOS programmes, privacy/data governance, and risk allocation across the drone ecosystem.</p>
</section>
<p><em>This post is for general information only and is not legal advice.</em></p>
<p><!-- End WordPress post content --></p>
<p>The post <a href="https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/">A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>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>What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5</title>
		<link>https://blakistons.co.uk/what-the-uk-drone-industry-can-learn-from-easas-adoption-of-sora-2-5/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 30 Sep 2025 10:57:46 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Drone Industry Concerns]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[European Union Policy Updates]]></category>
		<category><![CDATA[Legal Compliance]]></category>
		<category><![CDATA[Legal Conflicts]]></category>
		<category><![CDATA[Legal Frameworks]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Legal Investigations]]></category>
		<category><![CDATA[Legal Updates]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Compliance - Focuses on the importance of adherence to regulatory guidelines and consequences of violations.]]></category>
		<category><![CDATA[Regulatory Compliance - Includes insights on compliance with FAA]]></category>
		<category><![CDATA[Risk Assessment & Mitigation]]></category>
		<category><![CDATA[Risk Management and Insurance]]></category>
		<category><![CDATA[Safety and Risk Management - Emphasizes safety protocols]]></category>
		<category><![CDATA[Safety and Security in Aviation]]></category>
		<category><![CDATA[Tech Law and Regulation]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[bvlos uk]]></category>
		<category><![CDATA[drone law barrister]]></category>
		<category><![CDATA[drone operators compliance]]></category>
		<category><![CDATA[Drone Regulations UK]]></category>
		<category><![CDATA[easa drone rules]]></category>
		<category><![CDATA[osc applications]]></category>
		<category><![CDATA[sora 2.5]]></category>
		<category><![CDATA[specific operations risk assessment]]></category>
		<category><![CDATA[uk caa drones]]></category>
		<category><![CDATA[UK Drone Law]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2580</guid>

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

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

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

					<description><![CDATA[<p>Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir By Richard Ryan, Drone Lawyer The skies over the UK are on the verge of a transformative shift, thanks to the ambitious NATS OpenAir initiative. Designed to integrate drones and advanced air mobility (eVTOLs) into shared airspace alongside traditional aircraft, the proposal [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/transforming-uk-airspace-a-new-era-for-drones-and-aviation-with-nats-openair/">Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" src="https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-300x171.webp" alt="" width="300" height="171" class="alignnone size-medium wp-image-2520" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-300x171.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-1024x585.webp 1024w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-768x439.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-1536x878.webp 1536w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-600x343.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir.webp 1792w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir</strong></p>
<p><strong>By Richard Ryan, Drone Lawyer</strong></p>
<p>The skies over the UK are on the verge of a transformative shift, thanks to the ambitious NATS OpenAir initiative. Designed to integrate drones and advanced air mobility (eVTOLs) into shared airspace alongside traditional aircraft, the proposal promises innovation, efficiency, and safety. But as with any grand vision, the devil is in the detail.<br />
Here’s an in-depth look at what the OpenAir initiative is getting right, where there are gaps, and how it can evolve to meet the needs of all airspace users.<br />
________________________________________<br />
1. Prioritising Data Privacy and Ownership</p>
<p>One of the most valuable resources in aviation is data. For drone operators, who depend on real-time information about flight paths, weather, and airspace restrictions, access to reliable data is critical. However, the OpenAir proposal is light on specifics about who owns the data and how privacy will be protected.<br />
Without clear protections, drone operators might worry about their data being exploited—whether commercially or in ways that jeopardise their competitive edge.</p>
<p>The Fix:<br />
OpenAir must adopt a clear data privacy framework. Operators should retain ownership of their data, with mandatory anonymisation for any information shared beyond essential safety and operational use. Only the bare minimum of data required for regulatory compliance should be shared, and stringent safeguards must prevent its misuse.<br />
________________________________________<br />
2. Keeping the Playing Field Fair</p>
<p>OpenAir is envisioned as a centralised hub for managing UK airspace, which sounds great—until you consider the potential impact on smaller players. Consolidating services under one entity like OpenAir might inadvertently stifle competition among Uncrewed Traffic Management Service Providers (UTMSPs).</p>
<p>The Fix:<br />
To level the playing field, OpenAir should adopt open standards that allow seamless third-party integration. Smaller UTMSPs must be supported, not sidelined. Clear rules around equitable access to data and services will ensure innovation thrives without creating monopolies.<br />
________________________________________<br />
3. Setting Realistic Timelines</p>
<p>Integrating drones and eVTOLs into shared airspace isn’t a simple task. OpenAir’s proposed rollout timeline—beginning pilots in 2025 and achieving full deployment by 2028—might be overly ambitious, especially given the complexity of regulatory approvals and the need for robust infrastructure.</p>
<p>The Fix:<br />
A phased approach with realistic benchmarks is the way forward. OpenAir should focus on pilot projects in key areas where demand is highest (e.g., urban delivery drones or emergency medical services). This would provide valuable data to refine the system while reducing the risk of rushed implementation.<br />
________________________________________<br />
4. Managing Costs for Drone Operators</p>
<p>OpenAir’s &#8220;user pays&#8221; principle makes sense in theory—those who use the airspace services should cover the costs. But smaller operators, such as local delivery drone companies, could be disproportionately affected by high fees, potentially pricing them out of the market.</p>
<p>The Fix:<br />
Introduce tiered pricing. Small operators should pay less, at least during the initial phases. Alternatively, subsidies or credits could be offered to early adopters, ensuring fair access while fostering adoption across the board.<br />
________________________________________<br />
5. Addressing Legal Grey Areas</p>
<p>OpenAir aligns with the UK’s Airspace Modernisation Strategy, but its relationship with existing regulations like CAP 722 (which governs drone operations) needs to be crystal clear. Ambiguities in compliance requirements could delay approvals or lead to legal disputes.<br />
Similarly, liability concerns loom large. If there’s a system outage or data error, who’s responsible for the fallout? Drone operators? OpenAir? The CAA? NATS? DfT?</p>
<p>The Fix:<br />
OpenAir must explicitly state how its services integrate with CAP 722, especially for critical areas like Beyond Visual Line of Sight (BVLOS) operations. As for liability, service agreements must clearly define responsibilities, ensuring all parties—operators, OpenAir, and regulators—understand their obligations.<br />
________________________________________<br />
6. Building Trust Through Transparency</p>
<p>For OpenAir to succeed, trust is key. Stakeholders—including drone operators, regulators, and public service agencies—must feel confident in the system’s fairness and security.</p>
<p>The Fix:<br />
Establish an independent advisory board with representatives from all key groups, including Blakiston’s Chambers! This board would oversee the rollout of OpenAir, ensuring transparency and accountability. Regular public updates and feedback sessions would further build trust and address concerns early.<br />
________________________________________<br />
7. Looking to the Future</p>
<p>The potential of OpenAir is undeniable. By creating a unified platform for managing UK airspace, it could unlock opportunities ranging from efficient logistics to life-saving medical deliveries. But to truly succeed, OpenAir must:<br />
1.	Prioritise data privacy and ownership.<br />
2.	Ensure fair competition for all service providers.<br />
3.	Adopt a phased, realistic rollout plan.<br />
4.	Keep costs manageable for smaller operators.<br />
5.	Align with existing regulations like CAP 722.<br />
6.	Address liability concerns upfront.<br />
7.	Foster trust through transparency and stakeholder engagement.</p>
<p>The skies above us are changing, and with thoughtful planning, OpenAir could make the UK a global leader in integrated airspace management. But to get there, it must balance ambition with practicality, ensuring the system works for everyone—from global eVTOL operators to local delivery drones.<br />
________________________________________<br />
What do you think about the OpenAir proposal? Share your thoughts, especially if you&#8217;re a drone operator or part of the aviation industry. Your feedback could shape the future of our skies!</p>
<p><strong>About the Author</strong><br />
Richard Ryan is a UK-based barrister and drone law expert with over 20 years of legal experience. Specializing in regulatory, operational, and safety challenges, Richard advises defence companies, regulatory bodies, and government agencies on the complexities of UAS operations. A former advisor to the UK Civil Aviation Authority and the House of Lords’ AUTMA committee, Richard is currently pursuing a PhD at Cranfield University, focusing on the legal implications of drone integration into global airspace.<br />
Richard combines his legal expertise with a deep understanding of defence operations, having served in the British Army, including deployments to Iraq and Afghanistan. His insights bridge the gap between operational realities and legal requirements, ensuring clients navigate the rapidly evolving world of drone technology with confidence.</p>
<p>The post <a href="https://blakistons.co.uk/transforming-uk-airspace-a-new-era-for-drones-and-aviation-with-nats-openair/">Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Commercial and recreational drone use in the UK</title>
		<link>https://blakistons.co.uk/uk-strengthens-drone-laws-new-regulations-on-flight-restriction-zones-registration-and-pilot-competency/</link>
		
		<dc:creator><![CDATA[zeroabove]]></dc:creator>
		<pubDate>Mon, 11 Nov 2019 15:27:23 +0000</pubDate>
				<category><![CDATA[Air Traffic Control]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[chnology and Innovation]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Government Reports]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[Air Navigation Order 2016]]></category>
		<category><![CDATA[Air Traffic Management and Unmanned Aircraft Bill]]></category>
		<category><![CDATA[ATC Charges]]></category>
		<category><![CDATA[Civil Aviation Act 1982]]></category>
		<category><![CDATA[Drone Laws]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Penalties]]></category>
		<category><![CDATA[Drone Registration]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Flight Restriction Zones]]></category>
		<category><![CDATA[House of Commons Science and Technology Committee]]></category>
		<category><![CDATA[Remote Pilot Competency]]></category>
		<category><![CDATA[UK Government]]></category>
		<category><![CDATA[Unmanned Aircraft]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=130</guid>

					<description><![CDATA[<p>This is a report published by the House of Commons Science and Technology Committee in October 2019. The government has been busy to the many aspects of drones and finally is taking some positive measures. The report focuses on current regulations, primarily under the Civil Aviation Act 1982 and the Air Navigation Order 2016, as [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/uk-strengthens-drone-laws-new-regulations-on-flight-restriction-zones-registration-and-pilot-competency/">Commercial and recreational drone use in the UK</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>This is a report published by the House of Commons Science and Technology Committee in October 2019. The government has been busy to the many aspects of drones and finally is taking some positive measures.</p>
<p>The report focuses on current regulations, primarily under the Civil Aviation Act 1982 and the Air Navigation Order 2016, as amended in 2018 (Order 2019 No.261).</p>
<p>It is now for most, common knowledge that Flight Restriction Zones (FRZ) exist around airports and is now 5Km, increased from 1Km.  It was a concern for Air Traffic Control operators that by increasing the disctance it would capture more drone pilots flying their drones and calling the ATC asking for permission to fly, thereby increasing the workload of those ATC operators. It is clear that there is an inconsistent approach by ATC’s in how they deal with drone operators and some taking an inordinate amount of time to approve such a request.  Some ATC’s are levying charges for permission!</p>
<p>The report refers to forthcoming regulation and names the Drones Bill, which passage on to the statute books has been halted due to Brexit and a General Election. However, there will be new legislation that was mentioned in the recent Queen’s Speech, namely the Air Traffic Management and Unmanned Aircraft Bill.  The new bill does include to an extent what the original drones bill was going to include:</p>
<ol>
<li>Drone registration;</li>
<li>Remote pilot competency;</li>
<li>Personal details of drone operators.</li>
</ol>
<p>The consensus around registration is that law abiding professional drone operators will at some poiint engage in registration, however those wishing to act illegally shall not, a point which was acknowledged by the CAA. The report recommends that those operators that avoid registration should be subject to a sliding scale of penalties for failure to register, starting with a warning, and culminating in a fine and a prison sentence.  You have been warned!</p>
<p>The post <a href="https://blakistons.co.uk/uk-strengthens-drone-laws-new-regulations-on-flight-restriction-zones-registration-and-pilot-competency/">Commercial and recreational drone use in the UK</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
