# Flock Deconfliction Advisories and the LRPD Sharing Network This page documents the largest single category of records in the PDFOI-2026-1874 production: hundreds of automated Flock Safety "Deconfliction Advisory" emails received by the Little Rock Police Department between March 2024 and May 2026. Each advisory logs a specific Flock hot-list search — the searching agency, the target license plate, a UTC timestamp, and the list of overlapping "Alert Owners" — and collectively the advisories trace a Flock hot-list sharing network that reaches across central Arkansas and into roughly two dozen out-of-state agencies and at least one state fusion center. Because Flock generates and timestamps these notices automatically, they function as a de-facto, contemporaneous audit trail of LRPD's ALPR querying. ## What's inside The production is three OCR'd PDFs of printed LRPD email ("Emails 1-24.pdf", "Emails 25-35.pdf", "Emails 36-63.pdf"); most pages in this category were printed from the mailboxes of named LRPD recipients (e.g., Bryan Davenport, Brad Forrester, Levi Jones) and, for one large export, an LRPD records mailbox shown in the header as "Davis, Domikia." Each Deconfliction Advisory follows a fixed template: a header stating that Flock "has identified overlaps between a Flock Safety LPR hot list entry of yours and at least one other organization," a single line naming the searching organization, target plate, and UTC time, and a table of overlapping Alert Owners listing organization name, owner name, agency email, and (frequently) a direct phone number. Interleaved among the advisories are Flock newsletters, "Action Requested" share-request emails, camera-share notices, Axon Fusus release notes, and law-enforcement trade newsletters. The advisories in this production reproduce specific Arkansas and out-of-state license-plate numbers; those plate numbers are not reproduced here. Several advisories also include officers' direct-dial numbers; those are likewise not reproduced. ## Key takeaways ### The Deconfliction Advisory mechanism and its boilerplate Flock describes the product to the recipient as an overlap notice: "Please be advised that Flock Safety has identified overlaps between a Flock Safety LPR hot list entry of yours and at least one other organization" (Emails 1-24.pdf p. 562, "Please be advised that Flock Safety has identified overlaps between a Flock Safety LPR hot list entry of yours and at least one other organization."). Every advisory carries the same sharing boilerplate, which places the decision to share on the individual officer rather than the agency: "For purposes of collaboration and information sharing, the contact information associated with the overlapping organization(s) is provided below. Please note that the sharing of information involving this LPR overlap is the responsibility of each individual Alert Owner" (Emails 1-24.pdf p. 562, "the sharing of information involving this LPR overlap is the responsibility of each individual Alert Owner"). Each advisory states the searching agency, the plate, and the time to the minute in UTC. The earliest example in the production is from March 2024: "On March 20, 2024 at 4:17 PM UTC, a Flock Safety hot list search was conducted by Little Rock AR PD for target plate: arkansas, [plate not reproduced]" (Emails 1-24.pdf p. 418, "a Flock Safety hot list search was conducted by Little Rock AR PD for target plate"). The advisories therefore record both that a search happened and which agency ran it. ### The regional Arkansas network A single advisory at Emails 1-24.pdf p. 1454-1455 captures the breadth of the regional network in one overlap table. The advisory logs an LRPD search ("On May 21, 2026 at 8:41 AM UTC, a Flock Safety hot list search was conducted by Little Rock AR PD for target plate: arkansas, [plate not reproduced]" — Emails 1-24.pdf p. 1454) and then lists overlapping Alert Owners across the region: Little Rock AR PD, Springdale AR PD ([email protected]), Sherwood AR PD, North Little Rock AR PD, Pine Bluff AR PD ([email protected]), and Morrilton AR PD ([email protected]), alongside Arkansas State Police owners on the asp.arkansas.gov domain (Emails 1-24.pdf p. 1455, "dustin. [email protected]" and "[email protected]"). The same plate is shown being searched by multiple agencies on consecutive days, which establishes that the hot-list entry is shared across the regional network rather than held by LRPD alone. Sherwood PD personnel appear under two distinct domains within the same Flock network: sherwoodar.gov (e.g., John Epperson) and sherwoodpolice.org (e.g., Cole Davis, Danny Cuellar) (Emails 1-24.pdf p. 1455). The record shows the relationship operating in both directions: searches "conducted by North Little Rock AR PD" and "conducted by Sherwood AR PD" generate advisories that land in LRPD mailboxes. One Sherwood-originated search overlaps LRPD and the Pulaski County Sheriff's Office: "a Flock Safety hot list search was conducted by Sherwood AR PD for target plate: arkansas, [plate not reproduced]," with overlapping owners at Sherwood AR PD, the Pulaski County AR SO ([email protected]), and Little Rock AR PD (Emails 1-24.pdf p. 808-809, "a Flock Safety hot list search was conducted by\nSherwood AR PD for target plate"). The Arkansas State Police participation is notable because it is distinct from the [[ACIC NCIC Hot-List Feed]]: ASP appears here as a first-class Flock Alert Owner on the asp.arkansas.gov domain, sharing hot-list overlaps with LRPD directly through the Flock platform. ### The LRPD RTCC as a first-class Alert Owner The LRPD Real-Time Crime Center operates its own Flock account and appears as a registered Alert Owner. The address [email protected] is listed in overlap tables labeled "RTCC RTCC," confirming the RTCC maintains its own hot-list entries in addition to those held by individual officers (Emails 1-24.pdf p. 1455, "RTCC\nRTCC" / "[email protected]"). The RTCC account recurs as a co-owner across many advisories throughout the production. (Some OCR renderings show the address as "[email protected]"; this is read here as an OCR variant of [email protected].) ### Out-of-state and fusion-center reach The network extends well beyond Arkansas. An out-of-state agency running an Arkansas plate triggers a cross-share into LRPD's mailbox: "On February 3, 2026 at 8:56 PM UTC, a Flock Safety hot list search was conducted by Houston TX PD for target plate: arkansas, [plate not reproduced]" (Emails 1-24.pdf p. 205, "a Flock Safety hot list search was conducted by Houston TX PD"), with the overlap table distributing contact information for LRPD and Houston PD officers to each other. LRPD officers also run searches against out-of-state plates; advisories in this production log LRPD searches against Texas and Florida plates, among others (Emails 1-24.pdf p. 1491, "a Flock Safety hot list search was conducted by Little Rock AR PD for target plate: texas, [plate not reproduced]"). Separately, the production preserves an "Action Requested: Pending Flock Camera Share Requests" email to LRPD's Christina Goss listing organizations awaiting LRPD's approval of "Search" access. The list includes the Missouri Information Analysis Center — a state fusion center — alongside Mont Belvieu TX PD, Clover SC PD, Wheeler County TX SO, Pitt County NC SO, Othello WA PD, Shreveport LA PD, Tomball TX PD, Bel Aire KS PD, and Glenpool OK PD, each with a "Search" permission and a December 2025 request date (Emails 1-24.pdf p. 658, "Missouri Information Analysis\nCenter"). Other production pages document a further set of out-of-state agencies with active or pending Search access to LRPD's network, including TN ROCIC, the Michigan Department of Attorney General, the Riverside County (CA) District Attorney, and the St. Tammany Parish (LA) Sheriff's Office (Emails 1-24.pdf pp. 37-40, per the production digest). ### Intra-agency overlaps Many advisories show overlaps that are entirely internal to LRPD — multiple LRPD officers each holding a hot-list entry on the same plate. A pair of advisories from February 6, 2026 logs two LRPD searches for the same plate within minutes ("On February 6, 2026 at 8:15 AM UTC" and "On February 6, 2026 at 8:23 AM UTC," both "conducted by Little Rock AR PD" — Emails 1-24.pdf pp. 562, 566), with the overlapping Alert Owners all carrying littlerock.gov addresses and the set of listed owners growing between the first and second search (Emails 1-24.pdf p. 562, "the sharing of information involving this LPR overlap is the responsibility of each individual Alert Owner"). These intra-agency overlaps show that hot-list entries are maintained by individual officers, not only at the agency level. ## People and orgs mentioned - [[Little Rock Police Department]] — the subject agency; the searching organization and the recipient of the advisories. Its Real-Time Crime Center ([[Real-Time Crime Center (RTCC)]], [email protected]) is itself a Flock Alert Owner. - [[North Little Rock Police Department]] — regional Flock hot-list sharing partner; originates searches that overlap LRPD; some of its listed Alert Owners use asp.arkansas.gov addresses. - [[Sherwood Police Department]] — regional partner appearing under both sherwoodar.gov and sherwoodpolice.org; originates searches overlapping LRPD and Pulaski County SO. - [[Arkansas State Police]] — appears as a first-class Flock Alert Owner via the asp.arkansas.gov domain (Dustin Medford, Ethan Hiland); distinct from its ACIC role. - [[Pulaski County Sheriff's Office]] — regional partner (pcso.org) overlapping LRPD and Sherwood hot lists. - [[Flock Safety, Inc.]] — operates the LPR hot-list platform and generates the automated Deconfliction Advisories. - Springdale AR PD, Pine Bluff AR PD, Morrilton AR PD, Haskell AR PD — additional in-state agencies appearing as overlapping Alert Owners (named as plain text; not registry entities). - Houston TX PD, Missouri Information Analysis Center, Mont Belvieu TX PD, Clover SC PD, Wheeler County TX SO, Pitt County NC SO, Othello WA PD, Shreveport LA PD, Tomball TX PD, Bel Aire KS PD, Glenpool OK PD, TN ROCIC, Michigan Department of Attorney General, Riverside County (CA) DA, St. Tammany Parish (LA) SO — out-of-state agencies and a fusion center with overlapping searches or active/pending Search access (named as plain text). - Named LRPD recipients and Alert Owners (government employees in work role) include Bryan Davenport, Brad Forrester, Levi Jones, Colby Singleton, Haston Betts, Christina Goss, and others listed in overlap tables. ## Concepts invoked - [[Flock Deconfliction Advisory]] — the automated overlap-notification mechanism this page documents. - [[Flock Network Sharing - Hot Lists]] — the underlying hot-list sharing topology surfaced by the advisories. - [[Surveillance Data Sharing — Default-On Posture]] — the boilerplate's placement of sharing responsibility on the individual Alert Owner reflects a decentralized, opt-out-by-default posture. - [[Hot List]] — the shared list structure whose overlaps trigger the advisories. - [[Real-Time Crime Center (RTCC)]] — the LRPD unit operating [email protected] as a Flock Alert Owner. - [[Automatic License Plate Reader (ALPR)]] — the underlying technology generating the plate reads searched against the hot lists. ## Events documented - Recurring Flock hot-list searches by LRPD and partner agencies, March 20, 2024 through May 21, 2026 (the production's date range for this category). - A December 2025 batch of pending out-of-state "Search" access requests to LRPD's Flock network, including the Missouri Information Analysis Center (Emails 1-24.pdf p. 658). ## Cross-references - This is the LRPD analog to the SharedNetworks topology documented in the Conway production: a platform-mapped, multi-jurisdictional Flock hot-list sharing network, here visible through the deconfliction byproduct rather than a single network export. - The platform-logged, timestamped searches function as de-facto audit records of LRPD ALPR querying, which bears directly on the disclosure-posture question raised in [[T004 - Item-3 No-Records vs Deconfliction Audit Trail]]. - For LRPD's handling of records requests touching this category, see [[LRPD FOIA Handling and Disclosure Posture]]. - For the federal-access dimension of network sharing (Flock's agency-level federal data-sharing control), see [[Federal Data-Sharing Controls and Federal-Access Posture]]. - For audit-trail completeness and gaps in the parallel Axon Fusus ALPR stack, see [[Flock Audit and Compliance Controls and Gaps]]. ## Open questions / follow-ups - The advisories are a byproduct of overlaps, not a complete search log. The production does not include the SharedNetworks CSV or the monthly audit-log exports that the FOIA request sought, so the full scope of LRPD's network relationships and total search volume cannot be verified from the advisories alone. - Whether LRPD accepted, rejected, or left pending the December 2025 out-of-state Search-access requests (including the Missouri Information Analysis Center) is not shown in this production. - The exact count of distinct partner agencies and the agency-level versus officer-level configuration of hot-list sharing cannot be fully reconstructed from the advisory sample; these would require the platform's SharedNetworks and audit exports. - OCR renders the RTCC address variously as "[email protected]" and "[email protected]"; the latter is read here as an OCR artifact, but the production's native records would confirm.