128
drone flights in the published record.
2
flights in October 2026, the latest full month.
60 min
median flight. Half were shorter.
Yuma Police Department drones flew 128 times between 26 November 2024 and 21 October 2026, by the agency's own published record. 2 of those flights were in October 2026.
No flight locations in this capture of the record, so there is no map.
92 hours of flight time in the record.
9 in 10 flights were shorter than 240 minutes.
— The record publishes no times of day.
0 flights had a sensitive stated purpose. Those are counted but never listed or drawn.
Month by month
Flights per month, by takeoff date on the agency's local calendar. Click a month for its days.
The two hatched bars are the most recent months and are provisional. The current month is still in progress.
Why, in the agency's words
The agency's stated purpose for each flight, grouped into classes, as a share of all 128 flights.
Hour of day
Not published: this record carries dates only.
Flight list, October 2026
Every listable flight in the view, oldest first: date, takeoff time, purpose class, time airborne and the first eight characters of the source flight id. The filters above the map apply here too.
| Date | Takeoff (MST) | Purpose | Airborne | Flight |
|---|---|---|---|---|
| Mon 19 Oct 2026 | — | Other | 30 min | 290 |
| Wed 21 Oct 2026 | — | Other | 30 min | 291 |
All 2 listable flights in October 2026. Flights with a sensitive stated purpose are counted in the totals but not listed. Times are local to the agency.
How this page is made
- Nothing that landed in the last 48 hours is counted, listed or drawn.
- Drawn paths are simplified to 10 m and lose their first and last 200 m; flights too short to keep an interior are counted but not drawn.
- The record's free-text description is never read into a page. Flights whose stated purpose names a domestic, sexual-assault, kidnapping, welfare, mental-health or juvenile matter are counted in totals and appear in neither the flight list nor on the map.
- 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.
- Without filters the map draws at most 300 flights, sampled evenly from the latest full month, and the flight list is that month, capped at 500 rows. With filters the map draws at most 400 and the list at most 500, both sampled evenly, and the count line says when a cap applied. Each month's flights are a static JSON file under flights/ next to this page; the whole-record option is an even 300-flight sample.
- Record source: Yuma Police Department, via the agency's own ArcGIS flight log (https://services1.arcgis.com/tzW2OKwR84ufoH3y/arcgis/rest/services/City_of_Yuma_Drone_Flights_2_view/FeatureServer/0), licence: agency-run ArcGIS Online feature service, no licence stated on the layer; republication accepted by the owner 2026-11-01 (docs/rights-memo.md). Read from
../var/lib/drone-publish/work/sources/selfpub/yuma-pd-az.json, no network at build time. - What this record does not publish: no time of day (flights are dated; the hour chart, time-of-day filters and night share are not shown); no flight path or location. Nothing is inferred to fill those gaps.
Corrections and questions: file an issue in the korvid-labs repository (demo).