Europe loves to call itself the world’s regulatory gold standard for drones: safety-first, risk-based, future-ready. The poster child of that ambition is Specific Operations Risk Assessment (SORA)—the methodology that’s supposed to turn higher‑risk operations (BVLOS, urban flights, scalable services) from “no chance” into “approved, safely.” ‍

On paper, it’s elegant: define your Concept of Operations, assess ground and air risk, apply mitigations, calculate SAIL, then demonstrate compliance with Operational Safety Objectives.
In other words: structured freedom.

But Europe’s drone market doesn’t live on paper. It lives on runways, rooftops, ports, and infrastructure corridors where customers ask one brutal question: “When can you start?”

And across the continent, the uncomfortable answer has become: “Not sure.”

The real issue isn’t safety. It’s throughput.

SORA—by design—demands deep documentation and technical reasoning. That’s not inherently wrong. High‑risk operations should require high‑quality safety cases.
The problem is that the methodology has become resource-heavy and interpretation-sensitive, which makes it hard to scale across dozens of national authorities and thousands of applications. ‍

Even national authorities are signalling the strain. Switzerland’s civil aviation authority explicitly warns that processing time for SORA 2.5 applications might be longer than usual due to changes in the review process—while also noting that applicants may need specialised support if they lack aviation safety expertise in-house.

That’s not a “lazy regulator” story. That’s a systems story.

SORA’s hidden tax: inconsistency

A framework becomes a bottleneck when two competent reviewers can read the same evidence and reach different conclusions—triggering rounds of revisions that stretch timelines into months.
And the market is openly discussing the disparity: approvals can be weeks in one country and many months in another for comparable operations, largely because expectations and interpretations differ in practice.

This isn’t just frustrating—it’s commercially corrosive. In business, unpredictability is worse than strictness. You can plan around tough requirements. You cannot plan around “maybe 6 weeks, maybe 9 months.”

The paradox: the Open Category is winning by default

If the fastest path to revenue is staying in the Open Category, the industry will do exactly that—even if it limits scale and innovation.
That means Europe risks building a drone economy optimized for what’s easy to approve, not for what actually transforms infrastructure, logistics, inspection, or emergency response.

And that should terrify anyone serious about competitiveness.

Meanwhile, U‑space is talking scale on top of slow approvals

Europe’s U‑space narrative is about integrated, scalable drone traffic management: more flights, more automation, more density—safely. But the U‑space ecosystem depends on operators being able to access advanced operations predictably.
EUROCONTROL’s European Network of U-space Stakeholders Meeting in Helsinki (15 April 2026) is explicitly framed as a lessons‑learned exchange on ongoing implementation across Europe. [eurocontrol.int] [eurocontrol.int], [eurocontrol.int]

Here’s the contradiction: you cannot build a high-frequency drone economy on top of a low-speed authorisation pipeline.

If the gateway to “real operations” remains slow and uneven, U‑space risks becoming what Europe does best: an excellent concept with underwhelming deployment velocity.

SORA 2.5 is a step—maybe—but not the fix by itself

EASA has formally incorporated SORA 2.5 into the acceptable means of compliance and guidance material for Regulation (EU) 2019/947, explicitly aiming for simplifications and better harmonisation across Member States.
That’s promising. But the market’s lived experience suggests the real constraint isn’t the PDF—it’s the operational reality of review capacity, consistent interpretation, and predictable timelines. ‍

What needs to change (for real)

This doesn’t require less regulation. It requires regulation that scales.

• Consistency: clearer cross‑border expectations so “acceptable evidence” doesn’t mutate at every border. ‍
• Predictable timelines: even if conservative, businesses can plan when timelines are stable.
• Standardised artifacts: templates and “pre‑agreed evidence packages” for common BVLOS and urban use cases—so reviewers don’t reinvent the wheel. ‍
• A feedback loop that isn’t annual: the people building applications and reviewing them should be closing gaps continuously—not after the market has already moved on.

SORA can still be the backbone of Europe’s advanced drone operations. But if it keeps producing year-long uncertainty, it won’t be a backbone—it will be a bottleneck the market routes around.

‍