44% of today's logbook violations come from rules that didn't exist before ELDs

Data report · Carrierintel data desk · 916,533 Part 395 violations

Electronic Logging Devices were introduced to solve a real problem. Paper logs were difficult to verify, easy to falsify and dependent on drivers manually recording their Hours of Service. The ELD changed that: vehicle movement is captured automatically, duty-status changes are timestamped precisely, logs are standardized, and inspectors receive electronic records instead of interpreting handwritten grids.

From an enforcement perspective, that was a major shift toward more accurate and auditable records. But our data shows that digitizing the logbook also created something else: an entirely new category of violations that simply did not exist in the paper-log environment.

We analyzed 916,533 Part 395 violations recorded between September 1, 2024 and August 31, 2026. Of those, 403,368 — 44.0% — came from ELD-specific sections introduced with the modern electronic logging framework.

These violations include requirements involving:

These requirements either did not exist in the paper-log era or did not exist as standalone citation categories in the AOBRD era. Some had partial analogues: §395.15 required a working device and an instruction sheet, and special driving categories were annotated by hand on paper. The accurate framing is "impossible to cite on a paper log, and not a standalone code under AOBRD" — not "impossible in principle."

That does not mean these violations are invalid. It does not mean paper logs were better. And it does not mean electronic logging failed. But it does show that the transition from paper to ELDs did more than digitize the same compliance system. It expanded the compliance system itself.

Nearly half of logbook violations are now device-era violations

Out of 916,533 Part 395 violations in the 24-month window, 403,368 (44.0%) belonged to device-era ELD categories, spread across 76,972 carriers. Legacy HOS violations still made up the majority at 56.0%. But almost half of all logbook-related citations in the window came from requirements that depend on the existence of an electronic logging device.

One important caveat that the raw share hides: device-era codes carry very little weight. They account for 17.1% of Part 395 CSA points (544,384 of 3,187,957) and an out-of-service rate of 0.10% — 391 citations out of 403,368 — against 30.8% for legacy HOS violations. Drivers are almost never removed from service for them, but they fill the Hours-of-Service BASIC with small entries.

The modern logbook compliance environment no longer measures only how long the driver drove, whether he received enough rest, whether he exceeded the 11-hour limit or the 14-hour window, and whether the log was truthful. It now also measures whether the device was mounted correctly, whether the driver certified the log, whether the trailer and shipping-document numbers were entered, whether unassigned driving was resolved, whether required instructions were available, whether the ELD could transfer records, and whether the device was operating correctly.

The logbook is no longer only a record of working time. It is also a regulated software workflow.

What drivers are actually being cited for

Looking at the largest device-era sections makes this clearer.

Part 395 violations by device-era section, September 1, 2024 – August 31, 2026. "Carriers" is the number of distinct USDOT numbers cited under that section; a carrier cited under two sections is counted in both.

The individual codes provide an even more practical picture.

Highlighted rows are device-era codes whose FMCSA severity weight is above 1. Ten device-era codes carry such a weight; together they account for 46,736 violations — 11.6% of the device-era total — but 34.5% of its CSA points. Those are the technical ELD citations worth flagging in a score; the rest are background noise. Weights are FMCSA's published SMS input-violation weights, applied to our own counts.

These are all legitimate compliance requirements. But they also show how far modern logbook compliance has expanded beyond the original question of how long a driver worked or rested.

The ELD did more than replace paper

It is easy to describe the ELD as a digital version of the paper logbook. Technically, that is not what happened. A modern electronic log depends on an entire chain of technology: truck ECM → ELD hardware → vehicle connection → mobile application → server → output file → transfer system → eRODS. Every layer improves visibility. Every layer can also create another point of failure.

Paper logs could be falsified. But paper could not:

Those categories only became possible once the recording system itself became part of the regulation. Today's logbook compliance measures two things at the same time: what the driver did, and whether the technology documenting what the driver did was used exactly as required.

A driver can follow the HOS rule and still have an ELD violation

Consider a driver who drove within his legal hours, received the required rest, did not falsify his log and did not operate while fatigued. That driver can still receive an ELD-related violation. The device may not be mounted correctly. He may have forgotten to certify yesterday's records. A trailer number may be missing. The data-transfer procedure may fail. Required instructions may not be available. An unassigned-driving event may remain unresolved.

