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

Dearborn, Michigan · one day

Saturday 4 July 2026

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

45

drone flights over Dearborn that day.

12:20 am

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

7 min

median flight. Half were shorter.

Dearborn police drones flew 45 times on Saturday 4 July 2026, the first at 12:20 am and the last at 11:41 pm EDT, by Dearborn Police Department's published record.

45 drawable flights of 45. 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. Search24%
  2. Traffic and crashes18%
  3. Patrol support18%
  4. Other16%
  5. Assisting another agency13%
  6. Call for service9%
  7. Training and testing2%

Flights, in order

45 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:20 amCall for service5 min21cf08fa
12:37 amCall for service13 min89e32c11
1:38 amSearch8 minb89214d7
1:55 amSearch10 minc8ec2719
6:18 amOther9 min10fc0710
7:12 amTraffic and crashes5 min87c047b5
7:25 amAssisting another agency13 min3a1c44e8
8:12 amSearch8 minb464c5f3
8:51 amOther4 min41f97c75
8:55 amPatrol support13 minad8c3cb3
9:28 amPatrol support4 min4587c7f9
9:37 amPatrol support5 min542e356a
9:43 amSearch10 min742f97de
10:10 amPatrol support6 mind123d4be
10:21 amAssisting another agency6 min2f69eb2c
10:28 amOther6 min0d188586
11:04 amOther9 min0c015b73
11:10 amAssisting another agency9 min91f3a4eb
11:16 amTraffic and crashes7 min1062b373
11:28 amSearch4 minea0ba9ff
11:40 amAssisting another agency7 min5d3d1b70
12:00 pmAssisting another agency9 min7ccf35e5
12:12 pmPatrol support4 minc2d140a2
12:31 pmPatrol support3 mina6dd901c
12:34 pmPatrol support6 min7fb6609a
12:41 pmPatrol support6 min1077c405
1:30 pmOther6 min76f793a4
2:35 pmSearch14 min6f408fee
2:54 pmTraffic and crashes3 mine2f42237
3:25 pmTraffic and crashes13 minfff6db85
4:13 pmSearch20 min4d33960a
5:38 pmTraffic and crashes6 minc9777775
6:56 pmTraffic and crashes8 min114edd70
7:06 pmSearch14 minf0bfa58d
7:34 pmOther7 mindd50cdc3
8:09 pmTraffic and crashes10 minfa59a791
8:25 pmCall for service14 mincd0083f9
8:40 pmOther5 min7a72cb36
8:45 pmSearch16 mind1b66d89
9:03 pmTraffic and crashes6 min82cfac03
9:41 pmTraining and testing3 mine41c3b3e
10:44 pmAssisting another agency4 min3d47f156
11:04 pmCall for service5 minc497d189
11:16 pmSearch17 min82090d3e
11:41 pmSearch11 min524ce222

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.