Drone Law | UK SORA | CAA Regulation | AI Governance

Summary: CAA Decision No. 60 marks a significant development in the regulation of Specific category drone operations in the UK. Coming into force on 1 October 2026, it updates the UK SORA framework and introduces clearer expectations around compliance evidence, ground-risk mitigation, containment, kinetic energy analysis and evidence retention. For operators, the message is clear: compliance is no longer just a narrative safety case. It must be evidenced, retained and auditable.

1. Why Decision No. 60 Matters

The UK’s lower airspace is becoming increasingly complex. Beyond Visual Line of Sight operations, drone delivery, infrastructure inspection, emergency services use, autonomous routing and higher-risk commercial UAS activity all require a more mature regulatory framework.

CAA Decision No. 60 updates the Acceptable Means of Compliance and Guidance Material for UK Regulation (EU) 2019/947. In practical terms, it strengthens the UK Specific Operation Risk Assessment, or UK SORA, for operators seeking authorisation in the Specific category.

The legal significance is that UK SORA is becoming a structured assurance methodology. Operators must not merely state that an operation is safe. They must demonstrate that the aircraft, procedures, people, operational volume, ground environment, airspace risks, mitigations and emergency arrangements meet the required level of safety.

2. UK SORA Is Not a Box-Ticking Exercise

UK SORA exists to support the operational risk assessment required for Specific category operations. It considers both ground risk and air risk, then applies mitigations and operational safety objectives according to the Specific Assurance and Integrity Level, or SAIL.

The updated framework is particularly important because it clarifies how operators must gather, present and retain compliance evidence. This is a move away from generalised operational assertions and towards aviation-grade documentation.

3. The Three Compliance Pathways

Decision No. 60 identifies three broad routes for demonstrating compliance.

Operators must also retain compliance evidence for the duration of the operational authorisation and for three years after operations under that authorisation cease. That evidence may become critical in a CAA audit, incident investigation, insurance dispute or civil claim.

4. Ground Risk: What Happens If the Drone Falls?

Ground risk is central to UK SORA. The law is concerned not only with whether the drone can fly, but with what happens if it fails. Decision No. 60 provides more detailed guidance on how operators may reduce ground risk.

5. Kinetic Energy and Penetration Risk

Decision No. 60 gives particular importance to kinetic energy. This matters because it converts safety claims into measurable injury-risk analysis.

Operators should not rely on generic manufacturer statements. They need platform-specific evidence: mass, velocity, terminal impact behaviour, parachute performance, battery fire risk and representative structural analysis.

6. Containment and Fly-Away Risk

Containment is a central pillar of the updated UK SORA framework. It asks whether the unmanned aircraft can be kept within its operational volume and ground risk buffer, even after failure or loss of control.

For lower-risk operations, containment may be assessed qualitatively through design appraisal and procedural evidence. For higher-risk operations, the CAA may expect quantitative probability targets, such as demonstrating that the probability of exiting the relevant volume or buffer is below specified thresholds per flight hour.

Containment evidence may include geo-caging, tethering, independent flight termination systems, lost-link logic, command-and-control resilience, navigation integrity, power-system independence and emergency procedures.

7. EU AI Act and UK AI Standards

Decision No. 60 is not an AI regulation. However, many modern drone operations increasingly rely on AI-enabled functions, including detect-and-avoid, automated route planning, computer vision, landing assistance, ground-person detection, predictive maintenance and autonomous contingency management.

The EU AI Act is relevant as a benchmark for risk management, technical documentation, record-keeping, transparency, human oversight, robustness and cybersecurity. The UK does not currently have a single equivalent UK AI Act. Instead, it follows a sector-led, principles-based model based on safety, security and robustness; transparency and explainability; fairness; accountability and governance; and contestability and redress.

8. Data Protection and Surveillance Risk

Many Specific category operations involve cameras, thermal imaging, mapping payloads or AI-enabled object recognition. UK SORA primarily addresses safety, but operators must also consider privacy, data protection and surveillance risk.

If cameras or AI systems detect uninvolved persons, personal data may be captured, stored or analysed. Operators may need a data protection impact assessment, retention limits, access controls, privacy notices and clear rules on secondary use.

9. What Operators Should Do Before 1 October 2026

Operators should review their safety cases and evidence packs now. In particular, they should check:

• Aircraft mass, speed, kinetic energy and terminal velocity;
• Ground-risk assumptions and population-density evidence;
• Sheltering, operational restriction and observation claims;
• Parachute, flight termination and impact mitigation evidence;
• Containment evidence, including geo-caging and lost-link logic;
• AI-enabled functions, including detect-and-avoid and automated decision-support tools;
• Evidence retention systems;
• Supplier contracts for access to technical data.

10. Bottom Line

