<?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>CAA guidelines Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/caa-guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/caa-guidelines/</link>
	<description>Drone Law</description>
	<lastBuildDate>Mon, 06 Jul 2026 09:53:17 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>Navigating UK SORA: A Drone Lawyer’s Guide to CAA Decision No. 60</title>
		<link>https://blakistons.co.uk/navigating-uk-sora-a-drone-lawyers-guide-to-caa-decision-no-60/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 06 Jul 2026 09:53:17 +0000</pubDate>
				<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA) Policies]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Industry Challenges]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[International Drone Policies]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[Aerospace Law]]></category>
		<category><![CDATA[AI Governance]]></category>
		<category><![CDATA[Air Risk]]></category>
		<category><![CDATA[artificial intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[aviation safety]]></category>
		<category><![CDATA[Beyond Visual Line of Sight]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA Decision No. 60]]></category>
		<category><![CDATA[Civil Aviation Authority]]></category>
		<category><![CDATA[Commercial Drones]]></category>
		<category><![CDATA[Containment]]></category>
		<category><![CDATA[Detect and Avoid]]></category>
		<category><![CDATA[Drone Compliance]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Evidence Retention]]></category>
		<category><![CDATA[Flight Safety]]></category>
		<category><![CDATA[Flight Termination System]]></category>
		<category><![CDATA[Geo-caging]]></category>
		<category><![CDATA[Ground Risk]]></category>
		<category><![CDATA[Kinetic Energy]]></category>
		<category><![CDATA[Operational Authorisation]]></category>
		<category><![CDATA[Operational Safety Objectives]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[SAIL]]></category>
		<category><![CDATA[Specific Category]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UAV]]></category>
		<category><![CDATA[UK AI Framework]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[UK SORA]]></category>
		<category><![CDATA[Uncrewed Aircraft Systems]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2703</guid>

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

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

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

					<description><![CDATA[<p>Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations By Richard Ryan, Drone Lawyer As a UK drone lawyer, I’ve seen firsthand how tricky it can be to navigate the ever-changing skies of unmanned aviation regulation. The Civil Aviation Authority’s (CAA) “Unmanned Aircraft Operations in an [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/soaring-ahead-or-stuck-in-the-past-what-the-cap-3040-second-edition-means-for-your-drone-operations/">Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations</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/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations-300x300.webp" alt="" width="300" height="300" class="alignnone size-medium wp-image-2536" srcset="https://blakistons.co.uk/wp-content/uploads/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations-300x300.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations-150x150.webp 150w, https://blakistons.co.uk/wp-content/uploads/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations-768x768.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations-600x600.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations-100x100.webp 100w, https://blakistons.co.uk/wp-content/uploads/2024/12/241211_Soaring-Ahead-or-Stuck-in-the-Past_-What-the-CAP-3040-Second-Edition-Means-for-Your-Drone-Operations.webp 1024w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations</strong></p>
<p><strong>By Richard Ryan, Drone Lawyer</strong></p>
<p>As a UK drone lawyer, I’ve seen firsthand how tricky it can be to navigate the ever-changing skies of unmanned aviation regulation. The Civil Aviation Authority’s (CAA) “Unmanned Aircraft Operations in an Atypical Air Environment (AAE): Policy Concept” (CAP 3040) is no exception. After the initial excitement of the First Edition, many in the drone community were eagerly awaiting the Second Edition, hoping for clarifications, improvements, and a more future-focused framework.</p>
<p><strong>What’s New?</strong><br />
At a glance, the changes between the First and Second Editions might seem minimal—just a tweak to the reference for ADS-B (Automatic Dependent Surveillance-Broadcast) equipment, rolling back from RTCA DO-282C to the older DO-282B standard. But that’s not a small footnote. If you’ve been prepping your drone gear to meet DO-282C standards, you may now be left wondering why the rug’s been pulled from under you.</p>
<p><strong>The Tech Twist:</strong><br />
DO-282B is an earlier standard for ADS-B performance, while DO-282C was supposed to reflect newer technology and real-world lessons learned. Reverting to an older standard could mean extra work or unexpected costs if you’ve already made purchases or adapted your systems for DO-282C. It also raises questions about whether the policy is truly forward-looking, or inadvertently stifling progress at a critical time in UK drone innovation.</p>
<p><strong>Still Flying Through Foggy Regulations:</strong><br />
The Second Edition still leaves operators wrestling with a few nagging uncertainties:<br />
1.	Defining ‘Atypical Air Environment’: The document still lacks a crystal-clear definition of AAE. Without a firm legal baseline, you might struggle to know if your flight qualifies—adding confusion to your operations and potentially slowing down approvals.<br />
2.	Single Site Limitations: The CAA’s recommended approach of applying for just one site per Operational Authorisation (OA) remains. This can create unnecessary hurdles for those looking to scale up and serve multiple clients or routes.<br />
3.	Extra Admin, Less Innovation: Requirements like routine NOTAM submissions or intricate Electronic Conspicuity (EC) licensing haven’t been simplified. For many operators, these processes feel more bureaucratic than beneficial, potentially discouraging new entrants and curbing the industry’s growth.</p>
<p><strong>How to Navigate This Airspace Turbulence:</strong><br />
•	Stay Agile: Keep tabs on CAA communications and industry forums. If the CAA shifts requirements again, you’ll want to pivot quickly.<br />
•	Ask for Clarity: Don’t hesitate to reach out to uavenquiries@caa.co.uk for guidance, especially if you’ve already invested in tech aligned with DO-282C.<br />
•	Industry Collaboration: Connect with fellow operators, manufacturers, and drone associations. Shared experiences help identify practical solutions and give your concerns more weight when approaching regulators.<br />
•	Professional Advice: A drone-focused legal expert can help you interpret the Second Edition’s nuances, reduce compliance guesswork, and ensure you’re not sinking costs into the wrong standards.</p>
<p>Charting a Better Flight Path: While the Second Edition’s updates may feel like a step back, there’s still hope. The CAA emphasizes that CAP 3040 is an evolving concept. By voicing concerns, sharing data, and staying engaged, the drone community can help steer policy revisions that balance safety, innovation, and economic growth.</p>
<p><strong>The Bottom Line:</strong><br />
The CAP 3040 Second Edition is a reminder that regulatory frameworks are works in progress. This can be frustrating, yes—but it’s also an opportunity. Operators willing to adapt, learn, and advocate for sensible changes can help shape the UK’s drone landscape into one that truly welcomes innovation. Keep your engines running, your channels of communication open, and your ambitions high. Together, we can ensure that tomorrow’s regulations are as cutting-edge and future friendly as the drone technology they’re meant to guide.</p>
<p><strong>About the Author</strong><br />
Richard Ryan is a direct access barrister at Blakiston’s Chambers, specialising in drone law and unmanned aircraft regulation. Leveraging extensive knowledge of emerging aviation technologies and the UK’s complex regulatory landscape, Richard Ryan provides pragmatic guidance that empowers clients to navigate compliance challenges, secure operational approvals, and seize opportunities in the rapidly evolving drone sector. Known for translating intricate legal frameworks into actionable strategies, Richard Ryan is dedicated to shaping the policies that will define the future of unmanned aviation in the UK.</p>
<p>The post <a href="https://blakistons.co.uk/soaring-ahead-or-stuck-in-the-past-what-the-cap-3040-second-edition-means-for-your-drone-operations/">Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
