# Benton County SO P1873 Permit Supplement On 2026-08-03, the [[Benton County Sheriff's Office]] sent a 23-page P1873 permit packet and answered the July 22 follow-up inline (Gmail message `19fc92818daf13aa`). The attachment documents an approved Flock relocation plan on Highway 12 near Gentry; the email separately clarifies site status, offers larger retained files on USB, gives active Motorola/WatchGuard model counts, and identifies other County custodians. ## What's inside - [[Benton County P1873 Flock Relocation Permit]] — TCD Permit 1873, District special-permit and bond documents, a Sheriff's authorization letter, and Flock's engineering plan for `#07 W HWY 12 @ GENTRY - RELOCATION`. - Gmail message `19fc92818daf13aa` — current operational statements and routing for additional records; correspondence remains in Gmail rather than `raw/`. ## Key takeaways - **Six previously unqualified BCSO Flock sites are now agency-described as installed and operational.** The email says the two `"not installed/in permitting"` sites remain uninstalled and `"all others are installed and operational"`. It does not answer how many devices serve the east/westbound coordinate (Gmail message `19fc92818daf13aa`). - **P1873 is a BCSO/Flock permit, but it does not crosswalk to BCSO site record 1.** The final plan gives `36.276600, -94.579146`, `"LOOKING SOUTHEAST"`, and `"#07 W HWY 12 @ GENTRY - RELOCATION"` (`P1873...Signed.pdf`, p. 11). That point is 7.2 meters from ARDOT's P1873 GIS row but 181.3 meters from the separately disclosed BCSO site record 1. - **The completion page is blank.** It says `"Return this page when the work is complete"` but has no completion date or returned signature (`P1873...Signed.pdf`, p. 6). The packet therefore does not establish final inspection, acceptance, as-built placement, or current operation. - **Additional records are available but not delivered.** The custodian says current/historical SharedNetworks or Network Audit exports and six-month ALPR reports are too large for email and offers a USB for pickup, conditioned on replacement with a new sealed USB of the same size (Gmail message `19fc92818daf13aa`). - **The agency supplied active model counts rather than an inventory.** It reports `"47 m500’s 73 4re’s and 164 v300 or v700 that show active"` and says Motorola contracts are held by the County Judge. The statement does not split V300 from V700 or provide serials, assignments, dates, retention, or a native inventory (same message). - **Drone custody is elsewhere.** The response says `"EMA under the county judge has the drones"` (same message). - **The Marine discrepancy is narrowed but not fully documented.** The custodian says `"No records found, it will most likely just need to be updated"` about the official webpage. This makes stale web copy the leading explanation while leaving inventory/disposal history unproduced; see [[T015 - Benton County Marine Camera Status]]. ## People and organizations - [[Shawn Holloway]] — Sheriff and authorizer on the Countywide Flock letter. - [[Stacy G. Burge]] — ARDOT District Nine Engineer and special-permit/bond signatory. - [[Joseph D. Hawkins]] — ARDOT TSMO Division Head named on TCD Permit 1873. - [[Skylar Lindner]] and [[Cody Boudreaux]] — Flock project and permitting contacts on the plan. - [[Benton County Sheriff's Office]], [[Benton County]], [[Flock Safety, Inc.]], [[Motorola Solutions]], and [[Arkansas Department of Transportation]]. ## Events documented - [[2026-08-03 Benton County Produces P1873 Permit and Offers USB Records]] ## Open questions / follow-ups - Receive and ingest the offered USB production. - Obtain installation, inspection, acceptance, as-built, activation, relocation, and lifecycle records for P1873. - Clarify whether P1873 replaced, preceded, or is unrelated to BCSO site record 1. - Obtain the native Motorola/WatchGuard inventory and the contracts from the County Judge's custodian. - Obtain the EMA drone inventory and related policy, procurement, and deployment records. ## Safety and integrity The preserved PDF passed Microsoft Defender scanning, PDF parsing, active-content inspection, and full-page render review. Pages 1–7 required OCR; pages 8–23 contained native text. The frozen extraction records that distinction in `_extraction-methods.csv`.