CityDroneWatch
  1. CityDroneWatch
  2. Texas
  3. Laredo
  4. July 2026
  5. 1

Laredo, Texas · one day

Wednesday 1 July 2026

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

42

drone flights over Laredo that day.

12:04 am

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

10 min

median flight. Half were shorter.

Laredo police drones flew 42 times on Wednesday 1 July 2026, the first at 12:04 am and the last at 11:17 pm CDT, by Laredo Police Department's published record.

42 drawable flights of 42. 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 service69%
  2. Traffic and crashes19%
  3. Other10%
  4. Not stated2%

Flights, in order

42 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
12:04 amCall for service8 min5b34272e
12:15 amTraffic and crashes12 mina7e9d931
12:42 amTraffic and crashes7 mincab832ae
2:10 amTraffic and crashes15 mind0024aee
2:33 amCall for service17 min1852ea47
7:10 amOther4 min87cbaf8e
7:18 amCall for service10 min3379d4ef
9:06 amCall for service9 minc345a579
9:18 amCall for service5 min0215a134
9:24 amCall for service8 min15e1e5d3
9:40 amCall for service8 minab834906
10:07 amCall for service18 mina1505902
10:16 amOther14 min9e4295cd
12:09 pmCall for service10 min77683c08
12:20 pmCall for service11 min7d42e209
12:35 pmCall for service14 min69173375
1:00 pmCall for service8 min603602ec
1:09 pmTraffic and crashes5 mine30a37b4
2:49 pmCall for service9 min73bcabb5
2:53 pmCall for service4 min4cf6e4d6
2:55 pmCall for service6 min20713f59
3:04 pmCall for service11 min4bc81822
3:36 pmCall for service6 min1e81801d
3:43 pmCall for service7 min8532fdfa
3:51 pmCall for service5 mine3355dfb
4:15 pmCall for service10 mina6df764b
4:34 pmOther9 minbd7b1630
4:44 pmCall for service13 min060c3c57
4:46 pmCall for service8 min61d76e30
5:22 pmTraffic and crashes15 min2991eda6
5:29 pmCall for service9 min1645bb0d
6:11 pmTraffic and crashes12 min9c45664c
6:42 pmCall for service12 min53b3aac6
6:48 pmTraffic and crashes6 min134f1eac
6:57 pmTraffic and crashes11 min7ce8f56b
7:22 pmCall for service16 min3cb6ed82
7:23 pmCall for service15 min41f3d07b
7:47 pmOther16 mina6cdf370
9:17 pmNot stated43 s0f51a000
9:18 pmCall for service14 min7b8bf4a4
10:45 pmCall for service10 mina1ba6237
11:17 pmCall for service19 mind2f99ada

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: see the about page. See about this site for the sources and the publication rules.