FAA Part 108 vs EASA SORA 2.5 vs UK CAA SORA: A Complete Comparison of BVLOS Frameworks (2026)

Between April and September 2025, all three major Western aviation regulators released or significantly updated their BVLOS frameworks. The UK CAA launched its SORA digital platform in April. The FAA published the Part 108 NPRM in August. EASA adopted SORA 2.5 in September.

If you're a drone operator, manufacturer, or service provider working across any combination of these markets, you now face three distinct compliance pathways with zero mutual recognition between them. Your Part 108 approval means nothing in Europe. Your SORA authorisation carries no weight with the FAA. And nobody has put together a proper side-by-side comparison of all three. Until now.

This article is the FAA Part 108 vs EASA SORA BVLOS comparison that the industry has been missing. It covers the US, EU, and UK frameworks, structured around the decisions you actually have to make: how to assess risk, certify your aircraft, qualify your people, and get operations approved. Not a regulatory textbook. A practical guide you can plan around.

The Quick Comparison

Before we get into the detail, here's the overview. Print it. Pin it up. You'll keep coming back to it.

That's the snapshot. Now let's unpack what each of these means in practice.

Understanding the Fundamental Architecture

The single most important distinction between these frameworks is also the one most people miss: Part 108 is a regulation. SORA is a methodology.

The FAA's Part 108 is a standalone piece of law. A new part of the Code of Federal Regulations that creates a self-contained legal framework for BVLOS operations. It covers operations, airworthiness, personnel requirements, maintenance standards, and even establishes a companion Part 146 for Automated Data Service Providers that support UTM integration. One rulemaking, complete package.

EASA's SORA 2.5 is fundamentally different. It's not a regulation itself. SORA is a risk assessment methodology, developed by JARUS and published by EASA as an Acceptable Means of Compliance (AMC) under the existing EU Regulation 2019/947. It sits within the Specific category of EASA's three-tier system (Open, Specific, Certified) and tells operators how to assess and mitigate risk. The regulation already exists. SORA is the agreed method for complying with it.

The UK's version follows the EASA model structurally. UK SORA serves as an AMC under the UK's retained version of EU Reg 2019/947. But the CAA has layered on national adaptations: a digital application platform that went live in April 2025, specific guidance for Atypical Air Environments through CAP 3040, and a staged BVLOS roadmap laid out in CAP 3182.

Why does this structural difference matter?

Because it determines how much flexibility you have as an operator.

Under SORA, you build a safety case from the ground up. You define your concept of operations, assess your specific risks, propose your own mitigations, and present the whole package to your National Aviation Authority for review. The methodology gives you a structured process, but the output is tailored to your operation.

Under Part 108, the FAA has done much of that work for you. The rule pre-defines risk categories based on population density, specifies the technical requirements (detect-and-avoid, Remote ID, UTM integration), and determines whether you need a Permit or an Operating Certificate based on where and how you fly. Less flexibility, but potentially a faster and more predictable path to approval.

Think of it this way: SORA hands you a detailed template and asks you to build a safety case. Part 108 hands you a framework and asks you to fit your operation into it.

How Each Framework Assesses Risk

Risk assessment is where the philosophical differences between these frameworks get tangible. This is also where it starts to affect your day-to-day planning.

EASA SORA 2.5: The Quantitative Approach

SORA 2.5 runs operators through a structured 10-step process (down from 11 in SORA 2.0) that separately evaluates ground risk and air risk.

Ground risk is determined by the intrinsic Ground Risk Class (iGRC), which SORA 2.5 now calculates using a quantitative model anchored in population density data. Gone are the vague qualitative labels of "sparsely populated" or "populated environment" that caused so many interpretation headaches under SORA 2.0. Instead, operators use precise population density figures from EASA's harmonised dataset, built on JRC/Copernicus data and mapped to a hexagonal grid with 250-metre cells.

The iGRC is then modified by strategic mitigations. SORA 2.5 splits these into three distinct categories:

• M1A (Sheltering): Flying over people who are inside structures or protected vehicles
• M1B (Operational Restrictions): Limiting the operational volume to a controlled ground area
• M1C (Ground Observation): Using visual observers to confirm the area is clear

This replaced the less structured approach in SORA 2.0 and eliminated a lot of the ambiguity that frustrated both operators and regulators.

Air risk is classified by Air Risk Class (ARC-a through ARC-d), based on the airspace environment and the probability of encountering other aircraft. Worth noting: the air risk assessment is being overhauled more substantially in the coming SORA 3.0, so expect changes here.

