UAS (Unmanned Aircraft Systems) Archives - Blakistons

Navigating UK SORA: A Drone Lawyer’s Guide to CAA Decision No. 60

admin.richard — Mon, 06 Jul 2026 09:53:17 +0000

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.

Pathway	What It Means	Legal Significance
Declarative approach	The operator declares that it meets the relevant acceptable means of compliance.	Suitable for lower-risk requirements, but the declaration must still be accurate and supportable.
Agreed compliance basis	The operator and CAA agree in advance how compliance will be demonstrated.	Useful for novel or complex operations where evidence may include testing, analysis or design appraisal.
Compliance evidence approach	The operator submits both the compliance basis and the underlying evidence to the CAA.	The most rigorous route, likely to be required for higher-risk or technically complex operations.

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.

Mitigation	Description	Key Legal Risk
M1A: Sheltering	Relying on people being inside structures.	The aircraft must not be capable of penetrating the relevant structures.
M1B: Operational restrictions	Operating at times or in areas where fewer uninvolved people are present.	Population assumptions must be evidenced and realistic.
M1C: Ground observation	Using observers or technical systems to detect uninvolved people.	Detection capability, observer competence and response procedures must be credible.
M2: Impact mitigation	Reducing impact energy through parachutes, flight termination or design features.	Deployment reliability, minimum altitude, failure modes and secondary hazards must be addressed.

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.

Kinetic Energy	Risk Category	Operator Requirement
Up to 175 joules	Lower hazard	Generally less demanding penetration analysis, subject to the operational context.
175 to 7,000 joules	Medium hazard	Penetration analysis should be conducted against representative structures.
Over 7,000 joules	High hazard	More rigorous evidence is required, potentially including crashworthiness analysis and structural modelling.

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.

UK SORA Issue	AI Governance Standard	Practical Evidence
Operational risk assessment	Lifecycle risk management	Hazard log, AI failure-mode analysis, operating design domain and residual-risk register.
Compliance evidence	Technical documentation	Version-controlled technical file, test reports, software release notes and design appraisals.
Ground observation	Accuracy and human oversight	Detection metrics, false-negative analysis, lighting limits and observer escalation procedures.
Containment	Robustness and cybersecurity	Geo-cage testing, lost-link logic, GNSS spoofing assessment and command-link resilience.
Evidence retention	Record-keeping and auditability	Flight logs, telemetry, AI outputs, incident reviews and corrective actions.

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.

Nyan at Sea: One-Way Effectors, Counter-UAS Law and Defence AI Governance

admin.richard — Mon, 06 Jul 2026 09:42:00 +0000

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.

Governance Area	EU AI Act Benchmark	UK / MOD Equivalent	Application to One-Way Effectors
Risk management	Lifecycle risk management	Safety, security and robustness	Hazard logs for navigation failure, lost link, spoofing, target-data error and launch failure.
Technical documentation	Technical file and system description	Accountability and governance	Configuration records for airframe, launcher, software, payload and mission-planning tools.
Record-keeping	Automatic logging	Transparency and explainability	Mission logs, operator decisions, software versions, AI outputs and telemetry retention.
Human oversight	Human control and intervention	Human-centricity and responsibility	Clear authority for launch, retask, abort, termination and post-strike review.
Cyber resilience	Accuracy, robustness and cybersecurity	Reliability and security	Testing against jamming, spoofing, adversarial inputs, cyber compromise and degraded environments.

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.

UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots

admin.richard — Thu, 11 Jun 2026 17:44:48 +0000

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 practice is now essential.

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.

Law and Guidance Are Not the Same Thing

One of the most common misunderstandings among drone operators is the assumption that everything in the Drone Code or CAA guidance is itself law.

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.

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.

A useful way to think about compliance is:

Green: operating within CAA guidance and published best practice.
Amber: operating within the law but outside guidance.
Red: operating outside the legal framework.

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.

Registration Requirements

Most drones with a camera and weighing more than 100 grams require registration under the Drone and Model Aircraft Registration and Education Scheme.

Operators will generally need both an Operator ID and a Flyer ID.

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.

