Breathalyzer Manufacturer Under Criminal Investigation For Falsifying Maintenance Records And Calibration Results
from the watched-over-by-machines-of-questionable-aptitude dept
In 2018, a report came out that added even more doubt as to the reliability of breathalyzers. A number of factors -- including incorrect calibrations and ambient air temperature -- could turn innocent breath into guilty breath. Cops value breathalyzers since they're easy to deploy and don't have the warrant impediments of blood tests. But they're often relying on faulty equipment.
The 2018 discoveries were reaffirmed in 2019 when a New York Times investigation uncovered more problems with breathalyzers. Equipment used in the field was rarely recalibrated and active chemical agents rarely replaced. One breathalyzer used by Michigan police was found to have rats nesting inside of it.
Faulty equipment is only one of the problems. The bigger problem is that it's almost impossible to challenge in court. The private companies behind breathalyzer equipment have inserted themselves into court proceedings, claiming any examination of devices and source code could result in the exposure of proprietary information that (they imagine) could harm their market position and future sales.
Manufacturers are partially correct, but not for the reasons they've stated. The more these devices and their deployments are examined, the less they seem to be a gold standard for detecting intoxication. And now it's the producers of this equipment that might be facing criminal charges, as Blake Montgomery reports for The Daily Beast. (h/t BentFranklin via the Techdirt chat window)
A major breathalyzer manufacturer is under criminal investigation for possible forgery. Police forces nationwide have been using the same company’s machines to turn alleged drink-drivers into convicted ones—seizing licenses, imposing fines, and, in some cases, imprisoning people.
The manufacturer is Intoximeters, which produces the Datamaster DMT used by the Michigan State Police. An investigation into the vendor uncovered a great deal of concerning misconduct, according to this report by The Detroit News.
State police director Col. Joseph Gasper said in a statement his department also has launched a criminal investigation into the alleged fraud by the St. Louis, Missouri vendor, Intoximeters, Inc.
"Based on new information learned over the weekend, the Michigan State Police ... is aggressively investigating potential fraud committed by contract employees of Datamaster vendor, Intoximeters, and also moving today to take all 203 Datamaster DMT evidential breath alcohol testing instruments out of service until MSP can inspect and verify each instrument to ensure it is properly calibrated," Gasper said.
State police will now have to use blood draws to obtain evidence of intoxication. This reverses the MSP's first response, which was to perform recalibration of all the devices itself, rather than allow the apparently-untrustworthy employees of Intoximeters to do it.
This will likely trickle down to other Michigan law enforcement agencies currently using Intoximeters equipment. And it will trickle down to the state's courtrooms where defense attorneys are expected to start filing challenges to current prosecutions and past convictions that relied on evidence obtained with these devices.
This may mean Intoximeters may finally have to divulge information it has so far successfully managed to keep out of court. This sort of reasoning isn't going to fly if it's proven the company's employees falsified records.
[T]he company has resisted at least three Minnesota court mandates that police furnish the source code of its breathalyzer software to defendants, court records and interviews show. Instead of cooperating, Intoximeters has submitted documents saying it is open to police doing so—contingent on various conditions—and then opposed requests to actually follow through.
It's an intentionally-designed catch-22. Law enforcement agencies can hand over the source code to courts, except they really can't because their contracts with Intoximeter make it clear the source code belongs to the company, not the cop shop. The cops can't turn over what they don't own. And even when a court order directly targets the manufacturer, the Missouri-located company can dodge compliance --like it has in Minnesota -- by being out of the court's reach due to jurisdictional limits.
Preventing successful evidence challenges in court has allowed Intoximeters to operate with almost no accountability. And when that happens, things like the malfeasance currently under criminal investigation is pretty much guaranteed to follow. Every device maker bills its product as the evidentiary gold standard. But, as multiple investigations have shown, this standard is more tin than gold.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: accuracy, breathalyzer, calibration, falsifying records
Reader Comments
Subscribe: RSS
View by: Time | Thread
'... what evidence?'
And even when a court order directly targets the manufacturer, the Missouri-located company can dodge compliance --like it has in Minnesota -- by being out of the court's reach due to jurisdictional limits.
It strikes me that there's likely a very easy way to force the issue, and it's one that should have been applied from the very start:
If the defense can't examine and verify the evidence, it's not allowed in court.
Intoximeters(or any other company) wants to play keep-away then great, none of the evidence from any of their devices are admissible, such that police are just wasting their time if they try to introduce such evidence in court, and if they want admissible evidence either the company caves or the police find one with less restrictive rules.
A judge might not be able to force compliance due to jurisdictional limitations, but I'd be very surprised if they couldn't bar evidence under the standard that if the defense has no way to verify it to make sure it's accurate and/or collected legally it's not allowed.
[ link to this | view in thread ]
Re: '... what evidence?'
completely right, i dont understand how a court could in good conscience say well we can't get any details about this evidence so lets just assume that it is 100% correct and move on.
[ link to this | view in thread ]
Re: '... what evidence?'
The next step would be to forbid collection of "evidence" that's known to be inadmissible—i.e., establish a warrant requirement and forbid issuance of warrants not likely to result in usable evidence.
[ link to this | view in thread ]
I thought..
That to have a copyright and hold it, they had to Write it down and give a copy to the CR office?
And any changes had to be added to the CR.
This would be the only way to Protect your code from being copied Randomly, by another company.
Otherwise you could State that any other company was copying your CR. But why do that, when you would both have to SHOW the Programming.
But general Maintenance?? Cleaning the Machines?>? Updating the software??
And you thought general Forensics was bad.
[ link to this | view in thread ]
Re: '... what evidence?'
Exactly, I don't remember proprietary information or industrial secrets being mentioned anywhere in the Constitution, whereas being able to confront ones witnesses is.
[ link to this | view in thread ]
Re: '... what evidence?'
Courts don't want to bar evidence. DUIs are their meat and potatoes!
[ link to this | view in thread ]
Re: I thought..
Not since 1976.
[ link to this | view in thread ]
Opulence via Arcane Magicks
"Every device maker bills its product as the evidentiary gold standard."
The Alchemist's Dream Come True - turning stupidity into gold...stupidity's WAY more common than lead.
[ link to this | view in thread ]
Re: Re: '... what evidence?'
and the next step is to not allow any evidence and say it was a trial.
[ link to this | view in thread ]
How drunk were those rats?
[ link to this | view in thread ]
Re: '... what evidence?'
If I recall, MAD in the 90s put a stop to this very line of thought by passing a bunch of "Tough on DWI" laws. When people pushed back in court, MAD went even more crazy and passed laws that said the machines were true regardless of anything else.
More fun a lot of DWI laws kick in at accusation instead of conviction.
[ link to this | view in thread ]
Re: Re: '... what evidence?'
Nothin personal, juz bizniss
[ link to this | view in thread ]
Re:
They were drunk enough to be dead for a herd of elephants, according to the breathylizer.
[ link to this | view in thread ]
Re:
'... I know when your PC starts squeaking that's a good indicator that you need to replace the cooling fans, but what does it mean when the breathalyzer starts making that noise?'
[ link to this | view in thread ]
Re: Re: I thought..
And no roof you created anything..Cool..
[ link to this | view in thread ]
Re: Re:
That its going to squeal on you!
[ link to this | view in thread ]
just let someone else blow for you -- DUH!
(yez, im drunc)
[ link to this | view in thread ]
Re: Re: Re: I thought..
No proof, you created anything.. cool.
[ link to this | view in thread ]
Re: Re: I thought..
Well, you still do in order to sue for infringement.
[ link to this | view in thread ]