# Russellville Police Department Municipal police agency for Russellville (Pope County), Arkansas. Its first production (2026-07-23, first items of the July 21 request) supplies a native 17-device camera map — 13 directional fixed LPR cameras and 4 park Condor video cameras, all Flock products — plus the department's ALPR policy and a § 12-12-1805 semi-annual report recording **17,624,832 plate reads in the first half of 2026**, the corpus's largest documented six-month scan volume. ## People - [[David Ewing]] — Chief of Police; issuing authority of Policy 312.2 (effective 2024-09-01). - [[Phillip Varnell]] — Assistant Chief, Administrative Division; FOIA handler for the July 2026 request; the policy designates "the Administrative Assistant Chief" as LPR Administrator. ## Roles in this corpus - **All-Flock fixed network, video-first sequencing.** The devices export lists 13 `LPR Camera` sites (paired SB/NB and WB/EB corridors on Hwy 7, Hwy 27, Hwy 331, US 64, Weir Rd) and 4 park `Video Camera` Condors; the vendor tracker dates the Condor compute boxes to August–September 2025 and the LPR wave to February 10 – March 3, 2026 ([[Russellville Devices and Locations Spreadsheet]]; [[Russellville Flock Deployment Tracker Export]]; [[2026-02 Russellville LPR Installation Wave]]). - **Two Flock organizations.** The agency's own export names `Russellville AR PD` and `Russellville AR PD (Condor)`, with the City Park Condor riding the base org — agency-side confirmation of the base/Condor tenant split. - **Statutory reporting with outcome and query-audit detail.** The 2026 semi-annual report totals 1,851 matches (115 from other agencies' Shared Networks hot lists), 5 arrests across 4 cases, 2 recovered vehicles, and 881 manual queries with zero misuse complaints ([[Russellville 2026 Semi-Annual ALPR Usage Report]]). - **Express no-private-cameras posture.** "[W]e do not utilize privately owned cameras... we do not access cameras operated by private businesses or other privately owned cameras" (Gmail message `19f90c41f2b598d2`) — the corpus's clearest agency disavowal of private-camera integration. - **Custody boundary at Miovision.** Officers may hold accounts on Public Works' Miovision intersection cameras, but the department "does not own, operate, or administer" that system ([[City of Russellville]]). - **Executed Flock baseline; amendment status unresolved.** A customer- and vendor-signed 2024 order establishes 13 Falcon LPRs, four Condor PTZs, one eight-stream Wing gateway, FlockOS Advanced, thirty-day retention, a `$69,110` first-year subtotal, and `$62,160` annual recurring subtotal. A later solar-PTZ quote is non-binding, and the produced amendment copy is unsigned with blank product tables ([[Russellville Flock Contract and PTZ Amendment]], `Flock Contract.pdf`, pp. 2, 6, 8-13). - **ARDOT trail.** [[Statewide Traffic Control Devices Export]] contains seventeen Russellville-area rows under `P1927`/`P1944`/`P1945`/Case `678191` with blank lifecycle fields; no produced record crosswalks them to the 17-device inventory. - **A mature three-drone DroneSense program.** The current dashboard identifies two [[DJI]] Mavic 2 Enterprise Advanced aircraft and one Mavic 3 Thermal. The completed two-PDF join establishes 724 session rows and 719 dated takeoff events from 2023-11-28 through 2026-07-20 across 715 exact coordinate strings. Those rows appear in [[Arkansas Camera Map Data]] as deployment events, not fixed-camera sites ([[Russellville Drone Inventory Policy and Flight Coordinates]]). - **Produced UAS operating rules.** Policy 421.2, effective 2021-11-01, requires case-by-case approval outside scheduled training, warrant review for planned operations implicating a reasonable expectation of privacy, and DroneSense logging; it states that RPD operates under Part 107 and does not have a COA ([[Russellville Drone Inventory Policy and Flight Coordinates]], `Drone data.pdf`, pp. 2, 5, 8, 10). ## Notes The rolling production remains open. The new supplement resolves the current drone inventory, UAS policy, takeoff-coordinate, and original Flock-contract categories, but current sharing/tenant configuration, retained audits, mobile-unit inventory, bounded communications, Wing-connected streams, and proof of execution for the later PTZ amendment remain outstanding. Joshua clarified the Wing-stream and sharing-record terminology in writing on July 29 (Gmail `19faf179fb6e815d`). Policy 312.2's magnetic-mount provisions presuppose mobile LPR capability the produced inventory does not document.