Beyond Visual Line of Sight (BVLOS) Operations Archives - Blakistons

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

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

By Richard Ryan, barrister and drone lawyer

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

Outcome at a glance

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

Competence, cooperation and public interest flying

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

Lesson 1: Telemetry clarity

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

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

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

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

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

Five straightforward commitments

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

Technical reference: cross motorway separation

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

Assumptions from UK highway standards

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

Baseline components

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

Real world lateral separation (verge to verge)

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

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

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

Lean reading (narrow phrasing)

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

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

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

Add altitude for slant distance

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

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

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

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

Bottom line

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

About the author

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

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

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

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

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

“`By Richard Ryan, barrister and drone lawyer

What the paper actually shows (evidence you can cite)

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

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

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

Practical exposure points for stakeholders

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

What this means for drone pilots, operators, and companies

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

Implications for Drone Pilots

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

Implications for Operators

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

Implications for Drone Companies & Enterprise Users

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

Where legal support helps, assists, and mitigates

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

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

Talking points for meetings & panels

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

“`

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

When “Just a Minute” Becomes BVLOS: Legal Lessons for Drone Operators from CHIRP’s September 2025 Reports

admin.richard — Mon, 27 Oct 2025 19:14:43 +0000

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

VLOS is non-negotiable. Keep the aircraft in direct sight and be able to tell its orientation, with a full view of surrounding airspace.
Crowds are out of bounds. “Assemblies of people” are defined by the inability to disperse quickly, not by a headcount.
Operator ID labelling is strict. Visible, legible, on the airframe. Sub-250 g camera drones typically still require an Operator ID.
Endangerment provisions are broad. If someone is endangered or injured, regulators may consider reckless or negligent operation.
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

Based on incidents and analysis in CHIRP Drone/UAS FEEDBACK Edition 14 (September 2025).
BMFA pre-flight mnemonic SWEETS: handbook.bmfa.uk/13-general-model-safety
UK Drone and Model Aircraft Code: register-drones.caa.co.uk
Report a safety concern to CHIRP (confidential): chirp.co.uk/aviation/submit-a-report

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

Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland

admin.richard — Mon, 11 Nov 2024 07:47:06 +0000

Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland

By Richard Ryan, Blakiston’s Chambers

The recent Air Accident Investigation Unit (AAIU) report on the GEN 3.8 drone accident in Ireland gives us a significant case study on drone operations in urban areas. The incident highlights important safety and legal concerns that apply to unmanned aircraft systems (UAS), which are highly relevant to both Irish and UK drone regulations. This blog explores these issues in the context of the UK’s Aviation Act 1982 and the Air Navigation Order 2016 (ANO) and contrasts them with the legal framework in Ireland.

Overview of the Incident

In July 2022, a GEN 3.8 drone, conducting an urban delivery in Balbriggan, Ireland, experienced a mechanical failure when one of its propeller blades detached. This failure triggered an emergency descent and parachute deployment, causing a minor injury to a bystander. While the consequences of the accident were relatively minor, it underlines the importance of strong legal frameworks for safe drone operations, especially in populated areas.

The UK Legal Framework for Drone Operations

In the UK, drone operations are governed by several key laws and regulations:

1. Aviation Act 1982

The Aviation Act provides the overall legal framework for civil aviation in the UK. It gives the Civil Aviation Authority (CAA) the power to regulate aviation safety and enforce compliance.

The CAA can also develop specific regulations for unmanned aircraft to address the risks and challenges that drone technology presents.

2. Air Navigation Order 2016 (ANO)

The ANO is the primary legislation for regulating UAS operations. It categorizes drones into Open, Specific, and Certified categories, depending on the risk involved in the operation.

Article 241 of the ANO prohibits endangering people or property with a drone, requiring drones to maintain safe distances from people, buildings, and crowded areas. This is especially relevant for urban delivery flights.

3. Requirement for Operational Authorisation

For commercial operations, like the GEN 3.8 urban deliveries, an operational authorisation under the Specific category is required. This involves conducting a risk assessment and putting safety measures in place, such as emergency systems and proper documentation.

UK operators must prove to the CAA that they have identified and mitigated risks, which includes being prepared for mechanical issues like those seen in the GEN 3.8 case.

Comparison with Ireland’s Legal Framework

Ireland’s drone regulations are similar to those of the UK but have some key differences:

1. Regulatory Basis