Importantly, it is the operator who is registered rather than the drone itself.

Universal Rules for All Drone Flights

Maximum Altitude

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.

Visual Line of Sight

Visual Line of Sight remains a central requirement of UK drone regulation.

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.

First Person View Flying

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.

Airspace Restrictions

Many drone prosecutions arise from breaches of airspace restrictions rather than from technical flying errors.

Airspace should be checked before every flight using a reliable and current source of aeronautical information. The information should be refreshed immediately before launch.

Key restriction types include:

Flight Restriction Zones: permanent restricted areas around airports, prisons and protected sites.
Temporary Restrictions: restrictions created for events, security operations and public safety purposes.
NOTAMs: aviation notices which may affect drone operations.

Operators should use modern airspace mapping tools and should not assume that yesterday’s airspace position remains correct today.

A1, A2 and A3 Operational Categories

A1: Flying Over People

The A1 category provides the greatest flexibility. Certain drones under 250 grams may be flown over uninvolved persons, although flight over crowds remains prohibited.

This category generally includes legacy drones under 250g, UK0 and UK1 aircraft, C0 aircraft and C1 aircraft subject to transitional provisions.

A2: Flying Close to People

A2 operations allow flight near uninvolved persons but generally prohibit flight directly over them. Operators normally require an A2 Certificate of Competency.

Certain UK2 and C2 aircraft may operate with reduced separation distances where the applicable requirements are met.

A3: Flying Far from People

A3 operations are intended for open areas away from uninvolved persons and built-up environments.

Operators must generally maintain 50 metres from uninvolved persons and 150 metres from residential, commercial, industrial and recreational areas.

Article 16 Authorisations

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.

Ground Hazards and Article 241

Even where all technical drone requirements are satisfied, operators remain subject to wider safety duties.

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.

Ground hazards may include members of the public, vehicles, buildings, infrastructure, wildlife and protected environmental sites.

Particular care should be taken when operating near Sites of Special Scientific Interest and other environmentally protected areas.

Remote ID Arrives in 2026

One of the most significant developments is the introduction of Remote ID.

Remote ID creates an electronic identification system allowing drone operations to be identified through information transmitted by the aircraft.

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.

Operators should monitor CAA updates closely as implementation progresses.

Night Flying Requirements

Night flying remains permissible within the Open Category.

From 2026, operators will generally require a green flashing light attached to the aircraft.

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.

Insurance and Operational Responsibility

Recreational operators are generally not legally required to carry insurance, although doing so is strongly recommended.

Commercial operators typically require specialist aviation insurance compliant with applicable regulatory requirements.

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.

Conclusion

The 2026 changes represent an evolution rather than a revolution in UK drone regulation.

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.

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.

Disclaimer: This article is provided for general information only and does not constitute legal advice. Specific advice should be sought in relation to individual circumstances.

Richard Ryan is a practising barrister, Arbitrator , drone lawyer, and regulatory specialist with more than 20 years’ 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.

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.

The views expressed in this article are for general information purposes only and do not constitute legal advice.

The post UK Drone Rules from 1 January 2026: A Lawyer’s Practical Guide for Pilots appeared first on Blakistons.

admin.richard — Wed, 03 Jun 2026 16:49:56 +0000

White Paper

Beyond 2019

A New Counter Uncrewed Systems and Air Threat Resilience Strategy for the United Kingdom, After Ukraine and Iran

By Mr Richard Ryan, Barrister, Blakiston’s Chambers · June 2026

Status and method. This paper relies on primary and official sources, supplemented by reputable reporting for incident chronology. All facts are verified as at 2 June 2026. Battlefield figures drawn from active conflict reporting are attributed to their originating source and presented as attributed claims rather than judicially established fact. The paper contains no classified or privileged material. All footnote links are live.

The United Kingdom’s published national counter drone policy; the UK Counter-Unmanned Aircraft Strategy, presented to Parliament as Command Paper 187 on 21 October 2019^[1]; is materially out of date as a strategic document. It remains the only published national strategy in the field for the whole of government, yet it is now approximately six years and seven months old, and roughly three and a half years beyond its own planning horizon.

