CityDroneWatch
  1. CityDroneWatch
  2. Texas
  3. Laredo
  4. May 2026
  5. 20

Laredo, Texas · one day

Wednesday 20 May 2026

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

36

drone flights over Laredo that day.

12:20 am

first takeoff; the last was at 10:56 pm.

10 min

median flight. Half were shorter.

Laredo police drones flew 36 times on Wednesday 20 May 2026, the first at 12:20 am and the last at 10:56 pm CDT, by Laredo Police Department's published record.

36 drawable flights of 36. 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. Not stated8%
  3. Traffic and crashes6%
  4. Other3%
  5. Patrol support3%

Flights, in order

36 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:20 amCall for service10 min638bf669
12:32 amCall for service9 min2a49116c
12:51 amCall for service17 min01abbf39
2:36 amCall for service9 min1dd4f2b0
7:18 amCall for service15 min5fc37c61
8:05 amCall for service10 mina3db808e
9:04 amCall for service14 min766515d4
9:34 amTraffic and crashes8 minf014e566
9:45 amTraffic and crashes15 minba6e7a8d
10:26 amCall for service15 min031ed522
10:40 amCall for service13 min45e74c03
10:50 amCall for service11 min3a985458
11:18 amNot stated6 min901b0575
12:33 pmOther11 mind1fd6949
1:29 pmCall for service5 minc20246a7
2:07 pmCall for service20 minb50b1e10
3:09 pmCall for service11 min5656593b
3:13 pmNot stated10 minb046c47e
4:04 pmCall for service5 min3e238dc8
4:12 pmCall for service9 minfcc797c1
4:17 pmCall for service13 min50911448
5:17 pmCall for service10 minbdc91c37
5:25 pmCall for service16 mina38d1016
5:28 pmCall for service8 min52ac01be
5:58 pmCall for service10 min95ed8f6e
6:23 pmCall for service8 min233aa39b
6:47 pmCall for service10 mina4ab481a
6:50 pmCall for service19 minecc68a88
7:11 pmCall for service10 min527f86ab
7:42 pmCall for service7 min14bee8ca
7:54 pmNot stated2 min942ad2e0
8:41 pmCall for service14 min39d601d7
8:56 pmPatrol support15 min162c8b2f
9:13 pmCall for service8 min69a78f82
10:33 pmCall for service15 min792ddfad
10:56 pmCall for service11 mincf491a95

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).