Aviation Law and Regulations Archives - Blakistons

How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean

admin.richard — Thu, 06 Nov 2025 18:28:20 +0000

By Richard Ryan, barrister and drone lawyer

How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft — and what the defence carve-outs really mean.

In Brief…

Purely military AI systems are out of scope of the EU AI Act. If an AI system is developed or used exclusively for military/defence or national-security purposes, the Act does not apply. (EUR-Lex)
Dual-use is different. If the same autonomy stack, sensors or models are marketed or used for civilian purposes in the EU (for example, civil UAS, border or law-enforcement tasks), the Act can apply — with stringent duties for “high-risk” systems. (EUR-Lex)
Real-world testing is regulated. Pre-market R&D is generally excluded, but real-world testing isn’t — it requires specific safeguards and registration. (EUR-Lex)
Foundation models (GPAI) have their own rules from 2 Aug 2025; the defence carve-out in the Act is written for AI systems, not explicitly for models. If a model is placed on the EU market generally, the provider’s GPAI obligations can still bite. (EUR-Lex)

Context: sUAS News reports that GA-ASI is showcasing its autonomous fighter portfolio (for example, YFQ-42A CCA, MQ-20 Avenger) at the International Fighter Conference in Rome, 4–6 Nov 2025. This post overlays that scenario with the EU AI Act’s rules.

1) First principles: When does the EU AI Act apply?

The Act has extraterritorial reach. It covers (i) providers and deployers in the EU, (ii) providers placing on the EU market or putting systems into service in the EU — even if they are not established here — and (iii) providers/deployers in third countries where the AI system’s output is used in the EU. (EUR-Lex)

However, Article 2(3) draws a bright line: the Act does not apply to AI systems used exclusively for military, defence or national security. It also does not apply where a system is not placed on the EU market but its output is used in the EU exclusively for those purposes. Recital 24 reiterates this and clarifies that non-defence use falls back under the Act. (EUR-Lex)

What this means in Rome:

A closed, defence-only showcase for European militaries: out of scope.
A civil-use pitch, civil flight trials, or plans to sell autonomy modules to EU civilian buyers: in scope (see the high-risk section below). (EUR-Lex)

2) The key defence carve-outs (and their limits)

Carve-out #1 — Defence/military:

“This Regulation shall not apply to AI systems … used exclusively for military, defence or national security purposes.” (Article 2(3))

Two important nuances:

Exclusivity matters. The moment an autonomy stack or sensor suite is also marketed or used for civilian or law-enforcement tasks, the defence exclusion no longer shields those non-defence uses. (EUR-Lex)
Models vs systems. The text explicitly excludes AI systems for defence; it does not create an explicit defence exclusion for general-purpose AI models. If a GPAI model is placed on the EU market, Chapter V obligations for model providers can still apply — even if one downstream customer is a defence user. (More on GPAI below.) (EUR-Lex)

Carve-out #2 — Pre-market R&D:
R&D before placing on the market is generally outside scope, but real-world testing is not. Testing in real-world conditions triggers a dedicated regime (for example, registration, time limits, informed consent or special conditions for law enforcement, incident reporting). (EUR-Lex)

Carve-out #3 — Emergency derogations (non-defence):
For exceptional public-security reasons (or imminent threats to life/health), market surveillance authorities can authorise temporary use of a high-risk AI system before full conformity assessment — subject to strict conditions. Law-enforcement or civil-protection bodies can also use in urgent cases, then seek authorisation without undue delay. This is not a defence-specific carve-out, but it explains emergency deployments outside the military context. (EUR-Lex)

3) If the defence exclusion doesn’t apply, would autonomous fighters tech be “high-risk”?

Very likely yes — for civil variants or dual-use spin-outs:

Annex I (product-safety route). AI that is a safety component of products covered by sectoral EU safety laws is high-risk where those products need third-party conformity assessment. That list explicitly includes EU civil aviation law (Reg. 2018/1139) — covering unmanned aircraft and their remotely controllable equipment. In a civil-UAS configuration, an autonomy stack acting as a safety component would be regulated as high-risk. (EUR-Lex)
Annex III (stand-alone uses). Separate “high-risk” buckets also capture, for example, remote biometric identification and other sensitive functions (if and where permitted by Union/national law), critical infrastructure safety components, and more. If a fighter-born sensing suite were repurposed for civil border surveillance or public-space identification, you quickly hit these Annex III categories. (EUR-Lex)

