CityDroneWatch
  1. CityDroneWatch
  2. Nevada
  3. Las Vegas
  4. February 2026
  5. 8

Las Vegas, Nevada · one day

Sunday 8 February 2026

56 drone flights from Las Vegas Metropolitan Police Department's published record.

56

drone flights over Las Vegas that day.

4:05 am

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

—

durations not published in this record.

Las Vegas police drones flew 56 times on Sunday 8 February 2026, the first at 4:05 am and the last at 10:59 pm PST, by Las Vegas Metropolitan Police Department's published record.

56 flights with a published block-level point of 56. The record gives no path.
One flight, at its published block

Hour by hour

Takeoffs by hour, PST.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Not stated100%

Flights, in order

56 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 (PST)PurposeAirborneFlight
4:05 amNot stated—4e8c6f9d
4:22 amNot stated—130f2524
6:42 amNot stated—6de9d628
7:41 amNot stated—8e4fffaa
7:49 amNot stated—b5e1e386
8:17 amNot stated—723d1c1e
8:31 amNot stated—06d44257
8:40 amNot stated—7e614b2f
8:45 amNot stated—0acb7612
8:50 amNot stated—3e0461ff
8:52 amNot stated—1fc3548f
9:03 amNot stated—6c5f4344
9:17 amNot stated—27b2c6b1
9:33 amNot stated—b416fd34
9:56 amNot stated—e575c012
10:13 amNot stated—f8a4dc98
10:22 amNot stated—6edcda71
10:30 amNot stated—daad63c9
10:41 amNot stated—ce41aa1f
10:45 amNot stated—131ef4c3
10:50 amNot stated—1de6eb86
11:02 amNot stated—42626050
11:11 amNot stated—d5296be0
11:21 amNot stated—2a42f164
11:22 amNot stated—5df9800a
11:35 amNot stated—7bd712ba
12:40 pmNot stated—fe24d8de
1:24 pmNot stated—943f45cf
1:28 pmNot stated—6dab4f5d
1:31 pmNot stated—5af763dd
1:38 pmNot stated—2c2ade5b
1:39 pmNot stated—c2791ede
1:43 pmNot stated—5d385e3b
1:48 pmNot stated—2b7c05d9
1:55 pmNot stated—e0b794b0
2:16 pmNot stated—4288e807
2:28 pmNot stated—0eaf29f0
3:08 pmNot stated—5546eb9b
3:26 pmNot stated—13798e2b
3:47 pmNot stated—0d035009
3:50 pmNot stated—adededb9
3:53 pmNot stated—8ac95804
5:38 pmNot stated—f0811b6a
6:08 pmNot stated—c886c97d
6:28 pmNot stated—1653e9e6
6:49 pmNot stated—63e43c1b
6:49 pmNot stated—9116e915
7:42 pmNot stated—74ef0f03
9:01 pmNot stated—953aa3a0
9:19 pmNot stated—337a268f
9:41 pmNot stated—6baa164d
10:08 pmNot stated—a6674c8c
10:27 pmNot stated—8f2a23c7
10:48 pmNot stated—af74f356
10:53 pmNot stated—d9c2b3ea
10:59 pmNot stated—62685ef2

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.