drone operations Archives - Blakistons

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

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

By Richard Ryan, barrister and drone lawyer

Constructive outcome, practical lessons. A technical proximity breach was confirmed, a more serious allegation was dismissed, and there are clear takeaways that raise standards on evidence, cooperation and public safety.

Outcome at a glance

Count 1 (conviction): Operating an unmanned aircraft close to the site of an ongoing emergency response — Air Navigation Order 2016 Articles 265B(3), 265B(5)(j) and 265F(3)(c) (reflecting UAS.OPEN.060(3)).
Count 2 (dismissed): Obstructing or hindering emergency workers — Emergency Workers (Obstruction) Act 2006, sections 1 and 4 — no case to answer.
Sentence: £300 (reduced from £2,500). Deprivation order refused — the client’s equipment will be returned.

Competence, cooperation and public interest flying

The client is an experienced operator with hundreds of hours and thousands of flights, combining sound aviation literacy with routine work around public interest incidents. On the day in question, the client used aircraft tracking tools and air band monitoring, maintained a conservative standoff where no formal cordon existed, and landed promptly when requested by police. This was a measured and safety first response in a dynamic setting.

Lesson 1: Telemetry clarity

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

Keep a clean thin line map and a forensic overlay with timestamps for take off, orbit points, return to home and landing, plus measured distances to fixed features.
Use a thin line that clearly shows accurate telemetry when placed on a map, not a thick line that obscures part of the map.

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

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

Build redundancy: back up app and controller logs after each flight, use screen recordings of the flight user interface, and capture independent stills or video.
For sensitive assignments, consider periodic DAT offloads in advance.

Five straightforward commitments

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

Technical reference: cross motorway separation

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

Assumptions from UK highway standards

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

Baseline components

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

Real world lateral separation (verge to verge)

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

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

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

Lean reading (narrow phrasing)

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

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

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

Add altitude for slant distance

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

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

Practical effect: even before adding any field offset inside the field beyond the verge, cross motorway separation is around 36 to 38 m. Any field offset adds to that figure. Slant range increases further with altitude.

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

Bottom line

This is a constructive outcome. The most serious allegation fell away, the fine is modest, and the client retains their equipment. More importantly, the experience is being used to lead on best practice: clearer telemetry, stronger data resilience and exemplary on scene conduct, supporting emergency services, informing the public and keeping UK skies safe.

About the author

Richard Ryan is a Barrister (Direct Access), Mediator and Chartered Arbitrator based in the UK, specialising in drone and counter-drone law, aviation regulation, and complex commercial disputes. He advises operators, insurers and public bodies on SORA/AAE approvals, BVLOS programmes, privacy/data governance, and risk allocation across the drone ecosystem.

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

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

Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities

admin.richard — Tue, 28 Oct 2025 08:05:36 +0000

