Congress locks down U.S. seaports against drone attacks—with narrow exceptions.

What it does

This bill creates a federal ban on operating drones over U.S. seaports without authorization, establishing a 1,000-foot no-fly zone above seaports that handle at least 1 million tons of cargo annually or process multi-day cruise passengers. It allows exceptions for federal agencies, state/local law enforcement, seaport operators, and emergency responders, with civil penalties up to $25,000 and criminal penalties up to 10 years imprisonment for violations intended to facilitate terrorism or criminal activity.

Why we flagged it

The bill's core function is straightforward: it establishes a regulatory no-fly zone over seaports to prevent drone-based attacks or interference. This is a direct security restriction on a specific threat vector, not a subsidy, deregulation, or private carve-out.

What the text implies

• The definition of 'seaport' (1+ million tons cargo annually or multi-day cruise passengers) may exclude smaller regional ports, creating a two-tier security regime where some maritime facilities lack federal drone restrictions.
• The Administrator's authority to designate 'additional lateral or vertical airspace' beyond 1,000 feet is discretionary and may expand the no-fly zone without further congressional action, potentially affecting commercial drone operations in adjacent areas.
• State and local law enforcement can conduct drone operations with 'prior notification' to FAA and Coast Guard, but the bill does not specify enforcement mechanisms if notification is withheld or falsified.
• The 180-day rulemaking deadline may be insufficient to establish clear procedures for waiver applications, potentially creating uncertainty for legitimate seaport drone operators (e.g., inspection, security monitoring).
• Criminal penalties escalate sharply (2 years to 10 years) based on intent to 'facilitate criminal or terrorist activity,' but the bill does not define the evidentiary standard for proving such intent.

Section numbers refer to the bill text the analysis read — linked under Primary records below.

Who it affects

The bill restricts a genuine public safety threat (unauthorized drone operations at critical infrastructure) while preserving legitimate uses through narrow exceptions and due-process waivers. Ordinary citizens benefit from enhanced security at ports they use for travel and commerce, with no corresponding loss of rights or protections.

Who stands to gain

• drone detection and mitigation technology vendors
• seaport security contractors
• maritime security consulting firms

Named in the bill

Federal Aviation Administration (FAA), Department of Homeland Security (DHS), Department of Defense (DoD), U.S. Coast Guard, U.S. seaports (300+ facilities), State and local law enforcement

Where it stands

3 cosponsors: 3 Republicans.

• Jun 9, 2026 — Introduced · Congress.gov: “Introduced in House”
• Jun 9, 2026 — Referred to House Committee on Transportation and Infrastructure and House Committee on the Judiciary · Congress.gov: “Referred to the Committee on the Judiciary, and in addition to the Committee on Transportation and…”

Dates and quoted wording are Congress.gov's action record; the timeline shows status changes, not every procedural step.