The strategy was sound for its time. It identified the highest harm illegal uses of small drones; terrorism, smuggling into prisons, disruption of critical national infrastructure; and prescribed layered intervention, industry standards, responder powers and public education.^[2] But it was expressly confined to malicious and illegal use of small aerial drones, in a domestic policing and protective security frame. That frame has been overtaken by operational reality in Ukraine and the Iranian theatre: massed one way attack drones, combined drone and missile salvos, container and special forces launch, dense electronic warfare, fibre optic command links and AI assisted guidance now define the threat.

Subsequent UK documents do not update the 2019 strategy; they work around it. The Defence Drone Strategy (2024),^[3] the Strategic Defence Review 2025,^[4] NPSA’s site specific guidance,^[5] and the Ministry of Defence’s 2026 pursuit of new defeat powers at military sites^[6] together form a patchwork of sectoral adaptations laid over an unrevised core. This paper argues that the 2019 strategy should be retired as a standalone statement and replaced by an integrated Counter Uncrewed Systems and Air Threat Resilience Strategy, supported by a consolidated legal code for detection, disruption and defeat, and by an annual ministerial statement to Parliament.

1. The threat has become a strategic mass system

The central lesson of 2024–2026 is not that drones have become more common but that they have become a strategic mass system — a consumable class of munition and sensor used for saturation, decoying, attrition of intelligence assets, target acquisition and the deliberate erosion of a defender’s cost exchange ratio. On the night of 2 June 2026, Ukraine’s air force reported that Russia had launched 656 drones and 73 missiles in a single overnight barrage, of which 602 drones and 40 missiles were downed or suppressed.^[7]^[8] Single salvos now routinely exceed several hundred drones.

Critical infrastructure has been directly affected. In February 2025 a Russian Geran-2 (Shahed type) drone struck the New Safe Confinement over Chornobyl’s reactor four;^[9] by December 2025 the International Atomic Energy Agency assessed that the structure had lost its primary safety functions, including confinement.^[10] In May 2026 a drone strike caused a fire at an electrical generator on the perimeter of the United Arab Emirates’ Barakah nuclear plant; a civilian reactor site; leaving one unit running on emergency diesel generators.^[11]^[12]

The homeland and deployed force dimension is now concrete for the United Kingdom. In early March 2026 a Shahed type drone struck a runway at RAF Akrotiri in Cyprus; a British Sovereign Base Area; causing limited damage,^[13] and the UK flew defensive sorties and, where requested, acted in the collective self defence of regional allies.^[14] Ukraine’s Operation Spider’s Web (June 2025) had already shown that 117 first person view drones launched from concealed truck borne containers could strike strategic bomber bases far from any front line, damaging more than 40 aircraft, with some guidance reportedly AI assisted.^[15]

A necessary qualification

Not every battlefield lesson maps to the British mainland. The most credible open analysis holds that long range Shahed type strikes on Great Britain would face high attrition because of geography and warning time, while shorter range drones launched from containers or by hostile special forces remain a credible risk to high value assets at home. The policy implication is to discriminate between vectors; not to import foreign assumptions wholesale, and not to dismiss the threat. A refreshed strategy should say so candidly.

2. Why the 2019 strategy can no longer stand alone

2019 provision	Current reality	Assessment
Focus on the highest harm illegal use of small aerial drones in the UK.	Concern now extends to defence sites, CNI in crisis or conflict, and state launched drones and missiles.	Too narrow as a national frame.
Short planning horizon from 2019.	Document is c. 6.6 years old; NPSA requires regular review because methods change quickly.	Formally stale; refresh overdue.
Empower police and responders.	MoD now seeks its own defeat powers at Defence sites because police only authorities are inadequate.	Institutionally outdated.
Aerial drones only.	New Defence policy extends to land and maritime uncrewed systems.	Conceptually outdated.
Counter drone as a discrete problem.	NATO now treats small UAS through hypersonic missiles as one integrated air and missile defence continuum.^[16]	The silo is no longer tenable.