CAA Decision No. 60 marks a shift from descriptive drone safety cases to structured assurance. Operators must now be able to prove their safety claims through coherent, retained and auditable evidence.

The most important development is the convergence between aviation safety and AI governance. UK SORA asks whether the drone operation is safe. The EU AI Act and UK AI principles ask whether automated systems are risk-managed, documented, robust, explainable, secure and subject to human oversight. For modern drone operations, those are increasingly the same question.

Compliance is not what the operator says it does. Compliance is what the operator can prove.

About the Author

Richard Ryan is a barrister, Chartered Arbitrator and specialist in drone law, aviation regulation and artificial intelligence. He advises operators, manufacturers and public bodies on UK CAA regulation, UK SORA, BVLOS operations, AI governance and commercial drone operations. He is currently undertaking a PhD at Cranfield University researching the legal framework for autonomous aviation and future airspace integration.

This article is general legal commentary and does not constitute legal advice.

The post Navigating UK SORA: A Drone Lawyer’s Guide to CAA Decision No. 60 appeared first on Blakistons.

Drone Law | Counter-UAS | Defence AI | 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, counter-UAS defence, export controls and AI governance.

1. Why the Nyan Trial Matters

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.

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.

2. From Drone Novelty to Combat Mass

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.

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.

3. Autonomy: The Legal Question Is What the Machine Decides

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.

Commanders and lawyers should ask:

• Does the system merely navigate to a human-selected target?
• Does it detect, classify, prioritise or select targets?
• Can it be retasked, recalled, aborted or terminated after launch?
• What happens if GPS is jammed, spoofed or degraded?
• What mission data and operator decisions are recorded?

Those questions determine whether the system can be used consistently with distinction, proportionality, precautions in attack and applicable rules of engagement.

4. Article 36 Weapons Review

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.

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.

5. EU AI Act and UK AI Standards

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.

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.

6. Maritime Launch Changes the Legal Burden

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.

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.

7. The Counter-UAS Mirror

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.

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.

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.

8. Export Controls and Procurement Risk

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.

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.

9. Bottom Line

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.

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.

About the Author

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

This article is general legal commentary and does not constitute legal advice.

The post Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance appeared first on Blakistons.

The newsletters keep landing in my inbox with their countdowns. The latest one fixes on 2 August; the date the AI Office acquires real teeth over general-purpose AI models. I read these updates the way a coastal town reads tide tables: not because every wave matters to me, but because I need to know which ones will reach the door. So let me work through what this particular tide actually touches, from the perspective of someone who spends their days arguing about machines that fly.

The autonomy problem nobody wants to define

Start with the thing that makes drones legally interesting in the first place: autonomy is a spectrum, and the law hates spectrums.

A consumer quadcopter holding position in a breeze is running control loops that would have been called “artificial intelligence” in a 1980s research paper. A military loitering munition selecting between candidate targets is doing something most people would unhesitatingly call AI, and find alarming. Between those two poles sits an enormous, messy middle; obstacle avoidance, automated return-to-home, “follow me” tracking, swarm coordination, automated target recognition that merely flags rather than decides. Where on that spectrum does a drone become an “AI system” in the meaning of Article 3?

This matters enormously and almost nobody asks it cleanly. The Act’s definition turns on a system that infers, from inputs, how to generate outputs that influence environments. Plenty of drone autonomy stacks meet that bar comfortably. Plenty of others; deterministic flight controllers executing fixed logic; arguably don’t. I have sat across the table from engineers who insist their navigation system is “just maths,” and they’re not entirely wrong, but “just maths” is also a fair description of every neural network ever trained. The line is not where intuition puts it.

Why the military carve-out is a trap, not a shield

Here is where I watch clients relax too early.

The AI Act contains an exclusion for systems used exclusively for military, defence or national security purposes. Counter-drone work, in particular, loves to shelter under this. The reasoning goes: we detect and defeat hostile UAS, this is inherently a security function, therefore the Act doesn’t reach us. Lovely. Except “exclusively” is doing ruthless work in that sentence, and the dual-use reality of this entire sector makes the exclusion far narrower than people want it to be.

The same RF-detection and optical-tracking stack that protects an airbase gets sold, with a different sticker, to protect a stadium, a prison, a private estate. The moment that system has a civilian commercial life; the moment it is placed on the EU market for protecting critical infrastructure rather than fighting a war; the exclusion frays. And critical infrastructure protection is precisely the kind of use the high-risk classification regime is built to capture. A counter-UAS platform that automatically classifies an incursion and cues a response near an airport is not obviously outside the high-risk net just because its cousin wears camouflage.

