Arizona is ground zero for ELD tampering

The short version

On April 1, 2026, FMCSA began coding ELD tampering at roadside under §395.8(e)(2). Inspection data records it as 8E-HOSPDELDT for property carriers and 8E-HOSPVELDT for passenger carriers; the codebook describes it as "Tampering with an ELD so that the device does not accurately record and retain required data." It targets one thing: drivers and carriers who interfere with the Electronic Logging Device record their truck is required to keep.

Between April 1 and October 19, 2026, our tampering dataset holds 14,911 violation rows on 7,415 inspections of 5,213 carriers. It isn't evenly spread across the country. One state, Arizona, filed 1,940 of the 7,408 state-filed tampering inspections: 26.2%, more than any other state, with a near-total out-of-service rate.

Most cited carriers are small: the median declares 7 power units on its latest MCS-150. A few large fleets carry most of the declared trucks: seven fleets of more than 1,000 power units hold 272,946 of the 420,720 power units the cited carriers declare.

Arizona leads, but no longer alone

Here are the ten states with the most inspections that produced a §395.8(e)(2) tampering violation since April 1, 2026:

Inspections = distinct inspections with at least one tampering row; violations = tampering rows; OOS = inspections whose tampering row carries the out-of-service flag. The 7 federal (non-state) inspections are not in the state rows. Source: FMCSA violation and inspection data (open data via Socrata) in the Carrierintel ELD tampering dataset, 2026-04-01 → 2026-10-19, imported 2026-10-22, computed 2026-10-26.

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, specific code for a manipulated ELD record. It shows up on the carrier's inspection record like any other violation. Based on what we're seeing in the data, inspectors in Arizona and Oregon took to it fast: they filed 258 and 244 of the 867 tampering inspections in April.

One explanation discussed in the industry is that inspectors cross-check ELD records against other movement data, such as license-plate-reader cameras and toll records. Our data cannot confirm it: an inspection record does not say how the inspector found the tampering.

What this means for your fleet

Here is what the numbers very plainly say to anyone running trucks through these states:

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 every night. You can drill down to the individual carrier and see the inspection IDs.

The figures here were computed on 2026-10-26 on a replica of our production database, from the tampering dataset as imported on 2026-10-22 (inspection dates 2026-04-01 through 2026-10-19). They replace the figures first published on June 12, 2026. The SQL is published beside this article in the repository as eld-tampering-surge-2026.sql.

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, fleets that get ahead of it now will look very different in twelve months from fleets that don't.