A narrative topic page compiled from council records, the Arkansas Leader, and the other sources listed at the bottom of the page. Resident discussion from Facebook groups is paraphrased into themes; no posts are quoted.
The Flock Camera Fight
The story
For four and a half years, nine Flock Safety license-plate cameras watched the entrances and corridors of Cabot with almost no public debate. Then, in a single summer, they became the most argued-about subject in the city — in its Facebook groups first, then in its council chamber. As of late October 2026 the cameras sit covered and disconnected: not reinstated, not removed, with a funding ban pending and a review process still open.
Arrival, quietly (2021–2022). The Cabot Police Department tested Flock cameras for about three months in late 2021. The city signed a lease contract with Flock Safety in January 2022, and installation began in February 2022. Nine cameras eventually operated at sites across town (the Leader's October 2026 account lists locations including 202 S. Rockwood Drive, 150 Grayhawk Road, 3131 S. Second St., 1435 W. Main St., and 2900 S. Pine St.). The department's own LPR policy, issued under Chief Scott Steely on September 13, 2022, set the ground rules: only trained, assigned officers could use the system; a hot-list hit alone could not justify a traffic stop; captured plate data could be shared with other law-enforcement agencies for criminal-justice purposes but not sold or traded; and plate data the department preserved was capped at 150 days. There was no standalone council vote on adopting the system that the public could weigh in on. As Council Member Matt Webber later put it at the August 17, 2026 meeting, the council approved Flock only as a line item — the service appeared in the 2024, 2025, and 2026 budgets that way. The Leader reported the system's cost at $92,000 across 2023–2025, with $18,000 paid in 2026; the agreement could be cancelled by either side at any time.
Four years of operation (2022–2026). The cameras scanned plates and checked them against hot lists drawn from the National Crime Information Center, the Arkansas Crime Information Center, and department lists. The results the police department reported for January 1–June 30, 2026 were the system's best statistical case: 8.04 million license plates scanned, 688 matches against one or more lists, seven stolen vehicles recovered, and 19 arrests — including, the Leader reported, a sex offender and a fugitive extradited to Texas on a felony warrant. At some point before the shutdown, the department also suspended outside agencies' access to its Flock data, a fact that surfaced in the October hearing. Nothing in the record alleges that a Cabot officer misused the system.
The turn (2026). In January 2026, Council Member Corey Spangler emailed Mayor Ken Kincade suggesting the city look at its Flock policies. The mayor, the police chief, and the city attorney began a review. The public argument, though, ignited in the Facebook groups in July (see the discourse section below) — a DeFlock camera-mapping post on July 8, an accountability project's records-review post on July 13, and a resident's long FOIA-based explainer on July 29 that drew 167 comments. On August 6, 2026, Mayor Kincade ordered all nine cameras covered and disconnected. His stated reasons, in the Leader's and the Democrat-Gazette's accounts, were privacy concerns formed after further reading on the national debate and reports of improper uses elsewhere — while saying he did not believe Cabot's police had misused the system. He also told the council that in the past year only one person, an out-of-state emailer, had contacted him about the cameras before Spangler's January email prompted the review. The ADG reported the suspension on August 7; KATV and THV11 covered it August 7–8; Mayflower and Pea Ridge stopped their own Flock systems in the same stretch (ADG, August 10), and by August 28 at least seven Arkansas cities had stopped while the Arkansas Association of Chiefs of Police publicly endorsed plate readers.
Debate and deadlock (August–October 2026). The council debated the program on August 17, 2026, in a meeting where the process criticism (Webber's line-item point), the mayor's reasoning, and law-enforcement defenses all aired. A review committee worked through the fall — its packet materials included the police department's 2022 policy, the police chiefs' association model ALPR policy, and a September 1, 2026 summary Flock itself sent the department for the committee, in which the company said its system captures plate images and vehicle characteristics (not faces or biometrics), stores data on Amazon Web Services servers, and leaves data ownership and access control with the customer city. The committee met in October and gave recommendations to the council. On October 19, 2026, the city held a two-hour public hearing — the Leader reported up to 200 people participated — and that night took up three measures:
- - A resolution to permanently remove the cameras and poles failed 2–3–3: Hillenburg and Kyle Pickard voted yes; Cope, Stephen Redd, and James Reid voted no; Ed Long, Spangler, and Matt Webber abstained.
- - Resolution No. 34 of 2026, supporting the existing suspension and setting review criteria and procedures during it, was part of the same hearing.
- - Ordinance No. 33 of 2026, introduced by Spangler, received its first reading. Its title states its purpose: prohibiting the appropriation or expenditure of city funds for automated license plate reader systems, establishing municipal fiscal policy, protecting citizen privacy and data security, and recognizing existing contractual obligations.
Spangler abstained on the removal resolution, and his stated approach explains why: a resolution states a position, while an ordinance binds spending. His position, stated in his own group posts before and after the hearing, is to first undo the current third-party system — the outcome he argues a consensus already supports, uniting residents who oppose the cameras outright with camera supporters who object to a private company holding the data — and to treat any in-house system as a separate, later decision to be made in public, under public oversight, not as part of this fight. He is not proposing a city-run replacement now.
Where it stands (late October 2026). The cameras remain covered. The council has neither reinstated them nor voted their permanent removal; Ordinance No. 33 has had a first reading and no recorded vote — the October 19, 2026 council minutes are missing from the city's posted records, so the ordinance's path from here runs through future packets, not the code books.
What critics said
The criticism ran in both directions, and much of it was aimed as much at how the decision was made as at the cameras themselves.
- - The surveillance case. Privacy critics — including council candidate Courtney Roldan and former state Rep. R.D. Hopper at the October 19 hearing — described the system as mass government surveillance: a private company collecting plate data to cloud servers, shared with other agencies, building a searchable record of where law-abiding residents travel. Roldan's formulation, in the Leader's account, was that law-abiding citizens should be able to go about their daily lives without justifying why they should not be tracked, and that citizens should never have to justify wanting to be left alone. A speaker identified in the coverage as Cooper cited national examples of officers misusing plate data to track girlfriends and wives — while conceding that was not the norm — and asked why a network search should be allowed without the warrant that searching a phone, vehicle, or home would require.
- - The process case. The cameras were never the subject of a standalone council vote before installation; they were approved as budget line items. For process critics, a surveillance network that arrived by budget line and ran for four years before its first public hearing was the problem in itself, whatever the cameras' merits.
- - The case against the suspension. Retired law-enforcement voices at the August 17 debate argued that if no Cabot officer had misused the system, suspending it punished good officers and helped only, in one speaker's phrase, bad actors and their lawyers. Council Member Maggie Cope pressed the mayor directly: if nobody in the department misused it, what was the final straw? Three council members — Cope, Redd, and Reid — ultimately voted against permanent removal, and the department's January–June 2026 numbers (8.04 million scans, 688 matches, seven stolen vehicles, 19 arrests) were the factual core of the keep-the-cameras case.
- - The case against the abstention. Spangler's abstention on the removal resolution drew fire from within the anti-camera camp: in BCOC the day after the hearing he was accused of cowardice, and he answered in the group that he had literally introduced an ordinance to ban third-party ALPR the night before and preferred a well-thought-out, binding solution to a symbolic one. The exchange is a fair snapshot of the fall argument: agreement on ending the third-party arrangement, disagreement over the instrument.
The Facebook discourse
Flock was the dominant civic topic in Cabot's Facebook groups from August through October 2026 — but the striking thing, reading the groups backward, is how late the conversation started. The system operated from early 2022, and targeted searches of the major groups surface essentially no substantive discussion of it before July 2026. The discourse has a clear four-act arc:
Act one: ignition (July 2026). The conversation did not begin with a news story; it began with homework. On July 8, a Cabot Strong post shared DeFlock, the national camera-mapping project, urging residents to help track the cameras in their communities. On July 13, a post in BCOC reported that the Arkansas Public Accountability Project was reviewing Cabot Police Department records produced under a FOIA request on the ALPR system. On July 7, a BCOC thread framed the issue bluntly — it is not about safety. The act's peak was July 29, when a resident posted a long explainer in Cabot Strong laying out what they had learned about Cabot's Flock system through FOIA — contracts, reports, user lists, training records — and drew 167 comments. The comments on that single post contain the whole later argument in miniature: constitutional framing (the Fourth Amendment, warrants, probable cause, "Big Brother"); imported national stories (a case in which plate data was reportedly used to track a woman traveling for an abortion; a Michigan city whose council had been promised the cameras would stay off until it voted; reports of officers using the system to stalk); location-hunting (residents asking where every camera was and reporting sightings, including at a home-improvement store); pushback (you carry a GPS phone everywhere; we are filmed everywhere already; the government issued your plate number); and meta-skepticism (one commenter accused the explainer of being copy-pasted from a chatbot). An August 1 post in Cabot Strong — a lengthy personal statement from a member who said they had been fielding questions and concerns about the cameras — drew 70 more comments, and an August 10 share post calling an anti-Flock piece "a good read for your information" drew 114.
Act two: the suspension and the organizing (August 2026). When the mayor ordered the cameras covered on August 6, the groups became the story's distribution system: a THV11 reporter posted in Cabot Strong on August 7 seeking residents willing to be interviewed on camera (121 comments), and the same recruiting ran in the News and Commentary group. An August 11 question — what do Flock/Axon or any other plate readers really do, and who can access the data — shows the discourse's information hunger phase. By August 20, Cabot Strong hosted organizing in plain sight: a post asking who else was against the cameras, noting the covered cameras were supposedly temporary while removal was considered, and asking what people were already organizing. On August 30 a post demanded the "invasive cameras" be taken down. Moderation itself became part of the discourse in BCOC, where an August 8 admin notice that camera posts would be deleted (64 comments) drew free-speech pushback — even as at least one commenter cheered the removal news. The same argument did not look the same in every room: BCOC throttled it, WTF CABOT hosted a structured debate prompt on September 7 ("What's your take on Flock cameras?" — supporters citing worsening driving behavior, opponents describing a system that tracks more than plates, 40 comments), and a September 10 WTF post urged people who felt strongly online to convert opinion into civic participation and show up.
Act three: mobilization and the hearing (October 2026). In the run-up to October 19, the groups functioned as the town bulletin board the newspaper no longer is: an October 14 Cabot Strong post shared the town-hall notice as a public service, noting that very few people read the newspaper anymore and no other notification could be found; an October 16 post announced the Flock camera town hall (Monday, October 19, 6:30 p.m., Justice Center Building). Spangler used the groups as a campaign channel, pre-announcing his funding-ban ordinance on October 15 in News and Commentary and Cabot Strong (about 30 comments across the two) on the argument that ending third-party ALPR was an achievable consensus. On hearing night, a BCOC member posted a first-person account of attending intending to voice a couple of concerns about Flock and other ALPRs. The next day came the abstention fight described above — the discourse's center of gravity shifting, within 24 hours, from the cameras to the tactics of ending them.
Act four: the flip (late October 2026). On October 24, a Cabot Strong post about vandalism at Richie Road Park asked angrily why there were no cameras there — and drew 137 comments, with commenters complaining about graffiti, pressing for cameras mounted outside park facilities, and one tagging the mayor. After three months in which "cameras" in the groups almost always meant surveillance overreach, the word flipped valence: the absence of cameras became the grievance. The discourse ends the fall exactly where the council did — split, with the same technology framed as intrusion in one thread and as missing protection in another, and with no consensus in the groups any cleaner than the 2–3–3 on the council floor.
A note on volume and limits: Flock threads routinely drew 40–170 comments in groups whose ordinary civic posts draw a handful, and the topic crowded out nearly everything else civic for a season. But group search is relevance-ranked and much of BCOC's content is image-based, so the minable text record is a sample of the conversation, not the whole of it — and the four years of silence before July 2026 may partly reflect what search can no longer surface, not only what residents said at the time.
What the record shows
- - The timeline is documented at every step: the January 2022 lease and February 2022 installation (Leader, Oct. 21, 2026); the September 13, 2022 department LPR policy (in the Oct. 19, 2026 council packet); budget-line-item approval in 2024–2026 (Webber, at the Aug. 17 meeting); the January 2026 Spangler email and the review it prompted (Leader, Aug. 19, 2026); the mayor's August 6, 2026 suspension order; the August 17 debate; the October 19 hearing and the 2–3–3 removal vote (Leader, Oct. 21, 2026); Ordinance No. 33's first reading (Oct. 19, 2026 agenda and packet).
- - The performance numbers are the police department's own, as reported: 8.04 million plates scanned, 688 hot-list matches, seven stolen vehicles recovered, and 19 arrests for January–June 2026. They establish what the system did; they do not by themselves settle what it should do, and no independent audit of the figures appears in the record reviewed.
- - The retention question has two answers, and public discussion often merged them. Under the Flock agreement preserved in the Oct. 19, 2026 packet, Flock deletes footage on a rolling 30-day basis — the department's window to extract and archive anything it meant to keep was 30 days. Separately, the department's 2022 policy capped plate data the department itself preserved at 150 days, longer only for an ongoing investigation; the 150-day figure is the one the Leader reported as discussed at the October hearing, and it matches the cap in Arkansas Code § 12-12-1804(a)(2). So "30 days" and "150 days" are both documented — for different buckets: the vendor's cloud versus the department's own preserved records.
- - No local misuse is documented. Nothing in the coverage or the packet alleges a Cabot officer misused the system; the mayor said the same. Misuse examples cited in the debate were from other jurisdictions, offered as risk, not as local fact.
- - What remains unknown: the final outcome of Ordinance No. 33 (no recorded vote; the Oct. 19, 2026 minutes are missing from the city's postings); the review committee's full recommendations (the committee met in October and reported, but the complete text is not in the corpus); whether the outside-agency access suspension predated the policy review or followed the January email; and the outcome of the regional wave — at least seven Arkansas cities stopped Flock in August 2026, and the longer arc of those decisions is still being written elsewhere.
Connected threads
- - Criticism of Mayor Kincade — the suspension was the mayor's own order; that page pairs the Flock criticism he drew from both directions with his stated reasons and the wider record of his tenure.
- - Election 2026 — the camera fight ran straight into the fall ballot: a council candidate campaigned on the surveillance case at the hearing, and the funding-ban ordinance is part of the Ward 1, Position 2 incumbent's record in the race.
- - Growth & Traffic — the pro-camera argument in the groups leaned heavily on worsening driving and traffic enforcement, the same frustration that dominates the growth conversation.
- - The Crypto Mine and Act 314 — the mirror-image fight: there, residents mobilized against an outside project and state law overruled the locals; here, residents mobilized against a city system and the city itself pulled the plug — both arguments ran through the same Facebook groups.
Sources
- - Arkansas Leader, Oct. 21, 2026 — "Flock cameras stay covered in Cabot for now" (Jeffrey Smith): corpus
leader-2026/browser-download-20261026T181955.416149130Z-69-*.txt. Hearing, 2–3–3 vote, police-reported figures, contract dates, costs, Roldan/Hopper/Cooper remarks. - - Arkansas Leader, Aug. 19, 2026 — "Cabot council debates Flock cameras" (Jeffrey Smith): corpus
leader-2026/browser-download-20261026T182730.065434281Z-78-*.txt. The Aug. 6 order, Spangler's January 2026 email, Webber's line-item point, Cope's "final straw" question, the mayor's answers. - - Arkansas Leader, Aug. 26, 2026 — regional Flock debate coverage: corpus
leader-2026/browser-download-20261026T182708.128931874Z-77-*.txt. - - Cabot City Council packet, Oct. 19, 2026 (corpus
council/andcouncil-ocr/): agenda titles of Ordinance No. 33 and Resolution No. 34 of 2026; Cabot Police Department LPR policy (Sept. 13, 2022); IACP model ALPR policy; Flock Safety summary email to Capt. Gibson, Sept. 1, 2026. - - Arkansas Democrat-Gazette: "Cabot halts use of Flock license plate readers, pending review of technology," Aug. 7, 2026; "Mayflower joins Cabot, Pea Ridge in stopping use of Flock license plate readers," Aug. 10, 2026; "Arkansas police chiefs association endorses use of Flock license plate readers amid backlash," Aug. 28, 2026 (corpus
adg-index.md). - - KATV, "Cabot is suspending its use of Flock cameras amid privacy concerns," Aug. 8, 2026; THV11, "Cabot pauses Flock camera program amid debate on civil liberties," Aug. 7, 2026 (corpus
tv-index.md). - - Facebook groups — Cabot Strong (both groups of that name), WTF CABOT ARKANSAS, Cabot's Petty Citizens – BCOC, Cabot and Lonoke County News and Commentary: corpus
facebook-mining.md(Oct. 26, 2026) plus a fresh read-only search and comment pass, Oct. 30, 2026 (queries: "Flock," "license plate readers," "surveillance cameras"; bounded comment reads on the July 29, 2026 FOIA explainer thread). Themes paraphrased; no posts or comments quoted; no private individuals named. - - This site's Criticism of Mayor Kincade page: corpus
topics/mayor-kincade-criticism.md.