# Law-Enforcement Drone and UAS Programs Small unmanned aircraft systems (sUAS, "drones") operated by Arkansas law-enforcement agencies. Unlike [[Automatic License Plate Reader (ALPR)]] cameras, drones are **episodic and mobile**: they generate no persistent location footprint, but they produce a flight log, and a flight log is a location record of where an agency chose to deploy aerial surveillance and when. The corpus documents six agency programs. What distinguishes them analytically is not the hardware — it is that three agencies asked the same question about flight locations produced three incompatible answers. ## How it appears in the corpus | Agency | Platform | Evidentiary basis | Volume documented | Location posture | |---|---|---|---|---| | [[Faulkner County Sheriff's Office]] | [[Skydio]] X10 (`X10E SR47P`) | Native flight log + FAA credentials | **155 flights**, 2 airframes, ~31.7 flight-hours, 2024-10-01 → 2026-07-03 | **Full addresses and GPS, released unredacted** | | [[Russellville Police Department]] | [[DroneSense]] platform, three unnamed airframes | Native session log | **~700 flights**, 2023-12-11 → 2026-07-20 | **No location fields of any kind** | | [[Little Rock Police Department]] | Make/model not stated in the record | Internal training email, 2026-05-01 | Not quantified | No log produced | | [[Conway Police Department]] | [[Skydio]] | Asset-forfeiture ledger + Flock kickoff deck | Not quantified | No log produced | | [[Benton County Sheriff's Office]] | Not stated | Narrative FOIA response | "ad hoc" deployment | No log produced | | [[Rogers Police Department]] | Not stated | Policy 406.7 (RTIC) | Not quantified | No log produced | ### Rogers: the first Drone First Responder program Rogers PD's Policy 406.7 establishes a **DFR Chief Pilot**, "a sworn (or civilian) RTIC Member," responsible for "Overall upkeep of the DFR program and equipment," training of "RTIC/DFR personnel," regulatory compliance, and "effective and efficient day to day DFR operations." The policy treats drones as one of three co-equal real-time sensor streams, describing information "initially detected through RTIC unique sources (PSCN/ DFR/ALPR)." This is the corpus's first documented DFR program, and it changes the picture the rest of this page describes. The other five programs are episodic: a pilot flies a drone to a call. A DFR program launches from the crime centre as a dispatch response, which makes the drone a standing sensor rather than a deployed tool. The operational rules live in **SOG 417.2 Drone First Responder Program**, referenced repeatedly in 406.7 and **not produced**. Rogers therefore joins the corpus with the most consequential drone posture and the least visible one: no flight log, no airframe identification, no procurement record, and no operational policy in the corpus. Note the negative boundary this resolves. Benton County SO expressly stated its drones "are not part of a Drone as First Responder auto-launch system," and the DFR marketing reaching LRPD inboxes had no documented Arkansas deployment behind it ([[Flock Alpha and DJI Dock 3]]). Rogers supplies the deployment. ### The three location postures This is the load-bearing pattern. Two agencies produced a native flight log in the same week, against comparably worded requests: - **Faulkner County released everything.** The `flights SkydioX10.csv` export carries takeoff address, latitude, and longitude per flight, unredacted ([[FCSO Skydio X10 Flight Log]]). Many rows geolocate deployments to residential-grade street addresses. - **Russellville released a log with no location column at all.** The DroneSense export carries flight codes, times, durations, pilot surnames, and a two-value mission field — "RPD Call for service" and "Training Flights" — and nothing spatial ([[russellville-pd/2026-07-24-dronesense-flight-log/_overview|Russellville DroneSense Flight Log]]). DroneSense retains per-flight GPS tracks as a platform capability, so the location-bearing export is an unproduced category rather than a nonexistent one. - **Benton County described its program instead of logging it**, stating that its drones are deployed ad hoc, are not connected to ALPR or cloud programs, and are not part of a DFR auto-launch system ([[Benton County SO Camera Locations and System Status]]). The divergence is a disclosure-practice finding, not a capability finding: nothing in the corpus suggests the three platforms differ in what they record. ### Mapping treatment Under the editorial policy set 2026-07-24, produced drone takeoff coordinates are intentional mapping content. FCSO's 141 GPS-bearing rows (of 155) appear in [[Arkansas Camera Map Data]] as a visibly separate evidence stage, "Drone flight takeoff (logged)," each point carrying an express not-a-camera caveat and stripped of pilot-identity fields. They are dated deployment events, not installations. Russellville's log adds no points because it contains no coordinates. ### Convergence with the ALPR function At LRPD the drone unit is not organizationally separate from the ALPR program. The sUAS unit is run out of the **Technology & Equipment Unit** by Lt. [[Courtney Bewley]], who elsewhere in the same production appears as a Flock hot-list "Alert Owner" ([[LRPD sUAS Drone Unit]]). One unit and one lieutenant hold both the plate-reader footprint and the aerial one. Funding converges as well: Conway's drone package was bought with forfeiture money — `7/25/2024 — Drone package from Skydio — -$57,962.71` in the City Finance asset-forfeiture ledger ([[Conway Asset Forfeiture Log 2023-2026]]) — the same stream documented in [[Asset-Forfeiture Funding for Surveillance Procurement]]. A January 2025 Flock kickoff deck records Conway's stated goal as "Skydio 3, grant to purchase 2 more drones will be Skydio." ### Credentialing, where it is documented Only Faulkner County produced airworthiness and pilot paperwork: an FAA UAS Remote Pilot Certificate (number `5059508`, issued 13 Sep 2024, eighteen days before the flight log's first entry) and an aircraft registration (`FA3A4P4HWT`, issued 10/29/2024, expires 10/29/2027) whose Remote ID serial matches the log's primary airframe `sx76` ([[FCSO Drone Email and Specs]]). **No registration was produced for the second airframe**, which flew 23 of the 155 logged flights. LRPD documents its own pilot pipeline through quarterly training, named instructors, and a "SALT school" qualification pathway, without identifying aircraft. ## Stakeholders - **Operating agencies** — [[Faulkner County Sheriff's Office]], [[Russellville Police Department]], [[Little Rock Police Department]], [[Conway Police Department]], [[Benton County Sheriff's Office]], [[Rogers Police Department]]. - **Vendors** — [[Skydio]] (airframes at two agencies), [[DroneSense]] (operations platform at one), [[DJI]] and [[Flock Safety, Inc.]] as marketed but not corpus-documented Arkansas deployments (see [[Flock Alpha and DJI Dock 3]]). - **Named personnel** — [[Courtney Bewley]] and [[James Phillips]] (LRPD unit leadership), [[Chad Wooley]] (FCSO). ## Timeline - **2023-12-11** — earliest flight in Russellville's DroneSense log, predating the department's Flock network by over a year. - **2024-07-25** — Conway's `-$57,962.71` Skydio drone package posts to the asset-forfeiture ledger. - **2024-09-13** — FCSO pilot's FAA remote-pilot certificate issued. - **2024-10-01** — first flight in FCSO's Skydio X10 log. - **2024-10-29** — FCSO airframe `sx76` registered with the FAA. - **2026-05-01** — LRPD distributes "Required Reading- sUAS Quarterly Training and some updates" to its drone pilots. - **2026-07-03 / 2026-07-20** — last logged flights at FCSO and Russellville respectively. - **2026-07-24** — both native flight logs enter the corpus; drone takeoff coordinates become mapping content. ## Notes **No agency in this corpus has produced a drone or UAS policy.** Six documented programs, two of them with hundreds of logged flights, and the only appearances of the phrase in the corpus are records of the absence: FCSO produced "no drone policy, deployment authorization, or retention rule," Russellville's UAS policy and deployment-authorization records remain unproduced, and LRPD's production contains the unit's training material but not its operational deployment or imagery-retention rules. By contrast, body-worn camera policy is documented in detail at the same agencies — [[FCSO Body Worn Camera Policy 102]] specifies purge intervals and a use-of-force retention rule. The governance asymmetry between the two camera-bearing programs is documented, not interpreted. Neither flight log carries a purpose, case-number, or authorization field. Russellville's two-value mission field is the closest thing to a stated reason in the corpus, and it distinguishes only operations from training (roughly 55/45). Whether either agency retains per-flight justification records is an open records question at both. FCSO's log places takeoffs in thirteen municipalities, including North Little Rock, Searcy, and Pine Bluff — **outside Faulkner County**. The produced records do not state the legal basis (mutual aid, task force, or training) for out-of-county operation.