The clearest institutional signal came in February 2026, when the Ministry of Defence reported 266 drone incidents near UK military sites during 2025 (up from 126 in 2024) and sought fresh statutory powers through the Armed Forces Bill; extending beyond aerial drones to land and maritime systems; to allow Defence personnel to defeat drones at their own sites without waiting for police intervention.^[6] When the armed forces must legislate around a framework built for policing to protect their own bases, that framework has expired.

3. The legal framework: developed, but fragmented

Domestic powers have expanded since 2019 but remain complex. The Air Traffic Management and Unmanned Aircraft Act 2021 created bespoke constabulary powers to ground, stop, search, inspect and seize unmanned aircraft, and amended section 93 of the Police Act 1997 to facilitate authorisations for certain counter drone measures.^[17]^[18] In the civil regime, the Civil Aviation Authority’s Direct Remote ID requirements came into force on 1 January 2026 for UK1, UK2, UK3, UK5 and UK6 class drones, with extension to most drones carrying a camera from 1 January 2028.^[19]

Yet lawful defeat is markedly harder than detection. Operational use of a jammer is generally an offence under section 68 of the Wireless Telegraphy Act 2006, and Ofcom has no power to authorise operational use; only narrow trial and research licences in shielded conditions.^[20] Government is separately examining the enforcement framework around jammers.^[21] Kinetic or electronic interference may amount to unlawful property or wireless interference absent proper authorisation; the Act’s own explanatory notes acknowledge as much. Techniques that take over a drone by software may engage the Computer Misuse Act 1990 and the Investigatory Powers Act 2016, and sensing engages the Data Protection Act 2018, the UK GDPR and the Human Rights Act 1998, which requires the state both to protect life from foreseeable threats and to keep its sensing and defeat measures necessary and proportionate. A lawful defeat chain is a designed legal artefact, not an improvisation.

Overseas action sits within international law. The Government’s March 2026 legal position on Iranian regional attacks invoked the collective self defence of allies under Article 51 of the UN Charter, subject to necessity and proportionality and Security Council notification.^[14] Once in armed conflict, drones attract no special category: they are governed by the ordinary rules of distinction, proportionality and precaution applicable to all weapons.^[22]

4. Recommendations

The Government should replace the 2019 strategy with a new instrument covering the whole of government. Five propositions should anchor it:

Integrate, do not append. A single Counter Uncrewed Systems and Air Threat Resilience Strategy spanning the Home Office, MoD, Cabinet Office resilience, CAA, Ofcom, NPSA, the intelligence community, prisons and CNI operators, aligned to NATO’s integrated air and missile defence framework.^[16]
Consolidate the law. A statutory code (or, at minimum, statutory guidance) defining who may detect, disrupt and defeat uncrewed systems, where, against which threat category, under what authorisation, with what recording and what review after an incident — differentiating urban areas, prisons, airports, defence sites and overseas operations.
Adopt a layered baseline that is alert to cost. Use NPSA’s site specific, threat informed model as the national spine,^[23] plugging into a wider air and missile defence architecture for higher end threats, and prioritising defeat options that are low in collateral, deep in magazine and economically rational. A missile fired at every cheap drone is not a strategy; it is a budgetary confession.
Treat industry and export control as readiness. Link procurement, export licensing, sanctions intelligence and sovereign industrial strategy, with secure by design and open architecture requirements across C-UAS procurement. A state that cannot source the components of its own counter drone systems is not strategically autonomous.
Compliance and oversight by design. Require a written legal basis, data minimisation, retention limits and human oversight for every C-UAS deployment by a public authority; subject identification by AI to documented necessity and a review of error rates; and provide Parliament an annual ministerial statement on C-UAS powers, deployments, tests, safety incidents, rights compliance and lessons learned, with NPSA and the ICO involved where domestic surveillance is concerned.

5. Conclusion

None of this discards the 2019 strategy’s best inheritance; its insistence on layered intervention over an optimism founded on gadgets, an instinct NPSA’s later guidance has only reinforced.^[5] The task is not to repudiate 2019 but to lift its sound protective security spine into an architecture wide enough for the threat that now exists: a spectrum of low cost, autonomous and electronically contested uncrewed systems, ranging from nuisance to war. The 2019 strategy answered the question of its decade. It is time to ask the question of this one.

