WeVote
Log In

Bill

Bill

S 4768

A bill to provide for a requirement for networked autonomous kinetic capability against small unmanned aircraft systems.

119th Congress Introduced by John Cornyn

The bill would require a networked autonomous system to detect, assess, and physically neutralize small drones (sUAS) without human control.

Introduced in Senate
0
WeVote Research Nonpartisan
Bill Summary · S 4768

Summary of Bill: S. 4768 (Session 119) – A bill to provide for a requirement for networked autonomous kinetic capability against small unmanned aircraft systems

Purpose and intent

  • The bill aims to establish a formal requirement for a networked, autonomous, kinetic capability designed to counter small unmanned aerial systems (sUAS). In essence, it seeks to mandate a system that can detect, assess, and physically remove or neutralize small drones through autonomous means within a networked framework.
  • The sponsor (with a listed co-sponsor, Sen. John Cornyn) indicates a focus on improving defense readiness and situational safety by enabling more rapid and coordinated responses to sUAS threats.

Key provisions and changes (as described by the bill title and form of action)

  • Networked autonomous capability: The core requirement is the development or deployment of a system that is autonomous (capable of operating without real-time human control) and networked (able to communicate with other systems, platforms, or command-and-control networks) to counter sUAS.
  • Kinetic approach: The countermeasure is kinetic, meaning it involves physical intervention with the adversary drone—potential methods could include interception, disabling, or neutralization through mechanical, energetic, or projectile means, as authorized by the legislative framework.
  • Scope: small unmanned aircraft systems: The focus is explicitly on small drones, which are typically defined by weight, size, or operational characteristics that categorize them as sUAS rather than larger, traditional aircraft.
  • Strategic emphasis on rapid response: By mandating networked autonomy, the bill envisions faster decision loops and reduced reliance on manual or human-in-the-loop operations, potentially improving effectiveness in contested or high-threat environments.

Who/what would be affected

  • Defense and national security entities: Agencies and organizations responsible for air defense, counter-UAS operations, and related mission areas would be tasked with implementing or procuring the mandated capability.
  • Procurement and program offices: Systems integrating networked autonomous counter-sUAS solutions would require budget planning, acquisition processes, and interoperability standards.
  • Operational environments: The armed services or relevant security domains would engage with the new capability during training, exercises, and potential real-world counter-UAS scenarios.
  • Regulatory and safety considerations: Deployment of kinetic countermeasures would necessitate considerations around safety, collateral impact, rules of engagement, and accountability.

Procedural and timeline aspects

  • Introduced and referred: The bill was introduced in the Senate and referred to the Senate Committee on Armed Services on June 11, 2026.
  • Next steps in process: As with many defense-related measures, the bill would proceed through committee consideration, potential markups, and floor debate approvals before moving to the House (and/or conference) for final passage and enactment, subject to broader legislative timelines and negotiations.
  • Implementation timeline not specified in provided text: The available information does not include explicit deadlines or phased rollout schedules; such details would typically be established in committee reports or later enacted provisions.

Notes and considerations

  • The summary reflects the bill’s stated aim to mandate a networked autonomous kinetic solution against sUAS, emphasizing rapid, coordinated, and physical countermeasures against small drones.
  • Specific operational, ethical, legal, and safety frameworks (e.g., thresholds for use, risk to bystanders, rules of engagement, civilian harm considerations) would likely be developed in accompanying language, committee reports, or implementing directives if the bill progresses.

If you’d like, I can tailor this summary to focus on particular audiences (e.g., policymakers, defense contractors, or civil aviation stakeholders) or add hypothetical implementation scenarios based on common counter-UAS architectures.

Compiled from official sources — confirm details with the bill’s official record.

Sign in to ask a question.