CityDroneWatch
  1. CityDroneWatch
  2. Texas
  3. Laredo
  4. March 2026
  5. 23

Laredo, Texas · one day

Monday 23 March 2026

16 drone flights from Laredo Police Department's published record.

16

drone flights over Laredo that day.

2:19 pm

first takeoff; the last was at 11:38 pm.

11 min

median flight. Half were shorter.

Laredo police drones flew 16 times on Monday 23 March 2026, the first at 2:19 pm and the last at 11:38 pm CDT, by Laredo Police Department's published record.

16 drawable flights of 16. Each path is the whole flight, simplified; a flight with a sensitive stated purpose is drawn as an area.
One flight, takeoff to landingSensitive-purpose flight, as an area

Hour by hour

Takeoffs by hour, CDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service88%
  2. Patrol support6%
  3. Traffic and crashes6%

Flights, in order

16 flights. Those in the latest full month link to their own page; a flight with a sensitive stated purpose has no page of its own.

Takeoff (CDT)PurposeAirborneFlight
2:19 pmPatrol support11 min968dfc93
2:50 pmCall for service16 min25ac176d
3:18 pmCall for service10 min6da0bf8c
5:49 pmCall for service13 min760d07b7
6:04 pmTraffic and crashes11 min92c0709d
6:19 pmCall for service6 mined69595d
6:55 pmCall for service14 minc50fb09c
7:40 pmCall for service12 minaeadb471
8:10 pmCall for service12 min6c0fc0d2
8:46 pmCall for service5 min274bf5e2
9:17 pmCall for service7 min93e0f459
9:27 pmCall for service11 minb41dd102
9:45 pmCall for service14 mina1bf1055
10:29 pmCall for service6 minf43e7f8c
10:53 pmCall for service8 min957fb3ed
11:38 pmCall for service5 min02680bf1

How this page is made

  • Every flight in the agency's published record is counted and listed; drawn paths are the whole flight, simplified to 10 m.
  • The record's free-text description is never read into a page. A flight whose stated purpose names a domestic, sexual-assault, kidnapping, welfare, mental-health or juvenile matter is listed like any other but drawn as a generalised area, not a path.
  • Operators are the agency's own accounts in the record, numbered within the agency in order of first flight; no name or address is read into a page.
  • Purposes are the agency's own words, grouped into classes by a committed lookup table; unmatched values are "Other" and blank ones "Not stated".
  • Times are converted to the agency's clock through the IANA zone database, never a fixed offset.
  • A day is the agency's local calendar day of takeoff.

Corrections and questions: file an issue in the korvid-labs repository (demo).