About the author. Mr Richard Ryan is a barrister of Blakiston’s Chambers..

Footnotes & sources (23)

UK Counter-Unmanned Aircraft Strategy, CP 187, presented to Parliament 21 October 2019 (GOV.UK). https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy ↩
UK Counter-Unmanned Aircraft Strategy (HTML version), GOV.UK, published 21 October 2019. https://www.gov.uk/government/publications/uk-counter-unmanned-aircraft-strategy/table ↩
Defence Drone Strategy — the UK’s approach to Defence Uncrewed Systems, GOV.UK, published 22 February 2024. https://www.gov.uk/government/publications/defence-drone-strategy-the-uks-approach-to-defence-uncrewed-systems/defence-drone-strategy-the-uks-approach-to-defence-uncrewed-systems ↩
The Strategic Defence Review 2025 — Making Britain Safer, GOV.UK, published 2 June 2025. https://www.gov.uk/government/publications/the-strategic-defence-review-2025-making-britain-safer-secure-at-home-strong-abroad ↩
NPSA, “Counter Uncrewed Aerial Systems (C-UAS)” specialised guidance. https://www.npsa.gov.uk/specialised-guidance/uncrewed-aerial-systems/counter-uncrewed-aerial-systems-c-uas ↩
Ministry of Defence, “New powers for Defence personnel to defeat drones following doubling of incidents near bases” (266 incidents in 2025, up from 126), GOV.UK, 2 February 2026. https://www.gov.uk/government/news/new-powers-for-defence-personnel-to-defeat-drones-following-doubling-of-incidents-near-bases ↩
“Russia launched 656 drones and 73 missiles” — figures attributed to the Ukrainian Air Force; CBS News, 2 June 2026. https://www.cbsnews.com/news/russia-ukraine-war-major-attacks-missile-drone-kill-several-wound-dozens/ ↩
NPR, “Russian attack on Ukraine kills at least 14”, 2 June 2026 (corroborating launch and interception figures). https://www.npr.org/2026/06/02/nx-s1-5844071/russian-attack-ukraine ↩
Chornobyl New Safe Confinement struck by a Geran-2 (Shahed type) drone, 14 February 2025: Greenpeace Ukraine mission report, 20 March 2025. https://www.greenpeace.org/ukraine/en/news/3504/fifty-percent-of-north-roof-structure-of-chornobyl-new-safe-confinement-shelter-severely-damaged/ ↩
IAEA assessment (December 2025) that the New Safe Confinement had lost its primary safety functions, including confinement (reported via United24/Reuters). https://united24media.com/latest-news/iaea-chornobyls-new-safe-confinement-can-no-longer-contain-radiation-after-russian-drone-attack-14067 ↩
Drone strike causing a generator fire at the UAE’s Barakah nuclear plant, 17 May 2026: Al Jazeera, 17 May 2026. https://www.aljazeera.com/news/2026/5/17/drone-strike-sparks-fire-at-uaes-barakah-nuclear-power-plant ↩
NPR, “Drone strikes UAE nuclear plant”, 18 May 2026 (IAEA: one reactor on emergency diesel generators). https://www.npr.org/2026/05/18/g-s1-122534/drone-strikes-uae-nuclear-plant ↩
Reuters, “Iranian-made drone hits British air base in Cyprus” (RAF Akrotiri runway strike, limited damage), 2 March 2026. https://www.aol.com/articles/iranian-made-drone-hits-british-121630466.html ↩
Summary of the UK Government legal position: the legality of defensive action in respect of Iranian regional attacks, GOV.UK (10 Downing Street), March 2026. https://www.gov.uk/government/news/summary-of-the-uk-government-legal-position-the-legality-of-defensive-action-in-respect-of-iranian-regional-attacks ↩
CSIS, “How Ukraine’s Operation Spider’s Web Redefines Asymmetric Warfare” (117 drones; 40+ aircraft struck; some AI assisted guidance). https://www.csis.org/analysis/how-ukraines-spider-web-operation-redefines-asymmetric-warfare ↩
NATO Integrated Air and Missile Defence Policy, 13 February 2025 (threat spectrum “from small… UASs to all types of cruise and ballistic missiles, including hypersonic”). https://www.nato.int/cps/en/natohq/official_texts_233084.htm ↩
Air Traffic Management and Unmanned Aircraft Act 2021 (c. 12), legislation.gov.uk. https://www.legislation.gov.uk/ukpga/2021/12/contents/enacted ↩
Explanatory Notes to the Air Traffic Management and Unmanned Aircraft Act 2021 (kinetic/jamming measures may amount to unlawful interference; amendment of s. 93 Police Act 1997). https://www.legislation.gov.uk/ukpga/2021/12/pdfs/ukpgaen_20210012_en.pdf ↩
UK Civil Aviation Authority, “Remote ID (RID)” — Direct RID in force from 1 January 2026 for UK1, UK2, UK3, UK5 and UK6 drones; extension from 1 January 2028. https://www.caa.co.uk/drones/regulations-consultations-and-policy-programmes/policy-programmes/remote-id-rid/ ↩
Ofcom, “GPS jamming exercises” — operational use of a jammer is an offence under s. 68 Wireless Telegraphy Act 2006; Ofcom cannot authorise operational use. https://www.ofcom.org.uk/spectrum/frequencies/gps-jamming-exercises ↩
DSIT, “Possession of radiofrequency jammers and the relevant legal framework” (call for evidence), GOV.UK, 2026. https://www.gov.uk/government/calls-for-evidence/possession-of-radiofrequency-jammers-and-the-relevant-legal-framework/possession-of-radiofrequency-jammers-and-the-relevant-legal-framework ↩
ICRC, “FAQ: international humanitarian law and the use of drones in armed conflict” (distinction, proportionality, precaution). https://www.icrc.org/en/article/faq-international-humanitarian-law-drones-armed-conflict ↩
NPSA, “Countering Threats from Uncrewed Aerial Systems — Making Your Site Ready”. https://www.npsa.gov.uk/resources/c-uas-making-your-site-ready ↩

