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

<channel>
	<title>drone law Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/tag/drone-law/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/tag/drone-law/</link>
	<description>Drone Law</description>
	<lastBuildDate>Thu, 06 Nov 2025 18:28:20 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean</title>
		<link>https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 06 Nov 2025 18:28:20 +0000</pubDate>
				<category><![CDATA[AI and Drone Technology]]></category>
		<category><![CDATA[AI Governance and Ethics]]></category>
		<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[AI Technology]]></category>
		<category><![CDATA[Airspace Legislation]]></category>
		<category><![CDATA[Airspace Management]]></category>
		<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Autonomous Systems in Aviation]]></category>
		<category><![CDATA[Aviation Innovation]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Aviation Security]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Defence Procurement]]></category>
		<category><![CDATA[Defence Technology]]></category>
		<category><![CDATA[Defense Innovation]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[Emerging Technologies]]></category>
		<category><![CDATA[Emerging Technologies in Logistics]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[European Union Policy Updates]]></category>
		<category><![CDATA[Future Trends]]></category>
		<category><![CDATA[Government Reports]]></category>
		<category><![CDATA[High-Risk AI Applications]]></category>
		<category><![CDATA[Law Enforcement]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Legal Challenges]]></category>
		<category><![CDATA[Legal Conflicts]]></category>
		<category><![CDATA[Legal Frameworks]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[Legal Updates]]></category>
		<category><![CDATA[Local Government Policies]]></category>
		<category><![CDATA[Local Government Policy]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Public Safety]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance Strategies]]></category>
		<category><![CDATA[Regulatory Oversight]]></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[Technological Innovations in Drones]]></category>
		<category><![CDATA[Technology and Innovation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Defence Policy]]></category>
		<category><![CDATA[UK Government Policy]]></category>
		<category><![CDATA[autonomous fighters]]></category>
		<category><![CDATA[biometric identification]]></category>
		<category><![CDATA[CE marking]]></category>
		<category><![CDATA[defence law]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[EU aviation law]]></category>
		<category><![CDATA[GA-ASI]]></category>
		<category><![CDATA[GPAI]]></category>
		<category><![CDATA[high-risk AI]]></category>
		<category><![CDATA[International Fighter Conference]]></category>
		<category><![CDATA[manned-unmanned teaming]]></category>
		<category><![CDATA[real-world testing]]></category>
		<category><![CDATA[Rome]]></category>
		<category><![CDATA[UAS]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2624</guid>

					<description><![CDATA[<p>By Richard Ryan, barrister and drone lawyer How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft — and what the defence carve-outs really mean. In Brief&#8230; Purely military AI systems are out of scope of the EU AI Act. If an AI system is developed or used exclusively for military/defence or national-security [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/">How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Begin blog content (no title; WordPress provides its own) --></p>
<div>
By Richard Ryan, barrister and drone lawyer </p>
<p><em>How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft — and what the defence carve-outs really mean.</em></p>
<hr />
<h3>In Brief&#8230;</h3>
<ul>
<li><strong>Purely military AI systems are out of scope</strong> of the EU AI Act. If an AI system is <strong>developed or used exclusively for military/defence or national-security purposes</strong>, the Act does not apply. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Dual-use is different.</strong> If the same autonomy stack, sensors or models are marketed or used for <strong>civilian</strong> purposes in the EU (for example, civil UAS, border or law-enforcement tasks), the Act can apply — with stringent duties for “high-risk” systems. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Real-world testing is regulated.</strong> Pre-market R&amp;D is generally excluded, <strong>but real-world testing isn’t</strong> — it requires specific safeguards and registration. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Foundation models (GPAI)</strong> have their own rules from <strong>2 Aug 2025</strong>; the defence carve-out in the Act is written for <strong>AI systems</strong>, not explicitly for <strong>models</strong>. If a model is placed on the EU market generally, the provider’s GPAI obligations can still bite. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<blockquote>
<p><strong>Context:</strong> sUAS News reports that GA-ASI is showcasing its autonomous fighter portfolio (for example, YFQ-42A CCA, MQ-20 Avenger) at the International Fighter Conference in Rome, 4–6 Nov 2025. This post overlays that scenario with the EU AI Act’s rules.</p>
</blockquote>
<hr />
<h2>1) First principles: When does the EU AI Act apply?</h2>
<p>The Act has <strong>extraterritorial reach</strong>. It covers (i) providers and deployers in the EU, (ii) providers placing on the EU market or putting systems into service in the EU — even if they are not established here — and (iii) providers/deployers in third countries <strong>where the AI system’s output is used in the EU</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<p>However, <strong>Article 2(3)</strong> draws a bright line: the Act <strong>does not apply</strong> to <strong>AI systems used exclusively</strong> for <strong>military, defence or national security</strong>. It also does not apply where a system is <strong>not</strong> placed on the EU market but its <strong>output is used in the EU exclusively</strong> for those purposes. Recital 24 reiterates this and clarifies that <strong>non-defence use falls back under the Act</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<p><strong>What this means in Rome:</strong></p>
<ul>
<li>A <strong>closed, defence-only</strong> showcase for European militaries: <strong>out of scope</strong>.</li>
<li>A <strong>civil-use pitch</strong>, civil flight trials, or plans to sell autonomy modules to <strong>EU civilian buyers</strong>: <strong>in scope</strong> (see the high-risk section below). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>2) The key defence carve-outs (and their limits)</h2>
<p><strong>Carve-out #1 — Defence/military:</strong></p>
<blockquote>
<p>“This Regulation shall not apply to AI systems … used exclusively for military, defence or national security purposes.” (Article 2(3))</p>
</blockquote>
<p>Two important nuances:</p>
<ul>
<li><strong>Exclusivity matters.</strong> The moment an autonomy stack or sensor suite is also <strong>marketed or used for civilian</strong> or law-enforcement tasks, the <strong>defence exclusion no longer shields those non-defence uses</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Models vs systems.</strong> The text explicitly excludes <strong>AI systems</strong> for defence; it <strong>does not create an explicit defence exclusion for general-purpose AI models</strong>. If a <strong>GPAI model</strong> is <strong>placed on the EU market</strong>, Chapter V obligations for model providers can still apply — even if one downstream customer is a defence user. (More on GPAI below.) (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>Carve-out #2 — Pre-market R&amp;D:</strong><br />
  R&amp;D <strong>before</strong> placing on the market is generally outside scope, <strong>but real-world testing is not</strong>. Testing in real-world conditions triggers a dedicated regime (for example, registration, time limits, informed consent or special conditions for law enforcement, incident reporting). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<p><strong>Carve-out #3 — Emergency derogations (non-defence):</strong><br />
  For <strong>exceptional public-security reasons</strong> (or imminent threats to life/health), <strong>market surveillance authorities</strong> can authorise <strong>temporary use</strong> of a high-risk AI system <strong>before</strong> full conformity assessment — subject to strict conditions. Law-enforcement or civil-protection bodies can also use in urgent cases, then seek authorisation without undue delay. This is <strong>not</strong> a defence-specific carve-out, but it explains emergency deployments outside the military context. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>3) If the defence exclusion doesn’t apply, would autonomous fighters tech be “high-risk”?</h2>
<p>Very likely <strong>yes</strong> — for <strong>civil</strong> variants or dual-use spin-outs:</p>
<ul>
<li><strong>Annex I (product-safety route).</strong> AI that is a <strong>safety component</strong> of products covered by sectoral EU safety laws is <strong>high-risk</strong> where those products need <strong>third-party conformity assessment</strong>. That list <strong>explicitly includes EU civil aviation law (Reg. 2018/1139)</strong> — covering <strong>unmanned aircraft</strong> and their remotely controllable equipment. In a civil-UAS configuration, an autonomy stack acting as a safety component would be regulated as <strong>high-risk</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Annex III (stand-alone uses).</strong> Separate “high-risk” buckets also capture, for example, <strong>remote biometric identification</strong> and other sensitive functions (if and where permitted by Union/national law), <strong>critical infrastructure</strong> safety components, and more. If a fighter-born sensing suite were repurposed for <strong>civil border surveillance</strong> or <strong>public-space identification</strong>, you quickly hit these Annex III categories. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>What “high-risk” demands in practice</strong><br />
  Providers must implement a <strong>risk-management system</strong>, <strong>data governance</strong>, <strong>technical documentation</strong>, <strong>logging</strong>, <strong>transparency/instructions</strong>, <strong>human oversight</strong>, and <strong>accuracy/robustness/cybersecurity</strong> — then pass <strong>conformity assessment</strong>, issue an <strong>EU Declaration of Conformity</strong>, and affix <strong>CE marking</strong>. Deployers also carry duties (for example, monitoring, data relevance, user notification in some cases). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>4) Sensors on show: what about face recognition and other “red lines”?</h2>
