Future of Drone Regulations Archives - Blakistons

A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots

admin.richard — Thu, 06 Nov 2025 17:53:49 +0000

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 emergency response — Air Navigation Order 2016 Articles 265B(3), 265B(5)(j) and 265F(3)(c) (reflecting UAS.OPEN.060(3)).
Count 2 (dismissed): Obstructing or hindering emergency workers — Emergency Workers (Obstruction) Act 2006, sections 1 and 4 — no case to answer.
Sentence: £300 (reduced from £2,500). Deprivation order refused — the client’s equipment will be returned.

Competence, cooperation and public interest flying

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.

Lesson 1: Telemetry clarity

When presenting flight data, clarity matters. Plot the flight path with a thin, precise line so the base map remains legible, including fences, road edges, cordons and measured standoffs. A thick line can obscure the very features that prove separation.

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.
Use a thin line that clearly shows accurate telemetry when placed on a map, not a thick line that obscures part of the map.

Lesson 2: Plan for seizure and understand where DJI DAT lives

High fidelity DJI DAT logs are stored on the aircraft and typically require connecting the drone to a computer to extract. If a drone is seized by police, immediate access to those DAT files is difficult.

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.
For sensitive assignments, consider periodic DAT offloads in advance.

Five straightforward commitments

Thin line telemetry as the default for mapping outputs.
Evidence resilience: dual path logging (logs plus screen capture) and periodic DAT offloads.
Proportionate communications near emergency activity where appropriate.
A simple one page ops note on every job covering airspace, standoffs and abort triggers.
Calm, courteous engagement with officers, with a record of powers used and a property schedule if equipment is seized.

Technical reference: cross motorway separation

To contextualise the judge’s description (opposite side of a six lane motorway plus hard shoulder plus verge), the following uses standard UK dimensions.

Assumptions from UK highway standards

Lane width (motorways): 3.65 m per lane (DMRB CD 127). [1]
Hard shoulder width: 3.3 m (National Highways). [2]
Central reservation (median): assume about 3.0 m (DMRB derived guidance). [3]
Verge: varies by site; on trunk roads, about 3.0 m is common. Use 2.0 to 3.0 m to bracket reality. [4]

Baseline components

Six lanes = 6 x 3.65 = 21.90 m. [1]
Two hard shoulders = 6.60 m. [2]
Central reservation (median) about 3.00 m. [3]
Verge per side about 2.0 to 3.0 m. [4]

Real world lateral separation (verge to verge)

Distance = 6 lanes + 2 x hard shoulder + 2 x verge + median

With 2.0 m verges (conservative): 21.90 + 6.60 + 4.00 + 3.00 = 35.50 m
With 3.0 m verges (typical): 21.90 + 6.60 + 6.00 + 3.00 = 37.50 m

Figure to use: about 37.5 m horizontal separation verge to verge (typical). Lower bound: about 35.5 m if verges are unusually narrow.

Lean reading (narrow phrasing)

Six lanes plus one hard shoulder plus one verge (omitting the median and the opposite side shoulder and verge):

21.90 + 3.30 + (2.0 to 3.0) = 27.2 to 28.2 m

This underestimates the physical cross section that most operators and engineers would use.

Add altitude for slant distance

If height is h, the slant range is sqrt(lateral^2 + h^2).

With 37.5 m lateral: 48.0 m at 30 m AGL, 70.8 m at 60 m, 125.7 m at 120 m.
With 35.5 m lateral: 46.5 m at 30 m, 69.2 m at 60 m, 124.2 m at 120 m.

Practical effect: 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.

Standards: DMRB CD 127, National Highways, TII DN GEO 03036, Transport Scotland.

Bottom line

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.

About the author

Richard Ryan 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.

This post is for general information only and is not legal advice.

The post A Constructive Outcome for Safer Skies: What the Client’s Case Means for UK Drone Pilots appeared first on Blakistons.

When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports

admin.richard — Mon, 27 Oct 2025 19:14:43 +0000

