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

<channel>
	<title>Drone Safety and Operations Archives - Blakistons</title>
	<atom:link href="https://blakistons.co.uk/category/drone-safety-and-operations/feed/" rel="self" type="application/rss+xml" />
	<link>https://blakistons.co.uk/category/drone-safety-and-operations/</link>
	<description>Drone Law</description>
	<lastBuildDate>Mon, 06 Jul 2026 09:42:00 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</title>
		<link>https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 06 Jul 2026 09:42:00 +0000</pubDate>
				<category><![CDATA[AI and Drone Technology]]></category>
		<category><![CDATA[AI Regulation]]></category>
		<category><![CDATA[AI Technology]]></category>
		<category><![CDATA[Airspace Legislation]]></category>
		<category><![CDATA[Airspace Management and UTM Systems]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Autonomous Systems]]></category>
		<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[BVLOS Operations]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA) Policies]]></category>
		<category><![CDATA[Counter-Drone Technology]]></category>
		<category><![CDATA[Defence]]></category>
		<category><![CDATA[Defence Procurement]]></category>
		<category><![CDATA[Defence Technology]]></category>
		<category><![CDATA[Defense Innovation]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[EU AI Act Compliance]]></category>
		<category><![CDATA[EU Regulations and Compliance]]></category>
		<category><![CDATA[International Drone Policies]]></category>
		<category><![CDATA[International Drone Regulations]]></category>
		<category><![CDATA[Legal Analysis and Recommendations]]></category>
		<category><![CDATA[Military Law]]></category>
		<category><![CDATA[Military Procurement]]></category>
		<category><![CDATA[Military Technology]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Regulations and Compliance]]></category>
		<category><![CDATA[Regulatory and Legal Compliance]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Regulatory Oversight]]></category>
		<category><![CDATA[Technology and Warfare]]></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 Defence Policy]]></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[Uncategorised]]></category>
		<category><![CDATA[Unmanned Aerial Vehicles (UAV)]]></category>
		<category><![CDATA[Unmanned Aircraft Regulations]]></category>
		<category><![CDATA[Unmanned Aircraft Systems (UAS)]]></category>
		<category><![CDATA[Aerospace Law]]></category>
		<category><![CDATA[Airworthiness]]></category>
		<category><![CDATA[Article 36]]></category>
		<category><![CDATA[artificial intelligence]]></category>
		<category><![CDATA[BAE Systems]]></category>
		<category><![CDATA[British Army]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[Callen-Lenz]]></category>
		<category><![CDATA[Counter Drone]]></category>
		<category><![CDATA[counter-UAS]]></category>
		<category><![CDATA[Defence AI]]></category>
		<category><![CDATA[defence technology]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[drone regulation]]></category>
		<category><![CDATA[EU AI Act]]></category>
		<category><![CDATA[Export Controls]]></category>
		<category><![CDATA[Hybrid Navy]]></category>
		<category><![CDATA[Law of Armed Conflict]]></category>
		<category><![CDATA[Maritime Operations]]></category>
		<category><![CDATA[Maritime Security]]></category>
		<category><![CDATA[Military Aviation]]></category>
		<category><![CDATA[military drones]]></category>
		<category><![CDATA[Military Innovation]]></category>
		<category><![CDATA[NATO]]></category>
		<category><![CDATA[Naval Aviation]]></category>
		<category><![CDATA[Nyan]]></category>
		<category><![CDATA[One-Way Effectors]]></category>
		<category><![CDATA[Project Vantage]]></category>
		<category><![CDATA[Royal Navy]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UAV]]></category>
		<category><![CDATA[UK AI]]></category>
		<category><![CDATA[UK defence]]></category>
		<category><![CDATA[Uncrewed Aircraft Systems]]></category>
		<category><![CDATA[Weapons Review]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2698</guid>

					<description><![CDATA[<p>Drone Law &#124; Counter-UAS &#124; Defence AI &#124; One-Way Effectors Summary: The Royal Navy’s launch of the British-built Nyan One-Way Effector from XV Patrick Blackett is more than a drone trial. It is a legal and operational marker in the UK’s transition towards a Hybrid Navy, raising issues of targeting law, weapons review, military airworthiness, [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/">Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="drone-law-blog">
<p><strong>Drone Law | Counter-UAS | Defence AI | One-Way Effectors</strong></p>
<p><strong>Summary:</strong> The Royal Navy’s launch of the British-built Nyan One-Way Effector from XV Patrick Blackett is more than a drone trial. It is a legal and operational marker in the UK’s transition towards a Hybrid Navy, raising issues of targeting law, weapons review, military airworthiness, counter-UAS defence, export controls and AI governance.</p>
<h2>1. Why the Nyan Trial Matters</h2>
<p>The Royal Navy and British Army have tested the Nyan One-Way Effector, designed and built by BAE Systems’ Callen-Lenz, for both maritime and land operations. The system has a 2.9-metre wingspan and is designed to provide a precision strike capability. It has now been launched from the Royal Navy’s experimentation ship XV Patrick Blackett as part of Project Vantage, the programme focused on accelerating maritime one-way effector capability.</p>
<p>Legally, the phrase “one-way effector” should not distract from the underlying classification problem. Nyan may simultaneously be an aircraft, a military UAS, a weapon system, a munition, a software-enabled targeting platform and an export-controlled defence article. Each classification carries its own compliance burden.</p>
<h2>2. From Drone Novelty to Combat Mass</h2>
<p>The trial reflects the UK’s move towards crewed-uncrewed teaming and the Royal Navy’s Hybrid Navy concept. One-way effectors are intended to provide affordable combat mass, allowing crewed platforms to extend reach, increase tempo and complicate an adversary’s defensive picture.</p>
<p>However, affordability does not dilute legal responsibility. The cheaper and more numerous the weapon, the more frequently it may be used. The more frequently it is used, the more important lawful targeting architecture becomes.</p>
<h2>3. Autonomy: The Legal Question Is What the Machine Decides</h2>
<p>The key legal question is not whether Nyan is a drone, but what functions are automated or autonomous. Autonomy in navigation is not the same as autonomy in target selection. A system may fly itself to a pre-programmed target without being authorised to decide who or what is attacked.</p>
<p>Commanders and lawyers should ask:</p>
<ul>
<li>Does the system merely navigate to a human-selected target?</li>
<li>Does it detect, classify, prioritise or select targets?</li>
<li>Can it be retasked, recalled, aborted or terminated after launch?</li>
<li>What happens if GPS is jammed, spoofed or degraded?</li>
<li>What mission data and operator decisions are recorded?</li>
</ul>
<p>Those questions determine whether the system can be used consistently with distinction, proportionality, precautions in attack and applicable rules of engagement.</p>
<h2>4. Article 36 Weapons Review</h2>
<p>A one-way effector requires a disciplined weapons review. That review should not be limited to the airframe or warhead. It should include the launcher, mission-planning software, navigation system, datalinks, communications architecture, abort logic, cyber resilience, payload effects and integration with intelligence or targeting systems.</p>
<p>The review must also examine foreseeable use cases. Launching from land against a fixed target is materially different from launching from a moving naval platform against a maritime or coastal target. The latter introduces neutral shipping, civilian infrastructure, allied aircraft, electromagnetic interference, airspace deconfliction and more complex proportionality assessments.</p>
<h2>5. EU AI Act and UK AI Standards</h2>
<p>The EU AI Act generally excludes AI systems used exclusively for military, defence or national-security purposes. However, its high-risk AI standards remain useful benchmarks for dual-use suppliers, defence contractors, procurement assurance and civilian spin-outs.</p>
<p>The UK does not currently have a single equivalent “UK AI Act”. Instead, the UK uses a sector-led, principles-based model. In defence, this is supplemented by Ministry of Defence AI principles, including human-centricity, responsibility, understanding, bias and harm mitigation, and reliability.</p>
<table style="border-collapse: collapse; width: 100%; margin: 20px 0;">
<thead>
<tr>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Governance Area</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">EU AI Act Benchmark</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">UK / MOD Equivalent</th>
<th style="border: 1px solid #000; padding: 8px; text-align: left;">Application to One-Way Effectors</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Lifecycle risk management</td>
<td style="border: 1px solid #000; padding: 8px;">Safety, security and robustness</td>
<td style="border: 1px solid #000; padding: 8px;">Hazard logs for navigation failure, lost link, spoofing, target-data error and launch failure.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Technical documentation</td>
<td style="border: 1px solid #000; padding: 8px;">Technical file and system description</td>
<td style="border: 1px solid #000; padding: 8px;">Accountability and governance</td>
<td style="border: 1px solid #000; padding: 8px;">Configuration records for airframe, launcher, software, payload and mission-planning tools.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Record-keeping</td>
<td style="border: 1px solid #000; padding: 8px;">Automatic logging</td>
<td style="border: 1px solid #000; padding: 8px;">Transparency and explainability</td>
<td style="border: 1px solid #000; padding: 8px;">Mission logs, operator decisions, software versions, AI outputs and telemetry retention.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Human oversight</td>
<td style="border: 1px solid #000; padding: 8px;">Human control and intervention</td>
<td style="border: 1px solid #000; padding: 8px;">Human-centricity and responsibility</td>
<td style="border: 1px solid #000; padding: 8px;">Clear authority for launch, retask, abort, termination and post-strike review.</td>
</tr>
<tr>
<td style="border: 1px solid #000; padding: 8px;">Cyber resilience</td>
<td style="border: 1px solid #000; padding: 8px;">Accuracy, robustness and cybersecurity</td>
<td style="border: 1px solid #000; padding: 8px;">Reliability and security</td>
<td style="border: 1px solid #000; padding: 8px;">Testing against jamming, spoofing, adversarial inputs, cyber compromise and degraded environments.</td>
</tr>
</tbody>
</table>
<h2>6. Maritime Launch Changes the Legal Burden</h2>
<p>Launching from a ship is materially different from launching from a land range. The platform is moving. Weather and sea state affect launch reliability. The electromagnetic environment may be contested. The operating area may include neutral vessels, civil aircraft, allied aircraft, helicopters, missiles and other uncrewed systems.</p>
<p>The legal architecture must therefore include target validation, positive identification, proportionality analysis, precautions in attack, air and maritime deconfliction, and auditability. The question is not simply whether Nyan can be launched from a ship. The question is whether the Navy can generate a repeatable, auditable and legally defensible kill chain from a ship.</p>
<h2>7. The Counter-UAS Mirror</h2>
<p>Every one-way effector creates a corresponding defence problem. If the UK can launch low-cost precision effectors from ships, adversaries and proxies can attempt similar effects. Counter-UAS law is therefore inseparable from OWE deployment.</p>
<p>Defending ships, ports, airbases and critical infrastructure requires layered capabilities: detection, identification, tracking, electronic warfare, cyber effects, kinetic interceptors, directed energy, decoys, hardening, dispersal and forensic recovery.</p>
<p>In armed conflict, commanders will operate under the law of armed conflict and rules of engagement. In peacetime or grey-zone conditions, counter-drone operations may engage aviation law, communications law, property rights, criminal law, public safety, port security and military aid to civil authorities.</p>
<h2>8. Export Controls and Procurement Risk</h2>
<p>Sovereign manufacture does not remove export-control obligations. Airframes, propulsion systems, launchers, datalinks, payloads, source code, mission-planning tools, technical assistance and software updates may all require careful classification and licensing analysis.</p>
<p>Rapid procurement also creates legal debt if safety cases, software changes, data rights, AI assurance, cyber resilience and operator training are not properly documented. The solution is not to slow innovation, but to embed lawyers, engineers, safety specialists, AI assurance teams and operators into the experimentation cycle from the start.</p>
<h2>9. Bottom Line</h2>
<p>The Nyan sea launch is a significant step towards a British Hybrid Navy. Its real importance lies in the legal system-of-systems problem it exposes. A one-way effector is not merely a drone with a warhead. It moves through air law, weapons law, targeting law, AI governance, export-control law, safety regulation, procurement governance and counter-UAS doctrine.</p>
<p>The future fleet will not be judged only by how many drones it can launch. It will be judged by whether it can launch them lawfully, safely, proportionately, responsibly and at scale.</p>
<hr />
<h2>About the Author</h2>
<p><strong>Richard Ryan</strong> is a barrister, Chartered Arbitrator and specialist in drone law, counter-UAS, defence procurement and AI governance. He advises government, defence and technology organisations on autonomous systems, military aviation, export controls, commercial contracts and regulatory compliance. Richard is also undertaking a PhD at Cranfield University researching the future legal framework for BVLOS operations, autonomous aviation and Unmanned Traffic Management.</p>
<p><em>This article is general legal commentary and does not constitute legal advice.</em></p>
</div>
<p>The post <a href="https://blakistons.co.uk/nyan-at-sea-one-way-effectors-counter-uas-law-and-defence-ai-governance/">Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots</title>
		<link>https://blakistons.co.uk/uk-drone-rules-from-1-january-2026-a-lawyers-practical-guide-for-pilots/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Thu, 11 Jun 2026 17:44:48 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Regulations]]></category>
		<category><![CDATA[CAA guidelines]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA)]]></category>
		<category><![CDATA[Commercial Drone Operations]]></category>
		<category><![CDATA[Drone Industry]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - As the article provides legal insights specific to drone operations]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Legislation]]></category>
		<category><![CDATA[drone operations]]></category>
		<category><![CDATA[Drone Operators]]></category>
		<category><![CDATA[Drone Regulations]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[Drones]]></category>
		<category><![CDATA[Legal Insights]]></category>
		<category><![CDATA[Legal Insights for Drone Industry]]></category>
		<category><![CDATA[UAS (Unmanned Aircraft Systems)]]></category>
		<category><![CDATA[UAS Regulations]]></category>
		<category><![CDATA[UAV Regulations]]></category>
		<category><![CDATA[UAVs]]></category>
		<category><![CDATA[UK Aviation]]></category>
		<category><![CDATA[Uncategorised]]></category>
		<category><![CDATA[A1 category drones]]></category>
		<category><![CDATA[A2 CofC]]></category>
		<category><![CDATA[A3 category drones]]></category>
		<category><![CDATA[Air Navigation Order 2016]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[BVLOS]]></category>
		<category><![CDATA[CAA drone rules]]></category>
		<category><![CDATA[CAA regulations]]></category>
		<category><![CDATA[commercial drone operations]]></category>
		<category><![CDATA[drone airspace restrictions]]></category>
		<category><![CDATA[Drone Code]]></category>
		<category><![CDATA[drone compliance UK]]></category>
		<category><![CDATA[drone law UK]]></category>
		<category><![CDATA[Drone Lawyer]]></category>
		<category><![CDATA[drone legal advice]]></category>
		<category><![CDATA[drone registration UK]]></category>
		<category><![CDATA[drone regulations 2026]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[Flight Restriction Zones]]></category>
		<category><![CDATA[FPV drones UK]]></category>
		<category><![CDATA[FRZ drone rules]]></category>
		<category><![CDATA[recreational drone flying]]></category>
		<category><![CDATA[Remote ID UK]]></category>
		<category><![CDATA[UK drone pilots]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[UK drone rules]]></category>
		<category><![CDATA[Unmanned Aircraft Systems]]></category>
		<category><![CDATA[UTM]]></category>
		<category><![CDATA[Visual Line of Sight]]></category>
		<category><![CDATA[VLOS drones]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2685</guid>

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

					<description><![CDATA[<p>By Richard Ryan, barrister and drone lawyer Constructive outcome, practical lessons. A technical proximity breach was confirmed, a more serious allegation was dismissed, and there are clear takeaways that raise standards on evidence, cooperation and public safety. Outcome at a glance Count 1 (conviction): Operating an unmanned aircraft close to the site of an ongoing [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/">A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><!-- Begin WordPress post content (no H1 included; WordPress will supply the title) --></p>
<p>By Richard Ryan, barrister and drone lawyer</p>
<p><strong>Constructive outcome, practical lessons.</strong> A technical proximity breach was confirmed, a more serious allegation was dismissed, and there are clear takeaways that raise standards on evidence, cooperation and public safety.</p>
<section aria-labelledby="outcome">
<h2 id="outcome">Outcome at a glance</h2>
<ul>
<li><strong>Count 1 (conviction):</strong> Operating an unmanned aircraft close to the site of an ongoing emergency response — <strong>Air Navigation Order 2016</strong> Articles <strong>265B(3)</strong>, <strong>265B(5)(j)</strong> and <strong>265F(3)(c)</strong> (reflecting <strong>UAS.OPEN.060(3)</strong>).</li>
<li><strong>Count 2 (dismissed):</strong> Obstructing or hindering emergency workers — <strong>Emergency Workers (Obstruction) Act 2006</strong>, sections <strong>1</strong> and <strong>4</strong> — no case to answer.</li>
<li><strong>Sentence:</strong> <strong>£300</strong> (reduced from <strong>£2,500</strong>). <strong>Deprivation order refused</strong> — the client’s equipment will be returned.</li>
</ul>
<p></strong>.</p>
</section>
<section aria-labelledby="background">
<h2 id="background">Competence, cooperation and public interest flying</h2>
<p>The client is an experienced operator with hundreds of hours and thousands of flights, combining sound aviation literacy with routine work around public interest incidents. On the day in question, the client used aircraft tracking tools and air band monitoring, maintained a conservative standoff where no formal cordon existed, and landed promptly when requested by police. This was a measured and safety first response in a dynamic setting.</p>
</section>
<section aria-labelledby="lesson-telemetry">
<h2 id="lesson-telemetry">Lesson 1: Telemetry clarity</h2>
<p>When presenting flight data, clarity matters. Plot the flight path with a <strong>thin, precise line</strong> so the <strong>base map remains legible</strong>, including fences, road edges, cordons and measured standoffs. A thick line can obscure the very features that prove separation.</p>
<ul>
<li>Keep a clean thin line map and a forensic overlay with timestamps for take off, orbit points, return to home and landing, plus measured distances to fixed features.</li>
<li>Use a thin line that clearly shows accurate telemetry when placed on a map, not a thick line that obscures part of the map.</li>
</ul>
<p>  <!-- Optional image placeholder:
  

<figure>
    <img decoding="async" src="telemetry-thin-vs-thick.png" alt="Thin flight path line keeps the base map legible; thick line obscures fences, roads and standoffs." loading="lazy" />
    
 
<figcaption>Thin versus thick telemetry overlays (illustrative).</figcaption>
 

  </figure>


  --><br />
</section>
<section aria-labelledby="lesson-dat">
<h2 id="lesson-dat">Lesson 2: Plan for seizure and understand where DJI DAT lives</h2>
<p>High fidelity <strong>DJI DAT</strong> logs are stored on the aircraft and typically require <strong>connecting the drone to a computer</strong> to extract. If a drone is seized by police, immediate access to those DAT files is difficult.</p>
<ul>
<li>Build redundancy: back up app and controller logs after each flight, use screen recordings of the flight user interface, and capture independent stills or video.</li>
<li>For sensitive assignments, consider periodic DAT offloads in advance.</li>
</ul>
</section>
<section aria-labelledby="commitments">
<h2 id="commitments">Five straightforward commitments</h2>
<ol>
<li>Thin line telemetry as the default for mapping outputs.</li>
<li>Evidence resilience: dual path logging (logs plus screen capture) and periodic DAT offloads.</li>
<li>Proportionate communications near emergency activity where appropriate.</li>
<li>A simple one page ops note on every job covering airspace, standoffs and abort triggers.</li>
<li>Calm, courteous engagement with officers, with a record of powers used and a property schedule if equipment is seized.</li>
</ol>
</section>
<section aria-labelledby="tech-ref">
<h2 id="tech-ref">Technical reference: cross motorway separation</h2>
<p>To contextualise the judge’s description (opposite side of a six lane motorway plus hard shoulder plus verge), the following uses standard UK dimensions.</p>
<h3>Assumptions from UK highway standards</h3>
<ul>
<li><strong>Lane width (motorways):</strong> 3.65 m per lane (DMRB CD 127). <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">[1]</a></li>
<li><strong>Hard shoulder width:</strong> 3.3 m (National Highways). <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">[2]</a></li>
<li><strong>Central reservation (median):</strong> assume about 3.0 m (DMRB derived guidance). <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">[3]</a></li>
<li><strong>Verge:</strong> varies by site; on trunk roads, about 3.0 m is common. Use 2.0 to 3.0 m to bracket reality. <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">[4]</a></li>
</ul>
<h3>Baseline components</h3>
<ul>
<li>Six lanes = 6 x 3.65 = <strong>21.90 m</strong>. <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">[1]</a></li>
<li>Two hard shoulders = <strong>6.60 m</strong>. <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">[2]</a></li>
<li>Central reservation (median) about <strong>3.00 m</strong>. <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">[3]</a></li>
<li>Verge per side about <strong>2.0 to 3.0 m</strong>. <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">[4]</a></li>
</ul>
<h3>Real world lateral separation (verge to verge)</h3>
<p><code>Distance = 6 lanes + 2 x hard shoulder + 2 x verge + median</code></p>
<ul>
<li>With 2.0 m verges (conservative): <strong>21.90 + 6.60 + 4.00 + 3.00 = 35.50 m</strong></li>
<li>With 3.0 m verges (typical): <strong>21.90 + 6.60 + 6.00 + 3.00 = 37.50 m</strong></li>
</ul>
<p><strong>Figure to use:</strong> about <strong>37.5 m</strong> horizontal separation verge to verge (typical). <strong>Lower bound:</strong> about <strong>35.5 m</strong> if verges are unusually narrow.</p>
<h3>Lean reading (narrow phrasing)</h3>
<p>Six lanes plus one hard shoulder plus one verge (omitting the median and the opposite side shoulder and verge):</p>
<p><code>21.90 + 3.30 + (2.0 to 3.0) = 27.2 to 28.2 m</code></p>
<p>This underestimates the physical cross section that most operators and engineers would use.</p>
<h3>Add altitude for slant distance</h3>
<p>If height is h, the slant range is <code>sqrt(lateral^2 + h^2)</code>.</p>
<ul>
<li>With 37.5 m lateral: <strong>48.0 m</strong> at 30 m AGL, <strong>70.8 m</strong> at 60 m, <strong>125.7 m</strong> at 120 m.</li>
<li>With 35.5 m lateral: <strong>46.5 m</strong> at 30 m, <strong>69.2 m</strong> at 60 m, <strong>124.2 m</strong> at 120 m.</li>
</ul>
<p><strong>Practical effect:</strong> even before adding any field offset inside the field beyond the verge, cross motorway separation is around 36 to 38 m. Any field offset adds to that figure. Slant range increases further with altitude.</p>
<p>Standards: <a href="https://moderngov.fareham.gov.uk/documents/s27875/8.12%20DMRB%20CD127%20-%20Cross-sections%20and%20headrooms.pdf" rel="nofollow">DMRB CD 127</a>, <a href="https://nationalhighways.co.uk/our-work/smart-motorways-evidence-stocktake/emergency-area-width-review/" rel="nofollow">National Highways</a>, <a href="https://cdn.tii.ie/publications/DN-GEO-03036-01.pdf" rel="nofollow">TII DN GEO 03036</a>, <a href="https://www.transport.gov.scot/publication/dmrb-stage-3-report-pass-of-birnam-to-tay-crossing-a9-dualling/engineering-assessment/" rel="nofollow">Transport Scotland</a>.</p>
</section>
<section aria-labelledby="closing">
<h2 id="closing">Bottom line</h2>
<p>This is a constructive outcome. The most serious allegation fell away, the fine is modest, and the client retains their equipment. More importantly, the experience is being used to lead on best practice: clearer telemetry, stronger data resilience and exemplary on scene conduct, supporting emergency services, informing the public and keeping UK skies safe.</p>
</section>
<hr />
<section aria-labelledby="bio">
<h2 id="bio">About the author</h2>
<p><strong>Richard Ryan</strong> is a Barrister (Direct Access), Mediator and Chartered Arbitrator based in the UK, specialising in drone and counter-drone law, aviation regulation, and complex commercial disputes. He advises operators, insurers and public bodies on SORA/AAE approvals, BVLOS programmes, privacy/data governance, and risk allocation across the drone ecosystem.</p>
</section>
<p><em>This post is for general information only and is not legal advice.</em></p>
<p><!-- End WordPress post content --></p>
<p>The post <a href="https://blakistons.co.uk/a-constructive-outcome-for-safer-skies-what-the-clients-case-means-for-uk-drone-pilots/">A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>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>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>Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations</title>
		<link>https://blakistons.co.uk/consent-judgment-entered-against-philadelphia-drone-flyer-for-violations-of-faa-regulations/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Wed, 05 Feb 2025 11:10:25 +0000</pubDate>
				<category><![CDATA[Aviation Law]]></category>
		<category><![CDATA[Aviation Law and Regulations]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[FAA Regulations]]></category>
		<category><![CDATA[Legal Cases]]></category>
		<category><![CDATA[UK Drone Compliance]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[UK Law]]></category>
		<category><![CDATA[UK Legislation]]></category>
		<category><![CDATA[UK Policy]]></category>
		<category><![CDATA[aviation law]]></category>
		<category><![CDATA[consent judgment]]></category>
		<category><![CDATA[Drone Compliance]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[FAA enforcement]]></category>
		<category><![CDATA[FAA violations]]></category>
		<category><![CDATA[Philadelphia drone case]]></category>
		<category><![CDATA[sUAS regulations]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2552</guid>

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

					<description><![CDATA[<p>Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir By Richard Ryan, Drone Lawyer The skies over the UK are on the verge of a transformative shift, thanks to the ambitious NATS OpenAir initiative. Designed to integrate drones and advanced air mobility (eVTOLs) into shared airspace alongside traditional aircraft, the proposal [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/transforming-uk-airspace-a-new-era-for-drones-and-aviation-with-nats-openair/">Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir</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/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-300x171.webp" alt="" width="300" height="171" class="alignnone size-medium wp-image-2520" srcset="https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-300x171.webp 300w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-1024x585.webp 1024w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-768x439.webp 768w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-1536x878.webp 1536w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir-600x343.webp 600w, https://blakistons.co.uk/wp-content/uploads/2024/11/241126_Transforming-UK-Airspace-A-New-Era-for-Drones-and-Aviation-with-NATS-OpenAir.webp 1792w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<p><strong>Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir</strong></p>
<p><strong>By Richard Ryan, Drone Lawyer</strong></p>
<p>The skies over the UK are on the verge of a transformative shift, thanks to the ambitious NATS OpenAir initiative. Designed to integrate drones and advanced air mobility (eVTOLs) into shared airspace alongside traditional aircraft, the proposal promises innovation, efficiency, and safety. But as with any grand vision, the devil is in the detail.<br />
Here’s an in-depth look at what the OpenAir initiative is getting right, where there are gaps, and how it can evolve to meet the needs of all airspace users.<br />
________________________________________<br />
1. Prioritising Data Privacy and Ownership</p>
<p>One of the most valuable resources in aviation is data. For drone operators, who depend on real-time information about flight paths, weather, and airspace restrictions, access to reliable data is critical. However, the OpenAir proposal is light on specifics about who owns the data and how privacy will be protected.<br />
Without clear protections, drone operators might worry about their data being exploited—whether commercially or in ways that jeopardise their competitive edge.</p>
<p>The Fix:<br />
OpenAir must adopt a clear data privacy framework. Operators should retain ownership of their data, with mandatory anonymisation for any information shared beyond essential safety and operational use. Only the bare minimum of data required for regulatory compliance should be shared, and stringent safeguards must prevent its misuse.<br />
________________________________________<br />
2. Keeping the Playing Field Fair</p>
<p>OpenAir is envisioned as a centralised hub for managing UK airspace, which sounds great—until you consider the potential impact on smaller players. Consolidating services under one entity like OpenAir might inadvertently stifle competition among Uncrewed Traffic Management Service Providers (UTMSPs).</p>
<p>The Fix:<br />
To level the playing field, OpenAir should adopt open standards that allow seamless third-party integration. Smaller UTMSPs must be supported, not sidelined. Clear rules around equitable access to data and services will ensure innovation thrives without creating monopolies.<br />
________________________________________<br />
3. Setting Realistic Timelines</p>
<p>Integrating drones and eVTOLs into shared airspace isn’t a simple task. OpenAir’s proposed rollout timeline—beginning pilots in 2025 and achieving full deployment by 2028—might be overly ambitious, especially given the complexity of regulatory approvals and the need for robust infrastructure.</p>
<p>The Fix:<br />
A phased approach with realistic benchmarks is the way forward. OpenAir should focus on pilot projects in key areas where demand is highest (e.g., urban delivery drones or emergency medical services). This would provide valuable data to refine the system while reducing the risk of rushed implementation.<br />
________________________________________<br />
4. Managing Costs for Drone Operators</p>
<p>OpenAir’s &#8220;user pays&#8221; principle makes sense in theory—those who use the airspace services should cover the costs. But smaller operators, such as local delivery drone companies, could be disproportionately affected by high fees, potentially pricing them out of the market.</p>
<p>The Fix:<br />
Introduce tiered pricing. Small operators should pay less, at least during the initial phases. Alternatively, subsidies or credits could be offered to early adopters, ensuring fair access while fostering adoption across the board.<br />
________________________________________<br />
5. Addressing Legal Grey Areas</p>
<p>OpenAir aligns with the UK’s Airspace Modernisation Strategy, but its relationship with existing regulations like CAP 722 (which governs drone operations) needs to be crystal clear. Ambiguities in compliance requirements could delay approvals or lead to legal disputes.<br />
Similarly, liability concerns loom large. If there’s a system outage or data error, who’s responsible for the fallout? Drone operators? OpenAir? The CAA? NATS? DfT?</p>
<p>The Fix:<br />
OpenAir must explicitly state how its services integrate with CAP 722, especially for critical areas like Beyond Visual Line of Sight (BVLOS) operations. As for liability, service agreements must clearly define responsibilities, ensuring all parties—operators, OpenAir, and regulators—understand their obligations.<br />
________________________________________<br />
6. Building Trust Through Transparency</p>
<p>For OpenAir to succeed, trust is key. Stakeholders—including drone operators, regulators, and public service agencies—must feel confident in the system’s fairness and security.</p>
<p>The Fix:<br />
Establish an independent advisory board with representatives from all key groups, including Blakiston’s Chambers! This board would oversee the rollout of OpenAir, ensuring transparency and accountability. Regular public updates and feedback sessions would further build trust and address concerns early.<br />
________________________________________<br />
7. Looking to the Future</p>
<p>The potential of OpenAir is undeniable. By creating a unified platform for managing UK airspace, it could unlock opportunities ranging from efficient logistics to life-saving medical deliveries. But to truly succeed, OpenAir must:<br />
1.	Prioritise data privacy and ownership.<br />
2.	Ensure fair competition for all service providers.<br />
3.	Adopt a phased, realistic rollout plan.<br />
4.	Keep costs manageable for smaller operators.<br />
5.	Align with existing regulations like CAP 722.<br />
6.	Address liability concerns upfront.<br />
7.	Foster trust through transparency and stakeholder engagement.</p>
<p>The skies above us are changing, and with thoughtful planning, OpenAir could make the UK a global leader in integrated airspace management. But to get there, it must balance ambition with practicality, ensuring the system works for everyone—from global eVTOL operators to local delivery drones.<br />
________________________________________<br />
What do you think about the OpenAir proposal? Share your thoughts, especially if you&#8217;re a drone operator or part of the aviation industry. Your feedback could shape the future of our skies!</p>
<p><strong>About the Author</strong><br />
Richard Ryan is a UK-based barrister and drone law expert with over 20 years of legal experience. Specializing in regulatory, operational, and safety challenges, Richard advises defence companies, regulatory bodies, and government agencies on the complexities of UAS operations. A former advisor to the UK Civil Aviation Authority and the House of Lords’ AUTMA committee, Richard is currently pursuing a PhD at Cranfield University, focusing on the legal implications of drone integration into global airspace.<br />
Richard combines his legal expertise with a deep understanding of defence operations, having served in the British Army, including deployments to Iraq and Afghanistan. His insights bridge the gap between operational realities and legal requirements, ensuring clients navigate the rapidly evolving world of drone technology with confidence.</p>
<p>The post <a href="https://blakistons.co.uk/transforming-uk-airspace-a-new-era-for-drones-and-aviation-with-nats-openair/">Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland</title>
		<link>https://blakistons.co.uk/legal-issues-in-drone-operations-a-uk-perspective-on-safety-compliance-and-lessons-from-the-gen-3-8-incident-in-ireland/</link>
		
		<dc:creator><![CDATA[admin.richard]]></dc:creator>
		<pubDate>Mon, 11 Nov 2024 07:47:06 +0000</pubDate>
				<category><![CDATA[Aviation Incidents - Discusses significant aviation-related events with legal and safety implications.]]></category>
		<category><![CDATA[Aviation Regulation]]></category>
		<category><![CDATA[Aviation Safety]]></category>
		<category><![CDATA[Beyond Visual Line of Sight (BVLOS) Operations]]></category>
		<category><![CDATA[Case Studies - Provides a real-world incident analysis for educational purposes in drone law and compliance]]></category>
		<category><![CDATA[Civil Aviation Authority (CAA) Policies]]></category>
		<category><![CDATA[Drone Accidents & Case Studies]]></category>
		<category><![CDATA[Drone Law]]></category>
		<category><![CDATA[Drone Law - Covers legal aspects and compliance specific to drone operations and incidents.]]></category>
		<category><![CDATA[Drone Safety and Operations]]></category>
		<category><![CDATA[EASA]]></category>
		<category><![CDATA[Risk Assessment & Mitigation]]></category>
		<category><![CDATA[UK Drone Regulations]]></category>
		<category><![CDATA[Urban Drone Delivery]]></category>
		<category><![CDATA[Air Navigation Order]]></category>
		<category><![CDATA[Aviation Act 1982]]></category>
		<category><![CDATA[CAA]]></category>
		<category><![CDATA[drone accident]]></category>
		<category><![CDATA[drone law]]></category>
		<category><![CDATA[Drone Safety]]></category>
		<category><![CDATA[GEN 3.8 incident]]></category>
		<category><![CDATA[IAA]]></category>
		<category><![CDATA[Ireland drone law]]></category>
		<category><![CDATA[regulatory compliance]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[UAS]]></category>
		<category><![CDATA[UK drone regulations]]></category>
		<category><![CDATA[urban drone delivery]]></category>
		<guid isPermaLink="false">https://blakistons.co.uk/?p=2481</guid>

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

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

					<description><![CDATA[<p>Having reviewed the 65 pages of the AAIB-25876 report in respect of the Alauda Airspeeder MkII owned by Riotplan Proprietary Limited trading as Alauda Racing crash on 4 July 2019 at Goodwood Aerodrome, the following comments are relevant: 1.There is reference to the commanders flying experience in hours, which included the last 90 days and [&#8230;]</p>
<p>The post <a href="https://blakistons.co.uk/essential-lessons-for-drone-operators-from-the-alauda-airspeeder-mkii-crash-report/">What’s relevant for Drone Operators when the drone crashes – lessons learned from Alauda Airspeeder MkII?</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><span style="font-weight: 400;">Having reviewed the 65 pages of the AAIB-25876 report in respect of the Alauda Airspeeder MkII owned by Riotplan Proprietary Limited trading as Alauda Racing crash on 4 July 2019 at Goodwood Aerodrome, the following comments are relevant:</span></p>
<p><span style="font-weight: 400;">1.There is reference to the commanders flying experience in hours, which included the last 90 days and the last 28 days. Are your records up-to-date?</span></p>
<p><span style="font-weight: 400;">2. The operators Operating Safety Case (OSC) contained several statements that were shown to be untrue. What does your OSC state?</span></p>
<p><span style="font-weight: 400;">3. In this case the CAA did not meet the operator or inspect the UA before the accident flight. Why not invite the CAA to inspect your platform so that you have it on record?</span></p>
<p><span style="font-weight: 400;">4. The CAA were not present at the test flight. Why not invite the CAA to attend the test flight?</span></p>
<p><span style="font-weight: 400;">5. The UA sustained damage to its landing gear as a consequence of loss of power on a test flight the day before the accident. Under the regulations, the OSC and the exemption provided by the CAA, this was supposed to have been reported, but was not. If in doubt, report?</span></p>
<p><span style="font-weight: 400;">6. Observing on the day in question, were two members of the CAA’s UAS unit, who were involved in assessing the operator’s application for exemption.</span></p>
<p><em><span style="font-weight: 400;">7. </span></em>At the CAA UAS unit the section lead was a signatory on the exemption and he joined the CAA in May 2018. There have been numerous questions on resources that pertain to the CAA UAS unit. This is further endorsed by report which states “the CAA stated that the level of resources available meant it was not possible for the UA sector team to follow up every exemption.”</p>
<p><span style="font-weight: 400;">8. The CAA asked the Australian Civil Aviation Authority for further information, which does not appear to have been provided. However, the AAIB did ask CASA, and some information was provided. Does this mean that regulators will only correspond in the event of a serious incident? This is certainly going to become much more relevant for those drone operators that are operating in EU jurisdictions and how the EU intends to harmonise information in the future in order to allow drone operators to fly in different jurisdictions when qualified in another. It will be interesting to see how the UK intends to accept drone operators from the EU based upon UK regulations as these regulations may diverged in the future;</span></p>
<p><span style="font-weight: 400;">9. If you have a number of transmitters as part of your OSC that relate to redundancy, don’t leave them in the workshop!</span></p>
<p><span style="font-weight: 400;">10. The AAIB will appoint experts to examine certain aspects of the UA. In this case, experts were used to examine the circuit boards for compliance and specialist video forensic examiners using photogrammetry (interestingly from video, the expert was able to determine the UA’s heading, ground speed and altitude);</span></p>
<p><span style="font-weight: 400;">11. The AAIB compared this UA’s manufacture to EASA’s Special Conditions that relate to gliders with electric propulsion units and associated high-voltage batteries. In the event that there is an absence of regulation, comparisons will be made to other similar regulatory standards;</span></p>
<p><span style="font-weight: 400;">12. When writing mitigation measures for single points of failure, be mindful that if there is a failure in radio link communication that the UA will continue flying using its last known command. Interestingly, in this case there was no consideration on the effect of a kill switch not operating and that the hazard of a “flyaway” was not considered;</span></p>
<p><span style="font-weight: 400;">13. As a drone operator, do not state that your system has a return to home function when no GPS is fitted to the UA!</span></p>
<p><span style="font-weight: 400;">14. From an operator’s perspective, the operator in this case appears to make the admission that there was insufficient time and resources to adequately test and stabilise their equipment in unfamiliar surroundings. Additionally they stated that the team were all relatively inexperienced with aviation systems, procedures, required documentation and the need to formally understand and adhere to these processes. These are significant statements that underline the culture of an organisation in its approach to safe use of equipment and its emphasis on providing necessary training. Do your teams understand the legal obligations that relate to your operational authorisation and/or OSC?</span></p>
<p><span style="font-weight: 400;">15. As of August 2020, there are over 106,000 registered UA operators in the UK and over 45,000 operators flying model aircraft. That is a significant number of operators that require relevant training and understanding of their legal obligations;</span></p>
<p><span style="font-weight: 400;">16. According to the drones reunited website, the CAA state that most flyaways occur due to battery loss, poor signal, or a technology failure and some of this is also down to pilot error. It is essential that these aspects are covered in your risk assessment;</span></p>
<p><span style="font-weight: 400;">17. There are a number of amendments with respect to safety recommendations to CAP 722, which are:</span></p>
<ol>
<li style="list-style-type: none;">
<ol>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">detailed evaluation of any unmanned aircraft systems that use on-board systems to mitigate risks with risk severity classifications of “major, hazardous or catastrophic.”</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">guidance on the planning, completion and documenting of radiofrequency surveys to reduce the risk of radio-frequency interference or signal loss when operating unmanned aircraft systems;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">unmanned aircraft system operators that use unmanned aircraft which rely on a radiolinks to operate safety systems are to provide radiofrequency survey reports to the CAA for review;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">guidance on how to define an unmanned aircraft systems operational and safety areas, using up-to-date maps, accurate trajectory analysis and human automated safety system reaction times to ensure a safe operation;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">the CAA are to provide examples of unmanned aircraft system safety systems;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">the report recommends that the CAA introduce requirements to define a minimum standard for safety systems to be installed in unmanned aircraft systems operating under an operational authorisation to ensure adequate mitigation in the event of a malfunction;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">data recording systems which are capable of demonstrating compliance with the authorisations conditions, safe operation and the logging of any failures which may affect the safe operation of the unmanned aircraft system are to be required;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">minimum requirements for the monitoring of high-voltage stored energy devices to ensure safety of operations are recommended;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">operators of unmanned aircraft systems should have an effective safety management system in place prior to issuing an operational authorisation;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">expect an inspection from the CAA when seeking an operational authorisation for an unmanned aircraft system that the CAA have not previously had experience with;</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">expect the CAA to adopt appropriate design, production, maintenance and reliability standards for all unmanned aircraft systems with aircraft capable of imparting over 80 J of energy, the same recommendation is made to EASA. It will be interesting to see how this develops within the new CE marking regime that is to apply in the future;</span></li>
</ol>
</li>
</ol>
<p><span style="font-weight: 400;">This is a really useful case study for drone operators to consider. It certainly is a timely reminder to make sure that your operational safety cases and/or OSC’s are up-to-date and that all the staff that are involved in your operation are cognisant of their legal obligations with respect to the regulations, the OSC and the exemption provided by the Civil Aviation Authority. If you have any questions about this or any other legal issues, please email </span><a href="mailto:info@blakistons.com"><span style="font-weight: 400;">info@blakistons.com</span></a></p>
<p>The post <a href="https://blakistons.co.uk/essential-lessons-for-drone-operators-from-the-alauda-airspeeder-mkii-crash-report/">What’s relevant for Drone Operators when the drone crashes – lessons learned from Alauda Airspeeder MkII?</a> appeared first on <a href="https://blakistons.co.uk">Blakistons</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
