CityDroneWatch
  1. CityDroneWatch
  2. Texas
  3. Laredo
  4. June 2026
  5. 7

Laredo, Texas · one day

Sunday 7 June 2026

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

43

drone flights over Laredo that day.

12:27 am

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

10 min

median flight. Half were shorter.

Laredo police drones flew 43 times on Sunday 7 June 2026, the first at 12:27 am and the last at 11:53 pm CDT, by Laredo Police Department's published record.

43 drawable flights of 43. 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 service81%
  2. Traffic and crashes16%
  3. Other2%

Flights, in order

43 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:27 amTraffic and crashes12 min0274c55b
12:51 amCall for service6 minb1f1d6db
1:00 amCall for service5 min3abfb179
1:14 amCall for service8 min0bc00ffb
1:27 amCall for service12 min4f157ff6
1:42 amTraffic and crashes11 min07d20b92
2:12 amCall for service14 minf3e124b8
2:28 amCall for service15 min7c7e54d6
7:31 amCall for service14 minf4408ad7
8:14 amCall for service11 min1da7aa09
8:51 amCall for service6 min53751a04
9:39 amCall for service16 mindef960ff
9:58 amCall for service13 mine9c3d041
10:24 amCall for service5 minfe9309b0
11:05 amCall for service18 min95cf36f2
11:11 amTraffic and crashes8 mind12cd282
11:46 amCall for service16 mindbfbe7f7
11:56 amCall for service5 min37255ab8
12:02 pmCall for service2 minc6ed394d
12:04 pmCall for service1 min 38 s059336ab
12:15 pmTraffic and crashes12 min259a3620
12:18 pmTraffic and crashes13 min3d15fae2
12:35 pmCall for service6 mine7114b8c
12:46 pmCall for service6 min34cf3412
12:48 pmCall for service14 min682a9f9c
1:26 pmCall for service7 min5940fafa
1:37 pmCall for service7 min09a7f89d
1:40 pmCall for service6 mina5923321
1:51 pmCall for service8 mind6dddc71
2:41 pmCall for service13 mine2bf1065
4:39 pmCall for service14 minaf07269e
5:58 pmCall for service9 min7c07b591
7:36 pmCall for service13 minb61d59dc
8:25 pmTraffic and crashes10 min15f9c86c
8:37 pmCall for service12 min343e87e6
8:51 pmOther4 mince3ac6ae
9:10 pmCall for service11 min2ca5dafb
9:33 pmCall for service8 mine700d8c4
10:08 pmCall for service8 min016e787f
10:27 pmCall for service8 mine78c8d5d
10:40 pmCall for service12 min312f4902
11:22 pmTraffic and crashes8 min633990b1
11:53 pmCall for service10 min04abf544

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.