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

Toledo, Ohio · one day

Tuesday 8 September 2026

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

22

drone flights over Toledo that day.

12:14 am

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

16 min

median flight. Half were shorter.

Toledo police drones flew 22 times on Tuesday 8 September 2026, the first at 12:14 am and the last at 9:33 pm EDT, by Toledo Police Department's published record.

22 drawable flights of 22. 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. Other82%
  2. Not stated18%

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 (EDT)PurposeAirborneFlight
12:14 amOther19 minTOLOHPD-
12:38 amOther15 minTOLOHPD-
1:26 amOther17 minTOLOHPD-
2:02 amOther22 minTOLOHPD-
2:24 amOther18 minTOLOHPD-
3:36 amOther13 minTOLOHPD-
4:07 amOther8 minTOLOHPD-
4:38 amOther29 minTOLOHPD-
10:02 amNot stated24 minTOLOHPD-
10:26 amOther14 minTOLOHPD-
10:42 amOther18 minTOLOHPD-
11:00 amOther15 minTOLOHPD-
11:49 amOther18 minTOLOHPD-
1:03 pmNot stated17 minTOLOHPD-
1:59 pmNot stated6 minTOLOHPD-
2:05 pmNot stated4 minTOLOHPD-
2:59 pmOther16 minTOLOHPD-
3:19 pmOther9 minTOLOHPD-
3:52 pmOther16 minTOLOHPD-
4:48 pmOther4 minTOLOHPD-
6:01 pmOther20 minTOLOHPD-
9:33 pmOther7 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).