CityDroneWatch
  1. CityDroneWatch
  2. California
  3. Santa Ana
  4. July 2026
  5. 21

Santa Ana, California · one day

Tuesday 21 July 2026

31 drone flights from Santa Ana Police Department's published record.

31

drone flights over Santa Ana that day.

12:42 am

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

8 min

median flight. Half were shorter.

Santa Ana police drones flew 31 times on Tuesday 21 July 2026, the first at 12:42 am and the last at 11:53 pm PDT, by Santa Ana Police Department's published record.

31 drawable flights of 31. 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, PDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service74%
  2. Training and testing23%
  3. Not stated3%

Flights, in order

31 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 (PDT)PurposeAirborneFlight
12:42 amCall for service16 minb15f12ee
1:34 amCall for service18 minf081cd0a
1:55 amCall for service18 min238d8cdb
2:28 amCall for service4 min698a0034
3:10 amCall for service8 min5b08e4dc
7:13 amCall for service19 min574a3603
7:33 amTraining and testing1 min 55 s009ed7e6
9:09 amNot stated8 minf2b32053
9:52 amCall for service5 min60a12930
10:26 amTraining and testing2 mina0c2fbac
10:36 amTraining and testing3 minb87435ff
11:31 amTraining and testing1 min 09 s541055e4
11:55 amTraining and testing58 s58e2537b
12:43 pmCall for service9 min61dcb113
12:55 pmTraining and testing53 sf2ba30c9
1:08 pmCall for service14 min1faa32d0
2:06 pmCall for service5 min89e09b66
2:30 pmCall for service10 min9c8c478a
2:53 pmCall for service8 min72ca82a4
4:32 pmCall for service4 min85d8259b
4:56 pmCall for service17 min8c6e1f17
6:11 pmCall for service9 min0c7a6805
6:20 pmCall for service6 min48852905
7:22 pmCall for service4 min5c2c3205
8:28 pmCall for service5 min171b7d93
8:35 pmTraining and testing3 mina2f91b2e
9:17 pmCall for service3 min17602c22
9:21 pmCall for service16 min95acc806
10:48 pmCall for service18 min264d0650
11:11 pmCall for service18 minf3dc3a37
11:53 pmCall for service18 min8038547a

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