By Richard Ryan, Barrister & Drone Lawyer – practical takeaways, not legal advice for your specific situation.

Why this matters

CHIRP’s Drone/UAS FEEDBACK Edition 14 (September 2025) curates incidents that look ordinary until you view them through a law-and-liability lens:
three model-flying events that drifted into unintentional BVLOS, a Mini 2 injury at a carnival, a controller or app freeze mid-mission,
a fatigue-tinged flight that autolanded at 20 percent battery into a tree, and an RTH climb toward powerlines. Each contains avoidable legal exposure
that you can mitigate with better planning, clear roles, and a few settings changes.

The incidents, in plain English – and what the law expects

1) Unintentional BVLOS x3 (BMFA community)

What happened: 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.
Legal frame (UK): The Drone and Model Aircraft Code requires direct VLOS and the ability to determine orientation at all times. If you cannot do that, the flight is non-compliant.
Practical fix: Treat post-purchase alterations as airworthiness-significant and inspect them before each flight. Use BMFA’s SWEETS pre-flight. Adopt a simple “radial scan” habit: eyes out (aircraft and airspace) then quick glance down (controller or map) then eyes out again.

2) Nottingham Carnival injury (Mini 2)

What happened: A minor pressed “land” while the supervising adult was distracted; the drone struck another child who was sitting on someone’s shoulders. Police confiscated the aircraft. No Operator ID was displayed and it was flown over a crowd.
Legal frame (UK): Never fly over crowds or assemblies of people. Label the aircraft with a visible Operator ID. Where injury occurs, expect scrutiny under general endangerment provisions.
Practical fix: Establish a safe TOLA (take-off and landing area) away from the crowd. Use aviation-style handover phraseology: “You have control” / “I have control”. Keep controller audio alerts audible. Supervision of minors must be active and informed by the Code.

3) “My app froze” (Mavic 4 Pro + RC2; 87-waypoint mission)

What happened: Switching to Map View mid-mission froze the Fly app. The pilot used the hardware RTH button to recover the aircraft. Possible overload from running a large waypoint mission while screen-recording.
Legal frame: 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.
Practical fix: For long waypoint jobs, test the profile without screen-recording first. Pre-brief the hardware RTH action. Use a visual observer if you will be heads-down.

4) Fatigue and stress (power-line inspection)

What happened: The pilot became disoriented, lost VLOS about 1,700 ft from home, hit 20 percent battery, and, unaware that “land at 20 percent” was set, descended into a tree despite pressing RTH.
Practical fix: Know and brief your low-battery action (RTH vs auto-land vs hover) in the Operations Manual. Use two-crew where terrain or workload increases disorientation risk. Remember UK requirements to maintain VLOS and orientation at all times.

5) RTH vs powerlines (mapping mission)

What happened: 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.
Practical fix: Set RTH altitude 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.

Five legal pillars these cases keep hitting

VLOS is non-negotiable. Keep the aircraft in direct sight and be able to tell its orientation, with a full view of surrounding airspace.
Crowds are out of bounds. “Assemblies of people” are defined by the inability to disperse quickly, not by a headcount.
Operator ID labelling is strict. Visible, legible, on the airframe. Sub-250 g camera drones typically still require an Operator ID.
Endangerment provisions are broad. If someone is endangered or injured, regulators may consider reckless or negligent operation.
Automation is not absolution. You own the outcomes of RTH, low-battery actions, waypointing, and controller limits.

Turn the lessons into a defensible playbook

A. Pre-flight and design for failure

Modified anything? 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.
Weather is slippery. Do not rely on one app. Triangulate forecasts. Identify abort gates if visibility closes in (fog, showers, glare). Use SWEETS at the field.
Controller workload. For heavy waypoint missions, disable screen-recording unless proven stable. Rehearse hardware RTH and app-independent control.

B. RTH and battery settings you can defend

