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

Tactical Summary

The wireless industry just did what most commercial drone operators did not: it formally pushed back on the spectrum side of the new counter-drone regime. On August 3, 2026, CTIA, the trade association representing the major cellular carriers, filed four Petitions for Reconsideration and/or Clarification of the FCC actions that gave state and local agencies the spectrum authority to jam drones. On August 14, the FCC's Wireless Telecommunications Bureau and Office of Engineering and Technology opened a comment window on those petitions (Public Notice DA 26-853). Oppositions are due September 14, 2026. Replies are due September 29.

If you fly commercially, this proceeding is not background noise. The FCC's July package handed state, local, tribal, and territorial (SLTT) agencies a 180-day blanket nationwide Special Temporary Authority to operate radio-frequency counter-UAS systems, plus equipment-authorization relief and a set of legal rulings that thin out the interference protections that normally govern the band. CTIA is now asking the Commission to slow that down and put guardrails back. Whether those guardrails go in is, in plain operational terms, whether your command-and-control link and your Remote ID broadcast get treated as protected traffic or acceptable collateral when a jammer lights up near you.

We covered the operational rule itself in the SAFER SKIES interim final rule breakdown and the still-open DOJ/DHS comment window in the 17-days-to-comment operator piece. This post is the spectrum companion. Different docket, different agency, different deadline, and arguably the one with the most direct effect on whether you can keep a link.

What CTIA actually asked for

CTIA's four petitions each address the same four FCC actions taken on delegated authority: the Special Temporary Authority (STA) Order, the Equipment Authorization Waiver Order, the C-UAS Operations Declaratory Ruling, and the Experimental Testing Declaratory Ruling. The requested relief falls into two buckets.

On the two orders that authorize jamming hardware and spectrum use, CTIA wants explicit protection for lawful communications before nonfederal jamming proceeds. Its headline ask is that the FCC start with a carefully monitored pilot program rather than a blanket nationwide authority, so the agency can measure the actual interference risk before scaling. For the STA specifically, CTIA asks the Commission to clarify three things: that the authority is granted on a secondary, non-interference basis; that the Part 5 "stop buzzer" rules apply, meaning an operator must be able to shut the emission down immediately on request; and that an SLTT agency must notify, coordinate with, or get approval from affected incumbents before deploying a jammer. CTIA also wants the broad waiver of 18 separate parts of the FCC's rules replaced with narrow, specifically justified waivers.

On the two declaratory rulings, CTIA challenges the underlying legal theory. It argues the FCC cannot exempt SLTT agencies from Section 333 of the Communications Act, the bar on willful or malicious interference, when Congress declined to write that exemption into the SAFER SKIES Act itself. It contends the Commission misapplied the doctrine of derivative immunity, which reaches only parties acting as federal agents, to agencies the interim rule describes as operating independently. And on the experimental-testing ruling, CTIA argues the FCC's "self-interference" theory, that a licensee disrupting stations under its own control is not causing prohibited interference, conflicts with a Fourth Circuit decision reading Section 333's bar on interfering with "any" communications to include self-interference.

You do not have to agree with every legal argument to see the operational stake. Strip out the doctrine and CTIA is asking for the same things a careful drone operator should want: a pilot before a blanket rollout, a hard off switch, mandatory coordination with the people already using the band, and interference protection that is written down rather than assumed.

Why this hits the flight line, not just the boardroom

Most RF-based counter-UAS works by attacking the link, not the airframe. A mitigation system detects a target and floods the command-and-control frequencies, the GNSS band, or both, until the target loses control or fails safe. The physics do not care whose drone it is. A jammer aimed at a threat aircraft degrades every compatible receiver in its footprint, and that footprint is rarely a tidy circle. If you are flying a lawful, TFR-compliant, Remote ID-broadcasting mission a few hundred meters from a stadium, a correctional facility, or a critical-infrastructure site when a local system activates, you are inside the effect whether or not you are the target.

Three specific exposures are worth thinking through before you comment.

Your C2 link is the thing being attacked. The whole point of RF mitigation is to sever command and control. A blanket STA with no stop-buzzer requirement and no coordination duty means a lawful operator can lose the link with no warning and no recourse. CTIA's requested Part 5 stop-buzzer condition and pre-coordination requirement are the difference between a governed capability and an unannounced one.

Remote ID becomes evidence, or it becomes noise. You are now legally required to broadcast Remote ID. A well-designed mitigation program should ingest that broadcast and treat a compliant, identifiable aircraft differently from an anonymous one. Nothing in the current authority requires that. This is the strongest operator comment available: if an agency's system can receive Remote ID, a compliant broadcast should be a documented input to the threat assessment, not ignored while the jammer runs.

GNSS and comms collateral spreads past the fence line. RF mitigation that touches the GNSS band or shared cellular spectrum does not stop at the property boundary. That is precisely CTIA's institutional concern, and it maps directly onto yours. Geofenced, time-bound, logged emissions with reporting of collateral events are the guardrails that let you reconstruct what happened if a mission goes sideways near a protected site. We walked through the wider spectrum-and-licensing picture in the DA 26-314 drone spectrum reform breakdown, and the same tension runs through this proceeding.

The move: file an opposition-window comment by September 14

This is a reconsideration comment window, which means the mechanics differ slightly from a standard rulemaking. Under DA 26-853, parties file oppositions to CTIA's petitions by September 14, 2026, and replies by September 29. In practice, a substantive filing that supports specific relief CTIA requested is fully appropriate here even if it is not a formal opposition, and the record the Bureau builds is what informs whether these delegated actions get modified.

A focused operator filing does not need to litigate Section 333. It needs to connect the abstract interference concern to real flight operations. A structure that works: state who you are and where you fly, describe the concrete link-loss or GNSS exposure your operations face near protected categories, and endorse the specific safeguards, a pilot program before blanket authority, Part 5 stop-buzzer applicability, mandatory pre-coordination with affected incumbents, Remote ID as a threat-assessment input, and logged, reportable collateral interference. Reference the proceeding by the CTIA petitions and DA 26-853. File through the FCC's Electronic Comment Filing System.

One practical note on standing. You do not need to be a CTIA member or a carrier to file. A Part 107 operator, a public-safety drone-as-first-responder program manager, or a BVLOS delivery operator working near venues and infrastructure is an affected incumbent user of the same spectrum. That is exactly the constituency CTIA is arguing for, and an independent operator voice describing the actual mission profile strengthens the record in a way a trade association filing cannot.

The operator takeaway

The counter-drone authority is settled law. What is still open is the spectrum governance around it, and that governance decides whether lawful operators fly with protected links or with links that can be cut without notice. CTIA opened that fight on the interference side. The FCC put a September 14 clock on it. If your operations put you anywhere near a stadium, a prison, an event footprint, or critical infrastructure, the stop-buzzer rule and the coordination duty in this proceeding are worth more to your continued flying than almost anything in the daily drone news cycle.

If you need help translating your specific operating profile, your frequencies, your typical proximity to protected sites, into a filing that lands or into a compliance posture for flying near authorized C-UAS zones, that regulatory-to-operational translation is exactly the work we do. Reach out through the site.

Sources