The next challenge for drone logistics is not simply enabling BVLOS. It is making safe operations repeatable, commercially sustainable and scalable.
Reports that Zipline is seeking additional investment at a valuation approaching US$20 billion illustrate the considerable expectations surrounding autonomous logistics. But the more interesting story is not the valuation. It is the pathway that brought the company to this point.
Zipline did not begin by trying to persuade regulators and communities of the merits of delivering coffee or takeout. When I witnessed its early operations in Rwanda in 2017, the company was addressing a clearly defined logistics problem: moving blood and medical supplies rapidly and reliably to healthcare facilities.
From there came operating experience, safety evidence, regulatory confidence and expansion into larger markets, including consumer delivery.
There are important lessons in that progression.
A successful pilot should do more than demonstrate technical feasibility and regulatory compliance. It should validate the logistics proposition, establish operational reliability, generate safety evidence and build confidence among regulators, customers and other airspace users. Most importantly, it should reduce the uncertainty surrounding the transition to regular commercial service.
That transition is a distinct stage. An initial operation may become a scheduled daily service, progressively extend operating hours—including nighttime operations—and ultimately operate around the clock where demand justifies it.
Only then does the broader scaling challenge come fully into focus: increasing flight frequency, introducing multiple aircraft, adding routes and replicating operations in other locations and jurisdictions.
A pilot designed without a credible pathway to regular service risks demonstrating technical feasibility without solving the harder problem of implementation.
From permission to repeatability
Special authorizations, waivers and individually assessed safety cases have played an essential role in developing beyond visual line of sight (BVLOS) operations. They allow regulators and industry to learn while technologies, operating concepts and safety evidence mature.
But they are not, by themselves, a scalable commercial model.
If the 101st flight, the tenth route or the next operating location requires nearly the same regulatory effort as the first, the economics remain difficult regardless of how capable the aircraft may be.
The regulatory framework must therefore evolve from approving individual operations toward assuring the system that produces safe operations.
That system is much broader than the drone. It includes the operator and its safety management, aircraft and technical assurance, command-and-control links, detect-and-avoid (DAA) capability where required, flight management, surveillance, digital traffic services, maintenance and operational control. It also includes interfaces with regulators, air navigation service providers (ANSPs), infrastructure providers and other airspace users.
For an operator entering a new country, it also requires an appropriate local operating and regulatory structure.
Commercial aviation offers a useful analogy. Regulators do not approve every airline flight. They certify operators and establish the privileges under which suitably equipped aircraft, qualified personnel and effective management systems can conduct commercial operations.
Drone regulation is moving toward a comparable principle, proportionate to the risks involved.
Once the necessary elements have been demonstrated to an appropriate level of assurance, operations within a defined risk and performance envelope should become repeatable and expandable with progressively less regulatory friction.
Scaling means more than one thing
There are four interconnected dimensions to scaling drone logistics:
-
- Operational scaling: Moving from one aircraft and route to multiple aircraft, routes and operators conducting increasingly frequent operations.
- Geographic scaling: Extending proven operations to additional locations and regions without rebuilding the entire safety case.
- Risk-envelope scaling: Progressing from relatively benign environments into more demanding ones, including populated areas, controlled airspace, aerodromes and ports, as operational evidence and technical assurance increase.
- Regulatory portability: Enabling credible technical assurance, operating experience and safety evidence to be recognized or reused across jurisdictions.
The fourth dimension is particularly important.
An operator entering another jurisdiction may bring years of BVLOS experience, an established safety management system and substantial operational evidence. That experience should not automatically confer operating privileges in another country; national authorities remain responsible for safety oversight.
But neither should credible evidence have to be recreated simply because it was generated elsewhere.
The challenge is to distinguish between what must remain jurisdiction-specific—airspace access, local operating requirements and regulatory accountability—and what can reasonably be recognized or reused, including technical testing, safety evidence and proven risk mitigations.
Greater portability does not require identical regulations or automatic mutual recognition. It requires frameworks capable of crediting credible evidence while retaining national oversight.
Putting the BVLOS scaling puzzle together
No single regulatory change will make BVLOS scalable. What is emerging instead is a set of interconnected puzzle pieces: proportionate operational authorization, reusable technical assurance, capable operators, aircraft identification, appropriate airspace access and digital traffic-management services.
Canada, the European Union and the United States are assembling these pieces in different ways and at different speeds. The challenge is not simply to put each piece in place, but to ensure they fit together to support regular commercial operations and their subsequent expansion.
Scaling requirement |
Canada |
European Union |
United States |
Risk-based operational authorization |
Part IX, Level 1 Complex operations and operational risk assessment (ORA); more complex operations may require SFOCs. |
Open, Specific and Certified categories, with SORA supporting risk-based authorization. |
Part 107 and waivers, alongside exemptions and Part 135 certification; proposed Part 108 dedicated to BVLOS. |
Reusable technical assurance |
Standard 922, declarations and Pre-Validated Declarations (PVDs) provide mechanisms for reusable assurance. |
Product requirements, recognized standards and SORA-based assurance. |
Aircraft and system assurance through existing approvals; proposed performance-based BVLOS requirements. |
Operator certification and privileges |
RPAS Operator Certificate (RPOC) for Level 1 Complex operations; additional authorizations may remain necessary. |
Light UAS Operator Certificate (LUC) can provide privileges to qualified operators. |
Part 135 certification for commercial delivery; proposed Part 108 introduces further operator-level pathways. |
Remote identification |
Remote ID requirements proposed under NPA 2026-005. |
Direct Remote ID and network identification services within U-space. |
FAA Remote ID requirements established. |
Designated airspace and access |
RPAS designated-airspace and geo-awareness mechanisms proposed under NPA 2026-005. |
Designated U-space airspace supported by mandatory digital services. |
Existing controlled-airspace authorization and restriction mechanisms; further automation under development. |
Digital airspace and traffic management |
Developing RPAS Traffic Management (RTM), with NAV CANADA’s rFIMS architecture and RPAS Service Providers (RSPs). |
Regulated U-space framework with certified U-space Service Providers (USSPs). |
Federated UTM using UAS Service Suppliers (USSs); proposed Part 146 for Automated Data Service Providers (ADSPs). |
One-to-many operations |
Emerging operational and regulatory challenge. |
Possible under appropriate risk assessment, authorization and operational safeguards. |
Increasingly important to scalable BVLOS, including under the proposed Part 108 framework. |
Operator establishment and market entry |
Foreign commercial operators cannot hold an RPOC; Canadian operating arrangements and other authorizations may be required. |
Common EU framework facilitates operations by EU-established operators, subject to applicable requirements. |
Foreign entrants require appropriate U.S. operating, regulatory and commercial arrangements or partnerships. |
Recognition and portability of safety evidence |
Limited international recognition; opportunity to credit proven foreign technical and operational evidence. |
Common EU framework facilitates cross-border operations, although national implementation remains relevant. |
Primarily domestic approvals; recognition of foreign operational evidence remains limited. |
Regulatory comparison as of October 2026. FAA Parts 108 and 146 remain proposed and under federal review. Transport Canada’s NPA 2026-005 consultation closed on September 9, 2026; its proposed provisions are not yet in effect.
The comparison reveals that there is no single regulatory scaling problem.
Europe has developed a relatively comprehensive framework connecting operational risk assessment, operator capability and digital airspace services. The United States has demonstrated substantial commercial operations through existing certification and exemption pathways, while developing a more standardized BVLOS framework.
Canada has introduced risk-proportionate BVLOS provisions and potentially valuable mechanisms for reusable technical assurance. Its geography also offers compelling opportunities for remote-community, industrial and infrastructure logistics.
The harder Canadian test will be whether these pieces can support regular operations in more complex environments, particularly where RPAS must coexist with conventional aviation.
Scaling does not have to wait for new regulations
The U.S. provides an instructive example.
Amazon Prime Air and Zipline have expanded commercial delivery operations under existing FAA arrangements, including Part 135 certification, exemptions, operating specifications and airspace authorizations. These arrangements have supported progressive increases in operating areas, flight volumes and operating hours.
The lesson is twofold.
First, scalable commercial BVLOS is possible even before a comprehensive new regulatory framework is in place.
Second, using these pathways requires substantial organizational capability, regulatory expertise, infrastructure, aircraft, qualified personnel and sustained investment.
Amazon and Zipline have the resources to establish much of this capability themselves. Smaller operators, including those entering foreign markets, may need to develop local operating organizations and partnerships for enabling services.
Part 108 therefore matters not simply because it would enable BVLOS operations, but because it could make a pathway already demonstrated by well-resourced operators more standardized, predictable and accessible to others.
The next bottleneck: one pilot, one drone
Regulatory authorization alone will not make drone logistics economically scalable.
A business model in which every additional aircraft requires another pilot or operator has an inherent constraint. Labour costs increase broadly with fleet size even as aircraft become cheaper and more autonomous.
One-to-many operations—where a qualified operator supervises multiple autonomous aircraft and intervenes when necessary—offer a pathway to greater operational efficiency.
But they also change the airspace-management challenge.
Remote identification is an important enabler, supporting aircraft identification, traceability and situational awareness. It does not, by itself, provide the surveillance performance or separation assurance needed for safe traffic integration.
Airspace design presents a separate challenge. Designated airspace, such as Europe’s U-space, can facilitate concentrated drone operations through defined operating environments and mandatory digital services. But designation should enable integration rather than create permanent dependence on segregated corridors.
Digital traffic management must bring these elements together. Strategic deconfliction can prevent conflicting flight plans before departure. At higher traffic densities, automated tactical conflict detection and resolution may also become necessary as trajectories, weather and traffic conditions change.
These services become more than an administrative layer. They form part of the safety architecture that enables scale.
The objective should not be separate airspace for every drone operator, but proportionate arrangements that allow multiple operators, aircraft types and conventional aviation to coexist safely.
Start where the value is demonstrable
There is another lesson from the evolution of drone logistics.
Aviation safety regulation should not decide whether delivering a medical sample is more socially worthy than delivering a pizza. Safety requirements should remain risk- and performance-based.
However, governments, regulators, ANSPs, infrastructure owners and communities inevitably make choices about where to devote scarce resources to demonstrations, airspace integration and new infrastructure.
That is where economic and societal value matters.
The strongest candidates for early deployment are not necessarily the most technologically novel. They are those that begin with the question:
What existing logistics problem are we trying to solve?
Medical logistics, remote-community resupply, industrial samples, offshore operations, critical infrastructure and time-sensitive port logistics can often identify an existing baseline against which the drone alternative can be measured.
Potential benefits include fewer road kilometres, shorter delivery times, reduced emissions, lower personnel exposure to hazardous environments, improved supply-chain resilience and more reliable connectivity.
These benefits must be demonstrated rather than assumed. A commercially sustainable operation requires sufficient customer demand, dependable service, appropriate infrastructure and a viable cost structure.
They also matter for public acceptance. Communities may reasonably view increasing numbers of low-altitude aircraft differently depending on whether they solve a recognizable problem or simply add another convenience service.
A credible customer-led use case provides the foundation around which the operator, regulatory pathway and supporting infrastructure can be developed.
From a route to a network
Ultimately, scaling drone logistics requires more than proving that an aircraft can safely complete a mission.
It requires a progression from technical demonstration to a dependable service, and from that service to an operating model that can be expanded and replicated.
Technical assurance must become reusable. Operator competence and safety management must support appropriate privileges. Proven risk mitigations should be transferable to comparable operating environments. Digital traffic-management services must enable multiple aircraft and operators to share airspace safely.
Equally important, the industry needs practical ways to translate established operating experience into locally accountable commercial operations, including through partnerships and recognition of credible safety evidence.
The distinction can be summarized as follows:
Today’s authorization-intensive model:
Individual aircraft + route + safety case + regulatory authorization → approved operation
The scalable operating model:
Assured systems + qualified operator + approved supporting services + defined operating envelope → repeatable service → expanding network
The individual pieces of the BVLOS scaling puzzle are increasingly taking shape. The challenge now is to make them fit together into a coherent regulatory, operational and commercial framework.
The drone industry has demonstrated that BVLOS flight is possible. Individual companies have also demonstrated that autonomous logistics can operate at significant scale.
The next challenge is institutional rather than purely technological: creating regulatory and airspace-management systems in which a successful operation can progress from demonstration to regular service, expand in volume and complexity, and ultimately be replicated elsewhere without beginning again from first principles.
That does not mean lowering safety standards or automatically accepting another jurisdiction’s approvals. It means making safety assurance increasingly reusable, allowing credible evidence to be credited and placing greater regulatory reliance on demonstrated operator capability and performance.
The real measure of regulatory maturity will not be how many BVLOS demonstrations can be approved, but how effectively successful demonstrations become dependable services—and dependable services become networks.
That is when BVLOS moves from demonstration to infrastructure.
And that is when drone logistics truly begins to scale.
Further listening: I discussed Zipline’s early development and approach to autonomous medical logistics with co-founder Will Hetzler in an episode of the Aviation Innovation Podcast entitled “Meeting a Medical Need with Speed“ and recorded in November 2019.
Continue the Conversation
Leadership, complexity, and navigating change are ongoing conversations rather than fixed conclusions.
For ongoing reflections, perspectives, and commentary, connect with me on LinkedIn—or subscribe to be notified when new essays, podcast episodes, and other insights are released.


