By Wesley Alexander • August 18, 2026 • 8 min read

Tactical Summary

The interim final rule that lets your local sheriff detect, track, and in some cases seize or disable a drone is already in force. It took effect July 1, 2026. But it is an interim final rule, and the agencies left the door open: public comments on docket FBI-2026-0001 (and its DHS mirror, DHS-2026-0496) close September 4, 2026 at 11:59 p.m. Eastern. As of this writing that is 17 days out.

That window matters more than most operators realize. When DOJ and DHS used the good-cause exception to skip normal notice-and-comment and publish the rule as effective immediately, they did not skip comment entirely. They deferred it. The record you help build now is the record the agencies use to write the final rule. If legal commercial and public-safety operators stay silent, the final rule gets shaped entirely by counter-UAS vendors and law enforcement associations. You do not want your operational exposure defined by people who have no incentive to protect your flight.

If you have not read the underlying framework yet, start with our full breakdown of what the SAFER SKIES rule authorizes and where your lawful flight now carries mitigation exposure. This post is the companion: what to do with the comment window before it closes.

Why a legal operator has standing here

There is a persistent myth that rulemaking comments are for lawyers and trade associations. They are not. The Administrative Procedure Act treats a substantive comment from an affected party as part of the record the agency must consider, and courts have repeatedly held that agencies have to respond to significant comments or risk having the final rule vacated as arbitrary. A Part 107 remote pilot who routinely flies near a stadium, a prison perimeter mapping contractor, or a public-safety drone-as-first-responder program manager is an affected party in the plainest sense. Your aircraft is the thing this rule authorizes bringing down.

The agencies also explicitly asked for input on several open questions. Per the Congressional Research Service summary of the IFR, DOJ and DHS requested comment on data retention requirements and on whether the C-UAS certifications should expire, how long a validity period should run, and what renewal should require. Those are not abstract legal points. They are the exact levers that determine how tightly a local mitigation program is governed near your operations.

The four things worth commenting on

You do not need to write a law review article. A focused comment that identifies a concrete operational problem and proposes a specific fix carries more weight than ten pages of general objection. Here are the lanes where an operator voice is genuinely useful.

Deconfliction with lawful operations. The rule authorizes mitigation of a drone assessed as a credible threat to a protected category. It does not build a clean mechanism for a properly authorized, TFR-compliant, Remote ID-broadcasting commercial flight to be distinguished from a threat before force is applied. The detection net does not read intent, and it often cannot read a waiver. Comment on the need for a pre-coordination or notification pathway so a legal operator working near a protected site is not treated as hostile by default. Tie it to Remote ID: if an agency's system ingests Remote ID, a compliant broadcast should be a documented input to the threat assessment, not noise.

Certification expiration and recurrency. The agencies asked directly whether certifications should expire. Say yes, and say why. A Mitigation Certification authorizes electronic and kinetic action in shared airspace. Currency requirements are standard in every other domain where an operator can bring an aircraft down. Argue for a defined validity period with recurrent training through the National Counter-UAS Training Center, not an open-ended credential.

Spectrum discipline and collateral effects. Most RF-based mitigation works by interfering with the command-and-control link. The FCC's companion actions, including the 180-day blanket Special Temporary Authority, deliberately reduced the friction that kept local jamming rare. That is efficient for agencies and risky for everyone else sharing the band. A jammer aimed at a threat drone does not respect a neat boundary. Comment on the need for geofenced, time-bound, and logged RF mitigation, and for reporting of collateral interference events that affect authorized operations nearby. Our breakdown of the FCC spectrum and licensing side of this package covers why this is the part most operators miss.

Transparency of the authorized systems and after-action data. The Authorized Technologies List and the make-and-model Authorized Systems List govern what hardware an agency can legally field. Mitigation actions must be reported to DOJ and DHS. Comment for public or at least operator-accessible reporting on where and how often mitigation is used, so the industry can see the actual operational footprint rather than guessing. You cannot manage exposure you cannot measure.

How to actually file

Go to regulations.gov and search docket FBI-2026-0001. Use the "Comment" button on the interim final rule document. Comments are public and attributed unless you request otherwise, so write as the professional you are: state your role, your operating environment, and the specific problem. Reference the rule by its Federal Register citation and the section you are addressing. One tight, specific comment beats a form-letter pile-on, and agencies weight substantive engagement over volume.

A practical structure that works: one paragraph on who you are and where you operate, one paragraph on the concrete operational problem, one paragraph with a specific proposed change, and a closing line on the safety or fairness rationale. Keep receipts of your submission. If you run a program, have more than one qualified person file from their own operational perspective rather than a single organizational letter, because independent operator voices read as broader affected-party interest.

The operator takeaway

This is not a comment window about whether counter-drone authority should exist. That fight is over; Congress settled it in the FY2026 NDAA and the rule is live. This is about the operational governance that surrounds that authority: how it deconflicts with lawful flight, how tightly it is trained and time-limited, how its spectrum use is bounded, and how transparent its use is. Those details are still genuinely open, and they are exactly the details that decide whether a legal operator working near an event, a correctional facility, or a critical-infrastructure site is protected or exposed.

Seventeen days is enough time to write three good paragraphs. It is not enough time to wait for someone else to protect your flight. If your operations put you anywhere near a protected category, file before September 4.

If you want help translating your specific operating profile into a comment that lands, or into a compliance posture for flying near newly authorized C-UAS zones, that is exactly the kind of regulatory-to-operational translation we do. Reach out through the site.

Sources