What “high-risk” demands in practice
Providers must implement a risk-management system, data governance, technical documentation, logging, transparency/instructions, human oversight, and accuracy/robustness/cybersecurity — then pass conformity assessment, issue an EU Declaration of Conformity, and affix CE marking. Deployers also carry duties (for example, monitoring, data relevance, user notification in some cases). (EUR-Lex)

4) Sensors on show: what about face recognition and other “red lines”?

The EU bans several AI practices outright (from 2 Feb 2025), including:

Untargeted scraping of facial images to build recognition databases.
Biometric categorisation inferring sensitive traits (for example, race, political opinions, religion).
Emotion recognition in workplaces or schools (with narrow safety/medical exceptions).
Predictive “risk assessments” of criminality based solely on personality traits/profiling.
Real-time remote biometric identification (RBI) in public spaces for law enforcement — unless strictly authorised and necessary for narrowly defined objectives (for example, locating a specific suspect in serious crimes, preventing a specific imminent threat, finding missing persons), with prior judicial/independent approval and registration. (EUR-Lex)

Implication for a trade-show demo: training a camera on attendees to test real-time RBI in a public venue would likely be unlawful unless those strict law-enforcement exceptions and procedural safeguards apply — which they typically will not at a commercial defence conference. (EUR-Lex)

5) Real-world testing in the EU (civil or dual-use variants)

If a provider runs real-world flight tests in the EU (outside the defence exclusion), the Act requires — among other things — registration, an EU-established entity or EU legal representative, limits on duration (normally up to six months, extendable once), rules on informed consent (with special handling for law-enforcement tests), qualified oversight, and the ability to reverse/ignore the system’s outputs. Serious incidents must be reported promptly. (EUR-Lex)

6) Foundation models (GPAI): obligations can still attach

From 2 Aug 2025, Chapter V sets baseline transparency and copyright-policy duties for providers of general-purpose AI models (with extra obligations if the model presents systemic risks). The defence exclusion in Article 2(3) is framed for AI systems, not models. So, if a foundation model is placed on the EU market, the model provider can have obligations even if a downstream customer is a defence prime. (Open-source specifics and systemic-risk thresholds also apply.) (EUR-Lex)

7) Timelines you need in Rome (as of 6 Nov 2025)

Entry into force: 1 Aug 2024 (20 days after OJ publication).
Prohibited practices + core chapters (I–II): apply from 2 Feb 2025.
GPAI rules (Chapter V), plus other chapters (III §4, VII, XII, and Article 78): apply from 2 Aug 2025.
General application: 2 Aug 2026 (high-risk regime starts to bite broadly).
Article 6(1) Annex III classification trigger & related obligations: 2 Aug 2027. (EUR-Lex)

8) Enforcement and penalties

Violating prohibited practices (Article 5) can draw fines up to €35m or 7% of worldwide annual turnover, whichever is higher.
Other operator obligations can reach €15m or 3%; supplying misleading information can reach €7.5m or 1% (SMEs benefit from caps). Separate fine scales apply to EU institutions. (EUR-Lex)

9) Practical playbook for IFC attendees

If you are a defence OEM showing autonomy stacks:

Map uses: Defence-only (excluded) vs any civil or law-enforcement pathways (potentially in scope). Document the exclusivity of defence deployments if you rely on the carve-out. (EUR-Lex)
GPAI suppliers: If you place a foundation model on the EU market, expect Chapter V duties regardless of defence customers. (EUR-Lex)
No RBI demos on the show floor. Those prohibitions already apply in 2025. (EUR-Lex)
Planning EU flight tests for civil variants? Prepare for real-world testing conditions (registration, oversight, incident reporting). (EUR-Lex)
For civil UAS commercialisation, treat your autonomy as high-risk (EASA product-safety route), budget time for conformity assessment and CE marking. (EUR-Lex)

If you are a European ministry or agency:

Distinguish military operations (out of scope) from law-enforcement or border uses (in scope; watch RBI limits and high-risk duties). Consider Article 46 emergency derogations only in exceptional and documented cases. (EUR-Lex)

If you are a civil UAS integrator:

