Indiana Deputy Faces 441 Charges After Allegedly Using Flock Cameras to Track Wife, Ex-Girlfriend and Others

Investigators say Hancock County sheriff’s deputy conducted thousands of license-plate searches, many while off duty

GREENFIELD, Ind. — A Hancock County sheriff’s deputy is facing a staggering 441 criminal charges after investigators say he repeatedly used law-enforcement license-plate cameras for personal purposes, allegedly tracking his wife, a man she had known years earlier, a former girlfriend and members of her family.

James Heneghan, 33, was arrested Thursday after Indiana State Police served warrants stemming from seven criminal cases.

He faces 220 counts of fraud, 220 counts of official misconduct and one count of intimidation. The fraud charges are Class A misdemeanors, while official misconduct and intimidation are Level 6 felonies.

The allegations raise serious questions not only about the conduct of one law-enforcement officer, but also about who can access powerful automated license-plate-reader systems and what safeguards exist to prevent those systems from being used for personal surveillance.

Thousands of Flock Searches

According to charging documents described in local reporting, investigators examined Heneghan's use of Flock Safety's automated license-plate-reader database and found nearly 6,200 searches between December 2024 and March 2026.

Many allegedly occurred when Heneghan was not working.

Investigators reported thousands of searches while he was off duty, along with hundreds more while records showed him using paid time off or compensatory time. Authorities concluded that roughly 65 percent of the searches were conducted while Heneghan was off the clock.

Indiana State Police said an extensive audit uncovered unauthorized searches involving people Heneghan knew.

Man Connected to His Wife Allegedly Searched Hundreds of Times

One of the most striking allegations involves a man who had known Heneghan's wife years earlier.

Charging documents reportedly show that Heneghan searched a license plate registered to the man 922 times during May 2025, August 2025 and February 2026.

In February alone, investigators say Heneghan checked the man's vehicle location 213 times.

The stated justification for the searches was reportedly a DUI-related "traffic study."

But investigators said the man had never been charged with operating a vehicle while intoxicated and that they could find no Hancock County investigation involving him.

The man told investigators he did not know Heneghan and did not understand why a sheriff's deputy would repeatedly search for his vehicle.

His Wife's Vehicle Was Allegedly Tracked Too

Investigators say Heneghan also repeatedly searched for his own wife's vehicle.

Her license plate was allegedly searched 901 times during the same three periods.

In February 2026 alone, investigators say her location was checked 225 times, again with a DUI-related traffic study reportedly given as the justification.

Investigators said they found no record that she had been charged with OWI.

If the allegations are proven, the searches demonstrate how a technology designed to assist law enforcement can potentially provide someone with a detailed picture of another person's movements.

Former Girlfriend and Her Husband Also Searched

The investigation expanded to a woman who told authorities she had dated Heneghan more than a decade ago.

Investigators say Heneghan searched vehicles belonging to the woman and her husband approximately 226 times over a 441-day period.

The majority of those searches allegedly occurred while Heneghan was off duty.

Authorities said they found no criminal cases or active sheriff's department investigations involving either person that would explain the searches.

The woman told investigators she had not had personal contact with Heneghan in approximately 11 years, except for an occasion when she said someone contacted her through Snapchat using a false name.

She said she stopped communicating after realizing the person was Heneghan.

Traffic Stop Raises More Questions

The allegations involving the former girlfriend's family did not end with database searches.

Charging documents describe a January 2026 encounter involving the couple's daughter.

The daughter told her parents that Heneghan allegedly drove closely behind her, repeatedly accelerated and slowed down and made her feel pressured to increase her speed. He then pulled her over for speeding.

Investigators discovered that Heneghan had allegedly searched that vehicle through Flock nine times before the traffic stop.

The allegation could become an important part of the case because it potentially connects database searches with an actual law-enforcement encounter involving someone related to a person Heneghan allegedly monitored.

Threatening Text Leads to Intimidation Charge

The investigation initially began with an allegation unrelated to the Flock cameras.

Indiana State Police said it was asked in April to investigate threatening text messages allegedly sent by Heneghan.

According to an affidavit, Heneghan became involved in an angry exchange with a relative by marriage and allegedly sent a message warning that the relative's children would "suffer."

The recipient told investigators the message caused him to fear retaliation against his children.

That allegation resulted in the single Level 6 felony intimidation charge.

As investigators examined the intimidation complaint, Indiana State Police says detectives discovered evidence pointing toward improper use of automatic license-plate-reading cameras. That discovery ultimately led to the broader audit of Heneghan's database activity. 

A Much Bigger Question About Flock Cameras

The Heneghan case reaches beyond one deputy.

Flock cameras automatically capture license plates and other vehicle information as cars pass through their field of view. Law-enforcement agencies can search that information during investigations.

That capability can be enormously useful when police are searching for stolen vehicles, suspects or missing people.

But the allegations against Heneghan illustrate the other side of that power: What happens when someone with legitimate access allegedly uses the system for illegitimate purposes?

