Aviation Technology Archives - Blakistons https://blakistons.co.uk/category/aviation-technology/ Drone Law Mon, 01 Jun 2026 11:14:30 +0000 en-GB hourly 1 https://wordpress.org/?v=7.0.1 The Drone in the Room: What the AI Act’s August Deadline Actually Means for Unmanned Aircraft https://blakistons.co.uk/the-drone-in-the-room-what-the-ai-acts-august-deadline-actually-means-for-unmanned-aircraft/ Mon, 01 Jun 2026 11:14:30 +0000 https://blakistons.co.uk/?p=2661 There’s a particular kind of frustration that comes from practising in a field that everyone assumes is covered by a law that, on close reading, barely mentions it. Drone law is one of those fields. People hear “AI Act” and “drones” in the same breath and assume the two slot neatly together; that the great […]

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

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

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

The autonomy problem nobody wants to define

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

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

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

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

Here is where I watch clients relax too early.

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

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

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

Article 50 and the drone you can’t see

Now the part that genuinely changes behaviour on the ground.

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

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

The sandbox that slipped a year

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

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

What I’m telling clients

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

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

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

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

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

]]> How Europe’s new AI rulebook would (and wouldn’t) touch autonomous combat aircraft—and what the defence carve?outs really mean https://blakistons.co.uk/how-europes-new-ai-rulebook-would-and-wouldnt-touch-autonomous-combat-aircraft-and-what-the-defence-carveouts-really-mean/ Thu, 06 Nov 2025 18:28:20 +0000 https://blakistons.co.uk/?p=2624 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 […]

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.

]]>

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:

  1. 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)
  2. GPAI suppliers: If you place a foundation model on the EU market, expect Chapter V duties regardless of defence customers. (EUR-Lex)
  3. No RBI demos on the show floor. Those prohibitions already apply in 2025. (EUR-Lex)
  4. Planning EU flight tests for civil variants? Prepare for real-world testing conditions (registration, oversight, incident reporting). (EUR-Lex)
  5. 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

  1. Is the use exclusively defence or national security?
    Yes: AI system is out of scope.
    No: continue. (EUR-Lex)
  2. 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)
  3. 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)
  4. 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.

]]> Rapid Briefing: “UK Drone Regulations and Net Risk” (PwC, Sept 2025) — Issues, Gaps, Opportunities https://blakistons.co.uk/rapid-briefing-uk-drone-regulations-and-net-risk-pwc-sept-2025-issues-gaps-opportunities/ Tue, 28 Oct 2025 08:05:36 +0000 https://blakistons.co.uk/?p=2597 “`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 […]

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

]]> “`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)

  1. 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)
  2. Process opacity & cost-burden: SORA mitigations/AMC are qualitative ? inconsistent asks; high fees despite narrow temporal/spatial grants. (p. 35)
  3. Emergency-services capability gap: loss of E4506 creates avoidable delay/risk; forces work-arounds (State Aircraft) rather than transparent PDRA. (p. 27)
  4. AAE not yet a permissioning tool: policy concept ? scalable authorisation path (contrast EU PDRA-G03 for linear infrastructure). (pp. 28–31, 36)
  5. 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)
  6. 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)

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.

“`

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

]]> When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports https://blakistons.co.uk/when-just-a-minute-becomes-bvlos-legal-lessons-for-drone-operators-from-chirps-september-2025-reports/ Mon, 27 Oct 2025 19:14:43 +0000 https://blakistons.co.uk/?p=2590 By Richard Ryan, Barrister & Drone Lawyer – practical takeaways, not legal advice for your specific situation. Why this matters The incidents, in plain English – and what the law expects Unintentional BVLOS x3 (BMFA community) Nottingham Carnival injury (Mini 2) “My app froze” (Mavic 4 Pro + RC2) Fatigue and stress (power-line inspection) RTH […]

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

]]>

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

Why this matters

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

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

1) Unintentional BVLOS x3 (BMFA community)

  • What happened: One EDF jet lost power from a poor solder joint after a user modification; two other flights went BVLOS when sea fog or thermal lift arrived faster than forecast.
  • Legal frame (UK): The Drone and Model Aircraft Code requires direct VLOS and the ability to determine orientation at all times. If you cannot do that, the flight is non-compliant.
  • Practical fix: Treat post-purchase alterations as airworthiness-significant and inspect them before each flight. Use BMFA’s SWEETS pre-flight. Adopt a simple “radial scan” habit: eyes out (aircraft and airspace) then quick glance down (controller or map) then eyes out again.

2) Nottingham Carnival injury (Mini 2)

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

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

  • What happened: Switching to Map View mid-mission froze the Fly app. The pilot used the hardware RTH button to recover the aircraft. Possible overload from running a large waypoint mission while screen-recording.
  • Legal frame: You remain responsible for safe operation even when the UI hiccups. The defensible question is whether your procedures anticipated foreseeable failures, such as hardware RTH muscle memory, function checks, and reboot-on-the-ground policies.
  • Practical fix: For long waypoint jobs, test the profile without screen-recording first. Pre-brief the hardware RTH action. Use a visual observer if you will be heads-down.

4) Fatigue and stress (power-line inspection)

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

5) RTH vs powerlines (mapping mission)

  • What happened: An automated flight went off-nominal. On RTH, the aircraft likely contacted an obstacle while climbing. CHIRP notes the perception trap of judging wire clearance at range and reminds that wires sag mid-span.
  • Practical fix: Set RTH altitude locally before each flight, above towers, tree lines, cranes, and powerlines. Do not rely on obstacle avoidance to detect thin wires. Pre-flight, measure line heights relative to the home point and add margin for sag and wind.