The problem is real from a regulatory perspective. But it is different from exceeding the driving limit or operating without enough rest — and that distinction did not exist to the same degree in the paper-log environment. The technology used to document compliance has itself become a source of compliance exposure.

More precision creates more events

A handwritten logbook was inherently approximate. The ELD is designed to capture actual electronic events — one of its primary advantages. But greater precision can also turn very small operational events into meaningful changes in the electronic log.

Consider a driver who has been sleeping for six hours at a truck stop. Another truck needs to pass. The driver wakes up, moves his vehicle a short distance, parks again and returns to the sleeper berth. From a human-rest perspective, the interruption is minor. From the ELD's perspective, the truck moved — and an automatically recorded Driving event can now appear inside what the driver expected to become one continuous rest period.

The record is more precise. The operational consequence of that precision can be significant.

The logbook became a software product

Drivers are no longer interacting with one universal format. The Hours-of-Service regulation is federal. The ELD interface is not. Different providers implement the same required functions in different ways. One application may make Personal Conveyance easy to find; another may place it deeper inside the interface. One system may make unidentified driving obvious; another may use a less intuitive workflow. The same differences exist around Yard Move, log certification, inspection mode, edit requests, malfunction notifications, trailer information, shipping documents, data transfer and annotations.

The underlying regulation remains the same. The practical process of complying with it can change significantly from one ELD provider to another.

Change companies, learn the logbook again

Under paper logs, the basic interface was effectively universal. A driver changing companies did not have to relearn how a logbook worked. With ELDs, a driver moving from one fleet to another may need to relearn where Personal Conveyance is located, how Yard Move is activated, how unidentified driving is handled, how edits appear, how logs are certified, how inspection mode works, how records are transferred, what different warning icons mean, and how the application behaves when connectivity is lost.

The regulation did not change. The software did.

Our dataset does not prove that switching ELD providers causes more violations. But it creates a reasonable hypothesis: some ELD-related violations may be influenced not only by driver behavior, but also by software usability, training and familiarity with a specific platform.

ELD violations are not distributed evenly across the country

One of the most striking findings in the data is geographical. Technical ELD violation rates differ dramatically between states, per 1,000 inspections:

Device-era Part 395 violations per 1,000 roadside inspections by inspection state, September 1, 2024 – August 31, 2026. The denominator is every inspection recorded in that state, not only Part 395 ones. Federal (non-state) inspections are excluded from the ranking; they add 189,649 inspections and 2,445 device-era citations nationally.

Arizona writes about 97 times as many device-era citations per inspection as New Jersey (301.7 against 3.1 per 1,000). That pair is the comparison we name, not the extreme: the lowest state that cites at all is Delaware, at 1.8 per 1,000 — 30 device-era citations on 16,740 inspections — and the District of Columbia is lower still, with 7 citations on 7,788 inspections (0.9). Hawaii recorded none at all — zero device-era citations on 4,758 inspections in 24 months — and Puerto Rico, Guam and the US Virgin Islands also recorded zero. That is one of the clearest signals in the dataset that ELD citation volume is influenced by more than carrier behavior alone. Inspection practices matter.

The same carrier can accumulate a different record depending on where it runs

Imagine two similar carriers: same fleet size, same type of freight, same internal compliance practices, same ELD. One operates heavily through Arizona, Iowa and Georgia. The other operates primarily through New Jersey and Maryland. If inspectors in one group of states routinely check ELD mounting, manuals, certification and backup RODS while inspectors in another group rarely cite those issues, the two carriers accumulate very different violation histories.

That does not mean one fleet is 97 times safer than the other. Part of the difference reflects enforcement intensity and inspection style. We therefore treat geography as an important factor when interpreting ELD-related compliance data. A technical ELD citation is not only a carrier signal — in some cases it is also an enforcement-policy signal.

Arizona and Alabama are not the whole story

The geography of technical ELD violations is not identical to the geography of strict ELD tampering enforcement. Arizona and Alabama rank highly in both. But Iowa, Georgia, Indiana and Kansas also show very high technical ELD citation rates without showing the same level of strict tampering enforcement.

