CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Toledo
  4. August 2026
  5. 21

Toledo, Ohio · one day

Friday 21 August 2026

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

22

drone flights over Toledo that day.

12:23 am

first takeoff; the last was at 10:48 pm.

13 min

median flight. Half were shorter.

Toledo police drones flew 22 times on Friday 21 August 2026, the first at 12:23 am and the last at 10:48 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. Other73%
  2. Not stated27%

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:23 amOther15 minTOLOHPD-
12:42 amOther16 minTOLOHPD-
1:00 amOther13 minTOLOHPD-
2:38 amOther14 minTOLOHPD-
3:32 amOther13 minTOLOHPD-
7:38 amOther3 minTOLOHPD-
7:51 amOther19 minTOLOHPD-
8:25 amOther15 minTOLOHPD-
8:48 amNot stated1 min 54 sTOLOHPD-
9:21 amOther9 minTOLOHPD-
9:52 amOther11 minTOLOHPD-
10:40 amOther7 minTOLOHPD-
10:55 amOther24 minTOLOHPD-
11:23 amNot stated3 minTOLOHPD-
12:20 pmOther5 minTOLOHPD-
1:19 pmOther14 minTOLOHPD-
4:57 pmOther8 minTOLOHPD-
5:10 pmNot stated5 minTOLOHPD-
6:40 pmOther19 minTOLOHPD-
9:10 pmNot stated3 minTOLOHPD-
9:27 pmNot stated15 minTOLOHPD-
10:48 pmNot stated17 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).