CityDroneWatch
  1. CityDroneWatch
  2. California
  3. Chula Vista
  4. June 2026
  5. 13

Chula Vista, California · one day

Saturday 13 June 2026

22 drone flights from Chula Vista Police Department's published record.

22

drone flights over Chula Vista that day.

7:44 am

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

—

durations not published in this record.

Chula Vista police drones flew 22 times on Saturday 13 June 2026, the first at 7:44 am and the last at 11:58 pm PDT, by Chula Vista Police Department's published record.

18 flights with a published block-level point of 22. The record gives no path.
One flight, at its published block

Hour by hour

Takeoffs by hour, PDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service45%
  2. Other36%
  3. Not stated14%
  4. Traffic and crashes5%

Flights, in order

22 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
7:44 amOther—c7cd5f2f
8:20 amOther—a15e0c2e
10:02 amOther—1c4a1e4d
10:19 amNot stated—15817e63
11:10 amNot stated—79158e22
11:33 amOther—6e7b01a5
12:47 pmOther—84113b83
12:53 pmCall for service—155d0331
1:11 pmTraffic and crashes—b44d1836
2:05 pmCall for service—5e846bde
3:14 pmOther—2ea03818
3:59 pmCall for service—4ea62c28
4:17 pmCall for service—874f89d3
5:21 pmCall for service—a628cbdc
6:20 pmNot stated—4e5b7e5e
6:58 pmOther—696cc3cd
7:39 pmOther—8f1dc513
8:14 pmCall for service—ffa8afdb
8:41 pmCall for service—3703daae
10:41 pmCall for service—f29a6a4c
11:25 pmCall for service—9d784d05
11:58 pmCall for service—76d11e1d

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