🚨🚨 It's 9:45 p.m. on a Sunday in Batesville, Arkansas. Officers from the Batesville Police Department are on a call at a home on Buckeye Street. An off-duty BPD officer is there too — and he runs. Not on foot. In his personal vehicle, with his own coworkers now chasing him.
Five miles later, through the Batesville-Moorefield area, a Tactical Vehicle Intervention ends it. The officer is arrested and charged with felony fleeing, aggravated assault, driving while intoxicated, and reckless driving. By morning he's on administrative leave, and two separate investigations are already underway — a criminal one and an internal affairs one, running on parallel tracks, about the same set of facts.
That structure — not the pursuit itself — is the real story here. Because the moment two investigations open on one officer, a single misstep in interview sequencing can compromise both cases at once.
What Actually Happened
According to the Arkansas Department of Public Safety, Batesville PD asked the Arkansas State Police Criminal Investigation Division to handle the criminal side of the case rather than investigate its own officer. BPD is separately conducting its own internal affairs investigation. That's the correct first move — an outside agency for the criminal case, in-house for the administrative one. Most departments get that part right.
What trips departments up is everything that happens next.
Why Garrity Rights Turn This into a Two-Track Problem
Every internal affairs commander knows the name Garrity. Far fewer have a written protocol that actually operationalizes it during a live, high-profile case.
Garrity protections exist because an agency can compel an officer to answer questions administratively — under threat of discipline or termination — but only if that compelled statement can never be used against the officer criminally. Say it out loud to a room of investigators and everyone nods. Build the actual firewall between a criminal interview and a Garrity-compelled administrative interview, in the middle of an active case with prosecutors and the media watching? That's where the nodding stops.
In a case like this one — a criminal pursuit charge running alongside an internal affairs investigation into the same conduct — the two interviews cannot touch. If a criminal investigator gains access to, or even indirect knowledge of, a compelled administrative statement, the defense has a credible argument to suppress evidence or dismiss criminal charges outright. Get the sequencing wrong, and the agency doesn't just risk the discipline case. It risks the criminal case too.
The Practical Decision Tree
This is the piece worth pinning to the wall in every IA office:
Confirm an outside agency owns the criminal investigation. Never the officer's own department.
Physically and procedurally separate the two case files and the two sets of investigators. No shared notes. No shared personnel. No hallway conversations that cross the line.
Sequence the Garrity-compelled interview so it cannot reach the criminal investigators, directly or indirectly.
Document the Garrity warning in writing, signed, before any compelled interview begins — not verbally, not from memory.
Brief the officer's chain of command explicitly on what they can and cannot ask informally while both investigations are pending.
Loop in the prosecutor and agency counsel early to confirm the firewall procedure holds up before either interview happens — not after.
Skip any one of these steps and you haven't saved time. You've created appellate issues.
Where Supervisors Get This Wrong First
Here's the uncomfortable part: the biggest Garrity exposure in a case like this usually doesn't come from IA. It comes from the first-line supervisor, hours before IA is even in the building.
Off-duty conduct cases are especially prone to this because the first people on scene are often coworkers, not investigators. A well-meaning sergeant asks the involved officer "what happened?" before anyone has formalized the Garrity sequence — and that informal conversation can complicate everything that follows.
Supervisors need to know, cold, that the moment an officer is involved in conduct triggering parallel investigations, informal questioning stops. That's not IA's job to explain after the fact. It's a supervisor response competency, and it belongs in every department's first-line supervision training, not just the IA unit's.
Questions IA Commanders Should Consider
Do our first-line supervisors know not to interview an involved officer before IA and legal have structured the Garrity sequence?
Do we have a written firewall protocol separating our criminal and administrative investigators — not just an assumption that "everyone knows better"?
Would our current process survive a suppression motion if this exact scenario happened in our department tomorrow?
Leadership Takeaway
Parallel investigations aren't a scheduling detail or a paperwork formality. They're a structural safeguard — and the sequencing of interviews is where that safeguard either holds or fails. Get it wrong, and you can lose the criminal case, the administrative case, or both, on facts that were never in dispute.
Cases like the Batesville pursuit are exactly why our Garrity and Compelled Statements module in the Internal Affairs Certification course now includes this scenario as a live training example — alongside updated material on parallel investigations, off-duty conduct, and supervisor response. If your agency hasn't stress-tested its Garrity firewall recently, this is the week to do it.
Primary Source
Source: Arkansas Department of Public Safety, "Off-Duty Batesville Officer Arrested Following Pursuit," published July 20, 2026.
