The Army Will Flood the Zone With Drones. Flooding Is Not Training.

The Canadian Army is committing to drones at scale. Doctrine notes are being drafted, procurement timelines are advancing, and the intent to put unmanned systems in soldiers’ hands is real and accelerating. What is not accelerating at the same rate is the pipeline to qualify the people holding the controllers. Doctrine on paper, hardware in the field, competence assumed in between — that is the gap no procurement chart captures, and it is where operational programs fail.

Doctrine Is a Description, Not a Qualification

A robotic and autonomous systems doctrine note tells an organization what capable operators should be able to do. It does not make operators capable of doing it. This distinction sounds obvious until you watch a program manager treat publication of a doctrine document as the completion of a training problem rather than the beginning of one. The Canadian Army is not alone in this error — it is institutional gravity. Procurement timelines have hard deadlines and budget accountability. Operator qualification pipelines are slower, harder to measure, and easy to defer when hardware delivery is the visible milestone. The result is a force with aircraft and without the depth of airspace knowledge, emergency procedure proficiency, and crew resource management culture that turns hardware into capability. In Clarion’s experience training government clients, the operators who create the most serious risk are rarely the ones who know they are unprepared. They are the ones who have been handed a system, told it is intuitive, and deployed before anyone established what qualified actually means in their operating environment.

The Civilian Pipeline Shows How Hard This Is

The civilian sector just ran this experiment in public. Transport Canada’s November 4, 2025 BVLOS reforms created a structured credentialing pathway — the Level 1 Complex certificate — designed to qualify individual pilots for lower-risk beyond visual line of sight operations. The result, as of August 13, 2026, is 709 Level 1 Complex certificates issued nationally, against 23,427 Advanced pilot certificates. Roughly 3% of the Advanced pilot population has crossed the BVLOS threshold, and the organizational authorization layer — the RPOC, required for commercial BVLOS operations — sits at 615 active certificates. The civilian industry had every incentive to move fast: commercial contracts, competitive pressure, market opportunity. It is still thin. The military operates under different regulatory authority than Transport Canada’s CARs Part IX framework, but it faces identical human-factors constraints. Complex airspace does not become more forgiving because the operator is wearing a uniform. If the civilian pipeline — purpose-built, commercially motivated, regulation-supported — is producing BVLOS-qualified operators this slowly, the assumption that military distribution of hardware will produce operational readiness faster needs to be examined directly.

What a Real Qualification Pipeline Requires

Operational readiness for military drone programs requires four things the doctrine note cannot supply: structured ground school that covers airspace classification, emergency procedures, and crew coordination; scenario-based flight training evaluated by qualified reviewers, not self-assessed by the student; currency standards that define how often operators must fly to remain proficient; and a command culture that treats lapsed currency as a grounding condition, not an administrative inconvenience. In Clarion’s experience working with government operators, currency is where programs decay fastest. Initial training happens, operators qualify, and then six months pass without a structured flight. The controller still powers on. The aircraft still lifts. The proficiency is gone and no one has a system to detect it. The military’s organizational discipline — the same culture that enforces weapons qualification standards — is the asset here. That discipline needs to be applied to operator qualification with the same rigour applied to any other crew-served system. The Army would not issue a crew-served weapon system and assume the crew knows how to use it. Drones deserve the same standard.

The Accountability Question Nobody Is Asking

When an unmanned system causes a fratricide, a civilian airspace incursion, or a mission failure attributable to operator error, the doctrine note will not absorb the consequence — the unit commander will. That accountability exists right now, before the first aircraft lands wrong, and it is the lever that should be moving qualification infrastructure faster than it is. Program managers and commanding officers who are receiving drone systems need to be asking one question before accepting delivery: what is the written standard that defines a qualified operator in this unit, who has the authority to certify that standard is met, and what happens when it lapses? If that question does not have a crisp answer, the program has hardware and intent but not capability. The Army’s commitment to unmanned systems is strategically correct. The scale of that commitment makes the qualification gap more dangerous, not less. Speed of procurement that outpaces depth of training is not modernization — it is risk accumulation with a procurement label on it.