North Little Rock Police Department - Arkansas Surveillance Wiki

# North Little Rock Police Department The North Little Rock Police Department (NLRPD) is the municipal law-enforcement agency for North Little Rock, Arkansas, immediately across the Arkansas River from Little Rock. Its own `PDFOIA-2026-1331` production documents a parallel surveillance stack: twelve installed and twenty pending Flock sites, a 34-row SkyCop list, Genetec/SkyCop acquisitions and renewals from 2018 through 2025, Axon Fusus integration, and a 1,616-organization Flock sharing export. Earlier LRPD records independently document NLRPD as a recurring peer in the regional [[Flock Network Sharing - Hot Lists|Flock hot-list network]]. *Erratum, 2026-07-29: the earlier version of this page described NLRPD only as a counterparty in LRPD records and said its own procurement and camera count could not be verified. NLRPD's `PDFOIA-2026-1331` production now supplies direct agency records on those subjects.* ## NLRPD's documented LPR stack - **Flock deployment.** The current inventory marks twelve LPR rows `INSTALLED` and `Complete`, with completion dates from October 2023 through September 2025. It separately lists twenty pending sites, each with one proposed LPR camera and one proposed video camera ([[North Little Rock Flock Camera Inventory]], `Flock LPR List (1).docx`, rows `F#001`-`F#012` and `P#013`-`P#032`). - **SkyCop/Genetec continuity.** The procurement packet begins with a 2018 Genetec Security Center 5.7 platform and five SkyCop enclosures, documents further enclosure purchases through 2022, and carries 43 fixed-camera Genetec license renewals through 2025 ([[North Little Rock SkyCop and Genetec Procurement 2018-2025]], `SkyCop FOIA Documents_Redacted.pdf`, pp. 2, 16, 33, 39, 41, 43). - **CloudRunner subscriptions.** Two-unit CloudRunner subscription invoices state a 90-day retention period and continue into 2025 (`SkyCop FOIA Documents_Redacted.pdf`, pp. 4, 6, "includes 90 days retention"). - **Fusus integration.** Axon supplied NLRPD an October 2025 API v3 route for continuing Flock hot-alert delivery into Fusus after the legacy API sunset ([[North Little Rock Flock-to-Fusus API v3 and Axon Drone Pitch]], `Fusus Flock Integration Update into Fusus.pdf`, pp. 1-2). - **Usage reporting.** NLRPD reports 49,569,171 scans and 241,872 alerts across Flock and SkyCop for January-June 2026. Its embedded Flock dashboard shows zero successes and no data rather than the policy's separately required outcome categories ([[North Little Rock January-June 2026 ALPR Practice and Usage Report]]; [[T040 - NLRPD Required Outcome Categories vs Zero-Data Success Dashboard]]). ## Current sharing topology The July 16, 2026 export contains 1,616 organization rows: 1,113 with at least one NLRPD network shared outward, 1,027 with at least one network shared to NLRPD, and 524 with both directions populated. NLRPD's two outward network labels are `North Little Rock AR PD` and `North Little Rock AR PD - Genetec LPR` ([[North Little Rock Flock SharedNetworks Snapshot 2026-07-16]], `SharedNetworks_2026_July_16.csv`). The file establishes configured relationships, not search activity, individual-camera access, or outcomes. ## Role in this corpus: a Flock hot-list-sharing partner The deconfliction advisories in this production repeatedly show NLRPD and LRPD targeting the same plates on the shared Flock network. On February 14, 2026, an NLRPD search produced an overlap with multiple LRPD alert owners: "On February 14, 2026 at 5:39 PM UTC, a Flock Safety hot list search was conducted by North Little Rock AR PD for target plate: arkansas, [plate redacted]" (Emails 36-63.pdf p. 499, "a Flock Safety hot list search was conducted by North Little Rock AR PD for target plate: arkansas, [plate redacted]"). The overlap table on the following page lists LRPD owners (Levi Jones, Cesar Gonzalez, Isaac Coates, Timothy Hopkins) alongside an owner labeled "North Little Rock AR PD" (Emails 36-63.pdf p. 500). The sharing is bidirectional. An LRPD-initiated search on a different plate the prior day surfaced an NLRPD alert owner in the overlap: "On February 13, 2026 at 3:45 AM UTC, a Flock Safety hot list search was conducted by Little Rock AR PD for target plate: , [plate redacted]" (Emails 36-63.pdf p. 529, "a Flock Safety hot list search was conducted by Little Rock AR PD for target plate: , [plate redacted]"), with the overlap list naming "North Little Rock Nick Rodriguez [email protected] [phone not reproduced]" (Emails 36-63.pdf p. 530). The pattern recurs across other productions in the same FOIA response: additional NLRPD-initiated overlaps appear on plate [plate redacted] (Emails 25-35.pdf p. 634), plate [plate redacted] (Emails 1-24.pdf p. 1283), plate [plate redacted] (Emails 25-35.pdf p. 189), and plate [plate redacted] (Emails 1-24.pdf, chunk 12), indicating a standing rather than incidental sharing relationship between the two adjacent agencies. The advisory text itself frames the sharing as decentralized: each notice states that "the sharing of information involving this LPR overlap is the responsibility of each individual Alert Owner" (Emails 36-63.pdf p. 499, "the sharing of information involving this LPR overlap is the responsibility of each / individual Alert Owner"). Responsibility for any cross-agency exchange is placed on the named officer, not on either agency centrally. For the broader mechanism, see [[Flock Deconfliction Advisory]]. NLRPD is one node in a wider regional Flock hot-list network documented in this production that also includes [[Little Rock Police Department]], Sherwood AR PD, Springdale PD, Pine Bluff PD, Morrilton PD, Haskell PD, and the [[Arkansas State Police]] (Emails 36-63.pdf, chunk 6). The [[Little Rock Police Department]] Real-Time Crime Center ([email protected]) is itself a registered Flock alert owner that appears in many of these overlap tables. ## An unresolved data quirk: NLRPD-labeled owners on Arkansas State Police email domains Several alert owners labeled "North Little Rock AR PD" in these advisories carry email addresses on the [[Arkansas State Police]] domain (@asp.arkansas.gov) rather than a North Little Rock municipal domain. In the February 14, 2026 [plate redacted] overlap, the owner listed under "North Little Rock AR PD" is "Dustin Medford [email protected]" (Emails 36-63.pdf p. 500, "North / Little / Rock ... Dustin / Medford ... dustin. [email protected]"). The same officer recurs as an NLRPD-labeled owner with an asp.arkansas.gov address on plate [plate redacted] (Emails 1-24.pdf, chunk 12) and on plate [plate redacted] (Emails 25-35.pdf p. 189). Two further officers appear elsewhere in the production tagged to "North Little Rock AR PD" while using asp.arkansas.gov addresses — Ethan Hiland ([email protected]) and Timothy Brown — though those two appear in other chunks of the production rather than in the records reviewed for this page; their NLRPD-vs-ASP labeling is recorded in the analysis digest and is noted here without independent quote verification. By contrast, other "North Little Rock AR PD" owners use a North Little Rock police domain: "North Little Rock Nick Rodriguez [email protected]" (Emails 36-63.pdf p. 530). The OCR renders the domain as "nrpolice.org"; elsewhere in the production the same officer's address is rendered "[email protected]" (Emails 1-24.pdf p. 1283), suggesting "nlrpolice.org" is the underlying domain and the p. 530 rendering drops a character. The record does not state why some officers labeled as North Little Rock use Arkansas State Police email addresses. The two most ordinary explanations are (a) cross-commissioned or task-force officers who are formally with the [[Arkansas State Police]] but operate in or with North Little Rock, and (b) a Flock organization-label artifact in which an officer is attached to the "North Little Rock AR PD" org record in Flock while retaining their home-agency email. This production does not contain the information needed to choose between those readings, and this page does not assert which is correct. What the record establishes is the connectivity itself: searches attributed to "North Little Rock AR PD" overlap LRPD hot-list entries, and some of those NLRPD-attributed owners sit on the Arkansas State Police email domain — placing LRPD, NLRPD, and ASP on one interconnected Flock hot-list network. ## Current evidence gaps - NLRPD's executed/current Flock agreement, invoices, and payment records are not represented in `PDFOIA-2026-1331`. - The location lists provide no native coordinates or GIS data, and the production contains no ARDOT Case `01450679` permit record. - The package does not include the replaced 2014 policy, earlier reports within the current policy's eighteen-month preservation window, or retained search/user/network-audit exports. - Whether the asp.arkansas.gov-domain "North Little Rock AR PD" owners are cross-commissioned ASP personnel, task-force members, or a Flock label artifact. The record shows the discrepancy but not its cause. - The NLRPD-vs-ASP labeling of Ethan Hiland and Timothy Brown is carried from the analysis digest (other chunks of the same production) and was not independently quote-verified against page images for this page. ## Related pages [[north-little-rock-pd/PDFOIA-2026-1331/_overview|PDFOIA-2026-1331 Completion Production]] · [[Little Rock Police Department]] · [[Arkansas State Police]] · [[Flock Safety, Inc.]] · [[SkyCop, Inc.]] · [[Genetec, Inc.]] · [[Fusus]] · [[Flock Network Sharing - Hot Lists]] · [[Flock Deconfliction Advisory]] · [[Flock Deconfliction Advisories and the LRPD Sharing Network]]