Set RTH altitude locally, every time. Clear known obstacles and powerlines. Consider Advanced RTH where available.
Know low-battery behavior. Document thresholds in the Operations Manual, brief them to the crew, and confirm on the controller before take-off.

C. People, roles, and sterile cockpit

Observer next to you for heads-down tasks, with real-time verbal coordination.
Minors at the sticks? Only with active oversight, formal handovers, and never within or over a crowd.
Events and assemblies. Create buffer zones and safe TOLA sites. If a client insists on crowd-proximate shots, the safest and most defensible answer is often no without appropriate authorization and controls.

D. Evidence and reporting (preserve the facts)

After any occurrence, preserve flight logs, app caches, screen recordings, controller settings, and note battery and RTH configuration.
Consider confidential safety reporting to CHIRP in the UK (and NASA ASRS in the U.S.) to help the community learn without blame.

Bottom line

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,
or a controller pushed too hard. The Code’s core duties – VLOS, no crowds, proper ID labelling,
know your automation, and keep records – are your best legal shield when something goes wrong.

BMFA SWEETS: a quick pre-flight check

S — Sun: position now and later; glare; keep VLOS; avoid flying through the sun.
W — Wind: direction/strength/turbulence; safe areas for forced or dead-stick landings.
E — Environment: visibility (rain, mist, fog, fading light), people nearby, RF risks, space to fly a full circuit.
E — Emergencies: plan what you will do if there is a malfunction or airspace incursion; confirm failsafes.
T — Transmitter control: local Tx control and frequencies; correct model; trims/rates; Tx power/voltage.
S — Site rules: club rules, local byelaws, no-fly zones, height and airspace limits.

Note: some older guides use “Eventualities” for the first E. Meaning is the same: think ahead about what could happen and how you will handle it.

This article is general information, not legal advice. If an incident has occurred, speak to counsel at Blakiston’s Chambers before making statements to third parties and preserve all electronic evidence immediately.

Credit and resources

Based on incidents and analysis in CHIRP Drone/UAS FEEDBACK Edition 14 (September 2025).
BMFA pre-flight mnemonic SWEETS: handbook.bmfa.uk/13-general-model-safety
UK Drone and Model Aircraft Code: register-drones.caa.co.uk
Report a safety concern to CHIRP (confidential): chirp.co.uk/aviation/submit-a-report

The post When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports appeared first on Blakistons.

Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective

admin.richard — Tue, 07 Jan 2025 13:29:44 +0000

Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective

By Richard Ryan, UK Drone Lawyer