The post appeared first on Blakistons.

The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft

admin.richard — Mon, 01 Jun 2026 11:14:30 +0000

There’s a particular kind of frustration that comes from practising in a field that everyone assumes is covered by a law that, on close reading, barely mentions it. Drone law is one of those fields. People hear “AI Act” and “drones” in the same breath and assume the two slot neatly together; that the great European regulatory machine has, somewhere in its 113 articles, a tidy chapter telling me when my client’s counter-UAS system crosses a line. It doesn’t. And the gap between what people assume and what the text actually says is where most of my work now lives.

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.

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.

What the UK Drone Industry Can Learn from EASA’s Adoption of SORA 2.5

admin.richard — Tue, 30 Sep 2025 10:57:46 +0000

By Richard Ryan, Barrister & Drone Lawyer •
30th September 2025

Introduction

On 29 September 2025, the European Union Aviation Safety Agency (EASA) published ED Decision 2025/018/R, updating the Acceptable Means of Compliance (AMC) and Guidance Material (GM) to Implementing Regulation (EU) 2019/947. This update introduces the European version of the Specific Operations Risk Assessment (SORA) 2.5, developed by the Joint Authorities for Rulemaking on Unmanned Systems (JARUS).

Although the UK has left the EU regulatory framework, these developments are highly relevant. UK operators, manufacturers, and regulators can learn much from how EASA is simplifying compliance, clarifying roles, and promoting harmonisation across Member States.

What Changed under SORA 2.5?

Simplification of procedures: Ambiguities from earlier SORA versions have been removed, making it easier for operators and authorities to understand their obligations.
Clarity of roles: Responsibilities are now more clearly divided between operators, designers, and manufacturers. For example, design verification reports (DVRs) from EASA are required at SAIL IV, and type certification is required at SAIL V and VI.
Terminology alignment: EU-specific terms replace JARUS wording. For instance, “EVLOS” has been dropped in favour of “BVLOS with airspace observer”.
Containment requirements: Refined criteria for ground risk buffers and adjacent ground areas, particularly relevant for BVLOS and urban operations.
Flexibility for competent authorities: NAAs can use direct assessment, recognised entities, or qualified entities to review compliance.
Removal of weak cybersecurity rules: EASA stripped out JARUS’s cybersecurity provisions, deeming them disproportionate, but stressed that vulnerability assessments remain best practice.

