FRONTLINEPRIVACY
Stalking

Joplin officer dismissed in 2026 for running a single license plate 395 times in tracking system

2026-01-12·Joplin, Missouri

A Joplin, Missouri police officer was dismissed in January 2026 after allegedly running one specific license plate 395 times through a license plate reader tracking system. The misuse pattern resembled stalking via department databases.

What happened

KCTV5 reported in January 2026 that a Joplin, Missouri police officer was no longer employed by the department after allegedly misusing a license plate reader tracking system. According to the reporting, the officer ran the same license plate 395 times. The pattern of repeated lookups against a single plate is consistent with personal use of department tooling rather than legitimate investigative work, and the department took employment action.

What happened

On January 12, 2026, KCTV5 reported that a Joplin, Missouri police officer was no longer employed after allegedly misusing the department's license plate reader tracking system. According to the reporting, the officer queried one specific license plate 395 times.

License plate reader systems and similar tools log queries. The unusual frequency on a single plate is the pattern that gets flagged in audits. The department took employment action; KCTV5's coverage didn't name the officer or the plate's registered owner.

How it started

License plate reader systems were built to support active investigations. They are also one of the more powerful surveillance tools an officer has personal access to. Any system that logs movement to a plate level can be used to map a person's daily routine, their home, where their kids go to school, where they work.

The 395-query pattern is not investigative. The Joplin department's response, separation, suggests they reached the same conclusion.

What this means for you

Most cops we work with are worried about a stalker, an estranged partner, or an angry subject pulling their address off Whitepages. The Joplin case is a reminder that the same risk profile exists inside agencies. The mitigation on the inside is audit trails and policy. The mitigation on the outside is removing your address from the broker layer where anyone can pull it without leaving a log.

Missouri's Safe at Home program (Mo. Rev. Stat. § 589.660) is built around domestic violence and stalking victims, not officers as a class. There is no Missouri Daniel's Law analog. We handle the broker layer.


Editorial rules: Only public, already-reported incidents. Never name a non-public victim. Always end with the prevention takeaway tied to our service. Cite at minimum one public source per claim.

What would have prevented this

Most doxxing stories are about civilians using broker pages to find officers. This one is about an officer using department tools the same way. Both ends produce the same risk: someone's address and movements are tracked without their knowledge. Missouri has no [Daniel's Law](/laws/daniels-law) analog. Safe at Home (Mo. Rev. Stat. § 589.660) is victim-focused. Audit trails inside agencies catch some misuse after the fact. Broker removal closes off one of the easier external paths someone might use to do the same thing.

Public sources