Arizona just became ground zero for ELD tampering

The short version

On April 1, 2026, FMCSA officially activated a new violation code: 395.8(e)(2) — HOSPDELDT, a.k.a. "False ELD record of duty status (driver)." It targets one thing: drivers and carriers who edit, falsify, or otherwise tamper with the Electronic Logging Device data their truck is required to keep.

In just over two months, our pipeline has pulled 3,715 violation rows across 1,893 inspections tied to 1,558 unique carriers. And it isn't evenly spread across the country. One state — Arizona — accounts for nearly 17% of every tampering inspection nationwide, with a near-total Out-of-Service rate.

The 1,558 carriers cited operate roughly 52,000 drivers and 50,000 power units combined. This isn't an outlier story — it's a structural pattern.

Arizona is the story

Here's the state-by-state breakdown of every inspection that produced a §395.8(e)(2) tampering violation since April 1:

Source: FMCSA datasets (violations joined to inspections). Fetched live; counts move as new inspections close out.

A few things jump out:

Why this is happening now

The §395.8(e)(2) tampering code didn't exist before April 1. That doesn't mean tampering didn't exist — it means inspectors had no clean way to cite it. The closest tools were generic "false log" violations under 395.8 sub-parts, which fold into a much broader bucket and lose visibility.

What changed in April is that FMCSA gave roadside inspectors a single, surgical code: the truck has an ELD, the ELD record is provably manipulated, write 395.8(e)(2). It shows up immediately on the carrier's CSA file. And — based on what we're seeing in the data — inspectors in Arizona and Oregon took to it fast.

There's also a strong signal that this isn't being caught by random luck at the scale. A 90% hit-rate doesn't happen by accident. The most plausible explanation, and one widely discussed in the industry right now, is that inspection stations are cross-checking ELD records against external movement data — Automatic License Plate Reader (ALPR) cameras at weigh stations and along the interstate, DOT toll-tag pings, and state-level highway camera networks. If the ELD says the driver was off-duty in Flagstaff at 14:00 but an ALPR camera tagged the same plate rolling through Kingman at 13:45, that's a provable falsified log before the truck even pulls onto the scale. Arizona and Oregon both run dense ALPR coverage on their primary freight corridors, which lines up neatly with where the violations are clustering.

What this means for your fleet

We're a data aggregator. We don't write enforcement policy and we don't sell ELDs. But here is what the numbers very plainly say to anyone running trucks through the Southwest right now:

How we know this

Every number in this article comes from public FMCSA data. We don't editorialize the count — when you reload our ELD tampering dashboard the numbers are recomputed from the same datasets, in real time. You can drill down to the individual carrier and see the inspection IDs.

That's the whole point of what we do here: turn the firehose of FMCSA data into something a carrier can actually look at and make a decision from. If §395.8(e)(2) is going to be the next big CSA narrative — and the early data says it is — fleets that get ahead of it now will look very different in twelve months from fleets that don't.