Lessons for the UK CAA

Consistency and clarity – EASA has responded to industry feedback by clarifying operator versus manufacturer responsibilities. The UK’s guidance could benefit from similar precision, particularly in BVLOS authorisations.
Streamlining approvals – The two-phase SORA process (Phase 1 for risk identification, Phase 2 for compliance evidence) allows operators to obtain early regulatory feedback. This approach could make the UK’s OSC process faster and more predictable.
Population density mapping – EASA now recommends more accurate, dynamic maps to avoid over- or under-estimating risk in commercial and recreational areas. The UK could adopt a similar model, especially for urban drone delivery corridors.
Terminology alignment – Dropping “EVLOS” in favour of “BVLOS with AO” reflects operational reality and removes confusion. The UK should consider whether maintaining unique terminology helps or hinders international harmonisation.
Cybersecurity gap – By removing JARUS’s rules but encouraging vulnerability assessments, EASA has left space for proportionate, risk-based security. The CAA could similarly mandate cybersecurity risk assessments in line with wider aviation resilience standards.

Best Practice for UK Drone Pilots and Operators

Adopt SORA 2.5 methodology voluntarily – Even though the UK hasn’t formally adopted it, operators preparing risk assessments will benefit from aligning with European standards, especially if seeking approvals abroad.
Keep clear records – Maintain compliance matrices and comprehensive safety portfolios (CSPs) as outlined in SORA 2.5. This not only supports OSC applications but also protects operators in audits and insurance claims.
Use accurate population data – Don’t rely solely on outdated maps; supplement with local knowledge, real-time data, or site surveys to avoid underestimating risk.
Plan robust contingency procedures – Ensure abnormal and emergency procedures are well defined, tested, and rehearsed with crew. The new focus on containment means that “fly-away” risks must be demonstrably controlled.
Stay ahead on cybersecurity – Even though not mandated, conduct vulnerability assessments for command-and-control links and data storage. Cyber weaknesses could undermine insurance and liability cover.

Conclusion

EASA’s adoption of SORA 2.5 is a significant step towards regulatory clarity and harmonisation across Europe. The UK CAA should take note: simplifying authorisations, clarifying roles, and embracing proportionate risk-based approaches would strengthen the UK’s position as a leader in drone regulation.

For operators and pilots, the message is clear: best practice means anticipating international standards, not just meeting the minimum domestic requirement.

At Blakiston’s Chambers we advise drone operators, manufacturers, and service providers on all aspects of UK drone law, including airspace rights, regulatory compliance, and litigation risk. If your business is concerned about trespass or overflight liability, our team can help.

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

Airprox 2024294 – What Actually Happened at RAF Lakenheath?

admin.richard — Fri, 27 Jun 2025 13:41:37 +0000

Airprox 2024294 – What Actually Happened?

On the night of 22 November 2024 at 21:51 UTC, a National Police Air Service (NPAS) EC135 helicopter operating near RAF Lakenheath reported multiple “drones” manoeuvring around it. In reality, the objects were USAF F15 fighters engaged in authorised night training in Class G airspace (surface–FL150), coordinated by Lakenheath Approach (“Overlord”).

Summary of Key Facts:

Closest Point of Approach (CPA): 1 NM horizontal / 1900 ft vertical separation (recorded).
ATC Services:
- EC135 – Basic Service (no traffic information guaranteed).
- F-15s – Traffic Service (received information about the EC135).
Misidentification Factors:
- EC135’s TCAS did not display the F-15s.
- F-15 lighting did not resemble standard civil aircraft lighting.
- The crew believed the lights were drones due to their apparent behaviour and lack of TCAS confirmation.

The UK Airprox Board (UKAB) concluded that there was no risk of collision (Risk Category E) and attributed the report to misidentification and situational awareness breakdown rather than unsafe flying.

Why This Matters to Drone Operators