“`By Richard Ryan, barrister and drone lawyer

What the paper actually shows (evidence you can cite)

Insurers say risk is intrinsically low; very few third-party injury claims; risk has reduced over the decade with better tech/training. (pp. 9–11)
UK’s ‘zero-risk + case-by-case’ stance hasn’t produced safer skies than more prescriptive/permissive regimes (US/EU/Canada/Singapore); it has delayed progress. (pp. 12–13)
Net-risk lens: drones remove more risk than they introduce (e.g., falls from height, confined spaces, helicopter exposure). (pp. 14–18)
BVLOS doesn’t materially increase risk where well-managed; biggest predictors are location and safety management. (pp. 10–11, 19–22)
Incident data 2022–24: commercial operations show zero fatalities across UK, US, EU, Canada, Singapore; only a handful of serious injuries. (Appendix + country sections, pp. 55–61)
SORA friction/cost: UK SORA application at SAIL II is £3,495; mitigations/AMC still qualitative ? “OSC-style” uncertainty persists. (p. 35)
“Picking winners”: five BVLOS priorities (emergency response, powerlines, maritime SAR, rail, crop spraying). (pp. 6, 25–33)
Policy levers: shift to digital PDRAs for repeatable, low-risk scenarios; reuse prior approvals; model on EU PDRAs/Canada’s lower-risk BVLOS. (pp. 36–37; Appendix 1)
Emergency services gap: the old standing exemption (E4506) lapsed; routine BVLOS now hard to get—BTP resorted to State Aircraft rules. (p. 27)
Comparative table (risk models, UTM status, Remote ID, scale-up reality) explains why the UK feels “high-friction”. (p. 52)

Regulatory & enforcement issues to flag (and build matters around)

Incoherent risk calibration: the UK treats many Specific-category ops as high-risk despite cross-market low incident severity and strong insurer data. (pp. 9–13, 55–57)
Process opacity & cost-burden: SORA mitigations/AMC are qualitative ? inconsistent asks; high fees despite narrow temporal/spatial grants. (p. 35)
Emergency-services capability gap: loss of E4506 creates avoidable delay/risk; forces work-arounds (State Aircraft) rather than transparent PDRA. (p. 27)
AAE not yet a permissioning tool: policy concept ? scalable authorisation path (contrast EU PDRA-G03 for linear infrastructure). (pp. 28–31, 36)
Net-risk inversions: requirements like “observer in a boat” for coastal EVLOS can increase system risk and cost vs. sensor-driven shore control. (p. 21)
Data transparency: the UK has many “record-only” entries; EU public access is patchy; hard for operators/insurers to benchmark safety cases publicly. (pp. 54–61)

Practical exposure points for stakeholders

Insurers: common declinature trip-wires—ops outside the authorisation envelope; poor log preservation; weak maintenance/firmware governance. (pp. 9–11, 35–36)
Operators/pilots: SORA drift, local land-use limitations, and fragmented permissions across linear corridors; evidence-pack discipline needed. (pp. 28–31, 35–36, 56–57)
Associations/community: need bilingual templates/FAQs and incident learning loops; emphasise the airspace vs land-use distinction to reduce friction. (inferred)
Public bodies (blue-light, MCA, NR, utilities): proven benefits blocked by bespoke approvals—strong case for sector PDRA playbooks. (pp. 26–33, 36)

What this means for drone pilots, operators, and companies

As a drone lawyer, my reading of the PwC paper is that the safety record increasingly supports predictable, rules-based authorisations, but the UK still applies bespoke processes that create delay, cost and legal uncertainty. The winners will be those who treat compliance as an operational capability, not a paperwork chore.

Implications for Drone Pilots

Documentation is defence: retain native telemetry, app/controller logs, and pre-flight risk assessments. These are crucial in insurer claims and any CAA inquiry.
VLOS/BVLOS discipline: be explicit about how VLOS was maintained (or the BVLOS mitigations used). Ambiguity here is a common enforcement and insurance pain point.
Privacy on site: where people are identifiable, prepare a simple lawful-basis note and signage plan; it reduces complaint/escalation risk significantly.

Implications for Operators

Align your OA/ops manual with SORA and AAE logic: show how mitigations reduce both air and ground risk. Clear mapping cuts questions and accelerates approvals.
Design for repeatability: build PDRA-ready evidence packs for your most common jobs (e.g., rail/powerline corridors) so each new mission is a variation, not a reinvention.
Insurance resilience: standardise maintenance/firmware baselines and battery care logs; many declinatures stem from gaps here, not from the incident itself.
Contracts that reflect reality: flowing down responsibilities to subcontractors (airworthiness, data protection, incident reporting) reduces exposure and smooths procurement.

Implications for Drone Companies & Enterprise Users

Board-level accountability: appoint a named senior responsible owner (SRO) for UAS operations with decision logs—critical if decisions are later examined in court or by regulators.
Data governance as an asset: implement DPIAs where warranted, role-based access to imagery, retention/deletion schedules, and breach protocols. This increases tender scores and reduces enforcement risk.
Public value narrative: quantify how drone tasks remove traditional risks (work at height, road possessions, helicopter hours). This “net-risk” case supports proportional, scalable permissions.

Where legal support helps, assists, and mitigates

Approvals & permissions: structuring SORA/AAE applications with proportional mitigations, re-using prior evidence, and narrowing scope to reduce fees and conditions.
Policy & appeals: challenging irrational or net-risk-increasing conditions; seeking clarifications; and preparing proportionate alternatives that the regulator can accept.
Privacy & data: lawful-basis memos, DPIAs, signage/LLN templates, and response playbooks for complaints or subject access requests.
Insurance & claims: coverage mapping, notification strategy, and evidence preservation to avoid declinature; subrogation prospects where third parties contributed to loss.
Contracts: allocating risk cleanly across clients, operators and subcontractors (indemnities, limitation, IP/data ownership, incident reporting).

Bottom line: the sector is safe and maturing. Those who can demonstrate their risk controls, evidence compliance, and standardise approvals will grow fastest—with fewer legal shocks along the way.

Talking points for meetings & panels

Same safety, slower UK growth: insurers and incident data show low intrinsic risk—authorisations should be predictable and prescriptive, not bespoke. (pp. 9–13, 36–37)
Digital PDRAs now: for repeatable BVLOS (powerlines/rail/SAR/maritime/agri)—reuse evidence from prior OSCs; mirror EU PDRA/Canada logic. (pp. 25–33, 36)
Emergency drones need an emergency rulebook: the E4506 gap is pushing forces into State Aircraft work-arounds. (p. 27)
Incident reality: zero fatalities in 2022–24 across major markets; claims are mainly minor property/equipment—calibrate conditions accordingly. (pp. 55–61; pp. 9–11)

“`