Ground and air risk scores combine to determine a Specific Assurance and Integrity Level (SAIL), from SAIL I (lowest burden of evidence) to SAIL VI (highest). Your SAIL dictates the Operational Safety Objectives (OSOs) you need to meet and the level of evidence required to satisfy your NAA.

One significant change in 2.5 that caught some operators off guard: the Emergency Response Plan (ERP) is no longer a standalone M3 mitigation credit. If your SORA 2.0 safety case relied on ERP as M3, you'll need to revisit that.

FAA Part 108: Risk Built Into the Rules

Part 108 takes a different approach. Rather than asking operators to perform a per-operation risk assessment, the FAA has embedded risk into the regulatory structure itself.

The framework defines five population density categories, ranging from Category 1 (least populated) to Category 5 (most populated). Your category determines which tier of approval you need:

• Permitted Operations (lower-risk categories): Lighter oversight, simpler process
• Certificated Operations (higher-risk categories): Greater organisational requirements, more FAA scrutiny

The FAA doesn't use SORA. Full stop. This is a point many European operators find surprising. There is no direct correlation between SORA SAIL levels and Part 108 categories, something JARUS itself has acknowledged.

Instead, Part 108 prescribes specific performance-based requirements: detect-and-avoid capability, Remote ID, continuous position tracking, and integration with UTM through FAA-certified Automated Data Service Providers. You either meet these requirements or you don't. There's less room for an operator to propose alternative mitigations.

The upside is predictability. You know what you need before you start the process. The downside is rigidity. Critics argue it's less adaptable to operations where mitigations like geofencing, site access control, or parachute recovery systems could manage risk effectively regardless of what the population density map says.

UK SORA: The Hybrid

UK SORA follows the JARUS SORA methodology, making its risk assessment process structurally similar to EASA's. Ground risk and air risk feed into a SAIL determination, which drives OSO requirements.

Where the UK diverges is in how it applies the methodology to BVLOS specifically. The CAA has defined three distinct BVLOS pathways, each reflecting a different airspace environment:

1. Atypical Air Environment (AAE): Infrastructure corridors like railways, powerlines, and pipelines where manned aircraft rarely operate. This is where most near-term BVLOS activity will happen
2. Urban/Low-Level: Operations in built-up areas at low altitude
3. Fully Integrated: Operations in shared airspace alongside manned aircraft

Each pathway has staged maturity levels. AAE, for example, progresses from A0 to A1, and the CAA expects operators to build evidence through live operations before moving to the next stage.

The CAA also introduced dedicated guidance for AAEs through CAP 3040 Edition 3, which provides practical tools for designing operational volumes around real-world infrastructure. That includes a "smoothing" methodology for handling varying terrain heights along a corridor, and specific annexes covering railways, powerlines, pipelines, and bridges.

For operators already working within the EASA SORA framework, the UK version won't feel entirely foreign. But the BVLOS pathway structure adds a layer of specificity that EASA's approach lacks.

Airworthiness: Three Different Approaches to Aircraft Certification

All three frameworks agree that BVLOS operations demand more from the aircraft than basic VLOS flying. They just disagree on how much more, and how you prove it.

Part 108: Airworthiness Acceptance

