From the Public Safety edition of September 23, 2026
Five IMPD officers charged after audits find Flock ALPR misuse for personal tracking
Axios Indianapolis · Independent local journalism · Indianapolis / Marion County, Indiana, United States
- Publisher
- Axios Indianapolis
- Original publication
- September 23, 2026
- Source retrieved
- 2026-09-24
- Event date
- 2026-09-23
What happened
On Sept. 23, 2026, Marion County Prosecutor Ryan Mears announced criminal charges against five Indianapolis Metropolitan Police Department officers for misusing Flock ALPR cameras to track romantic partners, spouses, and women met in public. Michael Rogers (16 years) faces three counts each of fraud and official misconduct for allegedly thousands of improper searches; Jonathan Schultz (18 years) faces 26 total counts of stalking, fraud, and official misconduct after allegedly searching more than 1,000 plates and engineering encounters; Cassandra Crawley (7 years) faces eight counts each of fraud and official misconduct for hundreds of improper searches; Matthew Binford (4 years) faces one count each of fraud and official misconduct for allegedly using a superior’s laptop to track his ex-wife; Abigail Cramer (5 years) faces six counts each of fraud and official misconduct for hundreds of improper searches and has resigned. IMPD suspended the five and recommended termination (Cramer resigned). Internal audits in August and September uncovered irregular ALPR usage; IMPD updated policy to require tying every Flock search to a specific case or incident number. IMPD has hundreds of Flock cameras under a 2025 four-year contract expecting about $1M annually (up to $6M over the term). Mears called the audit-driven charges “just the beginning” of Flock-related cases.
Why it matters
Concrete U.S. municipal policing example of ALPR personal-misuse escalating to felony/misdemeanor charges, suspensions, and case-number policy hardening—core public-safety oversight evidence, not emergency services.
Evidence and measured results
Local Axios reporting of prosecutor news conference and IMPD statements. Corroborated in inspections of ABC News and WISH-TV pieces citing affidavits (e.g., Schultz plate-search volumes). Charges are allegations; trials/outcomes not observed here.
Limitations and uncertainty
Secondary journalism summarizing charging decisions; full affidavits not opened as primary PDFs here. Counts and search volumes are prosecutor/department allegations. Contract spend figures are department expectations, not audited invoices.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A large Flock deployment generated criminal charges after internal audits found officers using ALPR for personal stalking and tracking.
- Stakeholders
- Police chief
- County prosecutor
- Mayor / council
- Internal affairs / professional standards
- Community members tracked without cause
- Discovery questions
- When was your last ALPR irregular-usage audit?
- Is every search forced to a case or incident number?
- Can officers share credentials or use supervisors’ devices?
- What is the path from audit hit to IA and prosecutor referral?
- Value hypothesis
- Bounded value is preventing personal-misuse prosecutions and demonstrating enforceable purpose limits—not clearance-rate marketing from this case.
- Potential engagement
- 4–6 week ALPR misuse-control sprint: case-gate, credential hygiene, audit sampling, and IA referral playbook.
- Unsupported claims
- That charges prove systemic guilt of all Flock users
- Guaranteed reduction in stalking via software alone
- Crime-solving ROI of the Indianapolis camera network from this article
Pre-sales engineering
Role takeaway
- Fit
- Municipal Flock deployments with hundreds of cameras needing mandatory case linkage and anti-credential-sharing controls.
- Architecture and integration
- Flock query API/UI + RMS/CAD incident IDs + SSO/MFA per officer + anomaly detection on personal-plate patterns + IA export.
- Prerequisites
- Per-user authentication (no shared laptops)
- Mandatory case/incident field
- Retained searchable audit logs
- Constraints
- Existing four-year vendor contract
- High search volumes complicate manual review
- Allegations pending adjudication
- Security
- Block shared-device queries; alert on ex-partner plate patterns; preserve forensic logs for prosecutor use.
- Proof of value
- Irregular-usage detections before external tip
- Zero successful queries without case ID
- Revoked access for suspended officers within hours
Delivery
Role takeaway
- Work
- Execute audit→IA→charges workflow, impose suspensions/terminations, rewrite Flock policy for case numbers, and communicate to the public.
- Dependencies
- Prosecutor charging standards
- Vendor log completeness
- Union/disciplinary process
- Ownership
- Chief and professional standards; prosecutor owns criminal case decisions.
- Skills and adoption
- Retrain all ALPR users on case-linkage and personal-use prohibition with explicit stalking examples.
- Governance checkpoints
- August/September-style audit cadence institutionalized
- Policy update published
- Council notified of contract risk
- Acceptance criteria
- Case/incident required on every Flock search
- Charged officers’ access revoked
- Named owner for ongoing irregular-usage audits
- Risks
- Checkbox case numbers masking personal use
- Further cases straining IA capacity
- Public trust damage despite charging
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 platforms need case/incident mandatory fields, credential sharing prevention (superior’s laptop misuse), and audit pipelines that surface irregular personal-pattern queries before prosecutors intervene.
Governance
Who approves, reviews and stays accountable for outcomes?
Internal audits plus prosecutor referral show that policy PDFs alone failed; post-incident case-number mandates and termination recommendations become the accountability path.
Security and privacy
What data, permissions and controls need testing?
Personal stalking via agency ALPR access converts public-safety infrastructure into a victimization tool—illustrating why purpose limitation and credential hygiene are safety controls, not paperwork.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Field officers need fast case-ID entry; IA needs analytical capacity for thousands of questionable searches; victims need clear complaint channels when ALPR is used personally.
Procurement
What should contracts, pricing and exit terms secure?
Multi-year ~$1M/year ALPR contracts should include audit-assistance SLAs, credential controls, and termination/suspension access-kill requirements—price is not the only renewal criterion after criminal misuse.
Operating model
Which teams own the service once it runs?
ALPR becomes a continuous IA audit domain with prosecutor escalation paths, not a set-and-forget investigative convenience.
Publication history
- 2026-09-23Public Safety · Issue 174 resources
Stable resource ID: axios-impd-flock-misuse-charges-20260923