This bill authorizes the Secretary of State to conduct a domestic protection mission to counter credible threats posed by unmanned aircraft systems (UAS) or unmanned aircraft to State Department facilities, personnel, and assets located in the United States. The authority explicitly permits activities such as detection, interception of control communications, warning, disruption, seizure, and, where necessary, use of force against UAS without prior consent, subject to coordination and procedural safeguards.
The measure carves out statutory exceptions to several federal laws to enable those actions, requires interagency coordination (especially with the FAA and NTIA), sets privacy and records-retention guardrails, requires semiannual congressional briefings, and sunsets the authority after seven years. For compliance officers, aviation operators, and counsel, the bill creates an unusual domestic role for the Department of State that will intersect with FAA airspace management, communications law, and civil‑liberties oversight.
At a Glance
What It Does
The bill authorizes the Secretary of State to take a range of counter‑UAS actions—including monitoring, intercepting control signals, disrupting control, seizing, and destroying UAS—when a credible threat exists to designated facilities or assets. It allows the State Department to conduct research, testing, and training on counter‑UAS technologies and to accept assistance or funds from other federal and non‑federal entities.
Who It Affects
The bill directly affects Department of State Diplomatic Security personnel and contractors who protect U.S. diplomatic facilities in the United States; the Federal Aviation Administration (FAA) because of airspace impacts; telecommunications regulators (NTIA/FCC) where signal interception or disruption is used; and UAS operators whose aircraft may be intercepted, seized, or forfeited.
Why It Matters
This statute would be one of the first laws to vest a civilian foreign‑policy agency with explicit domestic counter‑UAS authorities, creating novel legal and operational overlaps between foreign affairs missions, aviation safety, communications law, and privacy protections. Entities responsible for airspace safety, spectrum management, and civil‑liberties compliance should expect new coordination and oversight requirements.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a time‑limited (seven‑year) domestic mission inside the Department of State focused on mitigating UAS threats to ‘‘covered facilities or assets’’ tied to the Department’s security and protection missions. It defines covered facilities by a risk‑based assessment that looks at threat intelligence, proximity to airports and populated areas, public access, and potential interference with communications or national‑security missions.
The Secretary may authorize trained State Department personnel and certain contractors to carry out specified counter‑UAS actions when the Secretary, in consultation with the FAA, determines a credible threat exists.
Those actions fall into two buckets: operational actions against specific UAS during an incident (detect, identify, monitor, intercept communications controlling the UAS, warn operators, disrupt control signals, seize or exercise control, confiscate, and employ reasonable force to disable or destroy) and preparatory activities (research, testing, training, and evaluation of equipment). The bill requires the State Department to test technologies and coordinate such testing and any operations with the FAA to avoid degrading aviation safety or interfering with airport operations or navigation.The bill also sets procedural and privacy constraints.
The Secretary must issue regulations and guidance, developed in consultation with the Department of Transportation and NTIA, that limit communications interception to what is necessary for the authorized actions and cap automatic retention of intercepted communications at 180 days unless specific exceptions apply (criminal investigation, national‑security support, statutory requirement, or litigation). The Secretary must provide unclassified semiannual briefings to a set of congressional committees that describe program activities, instances where counter‑UAS actions were used, impacts on the National Airspace System (NAS), and privacy/civil‑liberties safeguards.
Budget transparency requires a consolidated, unclassified funding display with an optional classified annex in each presidential budget submission.
The Five Things You Need to Know
The bill explicitly disapplies or carves out compliance with specific statutes—including 49 U.S.C. 46502, 18 U.S.C. sections 32, 1030, 1367, chapters 119 and 206, and section 705 of the Communications Act—to enable counter‑UAS activities by the Department of State.
Interception or access to communications used to control a UAS is allowed ‘‘only to the extent necessary’’ and records of intercepted communications must be deleted within 180 days unless needed for criminal investigation, ongoing security operations, or required by law.
Contractors may perform operations under the authority only if they are directly contracted by State, operate on government‑owned or -leased facilities, do not perform inherently governmental functions, and meet Department training and certification requirements.
Any UAS seized under the authority is subject to forfeiture to the United States under chapter 46 of title 18, and the Secretary may accept funds, supplies, or services from federal or non‑federal entities with or without reimbursement to support operations.
Before the Secretary implements actions or guidance, the bill requires coordination with the FAA and NTIA, mandates FAA review of testing to prevent aviation safety impacts, and compels semiannual unclassified briefings (with possible classified annexes) to multiple congressional committees for seven years.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Authority for Domestic Protection Mission
This subsection gives the Secretary of State authority to take actions necessary to mitigate a ‘‘credible threat’’ from UAS to covered facilities or assets in the United States and permits the Secretary to authorize Department personnel and contractors with protection duties to act. The text depends on the Secretary’s threat finding and consultation with the FAA to trigger operational authority, rather than creating a blanket power.
Enumerated Counter‑UAS Actions
The bill lists specific operational powers: detect, identify, monitor, and track UAS; intercept or access communications used to control the UAS; warn operators by multiple means; disrupt control signals; seize, exercise control of, or confiscate UAS; and use reasonable force to disable, damage, or destroy UAS. Practically, that list ties the Department to both kinetic and electronic countermeasures that have downstream effects on air traffic safety and communications integrity.
Research, Testing, and Interagency Coordination
Before deploying technologies operationally, the bill requires research, testing, training, and evaluation, and it conditions such activities on coordination with the FAA to avoid impacts to airport operations and the NAS. The Secretary must coordinate development of regulations and guidance with the FAA, FCC, and NTIA and must consult the FAA prior to any operational action to ensure aviation safety is preserved.
Privacy Protections and Limits on Use of Communications
Regulations must ensure communications interception complies with constitutional protections and federal law, limits interceptions to what is necessary, restricts retention of communications to 180 days absent narrow exceptions, and confines disclosure outside State to statutorily listed circumstances—investigative, law‑enforcement, national‑defense, or otherwise required by law.
Budget Transparency, Congressional Briefings, and Sunset
The Secretary must include a consolidated, unclassified funding display for these activities (with an optional classified annex) in presidential budget documents. The Department and DOT must provide semiannual unclassified briefings (with classified addenda if needed) to designated congressional committees for seven years, and the statutory authority terminates seven years after enactment.
This bill is one of many.
Codify tracks hundreds of bills on Foreign Affairs across all five countries.
Explore Foreign Affairs in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Department of State Diplomatic Security personnel: The bill provides explicit legal authority and tools to mitigate UAS threats to personnel and facilities on U.S. soil, potentially improving protective capabilities at high‑risk locations.
- Protected facilities and visiting principals: Embassies, consulates, and diplomatic events designated as covered assets receive a legal framework to respond rapidly to hostile or intrusive UAS activity that could otherwise be hard to address under existing aviation and communications laws.
- Federal agencies conducting joint missions (DOD, DHS, DOJ): The bill authorizes mutual support and information‑sharing that can help other agencies respond to exigent UAS threats when they request State Department assistance.
- Security contractors trained and certified by State: Contractors meeting the statute’s conditions can perform counter‑UAS research, testing, and operational tasks, creating contracting opportunities within defined constraints.
Who Bears the Cost
- Federal Aviation Administration (FAA): The FAA must review and coordinate testing and operational activities to preserve NAS safety and will face increased workload and operational risk assessments where State deploys counter‑UAS measures near airports or manned traffic.
- UAS operators and hobbyists: The bill authorizes seizure, forfeiture, and destruction of UAS deemed threats, creating direct legal and property risk for operators near covered facilities.
- Telecommunications stakeholders and spectrum managers (NTIA/FCC and industry): Interception and signal‑disruption activities raise spectrum‑management, interference, and compliance issues; private spectrum users could suffer unintended disruptions.
- Civil‑liberties organizations and privacy counsel: The statutory carve‑outs and operational discretion will force monitoring and oversight costs and potential litigation challenging interceptions or disclosures of communications.
Key Issues
The Core Tension
The central dilemma is balancing the Department of State’s need for effective, rapid protection of people and assets against the risks that domestic counter‑UAS operations pose to aviation safety, private communications, and civil liberties—choosing tools that neutralize threats without creating greater hazards in the national airspace or eroding constitutional safeguards.
The bill creates overlapping authorities in a domain—domestic airspace, communications interception, and law enforcement support—where roles are tightly delineated today. Operationalizing State Department counter‑UAS tools will require detailed interagency procedures and likely local memoranda of understanding with the FAA, NTIA, and law enforcement to avoid operational collisions: an electronic disruption that stops a hostile UAS could also interfere with nearby aviation communications or critical wireless services.
The requirement to coordinate and to conduct FAA‑reviewed testing mitigates but does not remove the risk that an emergency countermeasure could compromise manned flight or airport operations in practice.
Privacy protections in the bill set a 180‑day default retention for intercepted communications with narrow exceptions, and they require constitutional compliance ‘‘consistent with’’ the First and Fourth Amendments and federal law. Those phrases leave open doctrinal questions—particularly whether communications‑interception authorities here would satisfy probable‑cause or warrant requirements when the interception targets signals originating from private controllers.
The Department’s ability to accept non‑federal funds or services “notwithstanding any provision of law” could speed capability acquisition but raises oversight and procurement integrity concerns. Finally, while the bill provides for semiannual briefings and budget displays, significant portions of operations may be classified; balancing transparency to Congress and the public against operational security will be an ongoing implementation challenge.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.