The post Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities 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.

Trespass by Drones: Is Section 76 Civil Aviation Act 1982 Fit for Purpose?

admin.richard — Tue, 30 Sep 2025 09:51:14 +0000

Blakiston’s Chambers – Insight for Drone Operators •
30th September 2025

Why this matters for drone companies

The question of whether a drone operator can be sued for trespass when flying over private land is no longer a theoretical debate. With drones now routinely used for surveying, deliveries, inspections, and filming, landowners are increasingly asking whether they can stop flights above their property.

At the heart of this issue lies section 76 of the Civil Aviation Act 1982. Originally drafted for manned aviation, it has never been fully adapted to the realities of drones flying close to the ground, often well below 400 feet.

Recent High Court cases – Anglo-International Upholland Ltd v Wainwright (2023) and MBR Acres Ltd v Curtin (2025) – have thrown the law into sharper focus. For drone operators, the practical question is whether your drone can legally enter the airspace above a neighbour’s land without risking an injunction or damages claim.

Trespass: the basic position

Trespass is normally straightforward: step onto someone’s land without permission, and you’re liable – even if you cause no harm. Landowners don’t need to prove loss; mere entry is enough.

But what about airspace? Does a landowner “own the sky” above their property? Historically, English law used the maxim cujus est solum, ejus est usque ad coelum – whoever owns the soil owns all the way up to the heavens. Courts have long since rejected that absolute view. Instead, the law recognises ownership only of the airspace “necessary for the reasonable enjoyment of the land”.

For manned aircraft, Parliament drew a compromise in section 76(1): flights at a “reasonable height” cannot be challenged as trespass or nuisance. But what is a “reasonable height” when drones are often flown at 50 metres, 20 metres, or even lower?

Bernstein and the buffer zone

In Bernstein v Skyviews (1978), a landowner sued after an aircraft flew hundreds of feet above his estate to take photographs. The court held that this was not trespass, because the aircraft was too high to interfere with the landowner’s use of his land.

That decision gave us a rough principle: landowners control only the slice of airspace that matters to their ordinary use of land. The problem is that drones now operate in precisely that slice – near buildings, gardens, roads, and industrial sites – where interference with land use is most likely.

The new drone cases

1. Anglo-International (2023)

Drone flights over a derelict college were used to capture images which encouraged trespassers to enter the site. The judge treated the flights as mischievous and granted an injunction, holding that section 76 did not protect the operators.

The ruling was short and did not carefully analyse airspace ownership or flight height, but it showed courts are willing to act against drone flights if their purpose is seen as facilitating trespass or mischief.

2. MBR Acres (2025)

Animal rights campaigners used drones to film over a research facility. Some drones were flown as low as the height of a single-storey building, but evidence on height and operators was inconsistent.

The judge refused to grant an injunction. He accepted that flights at 50 metres or more did not interfere with the use of the land. Importantly, he suggested that other legal remedies – nuisance, harassment, or data protection – might be more appropriate than trespass.

What this means for drone operators