In Ireland, drone operations are regulated by the Irish Aviation Authority (IAA) under the EU’s Implementing Regulation (EU) 2019/947, which applies to all EU member states. Like the UK’s CAA, the IAA oversees aviation safety and authorises specific operations.

Since the UK left the EU, it has adapted its own regulations to keep pace with the rapid evolution of drone technology.

2. LUC Certificates and Specific Category Requirements

Similar to the UK’s Specific category authorisation, Ireland issues Light UAS Operator Certificates (LUC) to operators meeting specific standards. This allows them to conduct higher-risk operations under IAA oversight.

The GEN 3.8 drone operated under Ireland’s Specific category. However, there were delays in reporting the incident, showing the need for better communication between the operator, IAA, and the AAIU.

3. Accident Reporting Requirements

In Ireland, regulations require that any drone accident resulting in injury or significant damage must be reported to the AAIU. The GEN 3.8 incident was only reported after it appeared on social media, suggesting delays in the reporting process.

In the UK, the ANO 2016 requires that accidents are reported to the CAA immediately, with strict penalties for non-compliance. This ensures a timely investigation and response, which is essential for public safety.

Key Takeaways for UK Drone Operators

The GEN 3.8 incident highlights several important lessons for drone operators in the UK:

1. Strict Compliance with Manufacturer Guidelines

The GEN 3.8 incident showed that its propellers were not designed for the way they were used, which led to the failure. UK law requires operators to maintain drones as per the manufacturer’s guidelines to avoid similar problems.

2. Robust Reporting Mechanisms

The delay in reporting the GEN 3.8 incident shows why prompt reporting is essential. In the UK, operators must report any accidents involving injuries or property damage to the CAA without delay. This helps ensure quick investigation and corrective action.

3. Operational Risk Assessment and Safety Measures

UK operators must conduct a risk assessment before undertaking operations. The GEN 3.8’s emergency parachute deployment is a good example of how an effective Flight Termination System (FTS) can help mitigate risks.

4. Public Liability and Insurance Requirements

UK law requires commercial operators to carry public liability insurance to cover injuries or property damage. The GEN 3.8 accident is a reminder of why adequate insurance is crucial for managing liability in unforeseen incidents.

Conclusion: Strengthening Drone Safety Regulations

The GEN 3.8 incident serves as a valuable lesson for drone operators and regulators in the UK and Ireland. It emphasises the importance of following safety standards, having efficient reporting systems, and conducting thorough risk assessments. In the UK, the Aviation Act 1982 and ANO 2016 provide a solid foundation for managing the risks of urban drone operations. As drone technology evolves and urban deliveries become more common, the UK must keep improving its regulations to ensure public safety.

For operators, compliance is only the beginning. By understanding drone regulations and putting the best safety practices in place, they can ensure their operations are both safe and legally sound.

Disclaimer: This blog is for informational purposes only and does not constitute legal advice. For legal counsel regarding specific situations, please consult a qualified drone lawyer.

The post Legal Issues in Drone Operations: A UK Perspective on Safety, Compliance, and Lessons from the GEN 3.8 Incident in Ireland appeared first on Blakistons.

Analysis and Recommendations on CAP 3040 | First Edition

admin.richard — Wed, 06 Nov 2024 13:38:21 +0000

Analysis and Recommendations on CAP 3040 | First Edition

1. Executive Summary

The CAA’s policy concept aims to enable Beyond Visual Line of Sight (BVLOS) operations for Unmanned Aircraft Systems (UAS) within an Atypical Air Environment (AAE). While the initiative is commendable for promoting innovation, the policy, as currently drafted, presents several challenges:
– Ambiguity in Definitions: The lack of precise definitions for key terms like AAE may lead to inconsistent application and legal uncertainty.
– Operational Burdens: Requirements such as pre-flight notifications, electronic conspicuity, and high-intensity lighting may impose significant burdens on operators, especially small and medium enterprises (SMEs).
– Potential Stifling of Innovation: The cumulative effect of stringent requirements may deter new entrants and hinder technological advancement.
– Legal Efficacy: For the policy to have legal effect, certain elements need to be codified into law or regulations.

2. Issues for Drone Operators

a. Ambiguity in Definition of Atypical Air Environment (AAE)
– Lack of Clarity: The document does not provide a clear, legal definition of an AAE, leading to potential inconsistencies in interpretation.
– Examples vs. Definitions: Providing examples (e.g., within 100ft of a building) without a firm definition creates uncertainty for operators attempting to comply.