The central issue is not simply whether cameras exist in public places. It is whether a government employee can repeatedly query a database to reconstruct someone's movements without a legitimate investigative reason — and whether existing auditing systems can detect that behavior quickly enough.

According to Indiana State Police, the alleged unauthorized searches were discovered only after investigators began examining a separate intimidation complaint. 

That raises an unavoidable question for every law-enforcement agency using automated license-plate readers:

Who is watching the people doing the watching?

Deputy on Unpaid Leave

The Hancock County Sheriff's Office placed Heneghan on administrative leave after the allegations surfaced. Local reporting says he is now on administrative leave without pay while the department's merit board considers his termination. 

Indiana State Police arrested Heneghan Thursday morning and booked him into the Hancock County Jail. 

The sheer number of charges makes the case extraordinary, but the larger significance may ultimately be what it reveals about access to increasingly powerful surveillance technology.

License-plate-reader databases can give police an investigative tool that officers of an earlier generation could scarcely have imagined. But power that can be used to locate suspects can potentially be misused to locate spouses, former romantic partners, acquaintances or virtually anyone else whose vehicle appears in the system.

Technology can make surveillance easier.

Accountability has to keep pace with it.

Heneghan is accused, not convicted. The charges and descriptions of his conduct are allegations contained in investigative and charging records, and he is presumed innocent unless proven guilty in court.

Flock Cameras May Be Leaving Some Cities. That Does Not Mean Surveillance Is.

 

Public outrage has finally forced some cities to reconsider Flock Safety license-plate reader cameras. The reason is simple: people learned how easily a system sold as “public safety” can become a tool for tracking ordinary residents.

In Denver, records showed more than 1,400 searches tied to immigration enforcement concerns. That raised serious questions about whether local camera networks were being used, directly or indirectly, to assist federal immigration investigations. The issue was not merely the cameras themselves. It was who could search the data, why they were searching it, and whether the public had any meaningful say in the matter. 

But communities should not assume that canceling a Flock contract ends the surveillance debate.

A new generation of equipment is arriving under a different corporate name: Axon, the company already known to most Americans for Tasers, police body cameras, vehicle cameras and digital evidence storage. Axon now markets systems designed to combine license-plate recognition, live video feeds and camera networks into a single police-viewing platform.

One product, Axon Lightpost, is designed to use existing streetlight infrastructure. According to Axon’s own materials, it can provide automated license-plate recognition and live video streaming while drawing power from a streetlight. Axon says its plate-reading technology can capture plates at speeds up to roughly 155 mph and at distances up to 328 feet in daylight. 

That should prompt a basic question in every city: How many streetlights could quietly become surveillance points before residents are even told?

The concern is not that every camera is automatically unlawful or that police should be denied tools to solve violent crime. Cameras can help investigate shootings, locate missing people and identify stolen vehicles. The concern is that the same systems can create an always-on record of where innocent people travel, who they visit, what neighborhoods they enter and how often they go there.

Axon’s Fusus platform is central to that concern. It is designed to bring feeds from public cameras and participating private security cameras into a real-time operational view for police. In other words, the surveillance system is no longer just a pole-mounted camera. It can become an integrated network connecting license-plate readers, live video, body-camera footage, dispatch information and privately owned cameras. 

That is why the public discussion cannot stop at the name “Flock.”

A city may remove one vendor and still approve another system that gathers similar information, expands the number of cameras, or links police to a wider network of video sources. Longmont, Colorado, for example, moved away from Flock and approved a path toward Axon license-plate readers, though the Axon contract was not yet finalized at the time of reporting. 

Axon’s growing reach extends beyond cameras. The company announced a $625 million acquisition of Carbyne, a cloud-based 911 technology company. The deal is intended to connect emergency calls, dispatch systems, video and other public-safety information within Axon’s broader ecosystem. 

Carbyne’s past investors and founders have drawn scrutiny, including reporting on former Israeli Prime Minister Ehud Barak’s involvement and Jeffrey Epstein’s undisclosed investment through that relationship. But those historical connections, while worth transparent reporting and public scrutiny, are not proof that any American city’s 911 system is being operated for a foreign government or intelligence service. That claim requires evidence, not insinuation.

The real issue is already serious enough without exaggeration: private companies are building deeply connected public-safety systems that can collect, store, search and combine enormous amounts of data about the public.

Before any city signs an Axon, Fusus, Real-Time Crime Center or similar contract, residents deserve clear answers:

• What data will be collected, and for how long?

• Who can search it?

• Can outside agencies access it?

• Can it be used for immigration enforcement?

• Are private-camera owners voluntarily participating?

• Is a warrant required for certain searches?

• Will audit logs be public?

• Who independently checks for abuse?

A company name change is not a privacy policy. A new camera design is not accountability. And “public safety modernization” should never be a phrase used to avoid public oversight.

The question every resident should ask is not simply, “Does my city have Flock cameras?”

It is: “What surveillance system replaced them, who controls it, and what protections exist for the people being watched?”