Five legal pillars these cases keep hitting

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

Turn the lessons into a defensible playbook

A. Pre-flight and design for failure

  • Modified anything? Treat user soldering, adapters, and third-party leads as risk-relevant. Inspect that joint every flight until replaced with a proven assembly. Log the check.
  • Weather is slippery. Do not rely on one app. Triangulate forecasts. Identify abort gates if visibility closes in (fog, showers, glare). Use SWEETS at the field.
  • Controller workload. For heavy waypoint missions, disable screen-recording unless proven stable. Rehearse hardware RTH and app-independent control.

B. RTH and battery settings you can defend

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

C. People, roles, and sterile cockpit

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

D. Evidence and reporting (preserve the facts)

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

Bottom line

The risk here is ordinary: a conversation at the wrong moment, fog rolling in, a buried setting, an RTH altitude that did not clear wires,
or a controller pushed too hard. The Code’s core duties – VLOS, no crowds, proper ID labelling,
know your automation, and keep records – are your best legal shield when something goes wrong.

BMFA SWEETS: a quick pre-flight check

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

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

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

Credit and resources

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

]]> Taking Flight in Dubai: Joby Aviation Breaks Ground on Revolutionary Air Taxi Network at DXB https://blakistons.co.uk/taking-flight-in-dubai-joby-aviation-breaks-ground-on-revolutionary-air-taxi-network-at-dxb/ Tue, 12 Nov 2024 15:11:41 +0000 https://blakistons.co.uk/?p=2491 Taking Flight in Dubai: Joby Aviation Breaks Ground on Revolutionary Air Taxi Network at DXB By Richard Ryan, Drone Lawyer Joby Aviation’s recent announcement of its first vertiport construction at Dubai International Airport (DXB) marks a major milestone for urban air mobility. With ambitious plans to transform transportation across Dubai, Joby and its partners are […]

The post Taking Flight in Dubai: Joby Aviation Breaks Ground on Revolutionary Air Taxi Network at DXB appeared first on Blakistons.

]]>

Taking Flight in Dubai: Joby Aviation Breaks Ground on Revolutionary Air Taxi Network at DXB

By Richard Ryan, Drone Lawyer

Joby Aviation’s recent announcement of its first vertiport construction at Dubai International Airport (DXB) marks a major milestone for urban air mobility. With ambitious plans to transform transportation across Dubai, Joby and its partners are leading the charge towards a new era of electric air taxis, promising quick, quiet, and sustainable travel. Yet, as with any groundbreaking innovation, navigating the complex regulatory landscape and addressing key safety, operational, and cybersecurity concerns will be crucial to success.

Joby Aviation’s construction of Dubai’s first vertiport for electric air taxis raises several pertinent legal and regulatory questions, especially given its location at Dubai International Airport (DXB) and its integration with Dubai’s transport network. As a drone lawyer with expertise in regulatory, operational, and safety challenges related to urban air mobility, here are a few key considerations:

1. Regulatory Approval and Certification: Achieving regulatory compliance in the UAE is essential. Joby’s air taxi service will require an Air Operator Certificate from the UAE’s General Civil Aviation Authority (GCAA). Given the innovative nature of eVTOL operations, what specific regulatory frameworks will govern Joby’s flight operations, safety protocols, and airspace usage? Will Joby need to comply with additional, potentially bespoke requirements for eVTOLs that differ from those for traditional aircraft?

2. Safety and Security Protocols: Operating air taxis in close proximity to commercial aviation at DXB introduces significant safety and security considerations. What measures are in place to prevent mid-air collisions or interference with DXB’s existing air traffic, and how will Joby collaborate with airport authorities to coordinate airspace usage? Additionally, are there protocols to mitigate risks associated with cyber threats and physical security at vertiports?

3. Noise and Environmental Compliance: Although Joby’s aircraft produces less noise than traditional helicopters, will Dubai’s environmental regulations impose specific noise and emissions standards, especially near densely populated areas? Furthermore, how will the company handle environmental concerns around battery disposal, considering the high throughput expected at DXB and other locations?

4. Liability and Insurance: The integration of eVTOLs within a multimodal transport system raises unique liability questions. In cases of service interruptions, accidents, or technical failures, will Joby assume full liability, or will responsibility be shared with Dubai’s RTA or Skyports? Also, how will passenger safety be insured, given that air taxis represent a novel form of transport?

5. Passenger Rights and Accessibility: Will passengers have specific rights, such as for delays or cancellations? How will Joby address accessibility requirements to ensure that its service is inclusive, particularly for individuals with disabilities?

6. Data Privacy and Cybersecurity: As a high-tech service relying on data for booking, operations, and possibly biometrics for passenger verification, what data protection measures will Joby implement in line with UAE privacy laws? Furthermore, how will the company safeguard sensitive flight data from potential cyber threats, especially at high-profile locations like DXB?

Joby’s initiative is an exciting step forward for urban air mobility, yet it will require a multifaceted legal approach to navigate these complex regulatory, operational, and safety challenges effectively.

Author Bio:
As a drone lawyer specialising in regulatory, operational, and safety challenges related to drones and urban air mobility and eVTOL (electric Vertical Take-Off and Landing) aircraft, I bring expertise in assessing the legal and regulatory hurdles in emerging technologies like Joby’s Dubai venture. My focus includes issues from airspace integration to passenger rights and cybersecurity, offering a unique perspective on the legal considerations essential for this pioneering project.

The post Taking Flight in Dubai: Joby Aviation Breaks Ground on Revolutionary Air Taxi Network at DXB appeared first on Blakistons.

]]>