The targeted consultation on the high-risk classification guidelines, open until late June, is therefore not abstract bureaucracy to me. Those guidelines are where the boundary between “this is a security tool, leave it alone” and “this is a high-risk system, document everything” will actually get drawn through worked examples. Anyone in this sector who isn’t reading those drafts is choosing to be surprised later.

Article 50 and the drone you can’t see

Now the part that genuinely changes behaviour on the ground.

Article 50’s transparency obligations don’t care about risk tiers. They bite on situations; and one of those situations is biometric categorisation, another is emotion recognition, and another is content that interacts with or affects people. Picture the increasingly common deployment: a drone with a camera doing crowd monitoring, perimeter patrol, or event security. The instant that payload starts categorising people by biometric attributes, the deployer owes the exposed individuals notice. You cannot quietly run biometric categorisation from 120 metres up and treat the altitude as a privacy shield. The obligation attaches to what the system does, not to how far away the lens sits.

I find this is the provision that catches operators off guard, because it cuts against the entire instinct of aerial surveillance, which is to be unobtrusive. The law is, in effect, telling a category of drone operator that unobtrusiveness is now sometimes unlawful. That is a genuinely interesting collision between the technology’s reason for existing and the regulation’s reason for existing, and it is going to generate litigation.

The sandbox that slipped a year

There was a small piece of news in the recent updates that I suspect most readers skimmed: the establishment deadline for regulatory sandboxes has been pushed from August 2026 to August 2027.

For most industries that’s a footnote. For drones it’s meaningful, because the sandbox model is arguably better suited to unmanned aviation than to almost any other AI domain. We already have a mature culture of supervised, geographically-bounded testing; segregated airspace, specific operational risk assessments, temporary danger areas. A regulatory sandbox is conceptually just that culture extended from airworthiness into algorithmic compliance. The delay means the one mechanism that could let a counter-UAS startup test automated-response logic on real incursions, under supervision, with some shelter from fines, won’t materialise on the original timetable. The companies most in need of a structured way to prove their systems are safe will spend another year improvising compliance instead. Whether that protects the public or merely protects incumbents is the kind of question I find genuinely unresolved.

What I’m telling clients

The honest summary I give, stripped of comfort, runs roughly like this. The August date isn’t your date; it’s aimed at the makers of large general-purpose models, and most drone autonomy doesn’t live there. But the regime those powers belong to is the same regime whose high-risk rules and Article 50 duties absolutely will reach you, and the classification guidelines being drafted right now are where your fate gets decided. Don’t wait for enforcement to tell you which side of the line you’re on. The structured dialogue the AI Office favours means the first contact is likely to be a request for documentation, not a fine; which means the clients who survive comfortably are simply the ones who wrote the documentation before anyone asked.

Drones made autonomy visible; something you can point at in the sky. That visibility is exactly why this sector will be among the first places the AI Act’s abstractions get tested against physical reality. I’d rather my clients be the test case that wins than the cautionary one. The tide tables are right there in my inbox. The only real choice is whether to read them.

This is not legal advice; if you’re making compliance decisions about a specific system, get advice tailored to it.

About the author
Richard Ryan is a Direct Access Barrister at Blakiston’s Chambers, and a chartered arbitrator and accredited mediator, specialising in drone and counter-drone law. He advises operators, manufacturers, UTM providers, insurers and public bodies across the full UAS spectrum — regulatory permissions and BVLOS approvals, C-UAS deployment at airports, prisons and critical infrastructure, data and privacy, liability and high-value disputes. Instruct him directly or through solicitors.

The post The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft appeared first on Blakistons.

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.

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.

“`

The post Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities appeared first on Blakistons.

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

The post What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5 appeared first on Blakistons.

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.

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?

2. The operators Operating Safety Case (OSC) contained several statements that were shown to be untrue. What does your OSC state?

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?

4. The CAA were not present at the test flight. Why not invite the CAA to attend the test flight?

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?

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.

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

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;

9. If you have a number of transmitters as part of your OSC that relate to redundancy, don’t leave them in the workshop!

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

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;

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;

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!

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?

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;

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;

17. There are a number of amendments with respect to safety recommendations to CAP 722, which are:

1. 1. detailed evaluation of any unmanned aircraft systems that use on-board systems to mitigate risks with risk severity classifications of “major, hazardous or catastrophic.”
   2. 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;
   3. 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;
   4. 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;
   5. the CAA are to provide examples of unmanned aircraft system safety systems;
   6. 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;
   7. 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;
   8. minimum requirements for the monitoring of high-voltage stored energy devices to ensure safety of operations are recommended;
   9. operators of unmanned aircraft systems should have an effective safety management system in place prior to issuing an operational authorisation;
   10. 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;
   11. 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;

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 info@blakistons.com

The post What’s relevant for Drone Operators when the drone crashes – lessons learned from Alauda Airspeeder MkII? appeared first on Blakistons.