On 7 January 2025, The Guardian published an article highlighting the British AI consultancy Faculty AI’s involvement in the development of drone technology for defence clients, prompting renewed questions about where legal, ethical, and regulatory boundaries should lie for AI-driven military applications.
Faculty AI, already prominent for its work with various UK government departments (including the NHS and the Department for Education) and advisory services for the AI Safety Institute (AISI), has reportedly developed and deployed AI models on unmanned aerial vehicles (UAVs) for military purposes. Although it remains unclear whether these drones are intended for lethal operations, the revelations have amplified concerns about how best to regulate or restrict the use of AI in weapon systems.
Below, I explore the key legal issues and examine how the recently adopted EU AI Act—as well as the evolving UK regulatory framework—may shape the future of this sector.
________________________________________
1. Faculty AI’s Defence Work: A Brief Overview
1.1 Government and Public Sector Ties
Faculty AI, known for its work with the Vote Leave campaign in 2016, was later engaged by Dominic Cummings to provide data analytics during the pandemic. Since then, it has won multiple government contracts worth at least £26.6m, extending its work into healthcare (via the NHS), education, and policy consulting with the AISI on frontier AI safety.
1.2 UAV Development
The Guardian reports that Faculty AI has experience in deploying AI models on UAVs. Its partner firm, Hadean, indicated that the two companies collaborated on subject identification, tracking objects in movement, and exploring swarm deployment. While Faculty states that it aims to create “safer, more robust solutions”, details on whether these drones might be capable of lethal autonomous targeting remain undisclosed.
________________________________________
2. The EU AI Act: A New Regulatory Milestone
2.1 Status of the EU AI Act
Introduced by the European Commission in 2021 as a proposed regulation, the EU AI Act has since been adopted via the EU’s legislative process. As of early 2025, it is recognised as a binding regulation designed to harmonise AI rules across all EU Member States. Although the UK is no longer part of the EU, any UK-based company offering AI products or services within the EU must ensure compliance with the regulation’s requirements.
2.2 Risk-Tiered Framework
The EU AI Act operates on a tiered risk basis:
• Unacceptable risk: Certain AI applications (e.g., social scoring) are outright banned.
• High risk: This category includes critical infrastructure, healthcare, and—potentially—defence-related AI systems that could significantly affect people’s safety or fundamental rights. Such systems must meet strict transparency, oversight, and data governance requirements.
• Limited or minimal risk: These uses are subject to fewer obligations, generally focused on transparency (e.g., disclosing AI usage to end users).
For high-risk AI in military contexts, the EU AI Act demands robust human oversight, thorough documentation, and strict compliance obligations, particularly around accountability and the prevention of harm.
2.3 Potential Impact on Military Drones
While national security and defence largely remain the prerogative of individual EU Member States, the EU AI Act’s principles can still influence how companies and governments view the development of autonomous or semi-autonomous drones. Key considerations include:
• Transparent Data and Design: Documenting data sets, development processes, and operational parameters.
• Human in the Loop: Ensuring a human operator is always able to override or intervene in the AI’s decision-making. Other terms such as Human on the Loop and Human outside the Loop are also referred to.
• Liability and Penalties: Breaches can incur hefty fines—up to 6% of global turnover—thus acting as a significant deterrent against unethical or unlawful AI deployment.
________________________________________
3. The UK’s Approach to AI Regulation and Military Drones
3.1 Divergence from the EU?
Post-Brexit, the UK has chosen a “pro-innovation” approach to AI regulation. Rather than adopting a single, all-encompassing statute akin to the EU AI Act, the UK is implementing a sector-by-sector and risk-based strategy, guided by existing regulators such as the Information Commissioner’s Office and the Competition and Markets Authority.
3.2 AI Safety Institute (AISI)
Established under former Prime Minister Rishi Sunak in 2023, the AISI focuses on frontier AI safety research. Faculty AI’s role in testing large language models and advising the AISI on threats like disinformation and system security places the company in a key position to influence UK policy. Critics argue that this may create potential conflicts of interest if the same organisation is also developing AI for military use.
3.3 House of Lords Recommendations
In 2023, a House of Lords committee urged the UK Government to clarify the application of International Humanitarian Law (IHL) to lethal drone strikes and to work towards an international agreement limiting or banning fully autonomous weapons systems. The Government response acknowledged the importance of maintaining “human control” in critical decisions but did not enact binding legislation banning lethal autonomous drones outright.
________________________________________
4. Legal and Ethical Concerns for AI-Enabled Drones
4.1 International Humanitarian Law (IHL)
IHL principles—distinction (separating combatants from civilians) and proportionality (limiting harm relative to military objectives)—are central to discussions on AI-driven drones. Fully autonomous UAVs, capable of selecting and engaging targets without human intervention, raise profound legal questions on accountability, particularly if biases or system errors result in wrongful casualties.
4.2 Allocation of Liability
Traditionally, accountability in military operations lies with commanders and operators. With increasingly autonomous systems, however, liability could extend to technology developers, programmers, or even the purchaser of the system. Clarifying how legal responsibilities are distributed may become a focal point for future litigation and regulatory reform.
4.3 Export Controls
Companies like Faculty AI must also comply with arms-export rules when providing AI-targeting systems or related software to foreign entities. In the UK, export licences for military-grade technology are subject to domestic legislation and international protocols, such as the Wassenaar Arrangement on dual-use goods.
________________________________________
5. Looking Ahead: Balancing Innovation, Safety, and Accountability
5.1 Stronger National Frameworks
Although the UK favours a pro-innovation stance, there is growing pressure from Parliament and civil society for more rigorous, enforceable rules on potentially lethal AI applications. The EU AI Act may serve as a reference point for the UK to consider stricter domestic regulations.
5.2 International Collaboration
Calls for global agreements—treaties or non-binding accords—to prohibit fully autonomous weapons continue to gain momentum. The House of Lords committee specifically recommended international engagement to ensure that lethal force remains under human control.
5.3 Corporate Accountability
Organisations operating at the intersection of commercial defence contracts and government policy—such as Faculty AI—need transparent internal processes and robust ethics boards to mitigate conflicts of interest. Demonstrating genuine corporate responsibility will be vital for maintaining public trust.
5.4 Ethical and Safety Audits
As AI becomes more embedded in defence, mandatory ethical and safety audits may become standard practice. These would scrutinise algorithmic fairness, training data, and how effectively systems can identify and mitigate unintended harms.
________________________________________
6. Conclusion
Faculty AI’s role in developing AI for military drones underscores how high the stakes are when cutting-edge technology meets defence applications. With the EU AI Act now in force as a binding regulation, Europe has provided a blueprint for tighter control over “high-risk” AI systems. In contrast, the UK’s approach still offers substantial flexibility for companies, potentially raising both legal and ethical concerns around autonomy, accountability, and conflicts of interest.
From an IHL standpoint, keeping a human responsible for any life-and-death decision is imperative. As a UK drone lawyer, I urge policymakers, regulators, and industry stakeholders to keep asking: Where do we draw the line between legitimate defensive innovation and an unacceptable risk to civilians? Only by establishing clear, enforceable legal standards—anchored in international law and ethical scrutiny—can we ensure AI-powered drones serve to protect rather than endanger fundamental human values.

