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

Dearborn, Michigan · one day

Friday 24 July 2026

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

27

drone flights over Dearborn that day.

12:54 am

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

9 min

median flight. Half were shorter.

Dearborn police drones flew 27 times on Friday 24 July 2026, the first at 12:54 am and the last at 11:56 pm EDT, by Dearborn Police Department's published record.

27 drawable flights of 27. 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. Search44%
  2. Training and testing19%
  3. Traffic and crashes15%
  4. Patrol support7%
  5. Other7%
  6. Call for service7%

Flights, in order

27 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:54 amSearch20 min5d688bd7
1:49 amPatrol support18 min3a79f624
2:08 amOther8 mind6929737
2:57 amCall for service9 mindf2f5f72
9:15 amPatrol support17 min083e2dcf
11:14 amTraining and testing1 min 22 s4fe27bfb
11:23 amTraining and testing3 min30d56e6c
11:24 amTraining and testing2 minbc2a9017
11:42 amSearch7 mina5d1290d
11:52 amTraining and testing16 min267ffc34
1:10 pmSearch10 min50f3c457
1:23 pmTraining and testing1 min 58 s1f1a6a0d
1:42 pmTraffic and crashes10 min4227afc1
1:53 pmTraffic and crashes9 min3056946c
2:19 pmSearch10 min09e81ab0
2:33 pmSearch14 min60330b84
3:18 pmSearch8 min32dc9ede
3:26 pmTraffic and crashes9 min34c0a5a9
4:01 pmSearch12 min8ad84240
4:54 pmSearch3 min3732acf9
8:19 pmCall for service8 mind6995b04
8:35 pmTraffic and crashes8 min8bb2a05f
8:56 pmSearch19 min56d5046d
9:58 pmOther16 mined72e227
10:28 pmSearch10 minebc8854a
10:50 pmSearch20 minc1b40b03
11:56 pmSearch6 min7a82f375

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.