CityDroneWatch
  1. CityDroneWatch
  2. Michigan
  3. Dearborn
  4. June 2026
  5. 23

Dearborn, Michigan · one day

Tuesday 23 June 2026

36 drone flights from Dearborn Police Department's published record.

36

drone flights over Dearborn that day.

6:45 am

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

8 min

median flight. Half were shorter.

Dearborn police drones flew 36 times on Tuesday 23 June 2026, the first at 6:45 am and the last at 11:21 pm EDT, by Dearborn Police Department's published record.

36 drawable flights of 36. 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. Search31%
  2. Patrol support19%
  3. Traffic and crashes19%
  4. Call for service14%
  5. Training and testing8%
  6. Other6%
  7. Assisting another agency3%

Flights, in order

36 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
6:45 amPatrol support11 mine4e7399c
7:14 amOther7 minf7037917
7:19 amSearch15 mindf98dcab
7:41 amPatrol support9 mina02ace53
7:54 amTraffic and crashes19 mind81f6622
8:27 amPatrol support4 min56c8dc41
8:32 amPatrol support11 mine8f24e29
9:03 amPatrol support7 min06cb0ae3
9:36 amSearch16 min9ff23372
10:49 amTraffic and crashes3 minc85422a7
11:00 amTraffic and crashes9 mind5bc1934
11:14 amTraffic and crashes10 min1cfbd72f
11:29 amPatrol support5 min8e7fca46
11:38 amAssisting another agency7 min8f529d60
12:02 pmSearch13 min33be8e04
1:07 pmSearch10 minf6a325bd
1:27 pmSearch7 mind2aa16c6
1:37 pmCall for service11 min5c44571c
1:55 pmOther10 min87e7d3cb
2:20 pmTraining and testing4 minb90ac209
2:46 pmPatrol support3 min10cd566f
3:54 pmTraining and testing8 min3d762716
4:09 pmTraining and testing7 min787c42bd
4:40 pmSearch9 min6383749a
5:01 pmSearch6 mine2db8183
5:13 pmSearch16 min542c076a
5:25 pmSearch13 min1ef76d5b
5:43 pmTraffic and crashes4 mind00e12f5
5:54 pmCall for service6 min435e5b22
6:57 pmTraffic and crashes7 min67ed6a30
7:34 pmSearch13 mina7ccc775
7:46 pmSearch12 min42b13ca3
10:10 pmTraffic and crashes6 mina11ef61c
10:31 pmCall for service6 min31f886fd
11:09 pmCall for service9 mined33863a
11:21 pmCall for service5 minafc57660

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: see the about page. See about this site for the sources and the publication rules.