Trespass claims are harder to make stick than many landowners think. Courts are reluctant to find trespass unless flights interfere with the actual use of land (e.g. disrupting activity on site, flying extremely low, or endangering people).
Section 76 may be becoming redundant. Both Bernstein and MBR Acres suggest that unless a flight interferes with land use, there is no trespass at all – making section 76’s “reasonable height” defence almost irrelevant.
Purpose of flight matters – at least sometimes. In Anglo-International, mischievous use of drones was enough to justify an injunction. Operators engaged in legitimate commercial activity (surveying, deliveries, inspections) are on stronger ground.
Evidence is critical. Landowners will struggle to obtain injunctions unless they can prove height, frequency, and impact of flights. For operators, maintaining robust flight logs and compliance records (as required by the UK drone regulations) is the best defence.
Regulatory compliance is non-negotiable. Section 76 only protects operators if flights are lawful. Breach of drone regulations (flying beyond visual line of sight, too close to people, or over congested areas without permissions) will undermine any defence.

Looking ahead

The law remains unsettled. Drone operators should assume:

Routine overflights at safe, documented altitudes are unlikely to amount to trespass, provided they don’t interfere with land use.
Low-level flights directly over private land remain risky, particularly if they appear intrusive, harassing, or unsafe.
Other causes of action are emerging – nuisance, data protection, and harassment are likely to be more powerful tools for landowners than trespass.

For commercial operators, the key is to plan flight paths with landowner sensitivities in mind, document compliance, and keep up with evolving case law. What remains unclear is whether Parliament will modernise section 76 to deal explicitly with drones – or whether the courts will continue to adapt 20th-century law to 21st-century technology.

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

The post Trespass by Drones: Is Section 76 Civil Aviation Act 1982 Fit for Purpose? 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.

Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK

admin.richard — Tue, 04 Feb 2025 12:40:07 +0000

Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK
By Richard Ryan, Drone Lawyer

Introduction
Switzerland has emerged as a leading hub for drone innovation, in large part due to forward-looking policies and the seamless integration of unmanned aircraft into its broader aviation ecosystem. Although the UK has already adopted a risk-based regulatory framework for drones, lessons from the Swiss and European Union Aviation Safety Agency (EASA) experience could further advance the UK’s domestic industry.
This article compares Swiss and UK drone regulations, with a view to determining whether a more comprehensive legislative revision—drawing on Swiss and EASA best practices—could enhance safety, innovation, and public acceptance in the UK.

1. Background and Goals

1.1. Switzerland’s Drone Ecosystem
Switzerland’s success in fostering a dynamic civil drone industry rests on the following pillars:
1. Risk-Based Regulatory Model
Switzerland follows the three-category approach (Open, Specific, and Certified) as set out in the core EU regulations (Regulation (EU) 2019/947 and Regulation (EU) 2019/945), which it adopts under its bilateral air transport agreements with the EU.
2. Close Collaboration
Federal agencies (e.g., the Federal Office of Civil Aviation, FOCA), industry, and research institutions routinely coordinate to address regulatory and technological developments.
3. Strong International Ties
As a signatory to multiple bilateral and multilateral agreements (including the Agreement between the EU and the Swiss Confederation on Air Transport), Switzerland ensures legal certainty and alignment with global safety standards.

1.2. The UK Context
The UK also employs a risk-based framework, primarily structured by:
• The Air Navigation Order 2016 (ANO), as amended
• Civil Aviation Authority (CAA) publications, including CAP 722, which provides operational guidance for unmanned aircraft.
Although the UK’s regulations are already comprehensive, there is scope to streamline approval processes, bolster public confidence, and prepare for emerging drone technologies. Swiss and broader EASA approaches—particularly in the realm of U-Space services—offer potentially valuable lessons.

2. Swiss Legal Framework

2.1. Adoption of EU Drone Regulations
Under Swiss law, drones are governed by EU regulations (Regulations (EU) 2019/947 and 2019/945) through Switzerland’s bilateral air transport agreements with the EU. In practice, FOCA enacts these rules at the national level, sometimes incorporating local adaptations based on Swiss administrative structures.
2.1.1. Drone Categories
1. Open (low risk)
o Operations with minimal restrictions if the drone meets specific technical requirements (e.g., weight, speed, altitude limits) and usage conditions.
2. Specific (medium to high risk)
o Requires more rigorous operational authorisations and safety risk assessments.
3. Certified (highest risk)
o Applies to complex or large-scale operations, including cargo and passenger transport (e.g., eVTOL aircraft), though these frameworks are still evolving.
2.1.2. Integration with Traditional Aviation
• Coordination Through Skyguide: Switzerland’s air navigation service provider, Skyguide, is tasked with managing both manned and unmanned traffic. This seamless integration aims to promote safety and efficiency in shared airspace.
• National Emphasis on Collaboration: Swiss authorities maintain regular consultation with industry, research, and cantonal authorities to adapt regulations swiftly.
Relevance for the UK
• Risk Categorisation: The UK already uses a three-tier classification (Open, Specific, Certified), mirroring the Swiss/EASA approach.
• Approval Process: Automating and digitising authorisations—an area where Switzerland and Skyguide have been especially proactive—may help reduce administrative burdens for UK operators.

