# Jonesboro RTCC Camera Pull Log 2023-2026 `Real Time Intelligence Report.xlsx`, produced 2026-07-24 as Section 2 of `JPD-2026-851`. Thirty-one worksheets, one per month, **December 2023 through June 2026**, totalling **5,201 data rows**. This is the corpus's **first case-level record of surveillance-camera use**. Every other agency has produced inventories, contracts, policies, or statutory aggregates. This log records the individual act: an officer asked the Real Time Crime Center to check cameras for a case, and the RTCC wrote down which cameras, what kind of matter, whether anything was found, and whether an arrest followed. **Handling.** Published here in aggregate only. The log carries 4,387 free-text note entries, row-level case numbers, and 307 distinct officer-name values; those are not republished. The full extraction remains in the immutable corpus. This follows the [[FCSO Skydio X10 Flight Log]] precedent, where per-row incident detail was withheld and program-level figures published. ## Volume and growth | Period | Camera pulls logged | |---|---:| | December 2023 (first month) | 71 | | 2024 | 1,482 | | 2025 | 2,543 | | 2026, January–June | 1,105 | | **Total** | **5,201** | Activity rose about **72% from 2024 to 2025**. The 2026 half-year pace annualises to roughly 2,210, close to the 2025 level. The busiest single months are April 2025 (251), November 2025 (239), and May 2025 (236); the quietest are the first two months of operation, December 2023 (71) and April 2024 (75). ## Outcomes The columns are not uniformly present across all 31 tabs, so each figure below is counted where its field exists rather than against all 5,201 rows. The denominators are given. | Measure | Result | Of | |---|---|---:| | **Evidence found** | **3,956 yes** / 781 no (+21 "other", 9 "nothing found") | 4,767 | | **Arrest made** | **136 yes** / 1,527 no | 1,663 | | **FOIA-driven pull** | 694 yes / **4,083 no** | 4,777 | Three things follow from this. **Evidence is usually found.** Roughly **83%** of pulls with a recorded outcome returned evidence. That is a high yield, and it is the agency's own characterisation rather than an outside assessment. **Arrests are rare.** Where the arrest field is populated, **about 8%** of pulls are associated with an arrest — 136 across 1,663. Evidence found and arrest made are plainly not the same measure, and the log keeps them separate. **The system is overwhelmingly for internal investigation, not public records.** Only **694 of 4,777** pulls, about **15%**, are flagged as FOIA-driven. The remaining 85% are the Department checking its own cameras for its own cases. ## What the cameras are used for | Matter type | Count | |---|---:| | Traffic | 1,339 | | Criminal | 284 | | Both | 142 | | Discovery | 24 | **Traffic matters outnumber criminal ones by roughly 4.7 to one.** The Real Time Crime Center, as its own log describes it, is used predominantly for traffic work. ## Which cameras get pulled Token frequency across the "cameras used" field, which records intersections and systems in free form: | Token | Appearances | |---|---:| | Caraway | 162 | | **Flock** | **152** | | Highland | 141 | | Johnson | 112 | | Red Wolf | 103 | | Parker | 92 | | Nettleton | 92 | | Main | 69 | Named intersection pairings recur heavily: Red Wolf & Highland (71), Caraway & Highland (63), Red Wolf & Stallings (54), Red Wolf & Nettleton (53), Red Wolf & Race (53), Caraway & Nettleton (52). **Flock appears as a pull source 152 times, alongside the City's own intersection cameras in the same log.** The RTCC does not treat the plate-reader network as a separate system; it is one more camera source an analyst checks. This is the operational counterpart to the inventory documented in [[Jonesboro Camera and Views Inventory]]. ## The log was rebuilt three times The schema changes twice across the period, which is itself a finding about how the program was administered: | Era | Tabs | Shape | |---|---:|---| | **Dec 2023 – Oct 2024** | 11 | Microsoft Forms export: `Timestamp`, `Report type/Case Number/Accident`, `Type of Video Requested`, `FOIA`, `Did you request this or did you complete it`, `Upload/Export Complete`, `Evidence Found`, `Notes` | | **Nov 2024 – Aug 2025** | 9 | A second Microsoft Forms export adding `ID`, `Start time`, `Completion time`, `Email`, `Name` | | **Sept 2025 – Jun 2026** | 11 | A manually maintained table: `DATE FOUND/ATTEMPTED`, `CASE NUMBER`, `CAMERAS USED`, `ARREST MADE`, `TYPE`, `FOIA`, `UPLOAD/EXPORT COMPLETE`, `EVIDENCE FOUND`, `COMPLETED BY` | **January 2025 is an anomaly**: it uses the manual-table shape while the months on either side of it use Microsoft Forms v2. The consequence for anyone reading these numbers is that the series is not a single instrument measured consistently for thirty-one months. Fields appear, disappear, and change names, which is why every figure above carries its own denominator. ## Cross-references - [[jonesboro-pd/2026-07-24-jpd-851-section-2/_overview|Section 2 production overview]] - [[jonesboro-pd/2026-07-23-jpd-851-section-1/_overview|Section 1 production overview]]; [[Jonesboro Camera and Views Inventory]]; [[Jonesboro Unit LPR Vehicle List]] - [[Jonesboro Police Department]]; [[Real-Time Crime Center (RTCC)]]; [[ALPR Error Layers and Outcome Measurement]] - [[T020 - Jonesboro Shared-Camera Documentation Statement vs Inventory Entries]] ## Open questions / follow-ups - Whether "evidence found" is assessed at pull time or after review, and what standard the analyst applies. - Why arrest data is recorded on roughly a third of rows and absent from the rest. - What the 694 FOIA-flagged pulls correspond to, and whether the Department retains a separate log of records-request video work. - The relationship between this log and the Flock platform's own audit records; the Flock entries here are analyst-recorded, not a platform export. - Whether the two Microsoft Forms instruments still exist as separate retained datasets.