<?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>UK Drone Regulations Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/uk-drone-regulations/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/uk-drone-regulations/</link>
	<description>Drone Law</description>
	<lastBuildDate>Wed, 12 Nov 2025 16:25:55 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.3</generator>
	<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>When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports</title>
		<link>https://blakistons.co.uk/when-just-a-minute-becomes-bvlos-legal-lessons-for-drone-operators-from-chirps-september-2025-reports/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 27 Oct 2025 19:14:43 +0000</pubDate>
				<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Case Studies - Provides a real-world incident analysis for educational purposes in drone law and compliance]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Drone Accidents & Case Studies]]></category>
		<category><![CDATA[Drone Incidents]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Industry Concerns]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Government Reports]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Urban Air Mobility]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[ANO 2016 Article 241]]></category>
		<category><![CDATA[battery settings]]></category>
		<category><![CDATA[BMFA]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CHIRP]]></category>
		<category><![CDATA[crowds]]></category>
		<category><![CDATA[DJI]]></category>
		<category><![CDATA[Drone and Model Aircraft Code]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[event safety]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[Mavic 4 Pro]]></category>
		<category><![CDATA[Mini 2]]></category>
		<category><![CDATA[Nottingham Carnival]]></category>
		<category><![CDATA[operations manual]]></category>
		<category><![CDATA[Operator ID]]></category>
		<category><![CDATA[powerlines]]></category>
		<category><![CDATA[RC2 controller]]></category>
		<category><![CDATA[Return to Home]]></category>
		<category><![CDATA[RTH altitude]]></category>
		<category><![CDATA[screen recording]]></category>
		<category><![CDATA[SWEETS]]></category>
		<category><![CDATA[UK CAA]]></category>
		<category><![CDATA[visual observer]]></category>
		<category><![CDATA[VLOS]]></category>
		<category><![CDATA[waypoint missions]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2590</guid>

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

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

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

					<description><![CDATA[<p>Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations By Richard Ryan, Drone Lawyer (UK) In a noteworthy development across the pond (thanks to sUAS News for the notification!), the United States District Court for the Eastern District of Pennsylvania has entered a consent judgment against a Philadelphia resident, Mr Michael DiCiurcio, [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/consent-judgment-entered-against-philadelphia-drone-flyer-for-violations-of-faa-regulations/">Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations</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/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE-300x300.webp" alt="" width="300" height="300" class="alignnone size-medium wp-image-2553" srcset="https://blakistons.co.uk/wp-content/uploads/2025/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE-300x300.webp 300w, https://blakistons.co.uk/wp-content/uploads/2025/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE-150x150.webp 150w, https://blakistons.co.uk/wp-content/uploads/2025/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE-768x768.webp 768w, https://blakistons.co.uk/wp-content/uploads/2025/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE-600x600.webp 600w, https://blakistons.co.uk/wp-content/uploads/2025/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE-100x100.webp 100w, https://blakistons.co.uk/wp-content/uploads/2025/02/250205_Consent-Judgment-Entered-Against-Philadelphia-Drone-Flyer-for-Violations-of-FAA-Regulations_IMAGE.webp 1024w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations</strong></p>
<p><strong>By Richard Ryan, Drone Lawyer (UK)</strong></p>
<p>In a noteworthy development across the pond (thanks to sUAS News for the notification!), the United States District Court for the Eastern District of Pennsylvania has entered a consent judgment against a Philadelphia resident, Mr Michael DiCiurcio, for multiple breaches of Federal Aviation Administration (“FAA”) regulations and safety guidelines. Although this case has arisen under US law, it is a useful reminder for drone operators in the UK of the absolute necessity to adhere strictly to local regulations—particularly when flying in congested or controlled airspace.</p>
<p><strong>Background of the Case</strong><br />
According to the complaint, the United States alleges that Mr DiCiurcio operated small unmanned aircraft systems (“sUAS”), commonly referred to as drones, illegally and unsafely in the Philadelphia area from December 2019 onwards. Notable alleged violations include:<br />
1.	Night-time flights without proper authorisation.<br />
2.	Flying in close proximity to landmark buildings, including the William Penn Statue, the PSFS Building, and Liberty One Building—once nearly striking a church steeple.<br />
3.	Operating in controlled airspace near Philadelphia airport without permission, and over people and cars.<br />
4.	Losing control of a drone, causing it to fly uncontrolled over Philadelphia.<br />
The FAA had previously issued written warnings to Mr DiCiurcio, offering counselling and education regarding sUAS regulations. Despite these efforts, the government contends that Mr DiCiurcio continued to fly drones in a manner deemed careless, reckless, and endangering public safety.</p>
<p><strong>Terms of the Consent Judgment</strong><br />
On 23 January 2025, before Magistrate Judge Jose Arteaga, Mr DiCiurcio agreed to a consent judgment that includes several key terms:<br />
1.	Admissions of Liability<br />
o	Mr DiCiurcio admits that the allegations in the Verified Complaint are both true and accurate, and that they constitute violations of FAA regulations.<br />
2.	Permanent Ban on Drone Operations<br />
o	Mr DiCiurcio agrees never to operate any sUAS in the United States in any capacity, nor to seek any form of certification or licence to do so.<br />
3.	Removal of Online Content<br />
o	Mr DiCiurcio must take down his “Philly Drone Life” YouTube channel and is prohibited from reviving its content in any form.<br />
4.	Abandonment of Equipment<br />
o	He relinquishes ownership of the sUAS and related items previously surrendered to the FAA.<br />
Chief Judge Mitchell S. Goldberg signed the consent judgment on 29 January 2025.</p>
<p><strong>Enforcement and Commentary</strong><br />
FAA Deputy Administrator Katie Thomson emphasised that while the agency strives to educate drone operators, it will not hesitate to take stringent enforcement action when individuals “deliberately flout the rules.”<br />
U.S. Attorney for the Eastern District of Pennsylvania, Jacqueline C. Romero, reiterated that failing to observe sUAS regulations endangers people and property. The authorities involved have made it clear that they intend to take firm action against drone operators who disregard safety protocols and regulatory requirements.<br />
It is important to note that, as is typical in a civil proceeding, all allegations remain just that—allegations—until liability is formally established. In this instance, Mr DiCiurcio has effectively acknowledged those allegations by agreeing to the judgment.</p>
<p><strong>Lessons for UK Drone Operators</strong><br />
Although this case unfolded in the United States, the lessons are equally pertinent for drone enthusiasts and professional operators here in the UK:<br />
1.	Know Your Regulations<br />
o	In the UK, drone operations are governed by the Civil Aviation Authority (CAA). There are specific requirements based on the weight category of your drone and the environment in which you intend to fly (e.g., near airports, above crowds). Understanding these regulations is paramount.<br />
2.	Obtain the Necessary Permissions<br />
o	Just as the FAA requires authorisations for certain flights, UK law may also demand operational authorisations for flights in congested areas or controlled airspace. Always seek the appropriate permission before taking off.<br />
3.	Heed Warnings and Guidance<br />
o	If you ever receive a caution or formal notice from a regulatory body, treat it seriously. As illustrated by this case, repeated violations—particularly after being warned—can escalate into severe legal consequences.<br />
4.	Operate Safely and Responsibly<br />
o	Safety should always be at the forefront of every flight. This includes maintaining control of your sUAS, respecting no-fly zones, and refraining from operating drones while distracted or in hazardous conditions.</p>
<p><strong>Conclusion</strong><br />
The consent judgment against Mr DiCiurcio underscores the serious consequences drone operators may face if they wilfully violate aviation regulations. For those of us practising and flying drones in the UK, it serves as a timely reminder to remain vigilant, operate responsibly, and stay fully abreast of ever-evolving drone laws.<br />
While national regulations may differ, the underlying principle is universal: drones must be flown safely, ethically, and in compliance with applicable rules. Failing to do so jeopardises both the public and the future of drone innovation.</p>
<p><strong>About the Author</strong><br />
Richard Ryan is a UK-based Direct Access Barrister specialising in drone and aviation law, advising on regulatory compliance, operational approvals, and dispute resolution. With extensive experience navigating the complexities of both UK Civil Aviation Authority (CAA) regulations and international drone frameworks, Richard assists private clients, commercial operators, and industry stakeholders alike. Passionate about emerging technologies, Richard frequently speaks and writes on the legal aspects of unmanned aerial vehicle (UAV) operations, promoting safe, responsible, and innovative drone use. When he’s not in chambers, Richard is deeply engaged in exploring the latest developments in drone technology and advocating for robust regulatory standards that balance innovation with public safety.</p>
<p><strong>Disclaimer:</strong> This blog is for general information only and does not constitute legal advice. If you have specific questions about drone operations and regulatory compliance in the UK, please consult a qualified drone lawyer at Blakiston’s Chambers.</p>
<p>The post <a href="https://blakistons.co.uk/consent-judgment-entered-against-philadelphia-drone-flyer-for-violations-of-faa-regulations/">Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</title>
		<link>https://blakistons.co.uk/military-drones-and-ai-regulation-a-uk-drone-lawyers-perspective/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 07 Jan 2025 13:29:44 +0000</pubDate>
				<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[International Drone Regulations]]></category>
		<category><![CDATA[International Humanitarian Law]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[UK Defence Policy]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[AI Ethics]]></category>
		<category><![CDATA[AI regulation]]></category>
		<category><![CDATA[artificial intelligence]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Faculty AI]]></category>
		<category><![CDATA[frontier AI]]></category>
		<category><![CDATA[lethal autonomous weapons]]></category>
		<category><![CDATA[military drones]]></category>
		<category><![CDATA[UK drone lawyer]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2540</guid>

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

					<description><![CDATA[<p>Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland By Richard Ryan, Blakiston’s Chambers The recent Air Accident Investigation Unit (AAIU) report on the GEN 3.8 drone accident in Ireland gives us a significant case study on drone operations in urban areas. The incident [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/legal-issues-in-drone-operations-a-uk-perspective-on-safety-compliance-and-lessons-from-the-gen-3-8-incident-in-ireland/">Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-2482" src="https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland-300x300.webp" alt="" width="300" height="300" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland-300x300.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland-150x150.webp 150w, https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland-768x768.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland-600x600.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland-100x100.webp 100w, https://blakistons.co.uk/wp-content/uploads/2024/11/241111_Legal-Issues-in-Drone-Operations-A-UK-Perspective-on-Safety-Compliance-and-Lessons-from-the-GEN-3.8-Incident-in-Ireland.webp 1024w" sizes="auto, (max-width: 300px) 100vw, 300px" /><br />
Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland</p>
<p>By Richard Ryan, Blakiston’s Chambers</p>
<p>The recent Air Accident Investigation Unit (AAIU) report on the GEN 3.8 drone accident in Ireland gives us a significant case study on drone operations in urban areas. The incident highlights important safety and legal concerns that apply to unmanned aircraft systems (UAS), which are highly relevant to both Irish and UK drone regulations. This blog explores these issues in the context of the UK’s Aviation Act 1982 and the Air Navigation Order 2016 (ANO) and contrasts them with the legal framework in Ireland.</p>
<p>Overview of the Incident</p>
<p>In July 2022, a GEN 3.8 drone, conducting an urban delivery in Balbriggan, Ireland, experienced a mechanical failure when one of its propeller blades detached. This failure triggered an emergency descent and parachute deployment, causing a minor injury to a bystander. While the consequences of the accident were relatively minor, it underlines the importance of strong legal frameworks for safe drone operations, especially in populated areas.</p>
<p>The UK Legal Framework for Drone Operations</p>
<p>In the UK, drone operations are governed by several key laws and regulations:</p>
<p>1. Aviation Act 1982</p>
<p>The Aviation Act provides the overall legal framework for civil aviation in the UK. It gives the Civil Aviation Authority (CAA) the power to regulate aviation safety and enforce compliance.</p>
<p>The CAA can also develop specific regulations for unmanned aircraft to address the risks and challenges that drone technology presents.</p>
<p>2. Air Navigation Order 2016 (ANO)</p>
<p>The ANO is the primary legislation for regulating UAS operations. It categorizes drones into Open, Specific, and Certified categories, depending on the risk involved in the operation.</p>
<p>Article 241 of the ANO prohibits endangering people or property with a drone, requiring drones to maintain safe distances from people, buildings, and crowded areas. This is especially relevant for urban delivery flights.</p>
<p>3. Requirement for Operational Authorisation</p>
<p>For commercial operations, like the GEN 3.8 urban deliveries, an operational authorisation under the Specific category is required. This involves conducting a risk assessment and putting safety measures in place, such as emergency systems and proper documentation.</p>
<p>UK operators must prove to the CAA that they have identified and mitigated risks, which includes being prepared for mechanical issues like those seen in the GEN 3.8 case.</p>
<p>Comparison with Ireland’s Legal Framework</p>
<p>Ireland’s drone regulations are similar to those of the UK but have some key differences:</p>
<p>1. Regulatory Basis</p>
<p>In Ireland, drone operations are regulated by the Irish Aviation Authority (IAA) under the EU’s Implementing Regulation (EU) 2019/947, which applies to all EU member states. Like the UK’s CAA, the IAA oversees aviation safety and authorises specific operations.</p>
<p>Since the UK left the EU, it has adapted its own regulations to keep pace with the rapid evolution of drone technology.</p>
<p>2. LUC Certificates and Specific Category Requirements</p>
<p>Similar to the UK’s Specific category authorisation, Ireland issues Light UAS Operator Certificates (LUC) to operators meeting specific standards. This allows them to conduct higher-risk operations under IAA oversight.</p>
<p>The GEN 3.8 drone operated under Ireland’s Specific category. However, there were delays in reporting the incident, showing the need for better communication between the operator, IAA, and the AAIU.</p>
<p>3. Accident Reporting Requirements</p>
<p>In Ireland, regulations require that any drone accident resulting in injury or significant damage must be reported to the AAIU. The GEN 3.8 incident was only reported after it appeared on social media, suggesting delays in the reporting process.</p>
<p>In the UK, the ANO 2016 requires that accidents are reported to the CAA immediately, with strict penalties for non-compliance. This ensures a timely investigation and response, which is essential for public safety.</p>
<p>Key Takeaways for UK Drone Operators</p>
<p>The GEN 3.8 incident highlights several important lessons for drone operators in the UK:</p>
<p>1. Strict Compliance with Manufacturer Guidelines</p>
<p>The GEN 3.8 incident showed that its propellers were not designed for the way they were used, which led to the failure. UK law requires operators to maintain drones as per the manufacturer&#8217;s guidelines to avoid similar problems.</p>
<p>2. Robust Reporting Mechanisms</p>
<p>The delay in reporting the GEN 3.8 incident shows why prompt reporting is essential. In the UK, operators must report any accidents involving injuries or property damage to the CAA without delay. This helps ensure quick investigation and corrective action.</p>
<p>3. Operational Risk Assessment and Safety Measures</p>
<p>UK operators must conduct a risk assessment before undertaking operations. The GEN 3.8’s emergency parachute deployment is a good example of how an effective Flight Termination System (FTS) can help mitigate risks.</p>
<p>4. Public Liability and Insurance Requirements</p>
<p>UK law requires commercial operators to carry public liability insurance to cover injuries or property damage. The GEN 3.8 accident is a reminder of why adequate insurance is crucial for managing liability in unforeseen incidents.</p>
<p>Conclusion: Strengthening Drone Safety Regulations</p>
<p>The GEN 3.8 incident serves as a valuable lesson for drone operators and regulators in the UK and Ireland. It emphasises the importance of following safety standards, having efficient reporting systems, and conducting thorough risk assessments. In the UK, the Aviation Act 1982 and ANO 2016 provide a solid foundation for managing the risks of urban drone operations. As drone technology evolves and urban deliveries become more common, the UK must keep improving its regulations to ensure public safety.</p>
<p>For operators, compliance is only the beginning. By understanding drone regulations and putting the best safety practices in place, they can ensure their operations are both safe and legally sound.</p>
<p>Richard Ryan is an experienced drone lawyer specialising in unmanned aircraft systems (UAS) and aviation law. He provides expert legal guidance on regulatory compliance, licensing, and operational issues to clients navigating the complexities of drone technology.</p>
<p>Disclaimer: This blog is for informational purposes only and does not constitute legal advice. For legal counsel regarding specific situations, please consult a qualified drone lawyer.</p>
<p>The post <a href="https://blakistons.co.uk/legal-issues-in-drone-operations-a-uk-perspective-on-safety-compliance-and-lessons-from-the-gen-3-8-incident-in-ireland/">Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
