CityDroneWatch
  1. CityDroneWatch
  2. Texas
  3. Laredo
  4. April 2026
  5. 26

Laredo, Texas · one day

Sunday 26 April 2026

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

41

drone flights over Laredo that day.

12:03 am

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

10 min

median flight. Half were shorter.

Laredo police drones flew 41 times on Sunday 26 April 2026, the first at 12:03 am and the last at 11:41 pm CDT, by Laredo Police Department's published record.

41 drawable flights of 41. 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 service73%
  2. Traffic and crashes12%
  3. Other10%
  4. Patrol support5%

Flights, in order

41 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:03 amTraffic and crashes8 minbc0313f3
12:18 amCall for service11 min01805468
12:50 amOther15 minddc10a6f
1:10 amCall for service19 mina864f3a3
1:53 amCall for service8 min0deba1f1
2:04 amCall for service10 min033be670
2:32 amCall for service6 min6be3e915
2:39 amCall for service7 minac4c367b
2:47 amCall for service7 min771e6c34
2:54 amCall for service16 min19523851
7:33 amPatrol support9 min4eb5abaf
8:27 amCall for service18 minb38a801a
9:59 amCall for service13 mindd3f9169
10:33 amCall for service8 min823d6ab2
10:57 amTraffic and crashes13 min86f0adfe
11:18 amTraffic and crashes6 min7c0cf403
12:00 pmCall for service10 minb9406bda
12:20 pmCall for service11 mina90e11d3
12:45 pmCall for service18 mindaf02771
1:33 pmCall for service11 min74647631
2:04 pmCall for service13 min6a807640
2:25 pmOther14 min93b43d8e
2:41 pmCall for service11 min4280e825
4:20 pmTraffic and crashes11 mineceacdf8
4:31 pmCall for service17 min1eccf928
5:23 pmOther5 min35773807
5:43 pmCall for service10 minad55c7a9
6:06 pmCall for service12 min9c9f28d8
6:39 pmCall for service7 min8d3ba0ce
7:17 pmCall for service4 min9110aff7
7:22 pmCall for service16 min4a2dcda2
7:58 pmCall for service8 min8a26c4ae
8:33 pmCall for service51 s7ed8212b
8:38 pmCall for service9 mine8daccde
9:26 pmTraffic and crashes16 mine8001634
10:11 pmCall for service12 min4c37a627
10:58 pmOther8 min8c392758
11:14 pmCall for service5 min2d4ede33
11:19 pmPatrol support11 min4fc36c63
11:32 pmCall for service8 min4b8ee76c
11:41 pmCall for service7 min9be5ec9e

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.