That suggests different states emphasize different parts of ELD compliance. Some appear to focus heavily on the integrity of the underlying log. Others routinely inspect manuals, mounting, certification, transfer procedures and other technical requirements. The national ELD compliance picture is partly a collection of different state-level enforcement practices.

ELD-related violations are still growing

The absolute number of device-era violations increased year over year: 186,910 in the first twelve months of the window against 216,458 in the second. Measured per inspection, device-era violations grew by 9.1% — from 66.50 to 72.54 per 1,000 inspections. At the same time, their share of all Part 395 violations declined from 45.5% to 42.8%, largely because stricter HOS and tampering categories grew faster.

Only complete quarters are shown: the window opens on September 1, 2024 and closes on August 31, 2026, so the two quarters at its edges are partial. Inspection records also reach FMCSA's public dataset days or weeks after the inspection date, which understates the most recent period. That delay is in the FMCSA data itself; Carrierintel checks FMCSA for new inspections every hour.

This matters because it suggests technical ELD citations are not simply an early-adoption issue. The industry has been operating under mandatory ELD rules for years, yet device-era violations remain a very large part of modern logbook enforcement.

This is not just one kind of problem

The broad category of "ELD-related violations" contains several very different problems.

Grouping all of them together under one simple idea of "logbook problems" hides important differences.

Some violations may be created by complexity rather than intent

A modern driver must understand the HOS rule, the carrier's internal procedures, the ELD provider's interface, the specific device configuration, the inspection-transfer process, and the behavior of the application when something goes wrong. For a driver switching companies, part of that learning process begins again. For a small fleet, the person responsible for dispatch or safety may also be the person troubleshooting the ELD. That creates opportunities for mistakes that have little to do with intentional falsification.

The data does not allow us to say exactly what percentage of technical ELD violations comes from usability, training, technical failure or deliberate noncompliance. But the structure of the violations suggests all of these factors exist within the same dataset.

What 44% actually tells us

The most important conclusion is not that ELDs created "bad" violations. It is that the meaning of logbook compliance changed. Before electronic logging, compliance was primarily about hours, rest and the accuracy of the driver's record. Today it also includes software, hardware, workflow, certification, mounting, data transfer, documentation and electronic event management.

Across the 24-month window, 916,533 Part 395 violations were recorded, and 403,368 — 44.0% — belonged to device-era categories. Depending on the state, the frequency of those technical ELD citations differed by about 97 times between Arizona and New Jersey, by more again against Delaware's 1.8 per 1,000, and in Hawaii it was zero.

The modern driver is not simply complying with Hours of Service. The driver is complying with Hours of Service through a complex electronic system. And the performance of that system — together with driver familiarity, carrier training, software design and state enforcement practices — is now part of the compliance outcome.

The logbook became more accurate — and more complicated

Electronic logging made roadside records more detailed, standardized and auditable. It also transformed the logbook from a relatively simple document into a regulated technology platform. That transformation created new visibility, new workflows, new responsibilities — and hundreds of thousands of violation opportunities that did not exist as standalone citations in the paper-log era.

The data does not tell us that these requirements are unnecessary. It tells us something more basic: modern logbook compliance is no longer only about whether the driver had enough hours. It is also about whether the driver, the carrier and the ELD successfully managed the technology used to document those hours. In the 24 months to August 31, 2026, that technology-related layer accounted for 44% of all Part 395 violations in our dataset.

Methodology: all US roadside inspection violations coded under 49 CFR Part 395 with an inspection date between September 1, 2024 and August 31, 2026. Device-era = sections 395.20 through 395.34. Rates per 1,000 inspections use the 5,794,839 inspections recorded in the same window. CSA points are our violation counts multiplied by FMCSA's published SMS severity weights for the Hours-of-Service Compliance BASIC, before time weighting; the weight is available for 96.1% of the Part 395 rows and 99.9% of the device-era rows. Source: Carrierintel Part 395 dataset (FMCSA open data via Socrata), 2024-09-01 → 2026-08-31, computed 2026-09-13.