<p>The <strong>EU bans</strong> several AI practices outright (from <strong>2 Feb 2025</strong>), including:</p>
<ul>
<li><strong>Untargeted scraping</strong> of facial images to build recognition databases.</li>
<li><strong>Biometric categorisation</strong> inferring sensitive traits (for example, race, political opinions, religion).</li>
<li><strong>Emotion recognition</strong> in workplaces or schools (with narrow safety/medical exceptions).</li>
<li><strong>Predictive “risk assessments”</strong> of criminality based solely on personality traits/profiling.</li>
<li><strong>Real-time remote biometric identification (RBI) in public spaces for law enforcement</strong> — <strong>unless</strong> strictly authorised and necessary for narrowly defined objectives (for example, locating a specific suspect in serious crimes, preventing a specific imminent threat, finding missing persons), with prior judicial/independent approval and registration. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>Implication for a trade-show demo:</strong> training a camera on attendees to test <strong>real-time RBI</strong> in a public venue would <strong>likely be unlawful</strong> unless those strict law-enforcement exceptions and procedural safeguards apply — which they typically <strong>will not</strong> at a commercial defence conference. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>5) Real-world testing in the EU (civil or dual-use variants)</h2>
<p>If a provider runs <strong>real-world flight tests</strong> in the EU (outside the defence exclusion), the Act requires — among other things — <strong>registration</strong>, an EU-established entity or <strong>EU legal representative</strong>, limits on <strong>duration</strong> (normally up to six months, extendable once), rules on <strong>informed consent</strong> (with special handling for law-enforcement tests), <strong>qualified oversight</strong>, and the ability to <strong>reverse/ignore</strong> the system’s outputs. <strong>Serious incidents</strong> must be reported promptly. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>6) Foundation models (GPAI): obligations can still attach</h2>
<p>From <strong>2 Aug 2025</strong>, <strong>Chapter V</strong> sets <strong>baseline transparency and copyright-policy duties</strong> for <strong>providers of general-purpose AI models</strong> (with extra obligations if the model presents <strong>systemic risks</strong>). The defence exclusion in Article 2(3) is framed for <strong>AI systems</strong>, not <strong>models</strong>. So, if a foundation model is <strong>placed on the EU market</strong>, the <strong>model provider</strong> can have obligations even if a downstream customer is a defence prime. (Open-source specifics and systemic-risk thresholds also apply.) (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</p>
<hr />
<h2>7) Timelines you need in Rome (as of 6 Nov 2025)</h2>
<ul>
<li><strong>Entry into force:</strong> 1 Aug 2024 (20 days after OJ publication).</li>
<li><strong>Prohibited practices + core chapters (I–II):</strong> apply from <strong>2 Feb 2025</strong>.</li>
<li><strong>GPAI rules (Chapter V), plus other chapters (III §4, VII, XII, and Article 78):</strong> apply from <strong>2 Aug 2025</strong>.</li>
<li><strong>General application:</strong> <strong>2 Aug 2026</strong> (high-risk regime starts to bite broadly).</li>
<li><strong>Article 6(1) Annex III classification trigger &amp; related obligations:</strong> <strong>2 Aug 2027</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>8) Enforcement and penalties</h2>
<ul>
<li>Violating <strong>prohibited practices</strong> (Article 5) can draw fines up to <strong>€35m or 7%</strong> of worldwide annual turnover, whichever is higher.</li>
<li>Other operator obligations can reach <strong>€15m or 3%</strong>; supplying <strong>misleading information</strong> can reach <strong>€7.5m or 1%</strong> (SMEs benefit from caps). Separate fine scales apply to EU institutions. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>9) Practical playbook for IFC attendees</h2>
<p><strong>If you are a defence OEM showing autonomy stacks:</strong></p>
<ol>
<li><strong>Map uses</strong>: Defence-only (excluded) vs <strong>any civil or law-enforcement</strong> pathways (potentially in scope). Document the <strong>exclusivity</strong> of defence deployments if you rely on the carve-out. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>GPAI suppliers</strong>: If you place a <strong>foundation model</strong> on the EU market, expect <strong>Chapter V</strong> duties regardless of defence customers. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>No RBI demos</strong> on the show floor. Those prohibitions already apply in 2025. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li><strong>Planning EU flight tests</strong> for civil variants? Prepare for <strong>real-world testing</strong> conditions (registration, oversight, incident reporting). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
<li>For <strong>civil UAS commercialisation</strong>, treat your autonomy as <strong>high-risk</strong> (EASA product-safety route), budget time for <strong>conformity assessment</strong> and <strong>CE marking</strong>. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ol>
<p><strong>If you are a European ministry or agency:</strong></p>
<ul>
<li>Distinguish <strong>military operations</strong> (out of scope) from <strong>law-enforcement or border</strong> uses (in scope; watch <strong>RBI</strong> limits and high-risk duties). Consider <strong>Article 46</strong> emergency derogations only in <strong>exceptional</strong> and <strong>documented</strong> cases. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><strong>If you are a civil UAS integrator:</strong></p>
<ul>
<li>Expect the full <strong>high-risk</strong> package (risk management, data governance, human oversight, cybersecurity, logs, conformity assessment, CE). Build compliance into your <strong>system architecture</strong>, <strong>ML pipelines</strong>, <strong>safety cases</strong>, and <strong>ops manuals</strong> from day one. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<hr />
<h2>10) Quick decision pathway</h2>
<ol>
<li><strong>Is the use exclusively defence or national security?</strong><br />
      Yes: AI <strong>system</strong> is <strong>out of scope</strong>.<br />
      No: continue. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
<li><strong>Is it a civil product or law-enforcement/border use?</strong><br />
      Civil product with safety function (for example, civil UAS): <strong>High-risk</strong> via <strong>Annex I</strong> ? conformity assessment + CE. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)<br />
      Stand-alone sensitive use (for example, RBI, critical infrastructure): <strong>Annex III</strong> high-risk or <strong>Article 5</strong> prohibition applies. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
<li><strong>Is there a GPAI model being placed on the EU market?</strong><br />
      Yes: <strong>Chapter V</strong> duties for <strong>model providers</strong> from <strong>2 Aug 2025</strong>, separate from the defence carve-out for systems. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
<li><strong>Is this pre-market testing?</strong><br />
      <strong>Real-world testing</strong> rules apply (registration, oversight, incident reporting). (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)
    </li>