Expect the full high-risk package (risk management, data governance, human oversight, cybersecurity, logs, conformity assessment, CE). Build compliance into your system architecture, ML pipelines, safety cases, and ops manuals from day one. (EUR-Lex)

10) Quick decision pathway

Is the use exclusively defence or national security?
Yes: AI system is out of scope.
No: continue. (EUR-Lex)
Is it a civil product or law-enforcement/border use?
Civil product with safety function (for example, civil UAS): High-risk via Annex I ? conformity assessment + CE. (EUR-Lex)
Stand-alone sensitive use (for example, RBI, critical infrastructure): Annex III high-risk or Article 5 prohibition applies. (EUR-Lex)
Is there a GPAI model being placed on the EU market?
Yes: Chapter V duties for model providers from 2 Aug 2025, separate from the defence carve-out for systems. (EUR-Lex)
Is this pre-market testing?
Real-world testing rules apply (registration, oversight, incident reporting). (EUR-Lex)

Bottom line for “Autonomous Fighters in Rome”

A military-only display of GA-ASI’s autonomous fighters is outside the AI Act.
Any civil spin-off (cargo drones, civil surveillance, airport ops) or law-enforcement application in the EU will trigger the Act — often at the high-risk level — together with tight prohibitions around biometric uses in public spaces. Plan your compliance architecture accordingly. (EUR-Lex)

This article is informational and not legal advice. Citations are to the Official Journal text of the Artificial Intelligence Act (Regulation (EU) 2024/1689) for scope (Art. 2), prohibitions (Art. 5), high-risk regime (Ch. III), real-world testing (Arts. 57–61), GPAI (Ch. V incl. Art. 53), timelines (Art. 113), and penalties (Art. 99–101).

About the author — Richard Ryan

Richard Ryan is a UK barrister (Direct Access), mediator and Chartered Arbitrator (FCIArb), and a Bencher of Gray’s Inn. He practises across defence, aerospace, construction, engineering and commodities, with a leading specialism in drone and counter-drone law, unmanned aviation regulation, and AI-enabled safety and compliance. Richard advises government, primes and operators on EU/UK UAS frameworks, BVLOS, U-space/UTM and the EU AI Act. He leads Blakiston’s Chambers and contributes regularly to industry guidance and policy consultations.

The post How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean 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.

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.

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.

Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations

admin.richard — Wed, 05 Feb 2025 11:10:25 +0000

Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations

By Richard Ryan, Drone Lawyer (UK)

In a noteworthy development across the pond (thanks to sUAS News for the notification!), the United States District Court for the Eastern District of Pennsylvania has entered a consent judgment against a Philadelphia resident, Mr Michael DiCiurcio, for multiple breaches of Federal Aviation Administration (“FAA”) regulations and safety guidelines. Although this case has arisen under US law, it is a useful reminder for drone operators in the UK of the absolute necessity to adhere strictly to local regulations—particularly when flying in congested or controlled airspace.

Background of the Case
According to the complaint, the United States alleges that Mr DiCiurcio operated small unmanned aircraft systems (“sUAS”), commonly referred to as drones, illegally and unsafely in the Philadelphia area from December 2019 onwards. Notable alleged violations include:
1. Night-time flights without proper authorisation.
2. Flying in close proximity to landmark buildings, including the William Penn Statue, the PSFS Building, and Liberty One Building—once nearly striking a church steeple.
3. Operating in controlled airspace near Philadelphia airport without permission, and over people and cars.
4. Losing control of a drone, causing it to fly uncontrolled over Philadelphia.
The FAA had previously issued written warnings to Mr DiCiurcio, offering counselling and education regarding sUAS regulations. Despite these efforts, the government contends that Mr DiCiurcio continued to fly drones in a manner deemed careless, reckless, and endangering public safety.

Terms of the Consent Judgment
On 23 January 2025, before Magistrate Judge Jose Arteaga, Mr DiCiurcio agreed to a consent judgment that includes several key terms:
1. Admissions of Liability
o Mr DiCiurcio admits that the allegations in the Verified Complaint are both true and accurate, and that they constitute violations of FAA regulations.
2. Permanent Ban on Drone Operations
o Mr DiCiurcio agrees never to operate any sUAS in the United States in any capacity, nor to seek any form of certification or licence to do so.
3. Removal of Online Content
o Mr DiCiurcio must take down his “Philly Drone Life” YouTube channel and is prohibited from reviving its content in any form.
4. Abandonment of Equipment
o He relinquishes ownership of the sUAS and related items previously surrendered to the FAA.
Chief Judge Mitchell S. Goldberg signed the consent judgment on 29 January 2025.

