The Federal Aviation Administration isn't the only agency moving aggressively on drone regulation this month. While the FAA's Section 2209 NPRM grabbed headlines for its critical infrastructure flight restrictions, the Federal Communications Commission has been running a parallel proceeding that addresses the other half of the drone security equation: communications and spectrum.
Together, these two actions represent the most coordinated federal response to drone security concerns since the industry began scaling commercially.
The FCC's Side of the Equation
On April 1, 2026, the FCC released a Public Notice seeking comment on three interconnected issues that have been bottlenecking both commercial drone expansion and counter-drone deployment.
Spectrum Access for Drone Operations The FCC is examining how drones access radio spectrum for command-and-control links, payload data transmission, and beyond-visual-line-of-sight communications. Current rules leave significant ambiguity about which frequency bands drone operators can use, particularly for long-range operations.
Multiple utility coalitions, including a joint filing from major electric utility associations, identified the 5030-5091 MHz band as essential for infrastructure-scale BVLOS operations. The band was approved for drone use in 2024, but final implementing rules remain pending — creating a frustrating gap between authorization and operational reality.
Experimental Licensing Modernization The FCC is considering streamlined experimental authorizations for drone testing, particularly for advanced operations that don't fit neatly into existing regulatory categories. This could accelerate development of detect-and-avoid systems, autonomous navigation, and other technologies critical for scaled commercial deployment.
Counter-UAS Technology Legality Perhaps most significantly, the FCC is examining the legal barriers surrounding counter-drone technologies. Current law — specifically Section 333 of the Communications Act — creates uncertainty about whether detection, tracking, and mitigation systems violate prohibitions on interfering with radio communications.
Industry commenters have proposed frameworks distinguishing between passive detection functions and active mitigation, arguing that detection and tracking should face fewer regulatory hurdles than jamming or spoofing systems.
Why Both Agencies Are Acting Now
The simultaneous action isn't coincidence. Several converging factors have created urgency:
Documented Security Incidents Both agencies cite a documented rise in rogue drone activity near sensitive facilities. The FAA's NPRM references attempts to disrupt electrical grid infrastructure, unauthorized surveillance of chemical facilities, and contraband delivery to correctional facilities. The FCC's proceeding notes similar incidents where communication vulnerabilities enabled or exacerbated security breaches.
Executive Order Pressure President Trump's June 6, 2025 executive order "Restoring American Airspace Sovereignty" directed multiple agencies to coordinate on drone security. The order established a Federal Task Force and mandated cross-agency coordination that appears to be driving this synchronized regulatory push.
Industry Maturation The drone industry has reached a scale where fragmented regulation is no longer tenable. Commercial operators need certainty about both where they can fly (FAA) and how they can communicate (FCC). Critical infrastructure operators need clarity about both airspace restrictions (FAA) and counter-drone authorities (FCC).
The Spectrum Bottleneck
One issue receiving particular attention is the 5030-5091 MHz band. Approved for drone use in 2024 but still awaiting final implementing rules, this band sits in a frustrating regulatory limbo.
Utility operators argue this spectrum is essential for infrastructure-scale BVLOS operations — the kind of long-range, beyond-line-of-sight missions that power line inspection, pipeline monitoring, and large-scale surveying require. Without clear access rules, operators are forced to cobble together solutions using unlicensed bands or temporary experimental authorizations.
The FCC's proceeding could finally unlock this bandwidth, but the timeline remains uncertain. Reply comments are due May 18, 2026, with agency action likely following later in the year.
Counter-UAS: The Thorniest Issue
The counter-drone technology question highlights the tension between security needs and communications law. Section 333 of the Communications Act prohibits interference with radio communications — but defining what constitutes "interference" in the context of drone detection remains legally murky.
Industry stakeholders have proposed a six-function framework:
- Detection
- Tracking
- Identification
- Situational awareness
- Communications testing
- Mitigation
The argument: detection, tracking, and identification are fundamentally different from active mitigation (jamming, spoofing, capture) and should face different regulatory treatment. The FCC hasn't endorsed this framework but included it in the record for consideration.
What Happens Next
Immediate Timeline
- FCC reply comments due: May 18, 2026
- FAA Section 2209 comments due: July 6, 2026
Medium-Term Outlook Both agencies will review records and move toward final action. For the FAA, this means proceeding through standard notice-and-comment toward a final rule. For the FCC, the Public Notice is record-building that doesn't commit to specific regulatory paths — any rule changes would require additional agency action, likely through a separate NPRM.
Industry Implications Stakeholders should monitor parallel developments including ongoing FCC Covered List litigation, FAA-TSA BVLOS rulemaking, and legislative activity related to counter-UAS authority. The intersection of these proceedings will shape the operational environment for years.
Bottom Line
The FCC and FAA actions represent complementary rather than competing approaches to drone security. The FAA addresses where drones can fly; the FCC addresses how they communicate and how unauthorized drones can be countered.
For operators and infrastructure owners, engagement in both proceedings is essential. The comment periods offer opportunities to shape frameworks that will define the industry's operational boundaries. For counter-UAS developers, the FCC proceeding is particularly critical — it could finally provide the legal clarity needed to bring detection and mitigation technologies to market.
The coordinated timing suggests federal agencies are treating drone security as a priority rather than a peripheral concern. For an industry that's grown accustomed to regulatory ambiguity, this clarity — even if restrictive — may be welcome.