3. U-Space Infrastructure and Multiple Service Providers

3.1. What Is U-Space?
U-Space is a digital ecosystem designed to manage drone traffic autonomously or semi-autonomously. It includes network identification, flight authorisation services, and real-time data exchange among airspace users.

3.2. Switzerland’s U-Space Approach
• Multiple U-Space Service Providers (USSPs):
Switzerland aims to license several private or public providers within the same geographical area, fostering competition and innovation in drone traffic management.
• Key Features:
1. Network Identification: Ensures authorities (and possibly the public) can identify drones operating in U-Space airspace.
2. Automated Flight Authorisation: Minimises manual checks by aviation authorities.
3. Real-Time Data Exchange: Coordinates positions and flight plans among manned aircraft, unmanned aircraft, and air traffic control.

3.3. Implementation Timelines
• By 2025: Switzerland has signalled its intent to launch initial U-Space operations in regions including Zurich. [1]
• By 2030: Widespread U-Space maturity is anticipated across Europe, though this is an industry projection rather than a formal deadline.
Relevance for the UK
• Competition and Choice: Licensing multiple USSPs could provide UK operators with varying price points and service levels, driving innovation.
• Incremental Roll-Out: Concentrating U-Space in high-traffic urban areas first (London, Manchester, etc.) may mirror Zurich’s approach.
• Legal and Technological Foundation: Adapting the EU’s Implementing Regulation (EU) 2021/664 for U-Space to the UK’s post-Brexit landscape could maintain interoperability with European markets.

4. Noise Protection Measures

4.1. Swiss Perspective
Swiss authorities acknowledge that drone noise—while generally quieter than conventional aircraft—can be disruptive in residential or rural areas. Ongoing efforts include:
• Collaborating with EASA and ICAO working groups to develop drone-specific noise measurement standards.
• Encouraging technological innovations (e.g., quieter propellers, electric propulsion).
• Using geo-awareness tools to route flights around noise-sensitive areas.

4.2. Relevance for the UK
• Comprehensive Noise Mapping: Incorporating drone flight paths into local noise maps could help councils and the CAA manage public disturbances.
• Research and Design: Funding drone acoustics research could ensure any future noise regulations are evidence-based.
• Aligning Standards: Remaining aligned with emerging international noise standards could ease cross-border drone operations and manufacturing.

5. Privacy and Public Acceptance

5.1. Swiss Measures
• Mandatory Registration: Most drone operators must register and display their registration number, subject to weight and operational criteria.
• Remote Identification: Allows law enforcement and authorities to identify drones in real time, enhancing accountability.
• Geofencing and Flight Restriction Zones: Critical infrastructure or sensitive sites often have automated restrictions to prevent overflights.

5.2. Relevance for the UK
• Building Public Trust: The UK’s existing registration regime (for drones ?250g) could be coupled with more transparent robust remote ID requirements.
• Enforcement and Complaint Handling: Close coordination with local police and councils may expedite response times to drone-related incidents.
• Regulatory Consistency: Ensuring geofencing data is accurate and accessible will be crucial as drone usage scales up.

6. Spatial Planning and Infrastructure

6.1. Current Swiss Policy
• Different Treatment vs. Conventional Aviation: Small drone operations typically require minimal infrastructure and thus face limited planning procedures.
• “Intensive Use” Threshold: FOCA guidelines suggest that where a single site exceeds a certain number of flights (sometimes cited as over 1200 flights per year), formal land-use planning and environmental assessment may be triggered. However, application may vary depending on local (cantonal) regulations.

6.2. Future Vertiports
Swiss authorities anticipate the need for dedicated vertiports or droneports if large passenger/cargo eVTOLs become more commonplace. These facilities would require integration into national transport and aviation infrastructure plans.