Enforcement and Commentary
FAA Deputy Administrator Katie Thomson emphasised that while the agency strives to educate drone operators, it will not hesitate to take stringent enforcement action when individuals “deliberately flout the rules.”
U.S. Attorney for the Eastern District of Pennsylvania, Jacqueline C. Romero, reiterated that failing to observe sUAS regulations endangers people and property. The authorities involved have made it clear that they intend to take firm action against drone operators who disregard safety protocols and regulatory requirements.
It is important to note that, as is typical in a civil proceeding, all allegations remain just that—allegations—until liability is formally established. In this instance, Mr DiCiurcio has effectively acknowledged those allegations by agreeing to the judgment.

Lessons for UK Drone Operators
Although this case unfolded in the United States, the lessons are equally pertinent for drone enthusiasts and professional operators here in the UK:
1. Know Your Regulations
o In the UK, drone operations are governed by the Civil Aviation Authority (CAA). There are specific requirements based on the weight category of your drone and the environment in which you intend to fly (e.g., near airports, above crowds). Understanding these regulations is paramount.
2. Obtain the Necessary Permissions
o Just as the FAA requires authorisations for certain flights, UK law may also demand operational authorisations for flights in congested areas or controlled airspace. Always seek the appropriate permission before taking off.
3. Heed Warnings and Guidance
o If you ever receive a caution or formal notice from a regulatory body, treat it seriously. As illustrated by this case, repeated violations—particularly after being warned—can escalate into severe legal consequences.
4. Operate Safely and Responsibly
o Safety should always be at the forefront of every flight. This includes maintaining control of your sUAS, respecting no-fly zones, and refraining from operating drones while distracted or in hazardous conditions.

Conclusion
The consent judgment against Mr DiCiurcio underscores the serious consequences drone operators may face if they wilfully violate aviation regulations. For those of us practising and flying drones in the UK, it serves as a timely reminder to remain vigilant, operate responsibly, and stay fully abreast of ever-evolving drone laws.
While national regulations may differ, the underlying principle is universal: drones must be flown safely, ethically, and in compliance with applicable rules. Failing to do so jeopardises both the public and the future of drone innovation.

About the Author
Richard Ryan is a UK-based Direct Access Barrister specialising in drone and aviation law, advising on regulatory compliance, operational approvals, and dispute resolution. With extensive experience navigating the complexities of both UK Civil Aviation Authority (CAA) regulations and international drone frameworks, Richard assists private clients, commercial operators, and industry stakeholders alike. Passionate about emerging technologies, Richard frequently speaks and writes on the legal aspects of unmanned aerial vehicle (UAV) operations, promoting safe, responsible, and innovative drone use. When he’s not in chambers, Richard is deeply engaged in exploring the latest developments in drone technology and advocating for robust regulatory standards that balance innovation with public safety.

Disclaimer: This blog is for general information only and does not constitute legal advice. If you have specific questions about drone operations and regulatory compliance in the UK, please consult a qualified drone lawyer at Blakiston’s Chambers.

The post Consent Judgment Entered Against Philadelphia Drone Flyer for Violations of FAA Regulations 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.

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

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

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

By Richard Ryan, Drone Lawyer

The skies over the UK are on the verge of a transformative shift, thanks to the ambitious NATS OpenAir initiative. Designed to integrate drones and advanced air mobility (eVTOLs) into shared airspace alongside traditional aircraft, the proposal promises innovation, efficiency, and safety. But as with any grand vision, the devil is in the detail.
Here’s an in-depth look at what the OpenAir initiative is getting right, where there are gaps, and how it can evolve to meet the needs of all airspace users.
________________________________________
1. Prioritising Data Privacy and Ownership

One of the most valuable resources in aviation is data. For drone operators, who depend on real-time information about flight paths, weather, and airspace restrictions, access to reliable data is critical. However, the OpenAir proposal is light on specifics about who owns the data and how privacy will be protected.
Without clear protections, drone operators might worry about their data being exploited—whether commercially or in ways that jeopardise their competitive edge.

