A police officer was pulled over in Wyoming, Ohio, after his wife, or ex-wife, called the cops on him after an argument following their attendance at a Halloween party. The woman told dispatchers she and Michael Matheson, a sergeant with the St. Bernard Police Department, had gotten into an argument. She additionally told them Matheson was leaving in his truck, intoxicated and possibly armed with his duty weapon.
Have you seen these videos where innocent people get pulled over by the police due to a mistaken belief that their car is stolen? Then the police point their firearms at them and treat them like a criminal, before realizing the mistake. That can’t be constitutional, can it?
In April of this year, several people, including one child, were pulled over by the Lehi City Police when an officer said he received an alert and confirmed from dispatch that a vehicle had been stolen after running a license plate. The only problem was, it was a mistake. The vehicle was not stolen. The department has not explained the reason the officer ran their license plate in the first place.
They get pulled over and next thing you know, they see police officers approaching with guns pointed at them. One of the vehicle’s occupants pulled out his cell phone and began recording the incident. One thing led to another. The media began to report on it. KUTV reported that a high-risk traffic stop was performed on the vehicle, because according to the police statement, “routine protocol is to have guns pointed at the vehicle during a high-risk vehicle stop.”
A statement released Monday by the Central Utah Emergency Communications Center revealed that the dispatcher failed to recognize that the flagged information they reported back to the officer was actually a NCIC wanted HIT which was verified only by a partial vehicle identification number taken down in the incident which was never confirmed. The incomplete VIN of the stolen vehicle was identical to a string of seven numbers from the VIN of the vehicle that was wrongly pulled over. So, “the dispatcher failed to see that the actual plate number given was not stolen,” according to the Lehi Police Department statement. They said they have taken corrective action with the dispatcher involved.
So, the vehicle stopped was not stolen, nor was it displaying a stolen plate. The vehicle occupants were released from custody after about 20 minutes and then left the scene in their vehicle. Officials of the Lehi City Police Department called the incident “rare” and “unfortunate.” But this is not an isolated occurrence. This happens all the time.
Aurora, CO: A father records from a distance as cops approach his wife, guns drawn. His three year old child, still in the vehicle. This woman thought it was just going to be a regular traffic stop. But she was wrong. Bodycam footage shows the officers discussing the fact that they’re going to perform a so-called high-risk stop, with guns drawn, as per their department policy. This was apparently the result of officers marking the wrong box on a form. The vehicle had been previously repossessed and then reclaimed. But on the form it was marked stolen by mistake.
But that wasn’t the only time. It happened to another family. A woman with her car full of kids was in a parking lot in Aurora, looking for a nail salon, when all of a sudden police descended on her, allegedly because a license plate reader flagged her car as stolen. The family in the car, kids included, were made to exit the vehicle and lay on the ground.
The car was not stolen. Another mistake. What was the mistake this time? The actual stolen vehicle flagged by the plate reader was a motorcycle with the same number – but from a different state. So yet again: innocent people in a non-stolen car; police make the mistake; yet the innocent people get guns pointed at them. Why? They say it’s their policy. Officer safety, of course.
Raymore, MO: In August of 2022, a Raymore, Missouri couple was held at gunpoint by the Raymore Police. The video went viral first on Tik Tok and then hit the TV news.
So this was another mistake situation. Their son’s truck had been stolen just days before. But then it was recovered. The police then failed to take the truck off the stolen vehicle registry. So they got the “high risk stop” or “felony stop” treatment. Like the other victims, they were pissed and no longer back the blue types. This couple’s son is actually an attorney and he’s apparently pissed too – and summed it up well.
Fairfax, VA: In October of 2022, a mom and her 5 year old and 1 year old daughters were on their way to Walmart in Fairfax County, Virginia when they noticed a police car trailing them. Next thing you know, the vehicle pulled up beside them, then the police car rammed them, the police car striking their car head-on. Guns were drawn and she was handcuffed and her kids were put in a police car. Police later just said she ended up not being the person they were looking for. Another mistake. Apparently the vehicle was listed as “wanted.” But it wasn’t.
Norwalk, CT: It can even happen to the General Manager of the Yankees, Brian Cashman. Same old story. His Jeep was stolen and then recovered. But government employees did what government employees do. They just kept the stolen classification and then gave him the “high risk stop” treatment at gunpoint. At least for a few minutes before recognizing him and kissing his ass.
This is obviously far from an isolated incident. This apparently happens all the time. There are more examples out there. What do they all have in common? Innocent people – could be your father, mother, sister, wife – all held at gunpoint by your government agents, not in response to anything they did, nor any threat presented by them. Rather, it’s just their policy.
What happened to protect and serve? These are the people police officers have sworn to protect. All to often, those individuals are victimized in the interests of officer safety. In all of these incidents, though the police will apologize, they say it’s policy. Because it’s a “high risk” or “felony” stop. But is that enough to aim a gun at someone? I argue that it’s not.
What’s the law? Here, with Lehi, Utah being in the 10th Circuit, we have two real cases that happened that the courts have contrasted:
In Maresca v. Barnalillo County (10th. Cir. 2015), officers at gunpoint ordered a family out of a suspected stolen truck. The officers forced the family of two parents and three minor children to exit the vehicle and lie face down on the highway. The officers first removed the parents, who pleaded with the officers that there had been a mistake, that they should check the father’s license, and that there were children and a dog in the car. Even though one officer on the scene considered the situation “a little weird,” the officers ignored the parents’ repeated pleas to recheck whether the vehicle was in fact stolen and proceeded to order the three children out one-by-one.
The officers then handcuffed each family member (except the youngest) and locked them in separate patrol cars, keeping their weapons trained on the family throughout despite full compliance with their orders. The court found the forceful measures unnecessary and unconstitutional, primarily because the officers had no reason to believe the family possessed firearms.
Contrast that with a more recent case, Hemry v. Ross (10th Cir. 2023), where it was reported to the officers making the stop that the driver was a fugitive murderer. The court noted that in the case of a suspected stolen car, there’s nothing specific indicating that the car’s occupant may be armed. But where the driver is believed to be an actual murderer, officers acted reasonable in holding the man at gunpoint during the stop.
The point is, without more, police officers should not be aiming firearms at people. Reasonableness is the key. Aiming guns based on clerical entries and government policy is rarely going to be reasonable. Doing so should be based on actual perceived threats presented by the persons with whom they’re dealing.