1. Misidentification Risk

Even experienced police aircrew using EO/IR cameras mistook military jets for drones. This shows how easily drone operators can be blamed for aerial events they weren’t involved in.

2. Electronic Conspicuity Limitations

The EC135’s TCAS did not detect the F-15s despite them squawking Modes A and C. This highlights the ongoing limitations of EC systems in complex or mixed-use airspace, particularly at night.

3. ATC Service Levels – Know the Difference

Under a Basic Service, ATC is not required to provide traffic information. Drone operators should consider requesting a Traffic Service or Deconfliction Service for BVLOS, urban, or sensitive operations.

Public Perception: A Persistent Challenge

“Drone blame” is the default: Unidentified lights in the sky are often assumed to be drones, fuelling public concern and regulatory overreaction.
Poor understanding of airspace rules: The public often assumes ATC sees and controls everything — which is untrue in Class G.
Coordination gaps: The police helicopter tasking was not pre-notified to the USAF. This shows the need for better operational coordination.

Risk Assessment for UK Drone Operations

Potential Scenarios and Risk Levels:

Misidentification by other aircraft:
- Likelihood: Medium
- Severity: Low to Medium
- Risk Level: Moderate overall, but High reputationally
No traffic info under Basic Service:
- Likelihood: Medium
- Severity: Medium
- Risk Level: Moderate
Public/media backlash from perceived near-miss:
- Likelihood: High
- Severity: High
- Risk Level: High (especially for commercial operators)

Key Mitigations for Drone Operators:

Use dual EC systems (ADS-B OUT and ground-based detect-and-avoid).
Maintain a telemetry and flight log archive for every operation.
Pre-notify military ATC when operating near MOD airspace.
File CANPs, NOTAMs, or Temporary Danger Areas when applicable.
Train pilots to request an upgrade to Traffic Service where required.

Legal and Regulatory Observations

SERA.3205 and ANO Article 239 set the standard for proximity liability. Keep compliance well-documented.
Expect growing pressure for mandatory electronic conspicuity, with incidents like this cited in policy.
If blamed in media or police statements without evidence, drone operators may have grounds for defamation or economic loss claims. Get legal advice promptly.

Final Thoughts

This wasn’t a drone incident — but it could have been perceived as one.

The lesson? Control the narrative by controlling the data.
Record everything. Secure it. Share it when necessary. With the right evidence, drone operators can protect themselves from false blame and help improve UK airspace safety.

About the Author

Richard Ryan is a UK barrister and aviation lawyer specialising in drone regulation, UAS integration, and counter-drone law. A Fellow of the Chartered Institute of Arbitrators, he advises police forces, government bodies, and commercial operators on airspace compliance and emerging UTM frameworks. He is also completing a PhD on airspace integration and unmanned traffic management at Cranfield University.

The post Airprox 2024294 – What Actually Happened at RAF Lakenheath? appeared first on Blakistons.

What’s relevant for Drone Operators when the drone crashes – lessons learned from Alauda Airspeeder MkII?

zeroabove — Wed, 24 Feb 2021 15:49:39 +0000

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

Legal Framework of UTM for UAS – 2020 Digital Avionics Systems Conference

zeroabove — Wed, 23 Dec 2020 13:07:52 +0000

2020 Digital Avionics Systems Conference

UTM Operational Concept

The legal framework for UTM (Unmanned aircraft system Traffic Management) will need to develop as regulators grapple with issues that relate to legal responsibility and accountability as the proliferation of drones increases.

Unmanned Aircraft System (UAS) Traffic Management (UTM) Enabling Civilian Low-altitude Airspace and Unmanned Aircraft System Operations.

What is the problem?

Many beneficial civilian applications of the UAS have been proposed, that include goods delivery, medical deliveries, infrastructure surveillance, search and rescue and agricultural monitoring. Currently, there is no established UTM infrastructure to enable and safely manage the widespread use of BVLOS low-altitude airspace and UAS operations, regardless of the type of UAS.

To read the full article click here.

The post Legal Framework of UTM for UAS – 2020 Digital Avionics Systems Conference appeared first on Blakistons.