Transport Canada's Proposed Designated RPAS Airspace: What Digital Geo-Zones Would Change for Operators

Transport Canada published Notice of Proposed Amendment 2026-005 on June 8, 2026. The document, titled "RPAS: Remote Identification, Community-Based Organizations, and Designated Airspace," bundles three related proposals into one consultation. Remote identification has drawn most of the attention, and the community-based organization model deserves its own discussion. This post looks at the third piece, the one that gets the least attention and may matter most to how Canadian drone operators learn where they can fly: designated RPAS airspace, published as digital geo-zones.

It is a proposal, not a rule. Nothing in this post changes what an operator must do today. Transport Canada is collecting comments until September 9, 2026, and any final regulations would follow the Canada Gazette process. The value of reading the airspace proposal now is preparation: understanding the direction, spotting the details that affect your operation, and filing a comment while the window is open.

The problem the proposal is trying to solve

Right now, when Transport Canada needs to keep drones away from a sensitive site, it relies on section 5.1 of the Aeronautics Act. According to Transport Canada, that provision is intended for temporary restrictions. The long-term section 5.1 restrictions that affect remotely piloted aircraft are listed in the Designated Airspace Handbook, the same publication used for Class A to F airspace. The handbook is published on a 56-day cycle.

A 56-day publication cycle is a poor fit for drone airspace information. A restriction can be created, changed, or lifted while the handbook is between editions. A pilot who relies only on the handbook can plan against information that is already stale. The proposed framework answers that problem in three connected parts: a new airspace mechanism, a digital publication channel, and an on-aircraft alerting function.

What designated RPAS airspace would be

The proposal would create a purpose-built tool called designated RPAS airspace. Transport Canada describes it as a mechanism to restrict or set conditions on drone flight, on a temporary or permanent basis. It is not a new class of airspace. It would not change how the existing Class A to G system works, and it would not change how controlled airspace permissions function.

The mechanism would apply to drones only. Transport Canada has stated that it is not intended to create airspace that only drones can use. Other tools already exist to exclude crewed aircraft, including Class F airspace designations and section 5.1 of the Aeronautics Act. The new mechanism gives Transport Canada the means to create restrictions, prohibitions, caution areas, operational requirements, and equipage requirements for drones.

Transport Canada also describes the change as replacing the current practice of using section 5.1 for drones. The new framework would be permanent and enforceable, where section 5.1 was intended for temporary measures.

One detail matters for anyone who works near sensitive sites: requests would not come only from the regulator. Transport Canada has said anyone would be eligible to request a designated RPAS airspace restriction, including law enforcement and operators of critical infrastructure. For a request to be considered, the requester would need to demonstrate that the airspace request is in the public interest and that the restriction is necessary to ensure safety and security. Transport Canada is developing internal processes to assess requests and says it will provide guidance once those processes exist.

Geo-zones: the publication channel

The second part of the proposal is the geo-zone. A geo-zone is the digital expression of designated RPAS airspace, published as a map dataset that machines can read. Transport Canada is proposing near real-time distribution of geo-zone and designated airspace datasets through electronic means, downloaded via a firmware update to the pilot's ground control station.

The design matters for manufacturers as much as pilots. Transport Canada says the geo-zone datasets would be modeled closely after the standards established in EUROCAE ED318. Transport Canada would provide the datasets to manufacturers, and manufacturers of compatible drone models would be required to provide pilots with up-to-date geo-zone data and updates, drawn exclusively from the Transport Canada dataset. In other words, the proposal points to a single authoritative source for drone airspace restrictions, distributed through the equipment pilots already use.

Equally important is what geo-zones would not contain. Transport Canada has said the datasets would include designated RPAS airspace only, because the new mechanism applies only to drones. They would not communicate existing airspace structures such as Class A to F airspace. And restrictions that exist under other legal frameworks would stay outside the dataset. National and provincial parks, for example, restrict drones through rules that prohibit taking off and landing in parks, which is a legal restriction rather than an airspace restriction. That information will continue to be available in the Drone Site Selection Tool. The point is a practical one: a geo-zone dataset is not a complete map of every reason a flight might be unauthorized. Drone pilots remain responsible for understanding and following all applicable non-airspace rules and laws.

A transition period, not an instant cutover

Transport Canada anticipates a short transition period in which current RPAS restrictions would coexist in both the Designated Airspace Handbook and the new Transport Canada publication, which may be a website. After that, the intention is for the list of RPAS restricted airspaces to exist exclusively in the new publication and the geo-zone dataset.