b. Operational Requirements
– Pre-Tactical Flight Route Notification:
– Administrative Burden: Requiring Notices to Airmen (NOTAMs) for each operation may be impractical for frequent or short-duration flights.
– Coordination Complexity: Mandatory coordination with multiple stakeholders (e.g., military, emergency services) increases complexity.

– Electronic Conspicuity (EC):
– Equipment Availability: ADS-B equipment operating on 978 MHz UAT is not widely used in the UK, making compliance challenging.
– Licensing Issues: Reliance on OFCOM’s Innovation and Trial licensing procedures adds uncertainty and administrative hurdles and no doubt costs.

– High-Intensity Anti-Collision Lighting:
– Technical Challenges: The requirement may not be feasible for small UAS due to weight and power constraints.
– Cost Implications: Additional equipment increases operational costs, affecting profitability and competitiveness.

– Containment Solutions:
– Technical Barriers: Implementing robust geo-caging or equivalent systems may be technologically and financially prohibitive for some operators.

c. Application Process Limitations
– Single Site Per Submission:
– Operational Inefficiency: Limiting applications to one site may slow down deployment and increase administrative overhead.

d. Evolving Policy and Regulatory Uncertainty
– Continuous Review:
– Investment Risk: Operators may be hesitant to invest in compliance if policies are subject to change.
– Lack of Legal Certainty:
– Enforceability Issues: As a policy concept rather than law, operators may face legal ambiguities in enforcement and compliance.

3. Potential Impacts on the Drone Industry

a. Stifling Innovation and Market Entry
– Barrier to Entry: Stringent requirements may discourage startups and SMEs from entering the market.
– Reduced Experimentation: High compliance costs limit the ability to test new technologies and operational models.

b. Competitive Disadvantages
– Favoring Large Operators: Well-resourced companies are better equipped to meet the requirements, potentially leading to market monopolisation.

c. International Disparities
– Inconsistency with Global Standards: Reliance on U.S. standards (e.g., RTCA DO-282C) may create conflicts with other international regulations, affecting operators engaged in cross-border activities.

4. Recommendations for Amendments

a. Clarify Definitions and Parameters
– Precise Definition of AAE:
– Legal Clarity: Provide a clear, legally binding definition of AAE to reduce ambiguity.
– Criteria Establishment: Set specific parameters (e.g., exact distances, types of infrastructure) to qualify as an AAE.

b. Proportionality in Operational Requirements
– Risk-Based Approach:
– Scaled Requirements: Tailor operational requirements based on the risk profile of the UAS operation (e.g., size, weight, location).
– Exemptions for Low-Risk Operations:
– Simplify Compliance: Allow for exemptions or reduced requirements for operations posing minimal risk.

c. Streamline Application Process
– Multiple Sites Per Application:
– Administrative Efficiency: Permit applications covering multiple sites where appropriate, reducing bureaucratic hurdles.
– Standardised Procedures:
– Transparency: Develop clear guidelines and timelines for application processing.

d. Address Electronic Conspicuity Challenges
– Equipment Standardisation:
– Market Availability: Collaborate with manufacturers to ensure ADS-B equipment is accessible and affordable.
– Licensing Simplification:
– Permanent Licensing Arrangements: Work with OFCOM to establish permanent, streamlined licensing procedures for 978 MHz UAT.

e. Provide Flexibility in Mitigation Measures
– Alternative Solutions:
– Innovation Encouragement: Allow operators to propose alternative methods to achieve safety outcomes.
– Technology Neutrality:
– Avoid Prescriptive Requirements: Focus on performance outcomes rather than prescribing specific technologies.

f. Enhance Stakeholder Engagement
– Consultation Processes:
– Inclusive Policy Development: Engage with a broad range of stakeholders, including SMEs and industry groups.
– Support and Guidance:
– Educational Resources: Provide operators with clear guidance and training materials to aid compliance.

g. Align with UK Standards
– Develop Domestic Standards:
– Consistency: Establish UK-specific standards for technical requirements like anti-collision lighting.
– International Harmonisation:
– Global Compatibility: Ensure new standards are compatible with international regulations to facilitate cross-border operations.

5. Legal Requirements for Effective Implementation

a. Codification into Law
– Regulatory Framework:
– Statutory Instruments: Incorporate key policy elements into UK aviation law to provide legal enforceability.
– Amendments to Existing Regulations:
– Regulation (EU) 2019/947 Adaptation: Modify existing regulations to accommodate AAE operations and associated requirements.

