Counter-Drone Authority and Limits in Texas

Classify the technology and action

Optical observation, acoustic detection, radar, radio-frequency analysis, interception, jamming, takeover, and physical action are not legally interchangeable. The assessment should identify what the tool actually receives, transmits, stores, or changes and who operates it. A passive label should not substitute for technical facts about communications access.

The mission should also identify the protected site, threat, aircraft behavior, responsible agency, and legal authority. A drone's presence does not automatically establish unlawful conduct or justify every available response. Texas infrastructure law and federal airspace rules address different elements. [3]

Private party limits

Federal aircraft-destruction, communications, and interception laws can restrict actions against drones. The relevant statutes have their own elements and exceptions. A landowner should not infer authority to shoot, jam, seize, or take control merely because the aircraft is over private property or recording images. [4]

Lawful protective responses can include observation, documenting relevant facts, protecting people from an immediate hazard through appropriate noninterfering measures, and contacting competent authorities. The actual circumstances and law govern. This guide does not provide operational instructions for defeating aircraft or communications.

Conditional public agency authority

The 2026 interim final rule implements the amended counter-UAS framework for eligible state, local, tribal, and territorial law-enforcement and correctional agencies. The parallel Parts 124 identify conditions for participation, training, certification, technology, deployment, coordination, and reporting. The rule is not a universal grant to every public employee or private security provider. [1; 2]

An agency should identify its actual approval, personnel qualifications, permitted equipment, mission, location, and operating conditions. A facility owner's consent or request does not replace those requirements. Neither a purchase order nor completion of ordinary drone-pilot training establishes counter-UAS certification under the rule.

Detection information and privacy

Information collection should be examined separately from mitigation. Communications, identification data, images, and location records may raise different statutory and constitutional issues. The agency should identify the authority, purpose, access, retention, and disclosure rules for each category. [1; 4; 5]

Public-information requests and law-enforcement exceptions require their own record-specific analysis. A counter-UAS program's security purpose does not automatically make every contract, log, or recording confidential. Conversely, public status does not override a statute making particular information confidential. [6]

Texas infrastructure and local authority

Section 423.0045 regulates specified conduct at defined facilities and includes important exceptions. Establishing a Texas violation is different from establishing federal mitigation authority. The facility's qualification and the aircraft's conduct should be analyzed under the actual provision. [3]

Section 423.009 restricts local operational regulation while preserving specified powers. A local ordinance does not by itself authorize conduct forbidden by federal law. The program should identify the actual federal and state sources rather than assume one legal concern resolves all others. [3]

Procurement and oversight

Recommended procurement review examines legal eligibility, product function, approvals, training, spectrum, data, updates, records, and ongoing support. The agency should obtain enough technical information to determine what the tool actually does. A vendor's assertion that an instrument is lawful everywhere is not a substitute for the agency's authority.

Continuing review should address new tools, software, sites, personnel, missions, and changed law. Incident records should distinguish observed aircraft behavior, identification uncertainty, authorization, decisions, and effects. Those records support oversight and later analysis without assuming the system's classification is always correct.

Hypothetical facility request

A refinery asks local police to use a commercially sold jammer against an unidentified drone. The request does not establish that the facility has mitigation authority, that the agency is certified for the action, or that the device and mission meet federal conditions. Each element requires its own legal and factual basis before intervention.