# Jonesboro Police Department Municipal police agency for Jonesboro, Arkansas. Its `JPD-2026-851` productions supply a system-by-system inventory of **870 camera views**, a **116-vehicle** camera-equipped fleet list, a 5,201-row RTCC camera-pull log, ALPR activity logs, policy, procurement and grant records, and five ARDOT permit packets. Earlier records placed JPD in the Benton County Sheriff's Office's Flock SharedNetworks export and ARDOT's statewide traffic-control-device data. ## Roles in this corpus - **Multi-system camera operator.** The produced inventory spans intersections (257 views), the Eagle Eye pole program (117), Nettleton school Avigilon feeds (12), SkyVue poles (35), IVMS (3), facility Avigilon systems (332, including a Craighead County feed, JPD interview rooms, and private TrimGym and SW Church James feeds), Flock LPR (55 "including flex," plus the separate Bridger Place network and one decommissioned site), and Verkada Live View (59) ([[Jonesboro Camera and Views Inventory]]). - **Fleet-scale mobile ALPR.** 116 camera-equipped vehicles across patrol/K9/traffic/SRO/warrants/CID; the transmittal states "roughly 85 AXON systems mounted on patrol cars" and one unit with 3 Vigilant cameras ([[Jonesboro Unit LPR Vehicle List]]; Gmail message `19f8fde41db5c885`). - **Platform-custody posture.** The transmittal disclaims map copies, shared-camera documentation, and registry files as platform-resident — preserved against the inventory's own external-feed rows at [[T020 - Jonesboro Shared-Camera Documentation Statement vs Inventory Entries]]. - **Flock network relationship.** The BCSO export's line 278 lists `Jonesboro AR PD`, `Jonesboro AR PD (Flex)`, and `Bridger Place (AR)` in the inbound field while BCSO appears in the outward-sharing field ([[SharedNetworks 2026-07-22 Snapshot]], `SharedNetworks_2026_July_22.csv`, line 278). - **Craighead County detective access.** Craighead County's administrator states that Sheriff's Office detectives have access to JPD's Flock system for investigative purposes and that the underlying records are kept in JPD's system ([[2026-07 Craighead Itemizes FOIA Fee and Discloses JPD Flock Access]], Gmail message `19faaa30d85ff362`). The message does not enumerate accounts, permissions, searches, or an authorizing instrument. - **Access to Craighead County exterior video.** A County-produced file identifies a site-to-site VPN, 31 exterior Avigilon camera rows, and 32 JPD users at access level `JPD Shared Exterior` ([[Jonesboro Access to Craighead County Avigilon]], pp. 1–3). Configured access does not establish actual viewing or current account status. - **ARDOT permit and location trail.** [[Statewide Traffic Control Devices Export]] identifies Jonesboro-area ALPR/Flock rows under permits P1881, P1889, P1967, P1969, and P1982. The export's lifecycle fields and labels must control any site-specific status claim. - **Permit closeout records.** The completion package supplies City-signed returns for all five permit packets, covering eleven ALPR points. Those returns represent the City's completion statement; they do not themselves establish ARDOT inspection, acceptance, an as-built survey, or present operation ([[Jonesboro ARDOT ALPR Permit Packets P1881 P1889 P1967 P1969 P1982]]). - **Signalized-intersection inventory.** A dated City workbook supplies exact coordinates for 92 signalized intersections. Forty-six rows carry positive camera counts totaling **214 cameras**; one site-level map record represents each positive row because the workbook does not provide a coordinate per device ([[Jonesboro Signalized Intersection Camera Inventory 2026]]). - **ALPR activity reporting.** Flock's monthly scan total rises from 468,374 in March 2025 to 3,979,039 in June 2026. The separate six-tab Axon workbook reports 451,755 to 584,632 monthly scans for its available periods. The vendor-specific columns are not sufficiently defined to calculate comparable error or outcome rates ([[Jonesboro Flock and Axon ALPR Activity Logs 2025-2026]]). - **Written custody and audit duties.** Policy 715.02 requires an MOU before RTCC access to a participating entity's cameras, an IT-maintained user list, documented access and use, written officer video requests, and a secondary-dissemination log for outside LPR disclosures. Policy 714.02 requires monthly UAS audits and flight records that include reason, time, date, location, and outcome ([[Jonesboro UAS RTCC and ALPR Policies 714 and 715]], `2025 Policy Manual-Complete.pdf`, pp. 407–414). - **Mixed procurement and grant funding.** A 2023 `$103,411.00` Flock payment packet documents 34 Falcon LPRs and one Flex, while a `$100,000.00` state equipment grant and a `$55,553.52` federal PSN award funded a broader camera and mobile-computing stack ([[Jonesboro Flock Procurement Expansion Records 2023]]; [[Jonesboro Public Safety and Project Safe Neighborhoods Camera Grants]]). ## Notes The inventory's 870 views and the public March 2025 "767 RTCC cameras" figure are not reconciled by the records, and the 85-Axon statement does not map onto the 116-row vehicle list. The completion notice says Sections 6–8 must come from Flock because JPD does not keep those records, but the produced policy identifies several locally documented access, request, user, MOU, and dissemination-log categories. That custody conflict deepens [[T020 - Jonesboro Shared-Camera Documentation Statement vs Inventory Entries]]. > [!contradiction] > The live ARDOT export labels P1969 `Flock; Pend Sign` at Hwy 49 Sec 3 LM 8.026 ([[Statewide Traffic Control Devices Export]], `TrafficControlDevices.csv`, line 428), while the agency-produced packet contains a City-signed completion return dated 2026-04-16 ([[Jonesboro ARDOT ALPR Permit Packets P1881 P1889 P1967 P1969 P1982]], `ARDOT 1969.pdf`, p. 1). See [[T038 - Jonesboro P1969 Completion Return vs Pending-Sign Export]]. ## What the RTCC actually does Section 2 of `JPD-2026-851` produced the Real Time Crime Center's own case-level camera-pull log: **5,201 entries from December 2023 to June 2026**, one per request to check cameras for a case ([[Jonesboro RTCC Camera Pull Log 2023-2026]]). It is the only record of its kind in the corpus. - **Traffic matters outnumber criminal ones roughly 4.7 to one** (1,339 against 284). - **Evidence was found in roughly 83%** of pulls with a recorded outcome (3,956 of 4,767); **an arrest is associated with about 8%** where recorded (136 of 1,663). - **About 85% of pulls are internal investigative work** rather than records-request fulfillment (4,083 of 4,777 carry no FOIA flag). - **Flock appears 152 times as a pull source**, logged alongside City intersection cameras without distinction. - Volume grew about **72% from 2024 to 2025**; the busiest month is April 2025 at 251 pulls. The log was rebuilt three times over the period, moving from one Microsoft Forms instrument to another and then to a manually maintained table, so its fields are not consistent across all thirty-one monthly tabs. The Department also volunteered an express per-category disposition with the delivery: "Section number two is considered complete."