Bio – Richard Ryan, UK Drone Lawyer

Richard Ryan is a UK-based drone lawyer specialising in the regulatory, ethical, and commercial aspects of unmanned aerial vehicles (UAVs) and artificial intelligence (AI). Through a series of blogs, Richard Ryan has explored critical issues such as the EU AI Act, the UK’s evolving “pro-innovation” regulatory landscape, and the legal considerations surrounding military drones and lethal autonomous weapons systems.

Drawing on extensive experience in advising government bodies, technology companies, and public institutions, Richard Ryan brings a deep understanding of how international humanitarian law (IHL), export controls, and data protection obligations intersect in modern drone operations. Their writing emphasises the importance of maintaining human oversight in AI-driven systems, championing ethical development and transparent accountability mechanisms.

A trusted voice in the field, Richard Ryan regularly comments on emerging case law, parliamentary recommendations, and global discussions around frontier AI safety. The mission is to help stakeholders—from hobbyist drone operators to established aerospace firms—navigate the complexities of regulation, risk management, and innovation.

The post Military Drones and AI Regulation: A UK Drone Lawyer’s Perspective appeared first on Blakistons.

Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir

admin.richard — Tue, 26 Nov 2024 13:01:36 +0000

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 promises innovation, efficiency, and safety. But as with any grand vision, the devil is in the detail.
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.
________________________________________
1. Prioritising Data Privacy and Ownership

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.
Without clear protections, drone operators might worry about their data being exploited—whether commercially or in ways that jeopardise their competitive edge.

The Fix:
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.
________________________________________
2. Keeping the Playing Field Fair

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).

The Fix:
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.
________________________________________
3. Setting Realistic Timelines

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.

The Fix:
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.
________________________________________
4. Managing Costs for Drone Operators

OpenAir’s “user pays” 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.

The Fix:
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.
________________________________________
5. Addressing Legal Grey Areas

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.
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?

The Fix:
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.
________________________________________
6. Building Trust Through Transparency

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.

