# LRPD January-June 2026 ALPR Practice and Usage Report A three-page report identifying the [[Little Rock Police Department]] as the reporting entity and January 1 through June 30, 2026 as the reporting period. It states that it was compiled under Ark. Code Ann. § 12-12-1805 and combines two pages of report prose with system-generated Flock dashboards (`6 Month Report Jan-June 2026.pdf`, p. 1, "This report is compiled pursuant to Arkansas Code Annotated § 12-12-1805"). ## What's inside - **Page 1 - authority and volume.** The report states that the statute requires practice-and-usage data every six months "in a format sufficient for public review." It reports **103,375,512 plates scanned** and **350,211 confirmed matches (alerts)** (`6 Month Report Jan-June 2026.pdf`, p. 1). - **Page 2 - alert sources and topics.** Figure 1 is a system-generated dashboard for 2026-01-01 through 2026-06-30. The page says the figure reflects "the names and categories of hotlists or databases against which captured plate data was checked" (`6 Month Report Jan-June 2026.pdf`, p. 2). - **Page 3 - Flock outcomes and preservation.** Figure 2 reports Flock-defined successes and case/property figures. Section VII says the compiled data will be preserved for at least eighteen months and calls the report aggregated and system-generated (`6 Month Report Jan-June 2026.pdf`, p. 3, "will be preserved for a minimum of eighteen (18) months"). ## Reported activity | Measure | Reported value | |---|---:| | Plates scanned | 103,375,512 | | Confirmed matches / alerts | 350,211 | | Alert rate, calculated | 0.339% | | Scans per alert, calculated | about 295 | The calculated values divide the two page-1 totals; they are not figures printed by LRPD. ## Alert sources | Dashboard source | Alerts | Share of all alerts | |---|---:|---:| | Official hot lists | 79,996 | 22.8% | | LRPD custom hot lists | 223,952 | 63.9% | | Other custom hot lists on LRPD's networks | 46,263 | 13.2% | | **Total** | **350,211** | **100.0%** | The three visible source totals sum exactly to the page-1 alert total. The two custom-list categories together account for **270,215 alerts, or 77.2%** (`6 Month Report Jan-June 2026.pdf`, p. 2, Figure 1 labels "Official Hotlist Alerts," "Your Custom Hotlist Alerts," and "Other Custom Hotlist Alerts on Your Networks"). Figure 1's topic table also sums exactly to 350,211: | Topic | Alerts | |---|---:| | Custom Hotlist Alert | 223,952 | | Non Owned Custom Hotlist Alert | 46,263 | | Sex Offender | 42,789 | | Warrants | 18,357 | | Protection Order | 6,117 | | Gang or Suspected Terrorist | 3,948 | | Stolen Plate | 3,438 | | Violent Person | 2,723 | | Stolen Vehicle | 2,512 | | Missing Person | 87 | | Protective Interest | 18 | | Extreme Risk Protection Order | 5 | | CPIC Data Records | 1 | | Supervised Release | 1 | (`6 Month Report Jan-June 2026.pdf`, p. 2, "Total Alerts by Topic".) ## Displayed outcome measures The dashboard defines its unit more broadly than an arrest or prosecution: > "A 'success' is an arrest, lead, warrant, or stop occurring that has been explicitly associated with a hit on a Flock device." (`6 Month Report Jan-June 2026.pdf`, p. 3.) | Dashboard measure | Value | |---|---:| | Total successes | 91 | | Total cases cleared | 86 | | Total value of recovered property | $856,299 | | Stolen vehicles recovered | 54 | The same dashboard divides the 91 successes into **74 Cleared by Arrest**, **12 Cleared by Other Means**, **4 Lead Generated**, and **1 Investigation in Progress**; those four values sum exactly to 91 (`6 Month Report Jan-June 2026.pdf`, p. 3, Figure 2). > [!contradiction] Required outcome categories vs displayed dashboard > The report says Figure 2 "reflects" confirmed matches, matches that did not correlate to an alert after further investigation, and matches that resulted in arrest and prosecution. The visible dashboard instead reports a broader success construct and does not separately label either non-correlating matches or matches resulting in both arrest and prosecution (`6 Month Report Jan-June 2026.pdf`, p. 3). The opaque black rectangle beneath the outcome table has no explanatory label, so its purpose cannot be inferred. See [[T034 - LRPD Required Outcome Categories vs Flock Success Dashboard]]. ## Key takeaways - **Scale.** LRPD reports more than 103 million scans in six months, nearly six times the 17,624,832 reads in [[Russellville 2026 Semi-Annual ALPR Usage Report]] and nearly five times the 21,429,985 Flock reads in Springdale's January-June 2026 report ([[Springdale Semiannual LPR Reports 2025-2026]]). - **Custom-list dependence.** More than three quarters of alerts come from LRPD-owned or network-shared custom lists, not official hot lists. - **"Success" is not an accuracy measure.** The dashboard links 91 outcomes to Flock hits, but its definition includes leads, warrants, and stops. Dividing successes by alerts yields about 0.026%, or one recorded success per 3,848 alerts; that is an outcome-attribution ratio, not an OCR error rate, alert-validation rate, or causal estimate. - **The statutory outcome fields remain unresolved.** "Cleared by Arrest" is not the same field as "arrest and prosecution," and no separate non-correlation count is visible. ## People and orgs mentioned - [[Little Rock Police Department]] - reporting entity. - [[Flock Safety, Inc.]] - platform named in the page-3 success definition. No person is named on the face of the report. ## Concepts invoked - [[Arkansas Automatic License Plate Reader System Act]] - § 12-12-1805 reporting and eighteen-month preservation. - [[Automatic License Plate Reader (ALPR)]] · [[Hot List]] · [[Flock Network Sharing - Hot Lists]] - [[ALPR Error Layers and Outcome Measurement]] - distinguishes this outcome-attribution measure from OCR, hot-list, and verification error rates. ## Events documented - [[2026-06 Little Rock ALPR Reporting Period Ends]] ## Cross-references - [[PCSO ALPR Six-Month Practice and Usage Report]] - a comparable Flock report that says outcome data are not currently tracked. - [[Russellville 2026 Semi-Annual ALPR Usage Report]] - a report that separately documents alerts, verification, arrests, cases, recoveries, and manual-query auditing. - [[ASP Statewide ALPR Data Reports 2025-2026]] - reports confirmed matches, misidentifications, and arrest-and-prosecution figures as separate fields. ## Safety and handling - Exact file size: 253,791 bytes; SHA-256: `48a3e2048721d492632510244ca1af61f4b2b562f727c3bc25d6a0a6e969d71b`. - The PDF has three native-text pages. File-signature, Windows Defender, encryption, embedded-file, JavaScript, open-action, additional-action, and form checks found no active-content or malware indicator. - All three pages were rendered and visually reviewed. Page 3 contains an unexplained solid black rectangle below the outcome table. ## Open questions / follow-ups - What count should be reported for matches that did not correlate after further investigation? - How many matches resulted in both arrest and prosecution, rather than the broader "Cleared by Arrest" category? - What source records connect a Flock hit to each success type and prevent duplicate attribution across hits, cases, vehicles, and recoveries? - Why does the document proceed from Section IV to Section VII without visible Sections V or VI?