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

Dearborn, Michigan · one day

Tuesday 2 June 2026

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

51

drone flights over Dearborn that day.

12:29 am

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

8 min

median flight. Half were shorter.

Dearborn police drones flew 51 times on Tuesday 2 June 2026, the first at 12:29 am and the last at 11:57 pm EDT, by Dearborn Police Department's published record.

51 drawable flights of 51. 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. Search37%
  2. Training and testing24%
  3. Patrol support20%
  4. Traffic and crashes6%
  5. Other6%
  6. Not stated6%
  7. Assisting another agency2%

Flights, in order

51 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:29 amTraining and testing11 min042323fb
12:38 amPatrol support17 mina912fe84
1:24 amSearch10 min00a45ac0
2:08 amPatrol support6 mind2090a41
3:18 amTraining and testing13 min4407e85a
4:17 amTraining and testing13 min5df62229
6:22 amSearch7 min2ea9d9c3
6:37 amPatrol support18 min6c993be3
7:59 amPatrol support5 min6172ed13
9:18 amTraffic and crashes4 mine13d4989
10:28 amTraffic and crashes8 mine521ed09
11:14 amOther5 minc3423ddb
11:53 amOther18 min4ecabe27
12:15 pmSearch11 minb8f5387f
12:38 pmPatrol support8 min79e34cfd
12:41 pmSearch8 minb8533036
1:05 pmSearch7 min05155c12
1:05 pmNot stated11 minaaea9516
1:09 pmOther55 s3571fb93
1:22 pmSearch8 minf1ca48ea
1:48 pmSearch7 minf77a0c43
1:50 pmTraffic and crashes3 mind2a19605
2:11 pmSearch8 mina335ff6a
2:25 pmTraining and testing4 min12e5818b
2:47 pmTraining and testing10 min1afa1de0
2:47 pmTraining and testing13 mine5f6c9a3
3:06 pmSearch5 minf23906ea
3:12 pmNot stated5 min3f5c9aeb
3:17 pmSearch8 min8715d831
3:37 pmNot stated9 mine2bfffa4
3:39 pmSearch4 min8f430d53
3:59 pmTraining and testing8 minf9bc39d1
4:07 pmTraining and testing5 min4a94cf81
4:16 pmSearch17 min88f80a63
4:35 pmTraining and testing5 min904529f8
4:41 pmTraining and testing7 min119e51e1
5:01 pmSearch4 mine898af9a
5:14 pmSearch5 minbb42e677
5:23 pmSearch8 min8b66a087
5:37 pmSearch12 minad2f588a
5:41 pmSearch9 min8c63b529
5:57 pmTraining and testing1 min 05 s9220ef44
6:15 pmTraining and testing1 min 32 sf30ad549
6:41 pmSearch9 min11b4aeea
7:56 pmPatrol support11 mine47dbe41
8:36 pmPatrol support11 min16203b23
8:46 pmSearch10 mine1f66427
9:31 pmAssisting another agency13 min236fa5c9
10:27 pmPatrol support12 minc5c5feca
10:48 pmPatrol support17 minff118667
11:57 pmPatrol support10 mine82c8746

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.