The Fix:
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.
________________________________________
7. Looking to the Future

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:
1. Prioritise data privacy and ownership.
2. Ensure fair competition for all service providers.
3. Adopt a phased, realistic rollout plan.
4. Keep costs manageable for smaller operators.
5. Align with existing regulations like CAP 722.
6. Address liability concerns upfront.
7. Foster trust through transparency and stakeholder engagement.

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.
________________________________________
What do you think about the OpenAir proposal? Share your thoughts, especially if you’re a drone operator or part of the aviation industry. Your feedback could shape the future of our skies!

About the Author
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.
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.

The post Transforming UK Airspace: A New Era for Drones and Aviation with NATS OpenAir appeared first on Blakistons.

Navigating the Skies: Legal Perspectives on the UK’s Drone Revolution

admin.richard — Wed, 13 Nov 2024 11:50:26 +0000

Navigating the Skies: Legal Perspectives on the UK’s Drone Revolution
By Richard Ryan
November 2024
As an experienced drone lawyer in the UK with two decades of immersion in this rapidly evolving field, I’ve witnessed firsthand the transformative impact drones have across various industries. The recent ARPAS report “Drones In Action” (November 2024) showcases a spectrum of innovative applications, from housing inspections to emergency response. While these use cases highlight significant benefits—such as cost savings, improved safety, and enhanced efficiency—they also surface critical legal considerations that must be addressed to foster sustainable growth in the drone industry.
In this blog, I will analyse the legal issues arising from these drone applications, provide recommendations for regulators to facilitate industry development, and identify unresolved legal challenges.
________________________________________
Legal Issues Arising from Drone Use Cases

1. Airspace Regulation and Flight Permissions
Many of the use cases involve operations in complex airspace or beyond visual line of sight (BVLOS), such as:
• Decommissioning Nuclear Sites (Sellafield Ltd): BVLOS flights over sensitive areas.
• Train Track Inspection (Network Rail): Flights over live tracks without service interruption.
• Electric Grid Tower Inspections (National Grid): Operations near critical infrastructure.
• Live Flare Stack Offshore Inspections: BVLOS flights over the North Sea platforms.

Legal Considerations:
• Air Navigation Order 2016 (ANO 2016) and CAA Regulations require specific permissions for BVLOS operations and flights near congested areas or critical infrastructure.
• Safety Assessments: Operators must conduct rigorous safety cases and obtain Operational Authorisations from the CAA.
• Compliance with Flight Restriction Zones (FRZs): Especially near nuclear sites, railways, and power grids.

2. Data Protection and Privacy
Use cases involving data capture, such as:
• Housing Inspections: Capturing images of residential properties.
• University of Exeter’s Gutter Cleaning: Collecting extensive imagery over campus buildings.
• Site Security Management: Continuous surveillance operations.

Legal Considerations:
• General Data Protection Regulation (GDPR): Operators must ensure compliance when processing personal data.
• Privacy Impact Assessments: Necessary to evaluate risks to individuals’ privacy.
• Transparency and Consent: Informing affected individuals when feasible.

3. Environmental and Wildlife Impact
Operations in sensitive environmental areas:
• Peatland Restoration: Drone seeding over ecologically sensitive peatlands.
• Emergency Response: Drones used in flood monitoring by the Environment Agency.

Legal Considerations:
• Wildlife and Countryside Act 1981: Protects certain wildlife from disturbance.
• Environmental Impact Assessments: May be required for operations affecting protected areas.

4. Security and Counter-UAS Measures
Use cases involving critical infrastructure and potential security risks:
• Nuclear Sites: Potential for drones to be perceived as security threats.
• Emergency Services: Need to deconflict airspace during emergencies.

Legal Considerations:
• Security Regulations: Operators must coordinate with authorities to prevent misunderstandings.
• Counter-Unmanned Aircraft Systems (C-UAS): Awareness of anti-drone measures that could impact legitimate operations.

5. Insurance and Liability
All commercial drone operations must consider:
• Mandatory Insurance: Compliance with EC Regulation 785/2004 on insurance requirements.
• Liability for Damages: Clear understanding of responsibility in case of accidents or data breaches.
________________________________________
Pathways for Regulatory Enhancement