The Fix:
OpenAir must adopt a clear data privacy framework. Operators should retain ownership of their data, with mandatory anonymisation for any information shared beyond essential safety and operational use. Only the bare minimum of data required for regulatory compliance should be shared, and stringent safeguards must prevent its misuse.
________________________________________
2. Keeping the Playing Field Fair

OpenAir is envisioned as a centralised hub for managing UK airspace, which sounds great—until you consider the potential impact on smaller players. Consolidating services under one entity like OpenAir might inadvertently stifle competition among Uncrewed Traffic Management Service Providers (UTMSPs).

The Fix:
To level the playing field, OpenAir should adopt open standards that allow seamless third-party integration. Smaller UTMSPs must be supported, not sidelined. Clear rules around equitable access to data and services will ensure innovation thrives without creating monopolies.
________________________________________
3. Setting Realistic Timelines

Integrating drones and eVTOLs into shared airspace isn’t a simple task. OpenAir’s proposed rollout timeline—beginning pilots in 2025 and achieving full deployment by 2028—might be overly ambitious, especially given the complexity of regulatory approvals and the need for robust infrastructure.

The Fix:
A phased approach with realistic benchmarks is the way forward. OpenAir should focus on pilot projects in key areas where demand is highest (e.g., urban delivery drones or emergency medical services). This would provide valuable data to refine the system while reducing the risk of rushed implementation.
________________________________________
4. Managing Costs for Drone Operators

OpenAir’s “user pays” principle makes sense in theory—those who use the airspace services should cover the costs. But smaller operators, such as local delivery drone companies, could be disproportionately affected by high fees, potentially pricing them out of the market.

The Fix:
Introduce tiered pricing. Small operators should pay less, at least during the initial phases. Alternatively, subsidies or credits could be offered to early adopters, ensuring fair access while fostering adoption across the board.
________________________________________
5. Addressing Legal Grey Areas

OpenAir aligns with the UK’s Airspace Modernisation Strategy, but its relationship with existing regulations like CAP 722 (which governs drone operations) needs to be crystal clear. Ambiguities in compliance requirements could delay approvals or lead to legal disputes.
Similarly, liability concerns loom large. If there’s a system outage or data error, who’s responsible for the fallout? Drone operators? OpenAir? The CAA? NATS? DfT?

The Fix:
OpenAir must explicitly state how its services integrate with CAP 722, especially for critical areas like Beyond Visual Line of Sight (BVLOS) operations. As for liability, service agreements must clearly define responsibilities, ensuring all parties—operators, OpenAir, and regulators—understand their obligations.
________________________________________
6. Building Trust Through Transparency

For OpenAir to succeed, trust is key. Stakeholders—including drone operators, regulators, and public service agencies—must feel confident in the system’s fairness and security.

The Fix:
Establish an independent advisory board with representatives from all key groups, including Blakiston’s Chambers! This board would oversee the rollout of OpenAir, ensuring transparency and accountability. Regular public updates and feedback sessions would further build trust and address concerns early.
________________________________________
7. Looking to the Future

The potential of OpenAir is undeniable. By creating a unified platform for managing UK airspace, it could unlock opportunities ranging from efficient logistics to life-saving medical deliveries. But to truly succeed, OpenAir must:
1. Prioritise data privacy and ownership.
2. Ensure fair competition for all service providers.
3. Adopt a phased, realistic rollout plan.
4. Keep costs manageable for smaller operators.
5. Align with existing regulations like CAP 722.
6. Address liability concerns upfront.
7. Foster trust through transparency and stakeholder engagement.

The skies above us are changing, and with thoughtful planning, OpenAir could make the UK a global leader in integrated airspace management. But to get there, it must balance ambition with practicality, ensuring the system works for everyone—from global eVTOL operators to local delivery drones.
________________________________________
What do you think about the OpenAir proposal? Share your thoughts, especially if you’re a drone operator or part of the aviation industry. Your feedback could shape the future of our skies!

About the Author
Richard Ryan is a UK-based barrister and drone law expert with over 20 years of legal experience. Specializing in regulatory, operational, and safety challenges, Richard advises defence companies, regulatory bodies, and government agencies on the complexities of UAS operations. A former advisor to the UK Civil Aviation Authority and the House of Lords’ AUTMA committee, Richard is currently pursuing a PhD at Cranfield University, focusing on the legal implications of drone integration into global airspace.
Richard combines his legal expertise with a deep understanding of defence operations, having served in the British Army, including deployments to Iraq and Afghanistan. His insights bridge the gap between operational realities and legal requirements, ensuring clients navigate the rapidly evolving world of drone technology with confidence.

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