The FAA created a new concept for this: Airworthiness Acceptance. It sits on the safety spectrum between Part 107 (where there's effectively no airworthiness requirement) and traditional type certification (which would be overkill for most UAS operations).

Under this process, manufacturers declare compliance against design and performance standards using industry consensus standards, rather than going through full FAA type certification. It covers UAS up to 1,320 pounds (600 kg). Think of it as structured self-certification with FAA oversight.

Part 108 also introduced the idea of Simplified User Interaction, requiring that the aircraft's interface be designed so that the Flight Coordinator can manage the operation through high-level commands rather than direct stick-and-rudder control. This is a design requirement baked into the airworthiness process, not just an operational preference. More on why that matters in the personnel section below.

EASA SORA: Graduated by SAIL

EASA's approach scales airworthiness requirements to the SAIL level of the operation:

• Low SAIL (I-II): Manufacturers can self-declare compliance. Minimal regulatory oversight
• Medium SAIL (III-IV): Requires a Design Verification Report (DVR) or can use EASA's Functional Test-Based (FTB) Means of Compliance, allowing manufacturers to demonstrate compliance through extensive functional testing rather than full analysis against the Special Condition
• High SAIL (V-VI): Pushes into the Certified category, requiring compliance with EASA's Special Condition for Light UAS (SC-Light UAS), which is closer to traditional type certification

The FTB Means of Compliance is worth paying attention to. It represents EASA's effort to make medium-risk airworthiness achievable without the full cost and timeline of traditional certification. But it comes with significant testing requirements.

UK SORA: Following the EASA Model (For Now)

The UK broadly follows EASA's graduated approach, with UK-specific pathways still under development. Operators should expect airworthiness requirements to align closely with the SAIL-based model. Watch for CAA-specific guidance as the system matures.

The Harmonisation Gap

JARUS has been working to bridge the differences between jurisdictions. Their published comparison of FAA Durability and Reliability (D&R) requirements against EASA's Light UAS Special Condition found meaningful differences in flight hour requirements, applicability thresholds, and how each authority calculates the required Target Level of Safety.

A team of experts has been formed to harmonise these requirements across FAA, EASA, Transport Canada, and ANAC Brazil. But for now, if you're a manufacturer pursuing airworthiness in both the US and Europe, plan for two separate compliance programmes. The evidence might overlap. The processes don't.

Personnel: Who Flies the Drone?

This is where the frameworks diverge most dramatically. And where Part 108 has generated the most controversy.

Part 108: The End of the Pilot?

Part 108 redefines the human role in drone operations. Instead of a remote pilot directly controlling the aircraft, it introduces two new roles:

• Operations Supervisor: Responsible for overall operational safety and compliance
• Flight Coordinator: The person who interacts with the automated system, issuing high-level commands through a simplified user interface

The key word is "simplified." Part 108's vision is for UAS operations where the system handles the flying and the Flight Coordinator manages the mission. Think "dispatch" rather than "fly." The Flight Coordinator doesn't need to be able to recover the aircraft manually. The system is expected to handle that.

The pushback has been fierce. Many operators and industry associations warned that this approach effectively rules out traditional pilot-in-the-loop control and eliminates the safety backstop of direct human intervention. Companies running successful BVLOS operations right now, with skilled remote pilots maintaining real control, feel the rule was written for a future that hasn't quite arrived yet.

There's a legitimate question here about who Part 108 was designed for. The emphasis on automation and simplified interfaces strongly favours large, well-capitalised companies building fully automated delivery platforms. Wing, Amazon, that end of the market. Smaller operators running infrastructure inspections with a competent pilot at the controls? They're left wondering where they fit.

EASA SORA: Remote Pilot Stays Central

EASA's approach is deliberately neutral on automation. The remote pilot remains the central concept, but SORA doesn't prescribe how much control that pilot needs to have. If you can demonstrate through your safety case that automated systems manage risk adequately, SORA accommodates that. If your operation relies on a highly skilled pilot maintaining direct control, that works too.

The focus is on outcomes (can you meet the Operational Safety Objectives?) rather than methods (how automated is your platform?).

UK SORA: Tiered Pilot Competency

The UK has taken a more structured approach by introducing tiered Remote Pilot Certificates that match pilot competency to mission complexity:

• RPC-L1: Covers VLOS operations in low-risk environments
• RPC-L2: The baseline for AAE BVLOS operations (embedded in CAP 3040 Edition 3)
• Higher tiers exist for progressively more complex and higher-risk operations

This creates a clear professional development pathway. You know what qualification you need for the operation you want to run, and you know what you're working toward next. That kind of clarity has been missing from the industry for years.

What this means in practice

If you're building an operation around skilled human pilots, EASA and the UK give you more room. If you're building a highly automated platform and want the regulatory framework to reflect that, Part 108 aligns more closely with your vision (assuming you can meet its Simplified User Interaction requirements).

For operators managing pilot qualifications, training records, and competency assessments across a fleet operating under different frameworks, the admin burden compounds quickly. Tracking multiple pilots across different certification standards, maintaining training logs, and ensuring everyone's current across jurisdictions is exactly the kind of operational headache that Dronedesk was built to solve.

Getting Approved: Scalability and Speed

Every one of these frameworks was designed to move beyond case-by-case waivers. How well do they deliver on that promise?

Part 108: Operational Area Approvals

Part 108's scalability model works like this: you get your operation approved for a defined operational area, and then you can fly routine missions within that area without seeking permission each time. That's a significant step up from the Part 107 waiver system, where each waiver was site-specific, took months to process, and had to be repeated for every new location.

But critics have a point. Requiring FAA review and approval for every operational area could become another bottleneck. If the area approval process takes months and you need dozens of areas, you've just recreated the waiver problem with a different name. Whether Part 108 actually delivers scalability depends entirely on how the FAA implements it in the final rule.

Current Part 107 BVLOS waivers typically take 30 to 60 days. There's also no clear transition mechanism for existing waiver holders, which has left many current operators feeling exposed.

EASA SORA: The 4-to-8-Month Problem

SORA requires a per-operation assessment, submitted to and reviewed by your National Aviation Authority. In theory, this is flexible and proportionate. In practice, approval timelines across EU Member States commonly run between four and eight months.

That timeline is commercially painful. And there's a deeper structural issue: each SORA assessment effectively starts from zero. Your track record from previous operations doesn't earn you a faster review. Experience isn't banked. Trust isn't accumulated. Risk gets reset rather than refined.

SORA 2.5 does reduce the burden for lower-risk operations. SAIL II VLOS operations now only require a compliance matrix, with no full documentation review needed. That's a genuine improvement. But for complex BVLOS operations, the timeline problem persists.

The Light UAS Operator Certificate (LUC) exists as a fast-track mechanism for experienced operators, allowing them to self-authorise certain operations. But the bar for obtaining an LUC is high, and adoption has been limited.

UK SORA: The Digital Middle Ground

The UK has made the most visible effort to tackle approval speed. The CAA launched a digital application platform alongside UK SORA in April 2025, and the results for simpler operations have been impressive. PDRA-01 self-declaration processing dropped from a typical 14 days to roughly 30 minutes average.

More complex SORA-based applications still take longer, and the CAA's Scheme of Charges introduced tiered fees that can be meaningful for smaller operators: £500/year for a PDRA-01, with complex operations potentially running into the tens of thousands. But the direction of travel is encouraging. The CAA's stated target is routine BVLOS by 2027.

The bottom line on approvals

None of these frameworks has fully solved the scalability problem yet. Part 108 was designed for scale but hasn't been tested in the real world. EASA SORA is flexible but slow. UK SORA is promising but still maturing. If you're planning operations across all three jurisdictions, budget for meaningful regulatory lead time in each one.

Airspace Integration and Right-of-Way

This is where things get political.

Part 108: The Right-of-Way Controversy

The most controversial provision in the entire Part 108 NPRM has nothing to do with drones specifically. It's about what it asks of manned aviation.

Part 108 proposes giving BVLOS drones presumptive right-of-way over manned aircraft that aren't broadcasting their position electronically, through ADS-B Out or an approved electronic conspicuity device. Drones would still yield to manned aircraft in Class B and C airspace, near airports, and over Category 5 areas. But everywhere else? If a manned aircraft isn't broadcasting, the drone gets priority.

The reaction from manned aviation has been exactly what you'd expect. AOPA, EAA, ALPA, and NBAA all pushed back hard. Their argument: you can't shift the collision risk burden onto manned aircraft, especially general aviation pilots operating in uncontrolled airspace where ADS-B Out isn't currently required.

The FAA reopened the comment period specifically on this provision. It closed in February 2026. Whatever the final rule says on right-of-way will be one of the most-watched decisions in aviation regulation this decade.

EASA: U-space Keeps It Simple

EASA handles airspace integration through a separate regulation entirely. U-space (EU Regulation 2021/664) creates designated airspace volumes where specific services are mandated: network identification, geo-awareness, flight authorisation, and traffic information.

The right-of-way rule is straightforward: drones yield to all manned aircraft. No exceptions. No electronic conspicuity conditions. No ambiguity.

U-space is separate from SORA. You can complete a SORA assessment without reference to U-space, and the reverse is also true. But in practice, BVLOS operations in shared airspace will increasingly need both.

UK: The AAE Playbook

The UK's approach reflects the CAA's pragmatic temperament. Rather than trying to solve full airspace integration in one step, the CAA has focused on Atypical Air Environments, areas where manned aircraft don't normally operate: along railways, around wind farms, over pipelines, below powerlines.

By starting where the conflict with manned aviation is lowest, the CAA can build an evidence base for safe BVLOS operations before expanding into more complex airspace. The CAP 3182 roadmap makes this progression explicit, moving from AAE operations through urban environments to fully integrated flight.

Electronic conspicuity is a big part of the UK strategy. The CAA and Ofcom made the 978 MHz frequency available for airborne transmission on UAS in early 2025. CAP 3040 now expects drones in AAEs to carry a Universal Access Transceiver (UAT) that transmits on 978 MHz and receives on both 978 and 1090 MHz.

Compared to Part 108's confrontational approach to right-of-way, the UK's strategy is more incremental. Less ambitious in the short term, but less likely to spark a regulatory fight that delays everything.

Traffic Management Infrastructure

BVLOS at scale needs more than rules for drones. It needs the digital infrastructure to support them: traffic management, deconfliction services, real-time data feeds.

US: Part 146 and ADSPs

Part 108 doesn't just regulate operators and aircraft. It creates an entire companion regulatory framework, Part 146, for Automated Data Service Providers (ADSPs). These are the entities that will provide UTM services: processing Remote ID data, providing traffic information, supporting deconfliction.

Building service provider regulation into the same rulemaking as the operational rules is an ambitious move. It means the infrastructure has a regulatory basis from day one. Whether it attracts enough service providers to create a functioning market remains to be seen.

Part 108 also mandates continuous reliable connectivity for operations, with documented fallback plans. C2 link reliability, coverage, and real-time monitoring aren't optional extras. They're built into the regulatory requirements.

EU: U-space Service Providers

EASA's equivalent infrastructure sits within the U-space regulation. U-space Service Providers (USSPs) deliver the required services within designated U-space airspace. The model is more geographically bounded: U-space applies in specific volumes declared by Member States, not universally across all airspace.

The separation between SORA (how you assess risk) and U-space (what services support your operation) can create confusion. They're complementary systems that weren't designed as one. Operators need to satisfy both.

UK: Work in Progress

The UK's UTM infrastructure is the least mature of the three. The CAA is developing its approach as part of the wider Airspace Modernisation Strategy, with 2026 airspace architecture proposals expected to underpin integrated UAS operations. But there's no UK equivalent of Part 146 or a finalised U-space service model yet. For now, UTM considerations feed into the SORA assessment on a case-by-case basis.

What This Means for Multi-Jurisdictional Operators

If you're a manufacturer selling into the US, EU, and UK markets, or an operator running BVLOS programmes across these jurisdictions, here's the practical reality.

There's no mutual recognition. Not yet. Your Part 108 approval means nothing in Europe. Your SORA authorisation carries no weight with the FAA. Your UK SORA operational authorisation won't automatically be accepted by EU Member State NAAs.

AUVSI's comment on the Part 108 NPRM pushed for the FAA to allow JARUS SORA as an optional Means of Compliance input for Part 108 approvals, and to use existing bilateral agreements (BASA/IPA) to recognise foreign evidence. If the FAA accepts this in the final rule, it could be the first real bridge between systems. AUVSI was clear, though: SORA should be an optional input, not a precondition for US approval.

Strategic planning considerations

Which market first? If you're building a highly automated delivery operation, the US under Part 108 is likely your primary target. The regulation was designed with that use case front and centre. If you're running pilot-led infrastructure inspection, the UK's AAE pathway offers the most pragmatic near-term route to routine BVLOS.

Structure your safety evidence for reuse. Even without mutual recognition, the underlying safety logic overlaps significantly. Population density analysis, detect-and-avoid test data, C2 link reliability evidence: all of this is relevant across frameworks. Document it in a format that can be adapted for different jurisdictions, not locked into one authority's template.

Watch the harmonisation space. JARUS and ICAO working groups are actively trying to align requirements across FAA, EASA, Transport Canada, and ANAC Brazil. The trajectory is toward convergence on safety principles, even if compliance processes keep diverging. Companies that build to the most demanding common standard will be best positioned when mutual recognition frameworks emerge.

Budget for parallel compliance. Three jurisdictions means three sets of applications, three different documentation formats, three different review processes, and three different fee structures. There's no getting around it. The operational overhead is real, from tracking pilot certifications across standards to maintaining flight logs that meet each authority's requirements. A centralised operations platform like Dronedesk can help keep things sane, but the regulatory work itself is unavoidably parallel.

Timeline and What's Coming Next

Here's what to watch for in 2026 and beyond.

FAA Part 108: The final rule is expected in Spring 2026, driven by a 240-day deadline set in the June 2025 Executive Order on drone policy. Implementation will likely follow 6 to 12 months after publication. The final rule could look significantly different from the NPRM, given the volume and intensity of industry feedback, particularly on right-of-way provisions, the pilot role question, and the operational area approval process. Over 3,000 comments were submitted during the original comment period, with a further round of comments closing in February 2026.

EASA SORA 3.0: Already in preparation. The big change will be a substantially overhauled air risk assessment methodology. SORA 2.5 updated the ground risk model. Version 3.0 tackles the air side. No firm publication date yet, but JARUS has signalled this is active work. If your current operations are sensitive to air risk classification, keep an eye on this one.

UK BVLOS by 2027: The CAA's CAP 3182 roadmap targets routine BVLOS operations by 2027 across priority use cases (NHS deliveries, emergency services, infrastructure inspection, commercial delivery). Initial commercial Advanced Air Mobility passenger flights are expected by end of 2028. The pathway is iterative, using live operations to refine policy at each stage.

Harmonisation: JARUS and ICAO working groups continue to push for alignment. But expectations should be realistic. We're moving toward a world where the safety principles converge and the compliance processes remain distinct. Plan for that.

The key open question for the next two years is whether any form of mutual recognition will emerge. Even partial recognition (accepting foreign test data or safety evidence without requiring operators to restart from scratch in each jurisdiction) would make a meaningful difference for the industry. We're not there yet. But the groundwork is being laid.

FAQ

What is the difference between FAA Part 108 and EASA SORA?

Part 108 is a complete standalone regulation that defines operational rules, airworthiness standards, and personnel requirements for BVLOS in the US. SORA is a risk assessment methodology used within the EU's existing drone regulation (2019/947) to evaluate and authorise operations in the Specific category. Part 108 tells you what the rules are. SORA gives you a process for building a safety case.

Does the FAA use SORA?

No. The FAA doesn't use the SORA methodology. Part 108 uses its own framework based on five population density categories. AUVSI has recommended that the FAA accept SORA as an optional Means of Compliance input, but this hasn't been adopted in the proposed rule.

How does UK SORA differ from EASA SORA?

UK SORA uses the same JARUS methodology as EASA but with national adaptations: a digital application platform, UK-specific BVLOS pathways (AAE, Urban, Fully Integrated), tiered Remote Pilot Certificates, and guidance documents like CAP 3040 for infrastructure corridor operations. The core risk assessment logic is similar. The application process and BVLOS-specific policies differ.

When will Part 108 be finalised?

The FAA is expected to publish the final Part 108 rule in Spring 2026, driven by the deadline from the June 2025 Executive Order. Implementation will likely follow 6 to 12 months after publication. Expect significant changes from the NPRM based on the volume of industry feedback.

Can SORA evidence be used for FAA Part 108 compliance?

Not currently. There's no formal mechanism for cross-recognition. That said, the underlying safety data (population density analysis, DAA test results, C2 link reliability data) can be structured for reuse across both frameworks. The evidence itself may be relevant even if the compliance formats differ.

What is SORA 2.5 and what changed from 2.0?

SORA 2.5, adopted by EASA in September 2025, introduced a quantitative ground risk model (replacing qualitative assessments), reduced the process from 11 to 10 steps, split strategic mitigations into three clear categories (M1A, M1B, M1C), removed the Emergency Response Plan as a standalone mitigation credit, and reduced documentation requirements for SAIL II VLOS operations. Air risk assessment will be overhauled in the coming SORA 3.0.

Which BVLOS framework is easiest for operators to comply with?

It depends on your operation. For highly automated delivery platforms, Part 108's pre-defined structure may be most predictable. For pilot-led operations in low-conflict airspace, UK SORA's AAE pathway offers a pragmatic route. For operations requiring maximum flexibility in how you mitigate risk, EASA SORA's customisable safety case approach gives the most room, at the cost of longer approval timelines. None of them are simple. The question is which type of complexity best matches your business model.

What are the airworthiness requirements for BVLOS drones?

All three frameworks require more airworthiness rigour than VLOS. Part 108 introduces "Airworthiness Acceptance" (manufacturer declaration against design standards). EASA scales requirements by SAIL level, from self-declaration through Design Verification to full type certification. The UK follows the EASA graduated model. Requirements aren't aligned across jurisdictions, so manufacturers should plan for separate compliance programmes.

---

All three BVLOS regulatory frameworks are moving fast. Part 108 could look very different in its final form. SORA 3.0 is on the horizon. UK pathways are still being refined. We'll be updating this comparison as each framework evolves.

Want to stay on top of cross-jurisdictional BVLOS developments? Subscribe to our newsletter for regular updates on regulatory changes that affect commercial drone operations.