To facilitate easier business operations and industry development, regulators can consider the following recommendations:

1. Streamlining Permissions for BVLOS Operations
• Develop Standard Scenarios: Create predefined conditions under which BVLOS operations can be conducted without lengthy approval processes.
• Risk-Based Approaches: Adopt flexible frameworks that assess risk based on the operation’s specifics rather than a one-size-fits-all model.

2. Enhancing Regulatory Clarity and Guidance
• Clear Guidelines on Data Protection: Issue specific guidance on GDPR compliance for drone operators.
• Environmental Operation Protocols: Provide clear procedures for operations in or near protected areas to prevent ecological disturbances.

3. Facilitating Technological Advancements
• Support for UTM Systems: Implement unmanned traffic management systems to safely integrate drones into UK airspace.
• Encourage Innovation: Provide sandbox environments where companies can test new technologies under regulatory supervision.

4. Harmonizing Security Measures
• Establish Communication Channels: Create protocols for operators to notify authorities of intended flights near sensitive sites.
• Standardise C-UAS Policies: Ensure that anti-drone measures do not inadvertently disrupt lawful operations.

5. Simplifying Insurance Processes
• Unified Insurance Platforms: Work with the insurance industry to develop products tailored for drone operations.
• Liability Caps: Consider legislative caps on liability to reduce barriers for smaller operators.
________________________________________
Legal Issues Needing Resolution

1. Airspace Integration and Management
• National Airspace Policy for Drones: There is a pressing need for a comprehensive policy that integrates drones into the national airspace, balancing innovation with safety.

2. Privacy Laws Adaptation
• Modernising Legislation: Current privacy laws may not adequately address the nuances of drone surveillance. Legislation needs updating to reflect technological capabilities.

3. Standardisation of Training and Certification
• Pilot Competency: Establish standardized training programs and certifications to ensure all operators meet safety and competency requirements.

4. Addressing Environmental Concerns
• Environmental Regulations: Clear regulations are needed to manage the environmental impact of drones, particularly in wildlife areas.

5. International Coordination
• Cross-Border Operations: With companies operating internationally, harmonization with EU and international regulations is essential to facilitate operations and maintain competitiveness.
________________________________________
Other Relevant Issues
1. Public Perception and Acceptance
• Community Engagement: Efforts should be made to educate the public on the benefits of drones to alleviate concerns over privacy and safety.

2. Workforce Development
• Skill Shortages: Addressing the need for skilled professionals in the drone industry through education and training initiatives.

3. Ethical Considerations
• Responsible Use: Establishing ethical guidelines to govern the use of drones, particularly in sensitive contexts like surveillance and data collection.

4. Infrastructure Investment
• Support Facilities: Investment in infrastructure such as drone ports and charging stations to support the growing industry.

5. Encouraging SME Participation
• Reducing Barriers to Entry: Simplify regulatory processes to encourage small and medium-sized enterprises to enter the market, fostering innovation and competition.
________________________________________
Conclusion

The “Drones In Action” report highlights the immense potential of drone technology to revolutionize various sectors in the UK. However, to fully realize these benefits, it is imperative to address the legal challenges that accompany such technological advancements. Regulators play a crucial role in shaping a conducive environment that balances innovation with safety, privacy, and environmental stewardship.

By streamlining regulatory processes, updating legal frameworks, and fostering open communication between stakeholders, the UK can position itself at the forefront of the global drone industry. As we navigate this exciting frontier, collaboration between industry players, regulators, and legal professionals will be key to unlocking the full potential of drones while safeguarding public interests.
________________________________________
Author: Richard Ryan, an experienced drone lawyer specialising in UK aviation law, with 20 years of expertise in navigating the legal landscapes of unmanned aerial systems.

The post Navigating the Skies: Legal Perspectives on the UK’s Drone Revolution appeared first on Blakistons.