Navigating the Legal Skies: Overcoming Challenges in Drone Deliveries

admin.richard — Wed, 13 Nov 2024 15:07:47 +0000

Navigating the Legal Skies: Overcoming Challenges in Drone Deliveries

By Richard Ryan, Commercial Drone Lawyer

________________________________________
The drone delivery industry is on the cusp of revolutionising retail and logistics. According to PwC’s report, “Drone Deliveries: Taking Retail and Logistics to New Heights,” we can expect around 5 million business-to-consumer (B2C) drone deliveries worldwide in 2024. This number is projected to soar to 808 million deliveries, valued at $65 billion, by 2034. Major players like Walmart, Amazon, and DHL are already investing heavily in this transformative technology.
While the report provides a comprehensive market analysis and technological overview, it touches only briefly on the legal and regulatory hurdles that businesses must overcome. As a commercial drone lawyer with over two decades of experience, I believe it’s crucial to delve deeper into these legal intricacies to fully harness the potential of drone deliveries.
________________________________________
Bridging the Regulatory Gaps
Identified Gap: The report acknowledges regulatory challenges but lacks a detailed examination of existing frameworks across key markets like the UK, EU, and others.

Recommendation: Businesses should conduct a comparative analysis of international drone regulations. Understanding differences in areas such as Beyond Visual Line of Sight (BVLOS) operations, airspace classifications, and certification requirements is essential. In the UK, for instance, the Civil Aviation Authority (CAA) sets stringent rules that operators must navigate carefully.

Data Protection and Privacy Concerns
Identified Gap: There’s minimal discussion on how drone operations intersect with data protection laws, such as the UK General Data Protection Regulation (GDPR).

Recommendation: Companies must establish protocols to ensure compliance with data protection regulations. This includes securing any data collected during drone operations and being transparent about data usage with consumers. Privacy impact assessments can help identify and mitigate potential risks.

Liability and Insurance Complexities
Identified Gap: The report briefly mentions insurance and liability but doesn’t delve into the allocation of liability in incidents like accidents or data breaches.

Recommendation: It’s vital to understand the legal liabilities for all parties involved—operators, manufacturers, and service providers. Comprehensive insurance coverage is necessary to mitigate risks. Contracts should clearly outline liability clauses to protect the business in case of unforeseen events.

Intellectual Property Rights Protection
Identified Gap: The importance of securing intellectual property (IP) rights for drone technology and software isn’t discussed.

Recommendation: Protecting technological innovations through patents and trademarks is crucial. This not only safeguards the company’s assets but also provides a competitive edge in a rapidly evolving industry.
________________________________________
Legal Issues Requiring Further Explanation

Airspace Usage Rights
Issue: The legalities of low-altitude airspace usage are complex and not fully addressed in the report.
Explanation: In the UK, while airspace up to 500 feet is generally public, property owners have certain rights that could affect drone flights over their land. Clarifying these rights is essential to prevent legal disputes and ensure smooth operations.

Compliance with Aviation Laws
Issue: The process for complying with aviation laws, including obtaining necessary permissions from the CAA, needs more clarity.
Explanation: Detailed guidance on securing operational authorisations, especially for BVLOS flights, is crucial. Understanding the regulatory landscape helps in planning and reduces the risk of non-compliance.

Environmental Regulations
Issue: The report touches on environmental concerns like noise pollution and wildlife impact but doesn’t explore legal obligations in depth.
Explanation: Companies must conduct environmental impact assessments and comply with regulations to mitigate legal risks and foster community acceptance.
________________________________________
Legal Requirements to Overcome Industry Challenges

Standardisation of Regulations
Assistance: Advocate for harmonising drone regulations across different jurisdictions.
Benefit: This will simplify compliance for companies operating internationally and encourage industry growth.

Development of Unmanned Traffic Management (UTM) Systems
Assistance: Support the creation of UTM systems to safely integrate drones into national airspace.
Benefit: Enhanced safety measures can lead to regulatory bodies relaxing certain restrictions, facilitating smoother operations.

