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

<channel>
	<title>UK Aviation Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/uk-aviation/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/uk-aviation/</link>
	<description>Drone Law</description>
	<lastBuildDate>Thu, 11 Jun 2026 17:44:48 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots</title>
		<link>https://blakistons.co.uk/uk-drone-rules-from-1-january-2026-a-lawyers-practical-guide-for-pilots/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 11 Jun 2026 17:44:48 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[A1 category drones]]></category>
		<category><![CDATA[A2 CofC]]></category>
		<category><![CDATA[A3 category drones]]></category>
		<category><![CDATA[Air Navigation Order 2016]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA drone rules]]></category>
		<category><![CDATA[CAA regulations]]></category>
		<category><![CDATA[commercial drone operations]]></category>
		<category><![CDATA[drone airspace restrictions]]></category>
		<category><![CDATA[Drone Code]]></category>
		<category><![CDATA[drone compliance UK]]></category>
		<category><![CDATA[drone law UK]]></category>
		<category><![CDATA[Drone Lawyer]]></category>
		<category><![CDATA[drone legal advice]]></category>
		<category><![CDATA[drone registration UK]]></category>
		<category><![CDATA[drone regulations 2026]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[Flight Restriction Zones]]></category>
		<category><![CDATA[FPV drones UK]]></category>
		<category><![CDATA[FRZ drone rules]]></category>
		<category><![CDATA[recreational drone flying]]></category>
		<category><![CDATA[Remote ID UK]]></category>
		<category><![CDATA[UK drone pilots]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[UK drone rules]]></category>
		<category><![CDATA[Unmanned Aircraft Systems]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[Visual Line of Sight]]></category>
		<category><![CDATA[VLOS drones]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2685</guid>

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

					<description><![CDATA[<p>&#8220;`By Richard Ryan, barrister and drone lawyer What the paper actually shows (evidence you can cite) Insurers say risk is intrinsically low; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11) UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it has delayed [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/">Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img fetchpriority="high" decoding="async" src="https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-300x300.png" alt="" width="300" height="300" class="alignnone size-medium wp-image-2601" srcset="https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-300x300.png 300w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-150x150.png 150w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-768x768.png 768w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-600x600.png 600w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025-100x100.png 100w, https://blakistons.co.uk/wp-content/uploads/2025/10/251027_PWC-report-2025.png 1024w" sizes="(max-width: 300px) 100vw, 300px" />&#8220;`By Richard Ryan, barrister and drone lawyer</p>
<article>
<section>
<h2>What the paper actually shows (evidence you can cite)</h2>
<ul>
<li><strong>Insurers say risk is intrinsically low</strong>; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11)</li>
<li><strong>UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies</strong> than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it <strong>has delayed progress</strong>. (pp. 12–13)</li>
<li><strong>Net-risk lens:</strong> drones <strong>remove</strong> more risk than they introduce (e.g., falls from height, confined spaces, helicopter exposure). (pp. 14–18)</li>
<li><strong>BVLOS doesn’t materially increase risk</strong> where well-managed; biggest predictors are location and safety management. (pp. 10–11, 19–22)</li>
<li><strong>Incident data 2022–24:</strong> commercial operations show <strong>zero fatalities</strong> across UK, US, EU, Canada, Singapore; only a handful of serious injuries. (Appendix + country sections, pp. 55–61)</li>
<li><strong>SORA friction/cost:</strong> UK SORA application at SAIL II is <strong>£3,495</strong>; mitigations/AMC still qualitative ? “OSC-style” uncertainty persists. (p. 35)</li>
<li><strong>“Picking winners”:</strong> five BVLOS priorities (emergency response, powerlines, maritime SAR, rail, crop spraying). (pp. 6, 25–33)</li>
<li><strong>Policy levers:</strong> shift to <strong>digital PDRAs</strong> for repeatable, low-risk scenarios; reuse prior approvals; model on EU PDRAs/Canada’s lower-risk BVLOS. (pp. 36–37; Appendix 1)</li>
<li><strong>Emergency services gap:</strong> the old standing exemption (E4506) lapsed; routine BVLOS now hard to get—BTP resorted to <strong>State Aircraft</strong> rules. (p. 27)</li>
<li><strong>Comparative table</strong> (risk models, UTM status, Remote ID, scale-up reality) explains why the UK feels “high-friction”. (p. 52)</li>
</ul>
</section>
<section>
<h2>Regulatory &amp; enforcement issues to flag (and build matters around)</h2>
<ol>
<li><strong>Incoherent risk calibration:</strong> the UK treats many Specific-category ops as high-risk despite cross-market low incident severity and strong insurer data. (pp. 9–13, 55–57)</li>
<li><strong>Process opacity &amp; cost-burden:</strong> SORA mitigations/AMC are qualitative ? inconsistent asks; <strong>high fees</strong> despite narrow temporal/spatial grants. (p. 35)</li>
<li><strong>Emergency-services capability gap:</strong> loss of E4506 creates avoidable delay/risk; forces <strong>work-arounds</strong> (State Aircraft) rather than transparent PDRA. (p. 27)</li>
<li><strong>AAE not yet a permissioning tool:</strong> policy concept ? scalable authorisation path (contrast EU PDRA-G03 for linear infrastructure). (pp. 28–31, 36)</li>
<li><strong>Net-risk inversions:</strong> requirements like “observer in a boat” for coastal EVLOS can <strong>increase</strong> system risk and cost vs. sensor-driven shore control. (p. 21)</li>
<li><strong>Data transparency:</strong> the UK has many “record-only” entries; EU public access is patchy; hard for operators/insurers to benchmark safety cases publicly. (pp. 54–61)</li>
</ol>
</section>
<section>
<h2>Practical exposure points for stakeholders</h2>
<ul>
<li><strong>Insurers:</strong> common declinature trip-wires—ops outside the authorisation envelope; poor log preservation; weak maintenance/firmware governance. (pp. 9–11, 35–36)</li>
<li><strong>Operators/pilots:</strong> SORA drift, local land-use limitations, and fragmented permissions across linear corridors; evidence-pack discipline needed. (pp. 28–31, 35–36, 56–57)</li>
<li><strong>Associations/community:</strong> need bilingual templates/FAQs and incident learning loops; emphasise the <strong>airspace vs land-use</strong> distinction to reduce friction. (inferred)</li>
<li><strong>Public bodies (blue-light, MCA, NR, utilities):</strong> proven benefits blocked by bespoke approvals—strong case for <strong>sector PDRA playbooks</strong>. (pp. 26–33, 36)</li>
</ul>
</section>
<p>  <!-- NOTE: The previous section titled “Where you can add legal value (service lines you can sell now)” has been intentionally removed and will be addressed separately as part of practice growth content. --></p>
<section>
<h2>What this means for drone pilots, operators, and companies</h2>
<p>As a drone lawyer, my reading of the PwC paper is that the safety record increasingly supports <strong>predictable, rules-based authorisations</strong>, but the UK still applies bespoke processes that create delay, cost and legal uncertainty. The winners will be those who treat compliance as an operational capability, not a paperwork chore.</p>
<h3>Implications for Drone Pilots</h3>
<ul>
<li><strong>Documentation is defence:</strong> retain native telemetry, app/controller logs, and pre-flight risk assessments. These are crucial in insurer claims and any CAA inquiry.</li>
<li><strong>VLOS/BVLOS discipline:</strong> be explicit about how VLOS was maintained (or the BVLOS mitigations used). Ambiguity here is a common enforcement and insurance pain point.</li>
<li><strong>Privacy on site:</strong> where people are identifiable, prepare a simple lawful-basis note and signage plan; it reduces complaint/escalation risk significantly.</li>
</ul>
<h3>Implications for Operators</h3>
<ul>
<li><strong>Align your OA/ops manual with SORA and AAE logic:</strong> show how mitigations reduce <em>both</em> air and ground risk. Clear mapping cuts questions and accelerates approvals.</li>
<li><strong>Design for repeatability:</strong> build PDRA-ready evidence packs for your most common jobs (e.g., rail/powerline corridors) so each new mission is a variation, not a reinvention.</li>
<li><strong>Insurance resilience:</strong> standardise maintenance/firmware baselines and battery care logs; many declinatures stem from gaps here, not from the incident itself.</li>
<li><strong>Contracts that reflect reality:</strong> flowing down responsibilities to subcontractors (airworthiness, data protection, incident reporting) reduces exposure and smooths procurement.</li>
</ul>
<h3>Implications for Drone Companies &amp; Enterprise Users</h3>
<ul>
<li><strong>Board-level accountability:</strong> appoint a named senior responsible owner (SRO) for UAS operations with decision logs—critical if decisions are later examined in court or by regulators.</li>
<li><strong>Data governance as an asset:</strong> implement DPIAs where warranted, role-based access to imagery, retention/deletion schedules, and breach protocols. This increases tender scores and reduces enforcement risk.</li>
<li><strong>Public value narrative:</strong> quantify how drone tasks remove traditional risks (work at height, road possessions, helicopter hours). This “net-risk” case supports proportional, scalable permissions.</li>
</ul>
<h3>Where legal support helps, assists, and mitigates</h3>
<ul>
<li><strong>Approvals &amp; permissions:</strong> structuring SORA/AAE applications with proportional mitigations, re-using prior evidence, and narrowing scope to reduce fees and conditions.</li>
<li><strong>Policy &amp; appeals:</strong> challenging irrational or net-risk-increasing conditions; seeking clarifications; and preparing proportionate alternatives that the regulator can accept.</li>
<li><strong>Privacy &amp; data:</strong> lawful-basis memos, DPIAs, signage/LLN templates, and response playbooks for complaints or subject access requests.</li>
<li><strong>Insurance &amp; claims:</strong> coverage mapping, notification strategy, and evidence preservation to avoid declinature; subrogation prospects where third parties contributed to loss.</li>
<li><strong>Contracts:</strong> allocating risk cleanly across clients, operators and subcontractors (indemnities, limitation, IP/data ownership, incident reporting).</li>
</ul>
<p><em>Bottom line:</em> the sector is safe and maturing. Those who can <strong>demonstrate</strong> their risk controls, <strong>evidence</strong> compliance, and <strong>standardise</strong> approvals will grow fastest—with fewer legal shocks along the way.</p>
</section>
<section>
<h2>Talking points for meetings &amp; panels</h2>
<ul>
<li><strong>Same safety, slower UK growth:</strong> insurers and incident data show low intrinsic risk—authorisations should be <strong>predictable and prescriptive</strong>, not bespoke. (pp. 9–13, 36–37)</li>
<li><strong>Digital PDRAs now:</strong> for repeatable BVLOS (powerlines/rail/SAR/maritime/agri)—reuse evidence from prior OSCs; mirror EU PDRA/Canada logic. (pp. 25–33, 36)</li>
<li><strong>Emergency drones need an emergency rulebook:</strong> the E4506 gap is pushing forces into State Aircraft work-arounds. (p. 27)</li>
<li><strong>Incident reality:</strong> zero fatalities in 2022–24 across major markets; claims are mainly minor property/equipment—calibrate conditions accordingly. (pp. 55–61; pp. 9–11)</li>
</ul>
</section>
<hr />
<footer>
<section>
<h2>About the Author</h2>
<p><strong>Richard Ryan</strong> is a Barrister (Direct Access), Mediator and Chartered Arbitrator based in the UK, specialising in drone and counter-drone law, aviation regulation, and complex commercial disputes. He advises operators, insurers and public bodies on SORA/AAE approvals, BVLOS programmes, privacy/data governance, and risk allocation across the drone ecosystem.</p>
<p><em></em></p>
</section>
</footer>
</article>
<p>&#8220;`</p>
<p>The post <a href="https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/">Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports</title>
		<link>https://blakistons.co.uk/when-just-a-minute-becomes-bvlos-legal-lessons-for-drone-operators-from-chirps-september-2025-reports/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 27 Oct 2025 19:14:43 +0000</pubDate>
				<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Aviation Technology]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Case Studies - Provides a real-world incident analysis for educational purposes in drone law and compliance]]></category>
		<category><![CDATA[Civil Aviation]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Drone Accidents & Case Studies]]></category>
		<category><![CDATA[Drone Incidents]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Industry Concerns]]></category>
		<category><![CDATA[Drone Industry News]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Future of Drone Regulations]]></category>
		<category><![CDATA[Government Reports]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[UK Aviation Law]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK drone policy]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Urban Air Mobility]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[UTM (Unmanned Aircraft System Traffic Management)]]></category>
		<category><![CDATA[ANO 2016 Article 241]]></category>
		<category><![CDATA[battery settings]]></category>
		<category><![CDATA[BMFA]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CHIRP]]></category>
		<category><![CDATA[crowds]]></category>
		<category><![CDATA[DJI]]></category>
		<category><![CDATA[Drone and Model Aircraft Code]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[event safety]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[Mavic 4 Pro]]></category>
		<category><![CDATA[Mini 2]]></category>
		<category><![CDATA[Nottingham Carnival]]></category>
		<category><![CDATA[operations manual]]></category>
		<category><![CDATA[Operator ID]]></category>
		<category><![CDATA[powerlines]]></category>
		<category><![CDATA[RC2 controller]]></category>
		<category><![CDATA[Return to Home]]></category>
		<category><![CDATA[RTH altitude]]></category>
		<category><![CDATA[screen recording]]></category>
		<category><![CDATA[SWEETS]]></category>
		<category><![CDATA[UK CAA]]></category>
		<category><![CDATA[visual observer]]></category>
		<category><![CDATA[VLOS]]></category>
		<category><![CDATA[waypoint missions]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2590</guid>

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

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

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

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