From the Public Safety edition of September 28, 2026
IMPD Flock-misuse cases enter criminal court as STOP calls new guardrails inadequate
WRTV / Indiana’s I-Team · Independent local television journalism · Indianapolis, Indiana, United States
- Publisher
- WRTV
- Original publication
- September 28, 2026
- Source retrieved
- 2026-09-29
- Event date
- 2026-09-28
What happened
Updated Sept. 28, 2026, WRTV reported that criminal court proceedings are underway for five Indianapolis Metropolitan Police Department officers charged in connection with alleged misuse of Flock Safety ALPR—unauthorized searches involving intimate partners, exes, and strangers. Officer Michael Rogers, a 16-year veteran, appeared Monday on fraud and official-misconduct charges tied to lookups of vehicles linked to his wife and people close to her; the judge set a $5,000 cash bond with no-contact and no-firearms conditions. Officer Jonathan Schultz, who appeared Sept. 25, faces stalking charges in addition to fraud/official misconduct; charging documents describe following a victim and 178 Flock searches on one woman over three months; the magistrate set a $10,000 bond with GPS monitoring and a protective order covering 11 victims and two witnesses. WRTV quotes Surveillance Technology Oversight Project communications director Will Owen calling IMPD’s new guardrails insufficient and Flock’s newly announced controls a crisis PR stunt, urging Indianapolis to cancel. Chief Tanya Terry said it is too soon to know whether other officers abused access after the prosecutor described the five cases as just the beginning.
Why it matters
Municipal policing ALPR misuse moving from internal discipline into criminal court—public-safety accountability and civil-rights oversight.
Evidence and measured results
Sept 28-updated local TV investigation with court-appearance facts, bond conditions, charging-document vignettes, and named STOP/chief quotes.
Limitations and uncertainty
Charges are allegations and cases are ongoing; related Sept 23 charging stories already archived—this resource is the court-process update; STOP statement is advocacy; full audit findings not published in the article.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- ALPR credentials were allegedly used for months of intimate-partner and stranger surveillance, and cases are now in criminal court despite new vendor auditing promises.
- Stakeholders
- Police chief / professional standards
- Mayor / city-county council
- County prosecutor
- City counsel
- Civil-rights advocates (e.g., STOP)
- Discovery questions
- What is the median days-to-detect for unauthorized ALPR searches in the last 24 months?
- Are anomaly lockouts mandatory and admin-reviewed within 24 hours?
- Will keep-versus-cancel be a public civilian vote with audit results?
- How are victims notified and protected when officers are charged?
- Value hypothesis
- Bounded value is faster detection/lockout and prosecutable logs—or an orderly exit—not a claim that any vendor tool eliminates insider misuse.
- Potential engagement
- 4–6 week ALPR abuse-control review: log forensics sample, lockout SOP, IA/prosecutor playbook, keep/cancel options brief.
- Unsupported claims
- That the five charged officers are the only abusers
- That Flock Audit Assistance would have prevented these cases
- Guaranteed conviction outcomes
Pre-sales engineering
Role takeaway
- Fit
- Agencies on networked ALPR with broad officer search rights and weak real-time anomaly response.
- Architecture and integration
- Search service→purpose/case token→anomaly engine→automatic lockout→IA case file export; victim-protective order workflows outside the ALPR product.
- Prerequisites
- Immutable search logs
- Mandatory case codes that are validated not free-text theater
- Admin on-call for lockouts
- Identity-proofed accounts
- Constraints
- High legitimate query volume
- Multi-agency sharing networks
- Labor rules on suspension/termination
- Security
- Assume authorized-insider threat; monitor repeated queries on plates tied to officer associates; disable shared credentials.
- Proof of value
- Mean time-to-lockout on red-team abuse scripts
- Percent of searches with validated case tokens
- IA-ready log export time <1 business day
Delivery
Role takeaway
- Work
- Complete Flock audit, sustain court/IA coordination, harden lockout SOP, and schedule civilian keep/cancel decision with published metrics.
- Dependencies
- Prosecutor and courts
- Vendor admin tooling
- Union/HR process
- City counsel
- Ownership
- Professional standards commander with city counsel co-owner for keep/cancel recommendation.
- Skills and adoption
- Train supervisors to review anomaly queues daily; train officers that ALPR is auditable like NCIC.
- Governance checkpoints
- Weekly audit status to chief/mayor
- Lockout SOP signed
- Public keep/cancel hearing
- Acceptance criteria
- Audit complete with published summary statistics
- Mandatory lockout enabled
- Recorded civilian disposition on contract
- Risks
- Under-counting abusers
- Guardrail announcements without enforced lockouts
- Victim safety gaps during pretrial release
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
ALPR search systems need proactive lockouts, immutable justification logs, and supervisor alerting that surface intimate-partner query patterns before months-long abuse accumulates.
Governance
Who approves, reviews and stays accountable for outcomes?
Criminal charging and protective orders show policy FAQs and vendor Audit Assistance announcements are incomplete accountability; cancellation remains a live political option per STOP.
Security and privacy
What data, permissions and controls need testing?
Credentialed insider misuse against intimate partners is the dominant failure mode here—controls must assume malicious authorized users, not only outsider sharing.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
IA, prosecutors, and victim advocates need capacity for multi-defendant ALPR abuse cases; line officers need clear retraining that personal queries are criminal exposure.
Procurement
What should contracts, pricing and exit terms secure?
Renewals should condition payment on mandatory anomaly lockout, log export SLAs, and independent audit rights—cancellation remains a negotiated alternative.
Operating model
Which teams own the service once it runs?
Treat ALPR like a high-risk CJIS database with continuous monitoring, not a convenience search app; escalate from policy memos to criminal referral pathways when intimate-partner patterns appear.
Publication history
- 2026-09-28Public Safety · Issue 224 resources
Stable resource ID: wrtv-impd-flock-court-20260928