CityDroneWatch
  1. CityDroneWatch
  2. Michigan
  3. Dearborn
  4. May 2026
  5. 30

Dearborn, Michigan · one day

Saturday 30 May 2026

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

40

drone flights over Dearborn that day.

12:25 am

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

8 min

median flight. Half were shorter.

Dearborn police drones flew 40 times on Saturday 30 May 2026, the first at 12:25 am and the last at 10:34 pm EDT, by Dearborn Police Department's published record.

40 drawable flights of 40. 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. Patrol support55%
  2. Traffic and crashes25%
  3. Other8%
  4. Call for service8%
  5. Not stated5%

Flights, in order

40 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:25 amPatrol support5 min86b3b489
12:43 amPatrol support16 mine545991c
2:44 amPatrol support9 minbe55cdf3
6:35 amOther8 mincdd91aa8
6:44 amTraffic and crashes8 min85eb479a
7:07 amPatrol support3 min86b23cbc
8:25 amPatrol support6 min49d73ad5
8:34 amPatrol support7 min6be925df
11:12 amOther11 min9ab5188f
11:44 amPatrol support9 min99b4ca46
12:19 pmPatrol support7 min5216fff6
12:29 pmPatrol support19 minf5530789
12:51 pmPatrol support7 min74d7bfc7
1:03 pmNot stated9 minaaf0575d
1:13 pmPatrol support16 min3f219eba
1:26 pmNot stated6 min5d8c476e
1:35 pmPatrol support8 minfa700ae0
2:39 pmTraffic and crashes2 mine188464b
2:42 pmTraffic and crashes7 min1be4bba3
2:52 pmTraffic and crashes7 min7fdd70fb
2:57 pmPatrol support11 min65ca12fd
3:09 pmCall for service14 minaf733d60
3:38 pmTraffic and crashes5 min44f56773
3:52 pmOther12 min73042a83
4:16 pmCall for service15 min32ff2141
4:33 pmTraffic and crashes5 mind75701a7
4:48 pmTraffic and crashes5 min75c95cae
4:55 pmPatrol support12 min7e793ba9
5:25 pmPatrol support7 min87d48567
5:33 pmTraffic and crashes10 min6b1d9c90
5:46 pmTraffic and crashes6 minc04ddf98
6:01 pmPatrol support4 minde00e8db
6:05 pmTraffic and crashes7 minac990479
8:16 pmCall for service8 min84fc7eac
8:26 pmPatrol support6 min5431be7e
9:17 pmPatrol support6 minf39c101d
9:27 pmPatrol support10 min6d9c2b67
9:49 pmPatrol support7 min4be32f72
10:13 pmPatrol support8 minafa0ed5f
10:34 pmPatrol support11 min325241d3

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.