<?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>Emerging Technologies Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/emerging-technologies/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/emerging-technologies/</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=7.0.1</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>Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK</title>
		<link>https://blakistons.co.uk/development-and-regulation-of-civil-drones-lessons-from-switzerland-and-recommendations-for-the-uk/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Tue, 04 Feb 2025 12:40:07 +0000</pubDate>
				<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Emerging Technologies]]></category>
		<category><![CDATA[eVTOL]]></category>
		<category><![CDATA[Swiss Law]]></category>
		<category><![CDATA[U-Space]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[CAA]]></category>
		<category><![CDATA[Drone Infrastructure]]></category>
		<category><![CDATA[Drone Noise]]></category>
		<category><![CDATA[Drone Privacy]]></category>
		<category><![CDATA[Drone Sustainability]]></category>
		<category><![CDATA[FOCA]]></category>
		<category><![CDATA[Swiss Drone Regulations]]></category>
		<category><![CDATA[UK Drone Laws]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2547</guid>

					<description><![CDATA[<p>Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK By Richard Ryan, Drone Lawyer Introduction Switzerland has emerged as a leading hub for drone innovation, in large part due to forward-looking policies and the seamless integration of unmanned aircraft into its broader aviation ecosystem. Although the UK has already adopted [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/development-and-regulation-of-civil-drones-lessons-from-switzerland-and-recommendations-for-the-uk/">Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK</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/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image-300x171.webp" alt="" width="300" height="171" class="alignnone size-medium wp-image-2548" srcset="https://blakistons.co.uk/wp-content/uploads/2025/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image-300x171.webp 300w, https://blakistons.co.uk/wp-content/uploads/2025/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image-1024x585.webp 1024w, https://blakistons.co.uk/wp-content/uploads/2025/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image-768x439.webp 768w, https://blakistons.co.uk/wp-content/uploads/2025/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image-1536x878.webp 1536w, https://blakistons.co.uk/wp-content/uploads/2025/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image-600x343.webp 600w, https://blakistons.co.uk/wp-content/uploads/2025/02/250204_Development-and-Regulation-of-Civil-Drones-Lessons-from-Switzerland-and-Recommendations-for-the-UK_image.webp 1792w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK<br />
By Richard Ryan, Drone Lawyer</strong></p>
<p><strong>Introduction</strong><br />
Switzerland has emerged as a leading hub for drone innovation, in large part due to forward-looking policies and the seamless integration of unmanned aircraft into its broader aviation ecosystem. Although the UK has already adopted a risk-based regulatory framework for drones, lessons from the Swiss and European Union Aviation Safety Agency (EASA) experience could further advance the UK’s domestic industry.<br />
This article compares Swiss and UK drone regulations, with a view to determining whether a more comprehensive legislative revision—drawing on Swiss and EASA best practices—could enhance safety, innovation, and public acceptance in the UK.</p>
<p><strong>1. Background and Goals</strong></p>
<p>1.1. Switzerland’s Drone Ecosystem<br />
Switzerland’s success in fostering a dynamic civil drone industry rests on the following pillars:<br />
1.	Risk-Based Regulatory Model<br />
Switzerland follows the three-category approach (Open, Specific, and Certified) as set out in the core EU regulations (Regulation (EU) 2019/947 and Regulation (EU) 2019/945), which it adopts under its bilateral air transport agreements with the EU.<br />
2.	Close Collaboration<br />
Federal agencies (e.g., the Federal Office of Civil Aviation, FOCA), industry, and research institutions routinely coordinate to address regulatory and technological developments.<br />
3.	Strong International Ties<br />
As a signatory to multiple bilateral and multilateral agreements (including the Agreement between the EU and the Swiss Confederation on Air Transport), Switzerland ensures legal certainty and alignment with global safety standards.</p>
<p>1.2. The UK Context<br />
The UK also employs a risk-based framework, primarily structured by:<br />
•	The Air Navigation Order 2016 (ANO), as amended<br />
•	Civil Aviation Authority (CAA) publications, including CAP 722, which provides operational guidance for unmanned aircraft.<br />
Although the UK’s regulations are already comprehensive, there is scope to streamline approval processes, bolster public confidence, and prepare for emerging drone technologies. Swiss and broader EASA approaches—particularly in the realm of U-Space services—offer potentially valuable lessons.</p>
<p><strong>2. Swiss Legal Framework</strong></p>
<p>2.1. Adoption of EU Drone Regulations<br />
Under Swiss law, drones are governed by EU regulations (Regulations (EU) 2019/947 and 2019/945) through Switzerland’s bilateral air transport agreements with the EU. In practice, FOCA enacts these rules at the national level, sometimes incorporating local adaptations based on Swiss administrative structures.<br />
2.1.1. Drone Categories<br />
1.	Open (low risk)<br />
o	Operations with minimal restrictions if the drone meets specific technical requirements (e.g., weight, speed, altitude limits) and usage conditions.<br />
2.	Specific (medium to high risk)<br />
o	Requires more rigorous operational authorisations and safety risk assessments.<br />
3.	Certified (highest risk)<br />
o	Applies to complex or large-scale operations, including cargo and passenger transport (e.g., eVTOL aircraft), though these frameworks are still evolving.<br />
2.1.2. Integration with Traditional Aviation<br />
•	Coordination Through Skyguide: Switzerland’s air navigation service provider, Skyguide, is tasked with managing both manned and unmanned traffic. This seamless integration aims to promote safety and efficiency in shared airspace.<br />
•	National Emphasis on Collaboration: Swiss authorities maintain regular consultation with industry, research, and cantonal authorities to adapt regulations swiftly.<br />
Relevance for the UK<br />
•	Risk Categorisation: The UK already uses a three-tier classification (Open, Specific, Certified), mirroring the Swiss/EASA approach.<br />
•	Approval Process: Automating and digitising authorisations—an area where Switzerland and Skyguide have been especially proactive—may help reduce administrative burdens for UK operators.</p>
<p><strong>3. U-Space Infrastructure and Multiple Service Providers</strong></p>
<p>3.1. What Is U-Space?<br />
U-Space is a digital ecosystem designed to manage drone traffic autonomously or semi-autonomously. It includes network identification, flight authorisation services, and real-time data exchange among airspace users.</p>
<p>3.2. Switzerland’s U-Space Approach<br />
•	Multiple U-Space Service Providers (USSPs):<br />
Switzerland aims to license several private or public providers within the same geographical area, fostering competition and innovation in drone traffic management.<br />
•	Key Features:<br />
1.	Network Identification: Ensures authorities (and possibly the public) can identify drones operating in U-Space airspace.<br />
2.	Automated Flight Authorisation: Minimises manual checks by aviation authorities.<br />
3.	Real-Time Data Exchange: Coordinates positions and flight plans among manned aircraft, unmanned aircraft, and air traffic control.</p>
<p>3.3. Implementation Timelines<br />
•	By 2025: Switzerland has signalled its intent to launch initial U-Space operations in regions including Zurich. [1]<br />
•	By 2030: Widespread U-Space maturity is anticipated across Europe, though this is an industry projection rather than a formal deadline.<br />
Relevance for the UK<br />
•	Competition and Choice: Licensing multiple USSPs could provide UK operators with varying price points and service levels, driving innovation.<br />
•	Incremental Roll-Out: Concentrating U-Space in high-traffic urban areas first (London, Manchester, etc.) may mirror Zurich’s approach.<br />
•	Legal and Technological Foundation: Adapting the EU’s Implementing Regulation (EU) 2021/664 for U-Space to the UK’s post-Brexit landscape could maintain interoperability with European markets.</p>
<p><strong>4. Noise Protection Measures</strong></p>
<p>4.1. Swiss Perspective<br />
Swiss authorities acknowledge that drone noise—while generally quieter than conventional aircraft—can be disruptive in residential or rural areas. Ongoing efforts include:<br />
•	Collaborating with EASA and ICAO working groups to develop drone-specific noise measurement standards.<br />
•	Encouraging technological innovations (e.g., quieter propellers, electric propulsion).<br />
•	Using geo-awareness tools to route flights around noise-sensitive areas.</p>
<p>4.2. Relevance for the UK<br />
•	Comprehensive Noise Mapping: Incorporating drone flight paths into local noise maps could help councils and the CAA manage public disturbances.<br />
•	Research and Design: Funding drone acoustics research could ensure any future noise regulations are evidence-based.<br />
•	Aligning Standards: Remaining aligned with emerging international noise standards could ease cross-border drone operations and manufacturing.</p>
<p><strong>5. Privacy and Public Acceptance</strong></p>
<p>5.1. Swiss Measures<br />
•	Mandatory Registration: Most drone operators must register and display their registration number, subject to weight and operational criteria.<br />
•	Remote Identification: Allows law enforcement and authorities to identify drones in real time, enhancing accountability.<br />
•	Geofencing and Flight Restriction Zones: Critical infrastructure or sensitive sites often have automated restrictions to prevent overflights.</p>
<p>5.2. Relevance for the UK<br />
•	Building Public Trust: The UK’s existing registration regime (for drones ?250g) could be coupled with more transparent robust remote ID requirements.<br />
•	Enforcement and Complaint Handling: Close coordination with local police and councils may expedite response times to drone-related incidents.<br />
•	Regulatory Consistency: Ensuring geofencing data is accurate and accessible will be crucial as drone usage scales up.</p>
<p><strong>6. Spatial Planning and Infrastructure</strong></p>
<p>6.1. Current Swiss Policy<br />
•	Different Treatment vs. Conventional Aviation: Small drone operations typically require minimal infrastructure and thus face limited planning procedures.<br />
•	“Intensive Use” Threshold: FOCA guidelines suggest that where a single site exceeds a certain number of flights (sometimes cited as over 1200 flights per year), formal land-use planning and environmental assessment may be triggered. However, application may vary depending on local (cantonal) regulations.</p>
<p>6.2. Future Vertiports<br />
Swiss authorities anticipate the need for dedicated vertiports or droneports if large passenger/cargo eVTOLs become more commonplace. These facilities would require integration into national transport and aviation infrastructure plans.</p>
<p>6.3. Relevance for the UK<br />
•	Planning Approvals: The UK might consider more streamlined pathways for drone infrastructure, acknowledging that small drone operations have lower impact than full-scale airport developments.<br />
•	Emerging eVTOLs: A forward-looking approach—coordinated among the Department for Transport, local councils, and industry—could accommodate vertiport networks in urban hubs.<br />
•	Local Variations: Like Switzerland, the UK may allow local authorities discretion in how to apply thresholds for “intensive use,” but national guidance would help maintain consistency.</p>
<p><strong>7. Environmental Sustainability</strong></p>
<p>7.1. Potential Emissions Reductions<br />
•	Replacing Conventional Aircraft: Small drones can potentially replace helicopters for tasks like aerial surveys, agricultural spraying, or urgent deliveries, leading to immediate fuel and emissions savings.<br />
•	Lifecycle Analyses: Comprehensive studies are still limited, so definitive data on net environmental impact remains inconclusive.</p>
<p>7.2. Relevance for the UK<br />
•	Targeted Incentives: Encouraging drone use in sectors where carbon-intensive operations are widespread (e.g., logistics, agriculture, medical supply chains) could yield environmental benefits.<br />
•	Data Collection: Collaborating with academia and industry to produce rigorous lifecycle analyses would strengthen policy decisions.</p>
<p><strong>8. Should the UK Revise Its Complex Legislation?</strong></p>
<p>Given Switzerland’s experience and the growing demands of the UK drone sector, there is a robust case for a holistic review of UK drone regulations. Although the current framework—anchored in the Air Navigation Order 2016 and supplemented by CAP 722—is risk-based, integrating the best practices from Swiss and EASA models could amplify innovation and public trust.</p>
<p>8.1. Harmonising with EASA<br />
•	Voluntary Alignment: While the UK is no longer bound by EASA regulations post-Brexit, aligning technical and operational standards can facilitate cross-border operations and exports.<br />
•	Regulatory Autonomy: The UK can selectively adopt or adapt EASA rules that best serve its domestic market.</p>
<p>8.2. Streamlining Authorisations and Planning<br />
•	Digital Transformation: Emulating Switzerland’s push for automated approvals could reduce administrative burdens for operators in the UK.<br />
•	Consistent Local Guidance: As drones become integral to city services, local authorities should follow uniform guidelines on planning consent.</p>
<p>8.3. Fostering Public Trust<br />
•	Noise and Privacy Protections: Enhanced noise mapping, remote ID, and geofencing can address some of the most common community concerns.<br />
•	Robust Enforcement: Clear lines of responsibility between the CAA, local councils, and law enforcement agencies will be key.</p>
<p><strong>Conclusion</strong></p>
<p>Switzerland’s structured yet adaptive approach—emphasising competitive U-Space services, data-driven noise mitigation, robust privacy measures, and collaborative policymaking—offers valuable lessons for the UK. Despite a well-established risk-based framework, the UK could benefit from a more comprehensive review that incorporates Swiss successes and maintains compatibility with EASA standards where beneficial.<br />
By welcoming multiple U-Space Service Providers, digitising authorisations, and preparing for future vertiport infrastructure, the UK can remain at the forefront of drone technology. A more cohesive and modernised legal framework, coupled with effective enforcement and public engagement, will lay the foundation for a thriving, responsible, and future-ready UK drone sector.</p>
<p><strong>Author Bio: Richard Ryan</strong><br />
Richard Ryan is an experienced direct access barrister who has advised on drone regulations and airspace policy in both the UK and internationally. With a career spanning public and private sectors, he provides counsel on emerging areas of aviation law—from U-Space development to eVTOL certification. Richard regularly collaborates with industry associations, regulatory bodies, and academic institutions to help shape the future of safe and sustainable unmanned aircraft operations.</p>
<p><strong>References and Further Reading</strong><br />
1.	Swiss Federal Office of Civil Aviation (FOCA) – Drones and Models: https://www.bazl.admin.ch/bazl/en/home/good-to-know/drones-and-aircraft-models.html<br />
2.	Skyguide – Drones: https://www.skyguide.ch/en/company/corporate-topics/drones/<br />
3.	EU Drone Regulations (EU) 2019/947 &#038; 2019/945: EUR-Lex<br />
4.	Implementing Regulation (EU) 2021/664 – U-Space: EUR-Lex<br />
5.	UK Air Navigation Order 2016: Legislation.gov.uk<br />
6.	CAA – CAP 722: https://publicapps.caa.co.uk/modalapplication.aspx?appid=11&#038;mode=detail&#038;id=415<br />
________________________________________<br />
This article is intended for informational purposes only and does not constitute legal advice. Stakeholders are encouraged to consult the applicable regulations, guidance materials, and professional counsel for specific compliance obligations.</p>
<p>The post <a href="https://blakistons.co.uk/development-and-regulation-of-civil-drones-lessons-from-switzerland-and-recommendations-for-the-uk/">Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
