CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Toledo
  4. September 2026
  5. 23

Toledo, Ohio · one day

Wednesday 23 September 2026

10 drone flights from Toledo Police Department's published record.

10

drone flights over Toledo that day.

4:07 am

first takeoff; the last was at 9:20 pm.

14 min

median flight. Half were shorter.

Toledo police drones flew 10 times on Wednesday 23 September 2026, the first at 4:07 am and the last at 9:20 pm EDT, by Toledo Police Department's published record.

10 drawable flights of 10. 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, EDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Other90%
  2. Not stated10%

Flights, in order

10 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 (EDT)PurposeAirborneFlight
4:07 amOther26 minTOLOHPD-
7:27 amNot stated2 minTOLOHPD-
8:16 amOther7 minTOLOHPD-
9:21 amOther11 minTOLOHPD-
10:24 amOther3 minTOLOHPD-
10:38 amOther13 minTOLOHPD-
11:13 amOther17 minTOLOHPD-
12:27 pmOther16 minTOLOHPD-
3:58 pmOther21 minTOLOHPD-
9:20 pmOther26 minTOLOHPD-

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