For operators, the transition detail is worth noting. During the overlap, two sources would carry the same restrictions, and a pilot would need to know which one is current for a given day. After the move is complete, the handbook would no longer be the place to look for RPAS restrictions. That is the kind of change that quietly breaks a routine checklist if nobody updates the reference list.

Geo-awareness: information, not a fence

The third part is geo-awareness, a function on drones that are capable of supporting it. The aircraft would use accurate, current data to warn the pilot about a potential breach of airspace. Transport Canada has been explicit about what this is not.

Geo-awareness is not geofencing. It is not intended to physically prevent a drone from flying in designated RPAS airspace, and it would not require permission from a manufacturer or anyone else before takeoff. It provides information, alerting, and additional awareness while the drone is flying. The pilot remains the decision-maker.

It is also not detect-and-avoid, and it is not a deconfliction service. Transport Canada says the objective is to support pilot awareness through visual representation of the airspace and an alerting function for a potential breach. The proposal does not provide aircraft deconfliction and is not a means of detect-and-avoid between conventional aircraft and drones.

The requirements would apply to drones and drone pilots only. Crewed aircraft pilots may download the data for general awareness, but Transport Canada does not intend to introduce any obligation for them to do so.

For equipment owners, the cost picture is modest by Transport Canada's own description. The agency says it does not anticipate high compliance costs, in part because the geo-awareness requirement would be in line with international partners and industry standards, meaning that most drone models in Canada would already be compliant. Transport Canada also says it does not intend to require that all drone models be geo-awareness compliant; only compatible models would need to have the function active. Preliminary cost assumptions were published in the notice of proposed amendment itself, and a formal cost-benefit analysis will be included in the Regulatory Impact Assessment Statement during the Canada Gazette, Part I process.

What operators should do now

First, treat the proposal as a proposal. The current rules remain the current rules. Pilots should keep checking airspace the way they do today, including the tools Transport Canada already points to, such as the Drone Site Selection Tool, and the other sources that apply to their operations. Nothing in the NPA authorizes a new kind of flight or removes an existing requirement.

Second, use the consultation window. Transport Canada hosted public information sessions in July 2026 and has published a summary of the discussion points, organized by theme. The summary is a useful way to see the questions the agency is already hearing, and the presentation materials are available on request. Comments are due September 9, 2026, and Transport Canada's drone safety page points to an official survey for submitting feedback. If your operation would be affected by how restrictions are requested, published, or enforced, this is the moment to say so with specifics.

Third, ask the questions that matter to your operation. The summary already shows where the open items are: how requests will be assessed and what evidence of public interest will look like; how quickly geo-zone updates will reach ground control stations; how the transition between the handbook and the new publication will be communicated; and how the alerting function will behave in practice. Operators who fly near critical infrastructure, event sites, or areas that attract frequent restriction requests have the most at stake.

Fourth, check your equipment's relationship to the proposal. Transport Canada says most models would already be compliant with the geo-awareness direction because it aligns with international standards. That is still worth verifying for the specific aircraft in your fleet, because the proposal would place the update workflow on manufacturers and would make the Transport Canada dataset the exclusive source of geo-zone data. A fleet with mixed equipment may end up with different update paths, and that is a configuration question worth tracking before it becomes a regulatory one.

Finally, keep the boundary between airspace rules and other rules visible. The proposal is about airspace. It does not change privacy law, park rules, local bylaws, or the other legal frameworks that can make a flight unauthorized even where the airspace is open. A designated airspace dataset that does not include park takeoff-and-landing prohibitions is a good reminder that no single map is the whole legal picture.

The practical takeaway

The designated airspace part of NPA 2026-005 is a quiet but structural change. It would give Transport Canada a permanent, enforceable tool for restricting drone flight, replace the temporary-use provision that fills that role today, and move the publication of RPAS restrictions from a 56-day handbook cycle to near real-time digital datasets delivered through the ground control station. It would also establish a single authoritative source for drone airspace restrictions, which is genuinely useful if the data stays current and reaches pilots reliably.

None of that is law yet. The consultation is open until September 9, 2026, and the details will be refined through the Canada Gazette process. For a commercial drone team, the right response is to read the proposal, compare it with the way your team checks airspace today, and file a comment that describes the operational realities the draft does not yet address. The framework is heading toward digital airspace information for drones. Teams that plan for that direction now will have an easier transition when the rule lands.