Don’t just say you disagree. Show Transport Canada what changes in the real operation.
Transport Canada is asking for written feedback on proposed Remote Identification, Community-Based Organizations and Designated Airspace rules. This guide shows Canadian operators how to turn a general opinion into a specific, evidence-based submission.
NPA 2026-005 is a proposal, not a final rule. Formal comments must be submitted in writing through Transport Canada's official process.
Useful regulatory feedback explains the real operation, identifies the practical problem and proposes a workable alternative. “Remote ID is too expensive” gives Transport Canada little operational evidence. A stronger submission describes the fleet, missions, locations, affected workflow, likely cost or downtime, and a realistic transition or compliance option. Canadian businesses, public agencies, schools, training providers and recreational organizations can submit feedback through the official survey until September 9, 2026.
NPA 2026-005 is a proposal, not today's operating rule.
Transport Canada's public consultation covers a proposed amendment to Canada's RPAS framework. The proposal does not, by itself, change the rules that apply to today's flights.
Remote Identification
Proposed identification and positioning requirements for many RPAS operations, with manufacturer, pilot and service-provider implications.
Community-Based Organizations
A proposed framework for eligible recreational, educational and research organizations operating under approved safety procedures at fixed sites.
Designated Airspace
Proposed RPAS-specific tools for managing airspace access and communicating restrictions, operating requirements and other information digitally.
Useful evidence does not require a giant aviation department.
A small survey company, municipal department, volunteer public-safety team or university lab can explain implementation cost, staffing limits, fleet lifecycle and transition concerns that national-level commentary may miss.
Start with the operation, then build the argument.
Transport Canada can assess a comment more easily when the reviewer can see the operation behind it. Write down the mission before arguing for or against a specific provision.
Describe the work
State the aircraft, mission, operating environment, frequency and supervision model.
→Identify the problem
Explain which part of the proposal changes cost, compatibility, staffing, scheduling or risk.
→Quantify what you can
Use fleet counts, replacement cycles, training hours, downtime or implementation estimates.
→Offer a workable path
Suggest a transition period, technical pathway, reporting method or narrower requirement.
Weak: “Remote ID will be expensive.”
More useful: “Our organization operates six aircraft across recurring utility-inspection sites. A hardware-only Remote ID pathway could affect aircraft replacement timing, controller compatibility, fleet records and annual capital planning. We recommend a transition option that recognizes compliant retrofit modules and gives operators enough time to align replacements with existing lifecycle plans.”
Connect the technology proposal to fleet reality.
The proposal discusses performance-based Remote ID, manufacturer declarations, broadcast modules, public access to certain message elements and phased implementation. Operators can help by explaining where those pathways work — and where practical gaps remain.
Existing aircraft
- Which aircraft could have a native compliance pathway?
- Which aircraft may depend on a retrofit module or manufacturer update?
- What happens when an otherwise serviceable aircraft has no supported pathway?
- What transition period fits real fleet replacement cycles?
Privacy and access
- Which Remote ID fields should the public be able to view?
- How should aircraft and control-station location be displayed?
- Who should be able to connect a serial number with registration or operator identity?
- What safeguards should apply to stored or networked data?
Technical evidence
- How should an operator verify a model or module declaration?
- What serial-number, firmware, controller or registration records should a fleet retain?
- How should a field team prove that Remote ID was functioning before and during a flight?
- How should software and hardware changes be documented?
Implementation cost
- What would modules, replacement aircraft, training and administration cost?
- How much downtime would testing or fleet conversion create?
- How would the burden differ for small businesses, municipalities, volunteer teams and universities?
- Could a phased or risk-based approach reduce cost without removing accountability?
The proposal says public third-party applications could show required message elements such as aircraft and control-station locations without displaying the pilot's name. It also proposes that only Transport Canada would have access to registration and identity information linked to Remote ID data. These remain proposed details.
Describe the aircraft, software and site together.
A fleet comment should account for the controller, software, firmware, batteries, maintenance records and procurement cycle around the aircraft. A remote site may also depend on reliable connectivity, current airspace data and a defined supervision model.
Document the model, configuration, batteries and remaining service life.
Include the controller, software, firmware and supported update pathway.
Connect maintenance, procurement and fleet records to the proposed requirement.
Explain connectivity, airspace data, supervision and recurring mission needs.
Ask how new airspace information works during a real mission.
Transport Canada says one purpose of the proposal is to create more suitable mechanisms for managing RPAS airspace access and communicating access rules to pilots and operators.
The proposal discusses downloadable geo-zone datasets, collaboration with NAV CANADA, possible publication through a new Transport Canada publication or modified Designated Airspace Handbook, and geo-awareness functions for compatible systems.
Which official platform will publish Designated Airspace and geo-zone data?
How quickly will a new or changed restriction appear in operator-facing tools?
Will the data integrate with existing flight-planning, fleet and dispatch systems?
How will temporary changes and urgent restrictions be communicated?
How should recurring sites such as construction projects, mines, substations or dock locations be handled?
How will Designated Airspace interact with existing controlled-airspace authorization?
What changes for recurring or remote operations when connectivity is limited?
How should emergency-response access work when restrictions change quickly?
Strong feedback gives Transport Canada something concrete to assess.
Support or opposition becomes more useful when the submission explains the operational reason, adds evidence and offers a workable path.
Equipment questions and operating questions belong together.
Fleet configuration determines what can be updated, replaced or recorded. Operational context determines whether that technical pathway works at the job site.
SpeedyDrone
- Equipment and controller implications
- Current fleet configuration
- Product lifecycle and procurement timing
- Software, firmware and accessory ecosystems
- Customer questions about future purchases
AlteX droneHUB
- Regulatory education
- Pilot training
- Operational context
- Industry discussion
- Stakeholder engagement
SpeedyDrone and AlteX can help customers understand the equipment and operational questions, but every stakeholder should submit its own evidence and position through Transport Canada's official process.
Keep the final comment short, traceable and operational.
Regulatory feedback does not need inflated language. It needs a clear line from the proposal to the operation and a record Transport Canada can understand.
Keep confidential customer, security and personal information out of a public or regulatory submission unless it is necessary and you understand how it will be handled. Aggregated fleet and cost data may be enough to explain the issue.
Read the official notice and identify the exact section that affects your operation.
Gather fleet, mission, staffing, cost and transition facts before drafting.
Separate current Canadian requirements from the proposed changes.
Explain one issue at a time and connect each point to operational evidence.
Offer a workable alternative, clarification or implementation option where possible.
Submit through the official channel by September 9, 2026, and retain a copy of the final response.
Turn operational experience into written feedback.
Read the proposal, document the effect on your fleet or mission, and send your own evidence through Transport Canada's official consultation.
NPA 2026-005 feedback questions
When is the NPA 2026-005 feedback deadline?
Transport Canada's Drone Zone notices state that the public consultation closes on September 9, 2026.
Is NPA 2026-005 already Canadian law?
No. It is a Notice of Proposed Amendment. It does not change current operating requirements by itself, and the final wording may change after consultation and the formal regulatory process.
Who can submit feedback on the proposed drone rules?
The consultation is open to the public. Businesses, government departments, public-safety organizations, universities, training providers, recreational groups, manufacturers and individual operators may all have relevant evidence.
What should a useful regulatory comment include?
Describe the operation, identify the affected proposal, explain the practical effect, provide evidence such as fleet or cost data, and suggest a workable alternative or transition where possible.
What Remote ID information does the proposal discuss?
The proposal discusses aircraft identity, aircraft and control-station location and altitude, a timestamp and emergency status. It contemplates public access to required message elements without displaying the pilot's name, while Transport Canada would retain access to linked registration and identity information.
Can SpeedyDrone or AlteX submit feedback for my organization?
Their role is to help customers understand equipment, training and operational questions. Each stakeholder should submit its own evidence and position through Transport Canada's official process.
Where can I read the complete proposal?
Use Transport Canada's official NPA document and Drone Zone consultation notices. This guide and the related SpeedyDrone and AlteX articles provide practical context but do not replace the official text.
Where do I submit official NPA feedback?
Transport Canada's Drone Zone links to the official NPA survey. The official consultation document also lists a written-comments email address. Verify the current instructions on the Transport Canada notice before submitting.
Verify the proposal before submitting
- Transport Canada Drone Zone Issue 8: NPA consultation notice
- Transport Canada Drone Zone Issue 9: information sessions and formal-feedback reminder
- Transport Canada / CARAC: official Notice of Proposed Amendment document
- Transport Canada: official NPA feedback survey
- SpeedyDrone: Canada's Proposed Drone Regulation Changes
- AlteX droneHUB: Canada's Drone Regulations Are Changing
- SpeedyDrone: Transport Canada Drone Safety Regulations
- SpeedyDrone: DJI Enterprise Drones in Canada
Checked August 18, 2026. This article is practical educational information, not legal advice and not a submission on behalf of any operator. NPA 2026-005 is a proposal, not current operating authority. Review the official notice and current Canadian Aviation Regulations before making operational or compliance decisions.
