Your Drone’s Obstacle Avoidance System Does Not Make It Legal for BVLOS. Transport Canada Just Said So.

DJI’s marketing calls it obstacle avoidance. Transport Canada’s BVLOS framework calls the requirement Detect and Avoid. Canadian operators are building BVLOS programs assuming these are the same thing. They are not — and the regulatory consequences of that assumption fall entirely on the operator, not the manufacturer.

What Transport Canada’s BVLOS Framework Actually Requires

Transport Canada’s framework for Beyond Visual Line of Sight operations requires operators to demonstrate a Detect and Avoid capability as a condition of SFOC approval. The DAA requirement is not about proximity sensing or automated braking. It is about the ability to detect cooperative and non-cooperative aircraft — including manned aviation operating under VFR without transponders in low-altitude airspace — and take appropriate action to maintain safe separation.

Transport Canada’s updated regulatory framework, which came into effect November 4, 2025, reinforced the expectation that BVLOS operators demonstrate a complete safety case addressing airspace integration. Obstacle avoidance systems designed to prevent ground-level collisions with static or slow-moving objects are not architected to detect a Cessna 172 on a VFR cross-country. The sensor technology, detection envelope, processing logic, and response protocols are fundamentally different problems.

The Advanced Operations exam tests regulatory knowledge. Passing it does not produce an operator who can write a defensible BVLOS safety case. The gap between credential and operational readiness is exactly where DAA assumptions become expensive.

The Manufacturer’s Role in the Confusion

DJI is the named antagonist here because DJI dominates the Canadian commercial drone market — and their marketing language creates genuine regulatory confusion. DJI’s documentation for platforms like the Matrice 350 RTK and Mavic 3 Enterprise describes obstacle sensing systems as safety features. They are. But DJI’s product safety objectives and Transport Canada’s BVLOS airspace safety objectives are not the same document.

Manufacturers are not obligated to tell you whether their systems satisfy a specific national regulator’s SFOC conditions. They build to product specifications. Transport Canada evaluates safety cases. The operator is responsible for understanding where those two things diverge.

In Clarion’s experience training commercial and government operators, the disconnect is consistent: operators read manufacturer documentation, see the word “safety,” and conclude the regulatory box is checked. It is not. The SFOC review process will surface this gap. The question is whether you discover it in training and proposal development, or after a rejected application and delayed program launch — both of which have real operational and financial costs for the organizations depending on your timeline.

What a Compliant DAA Approach Actually Looks Like

A Transport Canada-compliant DAA system for BVLOS operations is a layered safety architecture, not a single product feature. Depending on the operational environment, it typically includes some combination of: ADS-B receivers providing cooperative traffic awareness, ground-based radar or acoustic detection for non-cooperative traffic, defined airspace deconfliction protocols coordinated with Nav Canada and local aviation stakeholders, and procedural mitigations including restricted operational envelopes, time-of-day limitations, or NOTAM-based airspace reservations.

For lower-risk BVLOS environments — sparse airspace, controlled corridors, segregated operations — a procedural DAA mitigation can satisfy Transport Canada’s requirements if the safety case is built rigorously and the operational parameters are clearly constrained. The critical point is that the safety case must be built deliberately, not inherited from a product spec sheet.

Clarion works with government and corporate operators on exactly this architecture — translating what TC requires into what the operation needs to demonstrate before an SFOC application is submitted. The platform you fly matters far less than the safety case you can defend.

The Strategic Problem You Cannot Delegate to Your Manufacturer

The instinct to point at hardware capability when building a regulatory compliance argument is understandable. Hardware is tangible. Manufacturer documentation is professional. And in many domains, a certified system is a certified system.

Canadian drone regulation does not work that way at the BVLOS level. Transport Canada evaluates the operator’s safety case — not the aircraft’s spec sheet. The SFOC regime is explicitly designed to require operators to demonstrate understanding of risk, airspace, and mitigation at the specific operation level. A manufacturer cannot do that for you, and marketing language about onboard intelligence does not transfer into regulatory compliance.

The operators and organizations — federal, provincial, and corporate — who are building durable BVLOS programs in Canada are investing in the safety case architecture before they invest in the platform. They are asking Transport Canada’s actual question — how does your operation remain safe in shared airspace with manned aviation — and answering it with evidence, not product features.

If your current BVLOS program plan relies on obstacle avoidance as the DAA answer, you do not have a compliance gap. You have a program design problem.