Public Engagement and Education
Assistance: Implement programmes to educate the public about drone operations, addressing safety and privacy concerns.
Benefit: Improved public perception can lead to a more favourable regulatory environment and increased consumer acceptance.
________________________________________
Recommendations for Businesses

1. Develop a Comprehensive Legal Compliance Strategy
Craft a detailed framework that addresses all legal aspects of drone operations, including airspace rights, data protection, liability, and environmental compliance.

2. Engage with Regulatory Bodies
Proactively collaborate with the CAA and other authorities to stay updated on regulatory changes and contribute to the development of favourable policies.

3. Invest in Risk Management and Insurance
Implement robust risk management strategies and secure comprehensive insurance to mitigate potential liabilities.

4. Protect Intellectual Property
Secure patents and trademarks for technological innovations to maintain a competitive advantage and prevent infringement issues.

5. Conduct Environmental Impact Assessments
Ensure all operations comply with environmental laws by conducting thorough assessments and implementing necessary mitigation strategies.
________________________________________
Conclusion
The potential of drone deliveries in transforming retail and logistics is immense. However, to fully capitalise on this opportunity, businesses must address the legal and regulatory challenges head-on. By proactively managing these aspects, companies can not only ensure compliance but also enhance operational efficiency and public acceptance.
________________________________________
About the Author
Richard Ryan is a seasoned commercial drone lawyer (direct access barrister) with many years of experience in advising on UAV operations, regulatory compliance, and aviation law. With a deep understanding of the legal intricacies of drone technology, Richard Ryan assists businesses in navigating the complex regulatory landscape to achieve successful drone integration.

The post Navigating the Legal Skies: Overcoming Challenges in Drone Deliveries appeared first on Blakistons.

Drone Operators: Navigating the Legal Landscape of Trespass

zeroabove — Wed, 25 Sep 2024 11:38:53 +0000

With the growing use of drones in commercial operations, the recent Anglo International Upholland Ltd v Wainwright [2023] case sets an important legal precedent for drone operators. The High Court ruled that flying drones over private property can constitute trespass, especially when used to capture images that facilitate unlawful activity, such as trespass.

This case highlights the complexity of balancing Section 76 of the Civil Aviation Act 1982 with trespass laws. Section 76 offers protection when drones fly at a “reasonable height,” but this case found that using drones for unauthorised photography over a site nullified such protection. Additionally, the court ruled that the very act of flying drones for unlawful purposes could constitute trespass, even without exact evidence on flight height.

For drone operators, this ruling underlines the need for compliance with air navigation laws, obtaining property owner consent, and carefully considering the purpose and operation of drone flights. As the sector evolves, it’s crucial to stay updated with legal developments to avoid potential liability.

Key Takeaways:

Section 76 protections may not apply if drones are used for improper purposes.
The court is increasingly willing to view drone use in trespass contexts.

Drone operators should obtain permission for flights over private property and comply with regulations to mitigate legal risks.
A list of relevant questions for the Civil Aviation Authority (CAA) in light of the Anglo International Upholland Ltd v Wainwright [2023] case:

How does the CAA interpret “reasonable height” under Section 76 of the Civil Aviation Act 1982 for drone flights over private property?
Does the CAA plan to update its guidance on drone operations to address trespass concerns post- Wainwright*?
What steps should drone operators take to ensure compliance with both air navigation laws and property trespass rules
Will there be new regulations requiring landowner consent for drones flying over private property?
How does the CAA plan to enforce penalties for drones used unlawfully over private property?
Could the CAA clarify its position on privacy violations and trespass when drones capture images without consent?
What considerations are in place for determining unlawful drone use, even if the flight does not breach flight height limits?
Is there a possibility for the CAA to introduce more stringent guidelines for recreational versus commercial drone flights regarding private land?
How should drone operators document compliance to avoid liability under both CAA regulations and civil trespass claims?
Does the CAA foresee future collaborations with property law bodies to provide comprehensive guidance on airspace use above private land?

Let’s see if the UK CAA responds… Richard Ryan, barrister

Blakiston’s Chambers – “Leading the way in drone and counter-drone law, safeguarding airspace innovation and security.”

richard.ryan@blakistons.com

The post Drone Operators: Navigating the Legal Landscape of Trespass 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.