The NPA comment period closed on September 9. Here is what is left in your hands

The comment period closed, and the written record is what counts

Transport Canada's proposed amendment to Part IX, published on 8 June 2026, covered Remote Identification, a lighter regime for community organizations, and a new way to designate drone airspace. The consultation ran to 9 September. If your team asked questions during the July information sessions and assumed that counted as participation, it does not. Transport Canada stated that questions posed in those sessions would not be registered as official feedback, and that formal comments had to be filed through the official channels. What sits in the record now is what was submitted in writing.

What the record already contains

Transport Canada compiled the most common questions from the July sessions into a published summary with its own answers. Three of those answers matter more than the rest for a commercial team. Legacy and home-built aircraft would comply by retrofitting a broadcast module. That is the provision that decides whether an existing fleet stays usable, and it is the one worth checking against your own hangar. Remote ID would attach to the aircraft, not to the pilot. Each drone would carry its own Remote ID, and the information would be added to that drone's registration record in the Drone Management Portal. A four aircraft fleet is four retrofit decisions and four record updates, not one licence change. Transport Canada does not intend to require pilots to retake exams or flight reviews, and points to the existing 24 month recency requirement as enough for pilots to absorb the new requirements. That removes most of the training cost from the picture and leaves hardware plus recordkeeping. The proposal also sets out only two carve-outs, for aircraft flown on a community organization's fixed site and for microdrones, and it would let a pilot apply for an SFOC to operate without Remote ID. There is no blanket exemption for first responders or search and rescue, which is worth knowing before someone on your team assumes one exists.

Nothing here is law yet

This is still a notice of proposed amendment. On the timelines Transport Canada has described, nothing becomes mandatory for years and the shape of the final rule is unsettled. Buying equipment against a draft remains a bad trade. One transition detail is worth filing, though. Transport Canada expects a period in which the current RPAS restrictions sit in both the Designated Airspace Handbook and the new publication before moving across completely. If your crews brief from the handbook today, plan for a stretch with two live sources.

The work that belongs on this quarter's calendar

The useful action is administrative and cheap. Build a single list of every airframe you own, and for each one record the model, the manufacturer, whether it is registered in the Drone Management Portal, and whether the manufacturer has published anything about broadcast capability. Separate the home-built and modified airframes, because those are the ones the retrofit route is written for. Then place a placeholder line in next year's budget for one broadcast module per aircraft that needs one. You will not have a unit price until the rule is final and products are listed. That is fine. A placeholder with a count against it is enough to stop the number arriving as a surprise later.

The operational takeaway

Build the airframe inventory in the next few weeks, while this is still a proposal and nobody is under time pressure. A fleet list with a retrofit count attached takes an hour and answers the only question that eventually matters: how many aircraft will I have to change?