Safety and Security in Aviation 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.

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

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

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

Introduction

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

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

What Changed under SORA 2.5?

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

Lessons for the UK CAA

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

Best Practice for UK Drone Pilots and Operators

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

Conclusion

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

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

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

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

Airprox 2024294 – What Actually Happened at RAF Lakenheath?

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

Airprox 2024294 – What Actually Happened?

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

Summary of Key Facts:

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

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

Why This Matters to Drone Operators

1. Misidentification Risk

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

2. Electronic Conspicuity Limitations

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

3. ATC Service Levels – Know the Difference

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

Public Perception: A Persistent Challenge

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

Risk Assessment for UK Drone Operations

Potential Scenarios and Risk Levels:

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

Key Mitigations for Drone Operators:

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

Legal and Regulatory Observations

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

Final Thoughts

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

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

About the Author

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

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

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

admin.richard — Tue, 12 Nov 2024 15:11:41 +0000

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.