b. Legal Certainty and Enforcement
– Clear Obligations:
– Operator Compliance: Define legal obligations clearly to ensure operators understand requirements.
– Enforcement Mechanisms:
– Penalties and Sanctions: Establish clear enforcement protocols for non-compliance to uphold safety standards.

6. Additional Relevant Points for the CAA

a. Balancing Safety with Innovation
– Proportional Regulation:
– Innovation Friendly: Ensure that safety regulations do not unnecessarily hinder technological advancement.
– Risk Management:
– Data-Driven Policies: Use empirical data to inform policy adjustments, maintaining safety without over-regulation.

b. Data Privacy and Confidentiality
– Data Handling Policies:
– Privacy Protection: Develop clear guidelines on data usage, storage, and sharing to protect operators’ proprietary information.

c. Future-Proofing Regulations
– Adaptive Frameworks:
– Technological Evolution: Design policies flexible enough to accommodate future technological developments.
– Regular Reviews:
– Stakeholder Feedback: Implement mechanisms for ongoing consultation and policy refinement.

d. International Cooperation
– Global Best Practices:
– Information Sharing: Engage with international aviation authorities to align policies and share lessons learned.
– Cross-Border Operations:
– Harmonized Regulations: Facilitate international drone operations by harmonizing standards where possible.

7. Conclusion

The CAA’s initiative to introduce the concept of Atypical Air Environment for BVLOS operations is a progressive step towards integrating UAS into the national airspace. However, without careful consideration and amendments, the policy may inadvertently stifle innovation and impose undue burdens on operators.
By clarifying definitions, scaling operational requirements appropriately, streamlining processes, and codifying necessary elements into law, the CAA can foster a regulatory environment that promotes both safety and innovation. Collaboration with industry stakeholders, legal experts, and technology providers will be crucial in refining the policy to achieve its intended objectives.

Recommendations Summary:

1. Clarify Definitions: Provide precise legal definitions for AAE and other key terms.
2. Proportional Requirements: Scale operational requirements based on risk assessments.
3. Streamline Processes: Allow multiple sites per application and simplify procedures.
4. Address EC Challenges: Ensure equipment availability and simplify licensing.
5. Flexibility in Mitigations: Permit alternative safety solutions and avoid prescriptive technologies.
6. Stakeholder Engagement: Enhance consultation and provide guidance resources.
7. Align Standards: Develop UK-specific technical standards and harmonise internationally.
8. Legal Codification: Incorporate essential policy elements into law for enforceability.
9. Balance Safety and Innovation: Maintain safety without hindering technological progress.
10. Protect Data Privacy: Establish clear data handling and confidentiality policies.
By implementing these recommendations, the CAA can create a robust regulatory framework that ensures safety while encouraging the growth and innovation of the UK’s drone industry.

8. Comparison with EASA PDRA03 and Lessons for the UK
Comparing the CAA’s position with the European Union Aviation Safety Agency’s (EASA) Pre-Defined Risk Assessment number 03 (PDRA03) reveals both opportunities and challenges for UK drone regulation. EASA’s PDRA03 offers a structured, risk-based framework that allows operators to self-declare compliance with specific conditions, reducing administrative burdens and accelerating operational approvals. This approach supports drone operators by providing clear guidelines while fostering innovation through flexibility in operations such as autonomous flights, multi-UAV control, and operations beyond visual line of sight (BVLOS) under certain conditions. In contrast, the CAA’s policy concept imposes more prescriptive requirements, such as mandatory NOTAM submissions for each operation and specific technical equipment like ADS-B transceivers, which may be unnecessary and bureaucratic for certain low-risk operations. The UK drone industry could benefit from adopting elements of the EASA PDRA03 by implementing a more proportionate, risk-based regulatory framework that emphasises operator declarations and standardised procedures. This would streamline the approval process, reduce administrative overheads, and encourage innovation while maintaining safety. Learning from the EU’s experience, the CAA can enhance its policies to better support the growth of the UK drone industry by embracing flexibility, reducing unnecessary bureaucratic requirements, and aligning more closely with international best practices.

Richard Ryan is an experienced drone lawyer specialising in unmanned aircraft systems (UAS) and aviation law. He provides expert legal guidance on regulatory compliance, licensing, and operational issues to clients navigating the complexities of drone technology.
Disclaimer: This blog is for informational purposes only and does not constitute legal advice. For legal counsel regarding specific situations, please consult a qualified drone lawyer.

The post Analysis and Recommendations on CAP 3040 | First Edition appeared first on Blakistons.