</ol>
<hr />
<h3>Bottom line for “Autonomous Fighters in Rome”</h3>
<ul>
<li>A <strong>military-only</strong> display of GA-ASI’s autonomous fighters is <strong>outside</strong> the AI Act.</li>
<li>Any <strong>civil</strong> spin-off (cargo drones, civil surveillance, airport ops) or <strong>law-enforcement</strong> application in the EU will trigger the Act — often at the <strong>high-risk</strong> level — together with <strong>tight prohibitions</strong> around biometric uses in public spaces. Plan your <strong>compliance architecture</strong> accordingly. (<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ%3AL_202401689" target="_blank" rel="noopener">EUR-Lex</a>)</li>
</ul>
<p><em>This article is informational and not legal advice. Citations are to the Official Journal text of the <strong>Artificial Intelligence Act (Regulation (EU) 2024/1689)</strong> for scope (Art. 2), prohibitions (Art. 5), high-risk regime (Ch. III), real-world testing (Arts. 57–61), GPAI (Ch. V incl. Art. 53), timelines (Art. 113), and penalties (Art. 99–101).</em></p>
<hr />
<section aria-label="Author bio">
<p><strong>About the author — Richard Ryan</strong></p>
<p>Richard Ryan is a UK barrister (Direct Access), mediator and Chartered Arbitrator (FCIArb), and a Bencher of Gray’s Inn. He practises across defence, aerospace, construction, engineering and commodities, with a leading specialism in drone and counter-drone law, unmanned aviation regulation, and AI-enabled safety and compliance. Richard advises government, primes and operators on EU/UK UAS frameworks, BVLOS, U-space/UTM and the EU AI Act. He leads Blakiston’s Chambers and contributes regularly to industry guidance and policy consultations.</p>
</section>
</div>
<p><!-- End blog content --></p>
<p>The post <a href="https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/">How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean</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>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 decoding="async" src="https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-300x300.webp" alt="" width="300" height="300" class="alignnone size-medium wp-image-2541" srcset="https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-300x300.webp 300w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-150x150.webp 150w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-768x768.webp 768w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-600x600.webp 600w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_-100x100.webp 100w, https://blakistons.co.uk/wp-content/uploads/2025/01/250107_Military-Drones-and-AI-Regulation_A-UK-Drone-Lawyers-Perspective_.webp 1024w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</strong></p>
<p><strong>By Richard Ryan, UK Drone Lawyer</strong></p>
<p>On 7 January 2025, The Guardian published an article highlighting the British AI consultancy Faculty AI’s involvement in the development of drone technology for defence clients, prompting renewed questions about where legal, ethical, and regulatory boundaries should lie for AI-driven military applications.<br />
Faculty AI, already prominent for its work with various UK government departments (including the NHS and the Department for Education) and advisory services for the AI Safety Institute (AISI), has reportedly developed and deployed AI models on unmanned aerial vehicles (UAVs) for military purposes. Although it remains unclear whether these drones are intended for lethal operations, the revelations have amplified concerns about how best to regulate or restrict the use of AI in weapon systems.<br />
Below, I explore the key legal issues and examine how the recently adopted <strong>EU AI Act</strong>—as well as the evolving UK regulatory framework—may shape the future of this sector.<br />
________________________________________<br />
<strong>1. Faculty AI’s Defence Work: A Brief Overview</strong><br />
<strong>1.1 Government and Public Sector Ties</strong><br />
Faculty AI, known for its work with the Vote Leave campaign in 2016, was later engaged by Dominic Cummings to provide data analytics during the pandemic. Since then, it has won multiple government contracts worth at least £26.6m, extending its work into healthcare (via the NHS), education, and policy consulting with the AISI on frontier AI safety.<br />
<strong>1.2 UAV Development</strong><br />
The Guardian reports that Faculty AI has experience in deploying AI models on UAVs. Its partner firm, Hadean, indicated that the two companies collaborated on subject identification, tracking objects in movement, and exploring swarm deployment. While Faculty states that it aims to create “safer, more robust solutions”, details on whether these drones might be capable of lethal autonomous targeting remain undisclosed.<br />
________________________________________<br />
<strong>2. The EU AI Act: A New Regulatory Milestone</strong><br />
<strong>2.1 Status of the EU AI Act</strong><br />
Introduced by the European Commission in 2021 as a proposed regulation, the EU AI Act has since been adopted via the EU’s legislative process. As of early 2025, it is recognised as a binding regulation designed to harmonise AI rules across all EU Member States. Although the UK is no longer part of the EU, any UK-based company offering AI products or services within the EU must ensure compliance with the regulation’s requirements.<br />
<strong>2.2 Risk-Tiered Framework</strong><br />
The EU AI Act operates on a tiered risk basis:<br />
•	<strong>Unacceptable risk</strong>: Certain AI applications (e.g., social scoring) are outright banned.<br />
•	<strong>High risk</strong>: This category includes critical infrastructure, healthcare, and—potentially—defence-related AI systems that could significantly affect people’s safety or fundamental rights. Such systems must meet strict transparency, oversight, and data governance requirements.<br />
•	<strong>Limited or minimal risk</strong>: These uses are subject to fewer obligations, generally focused on transparency (e.g., disclosing AI usage to end users).<br />
For <strong>high-risk</strong> AI in military contexts, the EU AI Act demands robust <strong>human oversight</strong>, thorough documentation, and strict compliance obligations, particularly around accountability and the prevention of harm.<br />
<strong>2.3 Potential Impact on Military Drones</strong><br />
While national security and defence largely remain the prerogative of individual EU Member States, the EU AI Act’s principles can still influence how companies and governments view the development of autonomous or semi-autonomous drones. Key considerations include:<br />
•	<strong>Transparent Data and Design</strong>: Documenting data sets, development processes, and operational parameters.<br />
•	<strong>Human in the Loop</strong>: Ensuring a human operator is always able to override or intervene in the AI’s decision-making. Other terms such as Human on the Loop and Human outside the Loop are also referred to.<br />
•	<strong>Liability and Penalties</strong>: Breaches can incur hefty fines—up to 6% of global turnover—thus acting as a significant deterrent against unethical or unlawful AI deployment.<br />
________________________________________<br />
<strong>3. The UK’s Approach to AI Regulation and Military Drones</strong><br />
<strong>3.1 Divergence from the EU?</strong><br />
Post-Brexit, the UK has chosen a “pro-innovation” approach to AI regulation. Rather than adopting a single, all-encompassing statute akin to the EU AI Act, the UK is implementing a sector-by-sector and risk-based strategy, guided by existing regulators such as the Information Commissioner’s Office and the Competition and Markets Authority.<br />
<strong>3.2 AI Safety Institute (AISI)</strong><br />
Established under former Prime Minister Rishi Sunak in 2023, the AISI focuses on frontier AI safety research. Faculty AI’s role in testing large language models and advising the AISI on threats like disinformation and system security places the company in a key position to influence UK policy. Critics argue that this may create potential conflicts of interest if the same organisation is also developing AI for military use.<br />
<strong>3.3 House of Lords Recommendations</strong><br />
In 2023, a House of Lords committee urged the UK Government to clarify the application of International Humanitarian Law (IHL) to lethal drone strikes and to work towards an international agreement limiting or banning fully autonomous weapons systems. The Government response acknowledged the importance of maintaining “human control” in critical decisions but did not enact binding legislation banning lethal autonomous drones outright.<br />
________________________________________<br />
<strong>4. Legal and Ethical Concerns for AI-Enabled Drones</strong><br />
<strong>4.1 International Humanitarian Law (IHL)</strong><br />
IHL principles—<strong>distinction</strong> (separating combatants from civilians) and <strong>proportionality</strong> (limiting harm relative to military objectives)—are central to discussions on AI-driven drones. Fully autonomous UAVs, capable of selecting and engaging targets without human intervention, raise profound legal questions on accountability, particularly if biases or system errors result in wrongful casualties.<br />
<strong>4.2 Allocation of Liability</strong><br />
Traditionally, accountability in military operations lies with commanders and operators. With increasingly autonomous systems, however, liability could extend to technology developers, programmers, or even the purchaser of the system. Clarifying how legal responsibilities are distributed may become a focal point for future litigation and regulatory reform.<br />
<strong>4.3 Export Controls</strong><br />
Companies like Faculty AI must also comply with arms-export rules when providing AI-targeting systems or related software to foreign entities. In the UK, export licences for military-grade technology are subject to domestic legislation and international protocols, such as the Wassenaar Arrangement on dual-use goods.<br />
________________________________________<br />
<strong>5. Looking Ahead: Balancing Innovation, Safety, and Accountability</strong><br />
<strong>5.1	Stronger National Frameworks</strong><br />
Although the UK favours a pro-innovation stance, there is growing pressure from Parliament and civil society for more rigorous, enforceable rules on potentially lethal AI applications. The EU AI Act may serve as a reference point for the UK to consider stricter domestic regulations.<br />
<strong>5.2	International Collaboration</strong><br />
Calls for global agreements—treaties or non-binding accords—to prohibit fully autonomous weapons continue to gain momentum. The House of Lords committee specifically recommended international engagement to ensure that lethal force remains under human control.<br />
<strong>5.3	Corporate Accountability</strong><br />
Organisations operating at the intersection of commercial defence contracts and government policy—such as Faculty AI—need transparent internal processes and robust ethics boards to mitigate conflicts of interest. Demonstrating genuine corporate responsibility will be vital for maintaining public trust.<br />
<strong>5.4	Ethical and Safety Audits</strong><br />
As AI becomes more embedded in defence, mandatory ethical and safety audits may become standard practice. These would scrutinise algorithmic fairness, training data, and how effectively systems can identify and mitigate unintended harms.<br />
________________________________________<br />
<strong>6. Conclusion</strong><br />
Faculty AI’s role in developing AI for military drones underscores how high the stakes are when cutting-edge technology meets defence applications. With the EU AI Act now in force as a binding regulation, Europe has provided a blueprint for tighter control over “high-risk” AI systems. In contrast, the UK’s approach still offers substantial flexibility for companies, potentially raising both legal and ethical concerns around autonomy, accountability, and conflicts of interest.<br />
From an IHL standpoint, keeping a human responsible for any life-and-death decision is imperative. As a UK drone lawyer, I urge policymakers, regulators, and industry stakeholders to keep asking: <strong>Where do we draw the line between legitimate defensive innovation and an unacceptable risk to civilians?</strong> Only by establishing clear, enforceable legal standards—anchored in international law and ethical scrutiny—can we ensure AI-powered drones serve to protect rather than endanger fundamental human values.</p>
<p><strong>Bio – Richard Ryan, UK Drone Lawyer</strong></p>
<p>Richard Ryan is a UK-based drone lawyer specialising in the regulatory, ethical, and commercial aspects of unmanned aerial vehicles (UAVs) and artificial intelligence (AI). Through a series of blogs, Richard Ryan has explored critical issues such as the EU AI Act, the UK’s evolving “pro-innovation” regulatory landscape, and the legal considerations surrounding military drones and lethal autonomous weapons systems.</p>
<p>Drawing on extensive experience in advising government bodies, technology companies, and public institutions, Richard Ryan brings a deep understanding of how international humanitarian law (IHL), export controls, and data protection obligations intersect in modern drone operations. Their writing emphasises the importance of maintaining human oversight in AI-driven systems, championing ethical development and transparent accountability mechanisms.</p>
<p>A trusted voice in the field, Richard Ryan regularly comments on emerging case law, parliamentary recommendations, and global discussions around frontier AI safety. The mission is to help stakeholders—from hobbyist drone operators to established aerospace firms—navigate the complexities of regulation, risk management, and innovation.</p>
<p>The post <a href="https://blakistons.co.uk/military-drones-and-ai-regulation-a-uk-drone-lawyers-perspective/">Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Drones, Security, and the Law: Understanding the UK’s Counter-Drone Framework</title>
		<link>https://blakistons.co.uk/drones-security-and-the-law-understanding-the-uks-counter-drone-framework/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Wed, 27 Nov 2024 09:11:04 +0000</pubDate>
				<category><![CDATA[Counter-Drone Technology]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[Wireless Telegraphy Act]]></category>
		<category><![CDATA[airspace protection]]></category>
		<category><![CDATA[aviation safety]]></category>
		<category><![CDATA[counter-drone measures]]></category>
		<category><![CDATA[drone detection]]></category>
		<category><![CDATA[drone jamming]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[drone security]]></category>
		<category><![CDATA[legal compliance]]></category>
		<category><![CDATA[military drone threats]]></category>
		<category><![CDATA[Ofcom licence]]></category>
		<category><![CDATA[RAF Lakenheath]]></category>
		<category><![CDATA[UK legislation]]></category>
		<category><![CDATA[Wireless Telegraphy Act 2006]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2522</guid>

					<description><![CDATA[<p>Drones, Security, and the Law: Understanding the UK’s Counter-Drone Framework By Richard Ryan, Drone &#038; Counter Drone Lawyer Drones have transformed industries, from agriculture to filmmaking, offering immense benefits. However, their misuse presents significant risks, including privacy violations, safety hazards, and national security threats. The UK&#8217;s legal framework, particularly the Wireless Telegraphy Act 2006, plays [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/drones-security-and-the-law-understanding-the-uks-counter-drone-framework/">Drones, Security, and the Law: Understanding the UK’s Counter-Drone Framework</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/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework-300x171.webp" alt="" width="300" height="171" class="alignnone size-medium wp-image-2523" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework-300x171.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework-1024x585.webp 1024w, https://blakistons.co.uk/wp-content/uploads/2024/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework-768x439.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework-1536x878.webp 1536w, https://blakistons.co.uk/wp-content/uploads/2024/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework-600x343.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/271124_Drones-Security-and-the-Law-Understanding-the-UKs-Counter-Drone-Framework.webp 1792w" sizes="auto, (max-width: 300px) 100vw, 300px" /></p>
<p><strong>Drones, Security, and the Law: Understanding the UK’s Counter-Drone Framework</strong></p>
<p><strong>By Richard Ryan, Drone &#038; Counter Drone Lawyer</strong></p>
<p>Drones have transformed industries, from agriculture to filmmaking, offering immense benefits. However, their misuse presents significant risks, including privacy violations, safety hazards, and national security threats. The UK&#8217;s legal framework, particularly the Wireless Telegraphy Act 2006, plays a critical role in managing these challenges, especially concerning the use of jamming devices to counter rogue drones.</p>
<p>Recent incidents, such as drone sightings near US airbases in Suffolk and Norfolk, underscore the importance of understanding these laws and their practical applications. Let’s delve into the Wireless Telegraphy Act 2006, licensing requirements, and how this legislation shapes counter-drone strategies.<br />
________________________________________<br />
<strong>The Wireless Telegraphy Act 2006: A Legal Cornerstone</strong></p>
<p>The Wireless Telegraphy Act 2006 regulates the use of wireless equipment in the UK, including jamming devices designed to neutralise drones by disrupting their communication signals. It ensures the responsible use of the electromagnetic spectrum to prevent harmful interference with critical communications, including emergency services and air traffic control.<br />
General Prohibition on Jamming Without a Licence</p>
<p>Section 8(1) of the Act states:<br />
It is unlawful—<br />
(a) to establish or use a wireless telegraphy station, or<br />
(b) to install or use wireless telegraphy apparatus,<br />
except under and in accordance with a licence (a “wireless telegraphy licence”) granted under this section by Ofcom.<br />
This provision creates a blanket prohibition on jamming devices unless explicitly authorised by Ofcom, the UK’s communications regulator.</p>
<p>Why Is Jamming Restricted?<br />
The restrictions exist to:<br />
1.	Minimise Interference: Prevent disruptions to essential networks, including emergency services, air traffic control, and legitimate drone operators.<br />
2.	Ensure Safety: Avoid unintended consequences, such as causing drones to crash, endangering lives or property.<br />
3.	Protect Spectrum Integrity: Maintain efficient use of the electromagnetic spectrum, preventing technical issues caused by unauthorised interference.<br />
________________________________________<br />
<strong>Licensing and Exemptions: The Path to Legal Use</strong></p>
<p>Licensing Requirements<br />
To use jamming technology legally, a licence from Ofcom is mandatory. Licences are typically granted only to:<br />
•	Law Enforcement Agencies: For public safety operations.<br />
•	The Military: For national defence and counter-terrorism efforts.<br />
•	High-Risk Sectors: Airports, energy plants, or critical infrastructure sites under strict regulatory oversight.</p>
<p>No Blanket Exemptions<br />
Section 8(3) of the Act allows Ofcom to exempt certain wireless apparatus from licensing. However, Section 8(5) explicitly excludes jamming devices from exemption due to their high potential for interference. Exempt devices must not:<br />
•	Endanger safety of life.<br />
•	Cause undue interference with wireless telegraphy.<br />
•	Adversely affect spectrum efficiency.<br />
Since jammers inherently disrupt wireless signals, they do not meet these criteria.<br />
________________________________________<br />
<strong>Proportionality and Transparency in Licensing</strong></p>
<p>Even when granted, licences for jamming devices must comply with principles outlined in Section 8(3B), ensuring:<br />
•	Objective Justification: Based on the specific risks posed by rogue drones.<br />
•	Proportionality: Countermeasures must align with the threat level.<br />
•	Transparency: Clear communication of licence terms to ensure non-discriminatory enforcement.<br />
For instance, a jamming licence for operations near airports must focus solely on mitigating rogue drones without disrupting legitimate communications or nearby authorised drone operations.<br />
________________________________________<br />
<strong>Practical Implications for Drone Jamming</strong></p>
<p>Private Individuals<br />
As a private individual, you cannot legally use jamming devices, even if a drone invades your privacy or trespasses on your property. Instead:<br />
•	Report the Incident: Contact the police or the Civil Aviation Authority (CAA).<br />
•	Avoid Unauthorised Action: Deploying a jammer is a criminal offence under the Wireless Telegraphy Act 2006.</p>
<p>Organisations in High-Risk Sectors<br />
If you represent a high-risk organisation, such as an airport or energy facility, you may apply for a jamming licence. This requires:<br />
•	Demonstrating Necessity: Proving that detection systems alone are insufficient.<br />
•	Ensuring Compliance: Implementing safeguards to prevent collateral interference and safety risks.</p>
<p>Alternatives to Jamming<br />
If a licence is not feasible, alternatives include:<br />
•	Detection Systems: Radar, RF sensors, and other tools to identify and track drones.<br />
•	Physical Mitigation: Devices like nets or capture drones that neutralise rogue drones without disrupting their signals.<br />
________________________________________<br />
<strong>Recent Developments: Drones Over US Airbases</strong></p>
<p>The recent deployment of British troops to US airbases in Suffolk and Norfolk highlights the real-world implications of counter-drone law. Drones have been sighted near RAF Lakenheath, RAF Mildenhall, and RAF Feltwell, sparking concerns over a potential &#8220;sinister&#8221; plot, with Russian involvement not ruled out.<br />
The RAF has offered advanced counter-drone systems, including the &#8220;Ninja&#8221; and &#8220;Orcus,&#8221; which can jam and control rogue drones, forcing them to return to their origin or reroute safely. These incidents underscore the necessity of authorised and regulated counter-drone measures to address evolving threats.<br />
________________________________________<br />
<strong>Key Takeaways from the Wireless Telegraphy Act 2006</strong></p>
<p>1.	Licensing is Essential: Section 8(1) prohibits the use of jamming devices without a licence from Ofcom.<br />
2.	No Exemptions for Jammers: Jamming devices inherently interfere with wireless signals and do not qualify for licensing exemptions.<br />
3.	Proportionality Matters: Licences are granted only for justified, targeted, and proportionate use.<br />
4.	Alternatives Exist: Detection systems and physical mitigation tools are viable options for those without licences.<br />
________________________________________<br />
<strong>Conclusion: Ensuring Compliance in Counter-Drone Operations</strong></p>
<p>The Wireless Telegraphy Act 2006 ensures a balanced approach to counter-drone operations, prioritising safety, efficiency, and lawful use of the electromagnetic spectrum. Unauthorised jamming is not only illegal but can lead to significant penalties, including fines and imprisonment.</p>
<p>As a counter-drone lawyer, I assist clients in navigating this complex regulatory landscape, from applying for Ofcom licences to ensuring compliance with drone and counter-drone laws. For tailored advice on counter-drone measures or legal representation. Together, we can help secure the skies while safeguarding your rights and responsibilities.</p>
<p>The post <a href="https://blakistons.co.uk/drones-security-and-the-law-understanding-the-uks-counter-drone-framework/">Drones, Security, and the Law: Understanding the UK’s Counter-Drone Framework</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>AI Drone Swarms and the EU AI Act: A Game-Changer in Modern Warfare?</title>
		<link>https://blakistons.co.uk/ai-drone-swarms-and-the-eu-ai-act-a-game-changer-in-modern-warfare/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Sat, 16 Nov 2024 17:44:52 +0000</pubDate>
				<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[AUKUS Partnership]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Defense Innovation]]></category>
		<category><![CDATA[Drone Swarms]]></category>
		<category><![CDATA[Ethical Considerations in AI]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[International Security]]></category>
		<category><![CDATA[Legal Implications of AI]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[Simulation and Sandboxing]]></category>
		<category><![CDATA[Technology and Warfare]]></category>
		<category><![CDATA[AI Drone Swarms]]></category>
		<category><![CDATA[AI Ethics]]></category>
		<category><![CDATA[Artificial Intelligence in Warfare]]></category>
		<category><![CDATA[AUKUS Trials]]></category>
		<category><![CDATA[Autonomous Military Technology]]></category>
		<category><![CDATA[Autonomous Systems Oversight]]></category>
		<category><![CDATA[Defence Innovation]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[Drone Swarm Risks]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Intellectual Property Risks]]></category>
		<category><![CDATA[Military AI Regulations]]></category>
		<category><![CDATA[regulatory compliance]]></category>
		<category><![CDATA[Richard Ryan]]></category>
		<category><![CDATA[Simulation Sandbox]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2504</guid>

					<description><![CDATA[<p>AI Drone Swarms and the EU AI Act: A Game-Changer in Modern Warfare? By Richard Ryan, Drone Lawyer The recent trials conducted by the AUKUS nations—Australia, the United Kingdom, and the United States—mark a significant milestone in the integration of artificial intelligence (AI) and autonomy within military operations. The deployment of AI-enabled uncrewed aerial vehicles [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/ai-drone-swarms-and-the-eu-ai-act-a-game-changer-in-modern-warfare/">AI Drone Swarms and the EU AI Act: A Game-Changer in Modern Warfare?</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/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare-300x171.webp" alt="" width="300" height="171" class="alignnone size-medium wp-image-2505" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare-300x171.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare-1024x585.webp 1024w, https://blakistons.co.uk/wp-content/uploads/2024/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare-768x439.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare-1536x878.webp 1536w, https://blakistons.co.uk/wp-content/uploads/2024/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare-600x343.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/241116_AI-Drone-Swarms-and-the-EU-AI-Act-A-Game-Changer-in-Modern-Warfare.webp 1792w" sizes="auto, (max-width: 300px) 100vw, 300px" /></p>
<p><strong>AI Drone Swarms and the EU AI Act: A Game-Changer in Modern Warfare?</strong></p>
<p><strong>By Richard Ryan, Drone Lawyer</strong></p>
<p>The recent trials conducted by the AUKUS nations—Australia, the United Kingdom, and the United States—mark a significant milestone in the integration of artificial intelligence (AI) and autonomy within military operations. The deployment of AI-enabled uncrewed aerial vehicles (UAVs) capable of locating, disabling, and destroying ground targets presents both remarkable advancements and complex legal challenges, particularly in the context of the European Union&#8217;s AI Act.</p>
<p>As a drone lawyer with over 20 years of experience in the UK, I find it imperative to dissect the interaction between these groundbreaking trials and the regulatory landscape shaped by the EU AI Act. This discussion aims to highlight the risks, oversight issues, and intellectual property considerations that arise when integrating AI algorithms into military UAV swarms.</p>
<p><strong>Understanding the EU AI Act&#8217;s Impact</strong></p>
<p>The EU AI Act seeks to establish a comprehensive regulatory framework for AI technologies, focusing on transparency, accountability, and human oversight. High-risk AI systems, which include those used in critical infrastructure and law enforcement, are subject to stringent requirements. Military applications, while often exempt from certain civilian regulations, still operate under international humanitarian laws and ethical guidelines that resonate with the Act&#8217;s principles.</p>
<p>The AUKUS trials demonstrate the use of AI in autonomous systems for military purposes. The AI-enabled UAVs operated collaboratively, sharing data seamlessly across nations. While the Act primarily governs civilian AI use within the EU, the ethical considerations it embodies cannot be ignored in military contexts, especially when such technologies might eventually influence civilian sectors.</p>
<p><strong>Risks and Oversight Challenges</strong></p>
<p>One of the foremost risks is the potential for AI algorithms to make autonomous decisions without adequate human oversight. The EU AI Act emphasizes the necessity of meaningful human control over AI systems, particularly those capable of impacting human lives. In the AUKUS trials, although a human operator was involved, the level of autonomy granted to the UAVs raises questions about compliance with the Act&#8217;s standards if similar technologies were deployed within the EU.</p>
<p>Data exchange and interoperability between the three nations introduce another layer of complexity. The seamless sharing of information enhances operational efficiency but also raises concerns about data protection and cybersecurity. Ensuring that sensitive data transmitted between UAVs and control systems is secure aligns with the Act&#8217;s requirements for robust data governance.</p>
<p><strong>The Case for a Simulation Sandbox</strong></p>
<p>To address compliance with the EU AI Act, conducting such trials within a simulation sandbox could be a prudent approach. A sandbox environment allows for the testing and validation of AI algorithms in a controlled setting, mitigating risks associated with real-world deployment. It enables developers to assess the AI&#8217;s decision-making processes, identify potential flaws, and ensure adherence to ethical and legal standards before actual implementation.</p>
<p>Moreover, a sandbox can facilitate transparency and accountability, key tenets of the EU AI Act. By documenting the AI&#8217;s performance and decision rationale within simulations, stakeholders can provide evidence of compliance and readiness for safe deployment.</p>
<p><strong>Intellectual Property Considerations</strong></p>
<p>Introducing AI algorithms into a regulatory sandbox presents intellectual property (IP) risks that must be carefully managed. Proprietary algorithms and technologies shared within the sandbox could be exposed to unauthorized access or misuse. Protecting IP rights is crucial to encourage innovation and maintain competitive advantages.</p>
<p>To mitigate these risks, clear agreements outlining the ownership, usage rights, and confidentiality obligations related to the AI algorithms are essential. Collaborative efforts, such as those seen in the AUKUS trials, require robust legal frameworks to safeguard each party&#8217;s IP while promoting shared development goals.</p>
<p><strong>Conclusion</strong></p>
<p>The integration of AI and autonomous systems in military applications is an evolving frontier that necessitates careful navigation of legal and ethical landscapes. The EU AI Act, while primarily focused on civilian applications, provides valuable guidance on managing high-risk AI systems.</p>
<p>By recognising the risks and oversight challenges presented by the AUKUS AI-enabled UAV trials, stakeholders can proactively address compliance issues. Utilising simulation sandboxes offers a viable pathway to refine these technologies within the bounds of regulatory requirements.</p>
<p>Intellectual property considerations remain a critical aspect of this process. Ensuring that AI algorithms are protected within collaborative environments will foster innovation while maintaining legal integrity.</p>
<p>As we advance into this new era of AI-driven military capabilities, a balanced approach that harmonises technological potential with regulatory compliance will be essential. The lessons learned from these trials will undoubtedly shape the future of AI in both military and civilian spheres.</p>
<p>&#8212;</p>
<p><strong>About Richard Ryan</strong></p>
<p>Richard Ryan is a leading drone lawyer based in the United Kingdom, with over 20 years of legal experience as a direct access barrister. Specializing in the legal aspects of unmanned aerial systems and AI technologies, Richard has advised government agencies, defense contractors, and private enterprises on compliance, intellectual property, and regulatory matters. His extensive expertise bridges the gap between cutting-edge technological advancements and the complex legal frameworks that govern them.</p>
<p>The post <a href="https://blakistons.co.uk/ai-drone-swarms-and-the-eu-ai-act-a-game-changer-in-modern-warfare/">AI Drone Swarms and the EU AI Act: A Game-Changer in Modern Warfare?</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>
		<item>
		<title>Analysis and Recommendations on CAP 3040 &#124; First Edition</title>
		<link>https://blakistons.co.uk/analysis-and-recommendations-on-cap-3040-first-edition/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Wed, 06 Nov 2024 13:38:21 +0000</pubDate>
				<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA) Policies]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[International Drone Regulations]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Legal Updates]]></category>
		<category><![CDATA[Policy Development and Amendments]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Technology and Innovation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Atypical Air Environment]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA]]></category>
		<category><![CDATA[CAP 3040]]></category>
		<category><![CDATA[Drone Industry Impact]]></category>
		<category><![CDATA[Drone Industry Innovation]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[Drone Lawyer]]></category>
		<category><![CDATA[Drone Operator Challenges]]></category>
		<category><![CDATA[Drone Policy Amendments]]></category>
		<category><![CDATA[Drone Regulations UK]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[EASA PDRA03]]></category>
		<category><![CDATA[Innovation in Drone Technology]]></category>
		<category><![CDATA[Policy Recommendations]]></category>
		<category><![CDATA[regulatory compliance]]></category>
		<category><![CDATA[Richard Ryan]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[Unmanned Aircraft Systems]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2476</guid>

					<description><![CDATA[<p>Analysis and Recommendations on CAP 3040 &#124; First Edition 1. Executive Summary The CAA&#8217;s policy concept aims to enable Beyond Visual Line of Sight (BVLOS) operations for Unmanned Aircraft Systems (UAS) within an Atypical Air Environment (AAE). While the initiative is commendable for promoting innovation, the policy, as currently drafted, presents several challenges: &#8211; Ambiguity [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/analysis-and-recommendations-on-cap-3040-first-edition/">Analysis and Recommendations on CAP 3040 | First Edition</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-2477" src="https://blakistons.co.uk/wp-content/uploads/2024/11/Picture3-Analysis-and-Recommendations-on-CAP-3040-First-Edition-300x256.png" alt="" width="300" height="256" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/Picture3-Analysis-and-Recommendations-on-CAP-3040-First-Edition-300x256.png 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture3-Analysis-and-Recommendations-on-CAP-3040-First-Edition-768x655.png 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture3-Analysis-and-Recommendations-on-CAP-3040-First-Edition-600x512.png 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture3-Analysis-and-Recommendations-on-CAP-3040-First-Edition.png 787w" sizes="auto, (max-width: 300px) 100vw, 300px" /></p>
<p>Analysis and Recommendations on CAP 3040 | First Edition</p>
<p> 1. Executive Summary</p>
<p>The CAA&#8217;s policy concept aims to enable Beyond Visual Line of Sight (BVLOS) operations for Unmanned Aircraft Systems (UAS) within an Atypical Air Environment (AAE). While the initiative is commendable for promoting innovation, the policy, as currently drafted, presents several challenges:<br />
&#8211; Ambiguity in Definitions: The lack of precise definitions for key terms like AAE may lead to inconsistent application and legal uncertainty.<br />
&#8211; Operational Burdens: Requirements such as pre-flight notifications, electronic conspicuity, and high-intensity lighting may impose significant burdens on operators, especially small and medium enterprises (SMEs).<br />
&#8211; Potential Stifling of Innovation: The cumulative effect of stringent requirements may deter new entrants and hinder technological advancement.<br />
&#8211; Legal Efficacy: For the policy to have legal effect, certain elements need to be codified into law or regulations.</p>
<p> 2. Issues for Drone Operators</p>
<p> a. Ambiguity in Definition of Atypical Air Environment (AAE)<br />
&#8211; Lack of Clarity: The document does not provide a clear, legal definition of an AAE, leading to potential inconsistencies in interpretation.<br />
&#8211; Examples vs. Definitions: Providing examples (e.g., within 100ft of a building) without a firm definition creates uncertainty for operators attempting to comply.</p>
<p> b. Operational Requirements<br />
&#8211; Pre-Tactical Flight Route Notification:<br />
  &#8211; Administrative Burden: Requiring Notices to Airmen (NOTAMs) for each operation may be impractical for frequent or short-duration flights.<br />
  &#8211; Coordination Complexity: Mandatory coordination with multiple stakeholders (e.g., military, emergency services) increases complexity.</p>
<p>&#8211; Electronic Conspicuity (EC):<br />
  &#8211; Equipment Availability: ADS-B equipment operating on 978 MHz UAT is not widely used in the UK, making compliance challenging.<br />
  &#8211; Licensing Issues: Reliance on OFCOM&#8217;s Innovation and Trial licensing procedures adds uncertainty and administrative hurdles and no doubt costs.</p>
<p>&#8211; High-Intensity Anti-Collision Lighting:<br />
  &#8211; Technical Challenges: The requirement may not be feasible for small UAS due to weight and power constraints.<br />
  &#8211; Cost Implications: Additional equipment increases operational costs, affecting profitability and competitiveness.</p>
<p>&#8211; Containment Solutions:<br />
  &#8211; Technical Barriers: Implementing robust geo-caging or equivalent systems may be technologically and financially prohibitive for some operators.</p>
<p> c. Application Process Limitations<br />
&#8211; Single Site Per Submission:<br />
  &#8211; Operational Inefficiency: Limiting applications to one site may slow down deployment and increase administrative overhead.</p>
<p> d. Evolving Policy and Regulatory Uncertainty<br />
&#8211; Continuous Review:<br />
  &#8211; Investment Risk: Operators may be hesitant to invest in compliance if policies are subject to change.<br />
&#8211; Lack of Legal Certainty:<br />
  &#8211; Enforceability Issues: As a policy concept rather than law, operators may face legal ambiguities in enforcement and compliance.</p>
<p> 3. Potential Impacts on the Drone Industry</p>
<p> a. Stifling Innovation and Market Entry<br />
&#8211; Barrier to Entry: Stringent requirements may discourage startups and SMEs from entering the market.<br />
&#8211; Reduced Experimentation: High compliance costs limit the ability to test new technologies and operational models.</p>
<p> b. Competitive Disadvantages<br />
&#8211; Favoring Large Operators: Well-resourced companies are better equipped to meet the requirements, potentially leading to market monopolisation.</p>
<p> c. International Disparities<br />
&#8211; Inconsistency with Global Standards: Reliance on U.S. standards (e.g., RTCA DO-282C) may create conflicts with other international regulations, affecting operators engaged in cross-border activities.</p>
<p> 4. Recommendations for Amendments</p>
<p> a. Clarify Definitions and Parameters<br />
&#8211; Precise Definition of AAE:<br />
  &#8211; Legal Clarity: Provide a clear, legally binding definition of AAE to reduce ambiguity.<br />
  &#8211; Criteria Establishment: Set specific parameters (e.g., exact distances, types of infrastructure) to qualify as an AAE.</p>
<p> b. Proportionality in Operational Requirements<br />
&#8211; Risk-Based Approach:<br />
  &#8211; Scaled Requirements: Tailor operational requirements based on the risk profile of the UAS operation (e.g., size, weight, location).<br />
&#8211; Exemptions for Low-Risk Operations:<br />
  &#8211; Simplify Compliance: Allow for exemptions or reduced requirements for operations posing minimal risk.</p>
<p> c. Streamline Application Process<br />
&#8211; Multiple Sites Per Application:<br />
  &#8211; Administrative Efficiency: Permit applications covering multiple sites where appropriate, reducing bureaucratic hurdles.<br />
&#8211; Standardised Procedures:<br />
  &#8211; Transparency: Develop clear guidelines and timelines for application processing.</p>
<p> d. Address Electronic Conspicuity Challenges<br />
&#8211; Equipment Standardisation:<br />
  &#8211; Market Availability: Collaborate with manufacturers to ensure ADS-B equipment is accessible and affordable.<br />
&#8211; Licensing Simplification:<br />
  &#8211; Permanent Licensing Arrangements: Work with OFCOM to establish permanent, streamlined licensing procedures for 978 MHz UAT.</p>
<p> e. Provide Flexibility in Mitigation Measures<br />
&#8211; Alternative Solutions:<br />
  &#8211; Innovation Encouragement: Allow operators to propose alternative methods to achieve safety outcomes.<br />
&#8211; Technology Neutrality:<br />
  &#8211; Avoid Prescriptive Requirements: Focus on performance outcomes rather than prescribing specific technologies.</p>
<p> f. Enhance Stakeholder Engagement<br />
&#8211; Consultation Processes:<br />
  &#8211; Inclusive Policy Development: Engage with a broad range of stakeholders, including SMEs and industry groups.<br />
&#8211; Support and Guidance:<br />
  &#8211; Educational Resources: Provide operators with clear guidance and training materials to aid compliance.</p>
<p> g. Align with UK Standards<br />
&#8211; Develop Domestic Standards:<br />
  &#8211; Consistency: Establish UK-specific standards for technical requirements like anti-collision lighting.<br />
&#8211; International Harmonisation:<br />
  &#8211; Global Compatibility: Ensure new standards are compatible with international regulations to facilitate cross-border operations.</p>
<p> 5. Legal Requirements for Effective Implementation</p>
<p> a. Codification into Law<br />
&#8211; Regulatory Framework:<br />
  &#8211; Statutory Instruments: Incorporate key policy elements into UK aviation law to provide legal enforceability.<br />
&#8211; Amendments to Existing Regulations:<br />
  &#8211; Regulation (EU) 2019/947 Adaptation: Modify existing regulations to accommodate AAE operations and associated requirements.</p>
<p> b. Legal Certainty and Enforcement<br />
&#8211; Clear Obligations:<br />
  &#8211; Operator Compliance: Define legal obligations clearly to ensure operators understand requirements.<br />
&#8211; Enforcement Mechanisms:<br />
  &#8211; Penalties and Sanctions: Establish clear enforcement protocols for non-compliance to uphold safety standards.</p>
<p> 6. Additional Relevant Points for the CAA</p>
<p> a. Balancing Safety with Innovation<br />
&#8211; Proportional Regulation:<br />
  &#8211; Innovation Friendly: Ensure that safety regulations do not unnecessarily hinder technological advancement.<br />
&#8211; Risk Management:<br />
  &#8211; Data-Driven Policies: Use empirical data to inform policy adjustments, maintaining safety without over-regulation.</p>
<p> b. Data Privacy and Confidentiality<br />
&#8211; Data Handling Policies:<br />
  &#8211; Privacy Protection: Develop clear guidelines on data usage, storage, and sharing to protect operators&#8217; proprietary information.</p>
<p> c. Future-Proofing Regulations<br />
&#8211; Adaptive Frameworks:<br />
  &#8211; Technological Evolution: Design policies flexible enough to accommodate future technological developments.<br />
&#8211; Regular Reviews:<br />
  &#8211; Stakeholder Feedback: Implement mechanisms for ongoing consultation and policy refinement.</p>
<p> d. International Cooperation<br />
&#8211; Global Best Practices:<br />
  &#8211; Information Sharing: Engage with international aviation authorities to align policies and share lessons learned.<br />
&#8211; Cross-Border Operations:<br />
  &#8211; Harmonized Regulations: Facilitate international drone operations by harmonizing standards where possible.</p>
<p> 7. Conclusion</p>
<p>The CAA&#8217;s initiative to introduce the concept of Atypical Air Environment for BVLOS operations is a progressive step towards integrating UAS into the national airspace. However, without careful consideration and amendments, the policy may inadvertently stifle innovation and impose undue burdens on operators.<br />
By clarifying definitions, scaling operational requirements appropriately, streamlining processes, and codifying necessary elements into law, the CAA can foster a regulatory environment that promotes both safety and innovation. Collaboration with industry stakeholders, legal experts, and technology providers will be crucial in refining the policy to achieve its intended objectives.</p>
<p>Recommendations Summary:</p>
<p>1. Clarify Definitions: Provide precise legal definitions for AAE and other key terms.<br />
2. Proportional Requirements: Scale operational requirements based on risk assessments.<br />
3. Streamline Processes: Allow multiple sites per application and simplify procedures.<br />
4. Address EC Challenges: Ensure equipment availability and simplify licensing.<br />
5. Flexibility in Mitigations: Permit alternative safety solutions and avoid prescriptive technologies.<br />
6. Stakeholder Engagement: Enhance consultation and provide guidance resources.<br />
7. Align Standards: Develop UK-specific technical standards and harmonise internationally.<br />
8. Legal Codification: Incorporate essential policy elements into law for enforceability.<br />
9. Balance Safety and Innovation: Maintain safety without hindering technological progress.<br />
10. Protect Data Privacy: Establish clear data handling and confidentiality policies.<br />
By implementing these recommendations, the CAA can create a robust regulatory framework that ensures safety while encouraging the growth and innovation of the UK&#8217;s drone industry.</p>
<p> 8. Comparison with EASA PDRA03 and Lessons for the UK<br />
Comparing the CAA&#8217;s position with the European Union Aviation Safety Agency&#8217;s (EASA) Pre-Defined Risk Assessment number 03 (PDRA03) reveals both opportunities and challenges for UK drone regulation. EASA&#8217;s PDRA03 offers a structured, risk-based framework that allows operators to self-declare compliance with specific conditions, reducing administrative burdens and accelerating operational approvals. This approach supports drone operators by providing clear guidelines while fostering innovation through flexibility in operations such as autonomous flights, multi-UAV control, and operations beyond visual line of sight (BVLOS) under certain conditions. In contrast, the CAA&#8217;s policy concept imposes more prescriptive requirements, such as mandatory NOTAM submissions for each operation and specific technical equipment like ADS-B transceivers, which may be unnecessary and bureaucratic for certain low-risk operations. The UK drone industry could benefit from adopting elements of the EASA PDRA03 by implementing a more proportionate, risk-based regulatory framework that emphasises operator declarations and standardised procedures. This would streamline the approval process, reduce administrative overheads, and encourage innovation while maintaining safety. Learning from the EU&#8217;s experience, the CAA can enhance its policies to better support the growth of the UK drone industry by embracing flexibility, reducing unnecessary bureaucratic requirements, and aligning more closely with international best practices.</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.<br />
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/analysis-and-recommendations-on-cap-3040-first-edition/">Analysis and Recommendations on CAP 3040 | First Edition</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Legal Lessons from the H3 Dynamics Drone Incident: A Wake-Up Call for Drone Pilots</title>
		<link>https://blakistons.co.uk/legal-lessons-from-the-h3-dynamics-drone-incident-a-wake-up-call-for-drone-pilots/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Wed, 06 Nov 2024 12:52:19 +0000</pubDate>
				<category><![CDATA[Air Mobility - Discusses the broader concept of air mobility innovations and regulatory considerations in urban transportation.]]></category>
		<category><![CDATA[and risk prevention for drone operators.]]></category>
		<category><![CDATA[Aviation Incidents - Discusses significant aviation-related events with legal and safety implications.]]></category>
		<category><![CDATA[Case Studies - Provides a real-world incident analysis for educational purposes in drone law and compliance]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Licensing Requirements - Details on licensing and certification needed for drone operation.]]></category>
		<category><![CDATA[Regulatory Compliance - Focuses on the importance of adherence to regulatory guidelines and consequences of violations.]]></category>
		<category><![CDATA[aviation safety]]></category>
		<category><![CDATA[CAAS regulations]]></category>
		<category><![CDATA[Centralised Flight Management System]]></category>
		<category><![CDATA[drone incident]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[drone licensing]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[drone pilot responsibilities]]></category>
		<category><![CDATA[H3 Dynamics]]></category>
		<category><![CDATA[legal implications]]></category>
		<category><![CDATA[operational guidelines]]></category>
		<category><![CDATA[regulatory compliance]]></category>
		<category><![CDATA[Singapore drone rules]]></category>
		<category><![CDATA[TUNDRA 2 drone]]></category>
		<category><![CDATA[unauthorised modifications]]></category>
		<category><![CDATA[unauthorized modifications]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2470</guid>

					<description><![CDATA[<p>Legal Lessons from the H3 Dynamics Drone Incident: A Wake-Up Call for Drone Pilots By Richard Ryan, Drone Lawyer The recent drone crash involving H3 Dynamics in Singapore serves as a stark reminder of the legal responsibilities that come with operating unmanned aircraft systems (UAS). On July 19, H3 Dynamics faced a serious incident when [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/legal-lessons-from-the-h3-dynamics-drone-incident-a-wake-up-call-for-drone-pilots/">Legal Lessons from the H3 Dynamics Drone Incident: A Wake-Up Call for Drone Pilots</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-2471" src="https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots-300x300.png" alt="" width="300" height="300" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots-300x300.png 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots-150x150.png 150w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots-768x768.png 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots-600x600.png 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots-100x100.png 100w, https://blakistons.co.uk/wp-content/uploads/2024/11/Picture2-Legal-Lessons-from-the-H3-Dynamics-Drone-Incident-A-Wake-Up-Call-for-Drone-Pilots.png 789w" sizes="auto, (max-width: 300px) 100vw, 300px" /></p>
<p>Legal Lessons from the H3 Dynamics Drone Incident: A Wake-Up Call for Drone Pilots</p>
<p>By Richard Ryan, Drone Lawyer</p>
<p>The recent drone crash involving H3 Dynamics in Singapore serves as a stark reminder of the legal responsibilities that come with operating unmanned aircraft systems (UAS). On July 19, H3 Dynamics faced a serious incident when their TUNDRA 2 drone lost control shortly after takeoff, crashing into a residential condominium and causing a fire. Although no injuries were reported, the incident has significant legal ramifications for the company and offers crucial lessons for all drone pilots.</p>
<p>Incident Overview<br />
During a series of test flights, the TUNDRA 2 drone—manufactured by Hexadrone but modified by H3 Dynamics—crashed into a building after losing control. The Civil Aviation Authority of Singapore (CAAS) conducted an investigation and uncovered multiple regulatory violations:<br />
1. Non-Compliance with Operations Manual: H3 Dynamics failed to follow procedures outlined in their own operations manual submitted to CAAS.<br />
2. Unauthorised Drone Modification: The drone was modified without prior notification or approval from CAAS.<br />
3. Unlicensed Pilot: The operator lacked a valid Unmanned Aircraft (UA) pilot license.<br />
4. Violation of CFMS Procedures: The company did not adhere to the Centralised Flight Management System protocols designed to monitor and manage drone flight paths.<br />
As a result, CAAS has revoked H3 Dynamics&#8217; permission to conduct flight tests and demonstrations and is proceeding with legal action against the company.</p>
<p>Legal Implications<br />
The incident highlights several legal issues that drone operators must be vigilant about:<br />
&#8211; Regulatory Compliance: Adhering to aviation regulations is not optional. Non-compliance can lead to legal penalties, including fines, suspension of operating licenses, and criminal charges.<br />
&#8211; Unauthorised Modifications: Altering a drone without regulatory approval can compromise safety and is often illegal. Modifications may affect the drone&#8217;s airworthiness and violate manufacturer specifications.<br />
&#8211; Licensing Requirements: Operating a drone without the necessary certifications is unlawful. Pilots must obtain and maintain valid licenses to ensure they are qualified to handle the aircraft safely.<br />
&#8211; Operational Protocols: Ignoring established procedures, such as those outlined in an operations manual or systems like the CFMS, can lead to accidents and legal consequences.</p>
<p>Key Takeaways for Drone Pilots<br />
1. Strictly Follow Operational Guidelines: Always adhere to the procedures in your operations manual. These guidelines are there to ensure safety and legal compliance.<br />
2. Obtain Necessary Approvals: Before making any modifications to your drone, secure the required approvals from relevant authorities like CAAS.<br />
3. Ensure Proper Licensing: Make sure that all drone operators hold valid and up-to-date licenses. Regularly check for any changes in licensing requirements.<br />
4. Comply with Flight Management Systems: Utilize systems like the CFMS to monitor your drone&#8217;s flight path and promptly address any deviations.<br />
5. Stay Informed on Regulations: Laws and regulations governing drone operations can change. Keep yourself updated to ensure ongoing compliance.</p>
<p>Conclusion<br />
The H3 Dynamics incident is a cautionary tale underscoring the importance of legal compliance in drone operations. As drone technology advances and becomes more integrated into various industries, operators must prioritise safety and adhere strictly to all regulatory requirements. Failure to do so not only endangers public safety but also exposes operators to severe legal consequences.</p>
<p>For professional advice on navigating the complexities of drone law, feel free to contact Blakiston’s Chambers. We specialise in helping drone pilots and companies comply with all legal and regulatory obligations.</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.<br />
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-lessons-from-the-h3-dynamics-drone-incident-a-wake-up-call-for-drone-pilots/">Legal Lessons from the H3 Dynamics Drone Incident: A Wake-Up Call for Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
