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

Laredo, Texas · one day

Thursday 21 May 2026

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

42

drone flights over Laredo that day.

12:30 am

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

11 min

median flight. Half were shorter.

Laredo police drones flew 42 times on Thursday 21 May 2026, the first at 12:30 am and the last at 11:32 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. Other14%
  3. Traffic and crashes12%
  4. Not stated2%
  5. Patrol support2%

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:30 amCall for service10 min40e9d35f
3:55 amCall for service12 minc0affbd4
7:27 amNot stated8 min96522887
8:37 amPatrol support8 min35661960
8:53 amOther3 min953216b6
9:05 amOther18 min85a21488
9:51 amCall for service15 min3d7d38f6
10:08 amCall for service12 mina3873f59
10:24 amTraffic and crashes3 min1b515347
10:29 amCall for service15 min32f5d574
10:41 amCall for service12 minfc51f3c3
10:49 amCall for service12 min02cd8ec0
10:54 amOther12 min104f5c99
11:22 amCall for service8 min9593b5ee
11:27 amCall for service8 min35162c1f
11:54 amCall for service15 mind915aecd
12:08 pmCall for service11 min559eded1
12:25 pmCall for service17 min69599c9b
12:36 pmCall for service8 min9f428a6a
1:00 pmTraffic and crashes9 min2131fb70
1:10 pmCall for service11 min879c788a
1:21 pmOther6 min7f2781de
1:24 pmCall for service13 min1e2de687
2:45 pmCall for service15 min129e04bb
3:30 pmCall for service15 min4a393c29
3:46 pmOther8 min1c7ed6de
3:50 pmCall for service15 min32303a8d
4:09 pmCall for service13 min397dc3e2
4:51 pmCall for service6 min35c96790
5:33 pmTraffic and crashes6 min4e6e0ed1
6:25 pmOther10 minc42df0e3
6:32 pmTraffic and crashes15 mind6cb0e9a
7:26 pmCall for service7 minb3ca5fa5
7:50 pmCall for service8 min2628d38b
8:04 pmCall for service8 min0489fbc8
8:15 pmCall for service8 min61886053
8:35 pmCall for service10 mind04fe7a6
9:22 pmCall for service14 min73811289
9:48 pmCall for service14 mina55d335a
10:28 pmCall for service14 minb5de18ef
11:06 pmCall for service8 min07bd498e
11:32 pmTraffic and crashes19 min122d5b63

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.