6.3. Relevance for the UK
• Planning Approvals: The UK might consider more streamlined pathways for drone infrastructure, acknowledging that small drone operations have lower impact than full-scale airport developments.
• Emerging eVTOLs: A forward-looking approach—coordinated among the Department for Transport, local councils, and industry—could accommodate vertiport networks in urban hubs.
• Local Variations: Like Switzerland, the UK may allow local authorities discretion in how to apply thresholds for “intensive use,” but national guidance would help maintain consistency.

7. Environmental Sustainability

7.1. Potential Emissions Reductions
• Replacing Conventional Aircraft: Small drones can potentially replace helicopters for tasks like aerial surveys, agricultural spraying, or urgent deliveries, leading to immediate fuel and emissions savings.
• Lifecycle Analyses: Comprehensive studies are still limited, so definitive data on net environmental impact remains inconclusive.

7.2. Relevance for the UK
• Targeted Incentives: Encouraging drone use in sectors where carbon-intensive operations are widespread (e.g., logistics, agriculture, medical supply chains) could yield environmental benefits.
• Data Collection: Collaborating with academia and industry to produce rigorous lifecycle analyses would strengthen policy decisions.

8. Should the UK Revise Its Complex Legislation?

Given Switzerland’s experience and the growing demands of the UK drone sector, there is a robust case for a holistic review of UK drone regulations. Although the current framework—anchored in the Air Navigation Order 2016 and supplemented by CAP 722—is risk-based, integrating the best practices from Swiss and EASA models could amplify innovation and public trust.

8.1. Harmonising with EASA
• Voluntary Alignment: While the UK is no longer bound by EASA regulations post-Brexit, aligning technical and operational standards can facilitate cross-border operations and exports.
• Regulatory Autonomy: The UK can selectively adopt or adapt EASA rules that best serve its domestic market.

8.2. Streamlining Authorisations and Planning
• Digital Transformation: Emulating Switzerland’s push for automated approvals could reduce administrative burdens for operators in the UK.
• Consistent Local Guidance: As drones become integral to city services, local authorities should follow uniform guidelines on planning consent.

8.3. Fostering Public Trust
• Noise and Privacy Protections: Enhanced noise mapping, remote ID, and geofencing can address some of the most common community concerns.
• Robust Enforcement: Clear lines of responsibility between the CAA, local councils, and law enforcement agencies will be key.

Conclusion

Switzerland’s structured yet adaptive approach—emphasising competitive U-Space services, data-driven noise mitigation, robust privacy measures, and collaborative policymaking—offers valuable lessons for the UK. Despite a well-established risk-based framework, the UK could benefit from a more comprehensive review that incorporates Swiss successes and maintains compatibility with EASA standards where beneficial.
By welcoming multiple U-Space Service Providers, digitising authorisations, and preparing for future vertiport infrastructure, the UK can remain at the forefront of drone technology. A more cohesive and modernised legal framework, coupled with effective enforcement and public engagement, will lay the foundation for a thriving, responsible, and future-ready UK drone sector.

Author Bio: Richard Ryan
Richard Ryan is an experienced direct access barrister who has advised on drone regulations and airspace policy in both the UK and internationally. With a career spanning public and private sectors, he provides counsel on emerging areas of aviation law—from U-Space development to eVTOL certification. Richard regularly collaborates with industry associations, regulatory bodies, and academic institutions to help shape the future of safe and sustainable unmanned aircraft operations.

References and Further Reading
1. Swiss Federal Office of Civil Aviation (FOCA) – Drones and Models: https://www.bazl.admin.ch/bazl/en/home/good-to-know/drones-and-aircraft-models.html
2. Skyguide – Drones: https://www.skyguide.ch/en/company/corporate-topics/drones/
3. EU Drone Regulations (EU) 2019/947 & 2019/945: EUR-Lex
4. Implementing Regulation (EU) 2021/664 – U-Space: EUR-Lex
5. UK Air Navigation Order 2016: Legislation.gov.uk
6. CAA – CAP 722: https://publicapps.caa.co.uk/modalapplication.aspx?appid=11&mode=detail&id=415
________________________________________
This article is intended for informational purposes only and does not constitute legal advice. Stakeholders are encouraged to consult the applicable regulations, guidance materials, and professional counsel for specific compliance obligations.

The post Development and Regulation of Civil Drones: Lessons from Switzerland and Recommendations for the UK appeared first on Blakistons.

Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations

admin.richard — Wed, 11 Dec 2024 17:35:43 +0000

Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations

By Richard Ryan, Drone Lawyer

As a UK drone lawyer, I’ve seen firsthand how tricky it can be to navigate the ever-changing skies of unmanned aviation regulation. The Civil Aviation Authority’s (CAA) “Unmanned Aircraft Operations in an Atypical Air Environment (AAE): Policy Concept” (CAP 3040) is no exception. After the initial excitement of the First Edition, many in the drone community were eagerly awaiting the Second Edition, hoping for clarifications, improvements, and a more future-focused framework.

What’s New?
At a glance, the changes between the First and Second Editions might seem minimal—just a tweak to the reference for ADS-B (Automatic Dependent Surveillance-Broadcast) equipment, rolling back from RTCA DO-282C to the older DO-282B standard. But that’s not a small footnote. If you’ve been prepping your drone gear to meet DO-282C standards, you may now be left wondering why the rug’s been pulled from under you.

The Tech Twist:
DO-282B is an earlier standard for ADS-B performance, while DO-282C was supposed to reflect newer technology and real-world lessons learned. Reverting to an older standard could mean extra work or unexpected costs if you’ve already made purchases or adapted your systems for DO-282C. It also raises questions about whether the policy is truly forward-looking, or inadvertently stifling progress at a critical time in UK drone innovation.

Still Flying Through Foggy Regulations:
The Second Edition still leaves operators wrestling with a few nagging uncertainties:
1. Defining ‘Atypical Air Environment’: The document still lacks a crystal-clear definition of AAE. Without a firm legal baseline, you might struggle to know if your flight qualifies—adding confusion to your operations and potentially slowing down approvals.
2. Single Site Limitations: The CAA’s recommended approach of applying for just one site per Operational Authorisation (OA) remains. This can create unnecessary hurdles for those looking to scale up and serve multiple clients or routes.
3. Extra Admin, Less Innovation: Requirements like routine NOTAM submissions or intricate Electronic Conspicuity (EC) licensing haven’t been simplified. For many operators, these processes feel more bureaucratic than beneficial, potentially discouraging new entrants and curbing the industry’s growth.

How to Navigate This Airspace Turbulence:
• Stay Agile: Keep tabs on CAA communications and industry forums. If the CAA shifts requirements again, you’ll want to pivot quickly.
• Ask for Clarity: Don’t hesitate to reach out to uavenquiries@caa.co.uk for guidance, especially if you’ve already invested in tech aligned with DO-282C.
• Industry Collaboration: Connect with fellow operators, manufacturers, and drone associations. Shared experiences help identify practical solutions and give your concerns more weight when approaching regulators.
• Professional Advice: A drone-focused legal expert can help you interpret the Second Edition’s nuances, reduce compliance guesswork, and ensure you’re not sinking costs into the wrong standards.

Charting a Better Flight Path: While the Second Edition’s updates may feel like a step back, there’s still hope. The CAA emphasizes that CAP 3040 is an evolving concept. By voicing concerns, sharing data, and staying engaged, the drone community can help steer policy revisions that balance safety, innovation, and economic growth.

The Bottom Line:
The CAP 3040 Second Edition is a reminder that regulatory frameworks are works in progress. This can be frustrating, yes—but it’s also an opportunity. Operators willing to adapt, learn, and advocate for sensible changes can help shape the UK’s drone landscape into one that truly welcomes innovation. Keep your engines running, your channels of communication open, and your ambitions high. Together, we can ensure that tomorrow’s regulations are as cutting-edge and future friendly as the drone technology they’re meant to guide.

About the Author
Richard Ryan is a direct access barrister at Blakiston’s Chambers, specialising in drone law and unmanned aircraft regulation. Leveraging extensive knowledge of emerging aviation technologies and the UK’s complex regulatory landscape, Richard Ryan provides pragmatic guidance that empowers clients to navigate compliance challenges, secure operational approvals, and seize opportunities in the rapidly evolving drone sector. Known for translating intricate legal frameworks into actionable strategies, Richard Ryan is dedicated to shaping the policies that will define the future of unmanned aviation in the UK.

The post Soaring Ahead or Stuck in the Past? What the CAP 3040 Second Edition Means for Your Drone Operations appeared first on Blakistons.