Texas Police, Fire, and Public Agency Drone Programs

Published October 18, 2026

Law checked through October 18, 2026.

A Texas public drone program needs appropriate FAA authority, a lawful mission, Chapter 423 analysis, applicable policies, records, security, and reporting. Police, fire, and other public agencies should not be assumed to have identical exceptions or obligations. Current § 423.008 has agency, population, use-period, timing, and publication conditions. Drone operation and counter-drone mitigation remain separate subjects. [1; 2]

Choose the aviation pathway

The FAA Public Safety Toolkit describes civil Part 107 operations and the public-aircraft pathway. Public ownership alone does not resolve every qualification. The program should identify the actual aircraft, mission, pilot, authorization, and conditions, including any BVLOS or emergency relief. [1]

An approval should be retained and matched to the current configuration and service area. A drone-as-first-responder demonstration does not by itself authorize routine dispatch under different staffing, airspace, or visibility conditions. The applicable instrument controls.

Texas lawful image capture

Chapter 423 lists lawful capture purposes, including specified governmental, law-enforcement, emergency, and other activities. Each has its own wording and conditions. A public agency should identify the provision supporting the actual mission rather than rely on public status alone. [2, § 423.002]

Warrants, consent, exigent circumstances, public safety, and other legal bases require their own facts. Capture, use, disclosure, and incidental imagery also receive separate treatment. Section 423.005 can restrict evidence use and disclosure of specified images, subject to its exception. A flight log should identify the mission basis without assuming it permits every later use. [2]

Current law enforcement use reporting

Section 423.008 requires the specified state law-enforcement agencies and county or municipal law-enforcement agencies in jurisdictions with populations greater than 150,000 that used or operated UAS during the preceding 24 months to make the report under its terms. The reporting window is January 1 through January 15 of each odd-numbered year. The report is posted on the agency's public website or otherwise made available as the statute specifies. [2]

Required information includes use organized by the listed details, assistance to criminal investigations, other law-enforcement operations, information about nonsubject persons or property, and specified costs. The current text reflects SB 2569's 2025 amendment. The program's records should support those fields; the provision should not be rewritten as an annual report required from every fire department. [2]

Program policies and constitutional authority

Section 423.007 directs DPS rules and guidelines for law-enforcement use. The actual current materials and the agency's own approved procedures should be identified. Procurement does not create search authority, and the Fourth Amendment continues to require analysis of the governmental conduct and circumstances. [2; 3]

Recommended policies cover mission approval, pilots, supervision, sensors, recognition, emergency dispatch, records, retention, complaints, and new functions. TRAIGA can add specific governmental AI obligations. A new identification feature should trigger review rather than be treated as ordinary maintenance. [4]

Security, procurement, and records

The agency should identify current prohibited-technology policies, federal funding conditions, FCC status, and product-specific exceptions. Those sourcing questions are distinct from FAA permission. A vendor's assertion of public-safety suitability is not enough to establish eligibility under every program. [5; 6]

Chapter 552 can reach vendor-held footage, mission records, and contracts within its conditions. Law-enforcement, privacy, and other exceptions require record-specific analysis. The agreement should secure access, search, export, retention, and transition support. A cloud service should not leave the agency unable to comply with its actual duties. [7]

Incident response and continuing review

The program should identify aviation reporting, safety response, information incidents, preservation, insurance, and contract notice separately. An internal mission report is not automatically an FAA report or a Texas public-use report. Relevant knowledge, thresholds, and deadlines must be tracked by authority.

Review should respond to actual changes in aircraft, software, personnel, geography, sensors, mission, and law. A program approved for emergency mapping should not silently expand into routine identification or counter-UAS mitigation. The legal authority for each activity should remain visible.