FMCSA 2026 Trucking Enforcement Changes

What Changed on July 9, 2026

FMCSA’s July 9 notice announced the removal of 10 additional ELDs. The agency’s live site identifies them as Ontime Logs iosix, LAST MINUTE ELD, Porter ELD, Zee HOS Compliance, EV ELD IOSIX, Light and Travel ELD, PREMIERRIDE LOGS, 2BRO ELD, 305 ELD, and TT ELD 40.

The live FMCSA page states that carriers using those devices must replace them before September 8, 2026. That deadline is separate from the July 20 deadline attached to the May group. Combining the two lists or deadlines can create an inaccurate compliance summary.

The July removal does not mean the devices were part of the May action, even if both notices use similar language about minimum requirements. Each device should be checked by its listed name, provider information, model, identifier, removal date, and current status.

The shorter newsroom page does not supply a crash analysis, a device-by-device technical report, or a conclusion about hours recorded in a particular vehicle. Its core fact is regulatory status: 10 devices were removed from the registered list, and carriers received a replacement period.

How the Federal ELD List Works

FMCSA describes its list as a list of registered, self-certified ELDs. Providers certify that their devices meet the ELD specifications so the products can appear on the list. FMCSA supplies testing methods, trains enforcement personnel, and can work with manufacturers to correct issues or remove devices that do not meet minimum requirements.

Self-certification is important context. A listing means the provider made the required certification and registration. It should not be described as FMCSA personally testing and guaranteeing every unit, software version, installation, wireless connection, or output file.

Motor carriers and drivers have their own responsibilities. FMCSA says carriers use the registered list to select devices, train drivers to use them, and make sure the ELDs function properly in non-exempt vehicles. A compliant model can still be installed incorrectly, used improperly, suffer a malfunction, or produce an incomplete record.

The live site separates registered devices from revoked devices and publishes news about changes. A screenshot or old vendor page may not show the current status. A dated article should therefore identify what was true on its update date and link directly to FMCSA’s current list.

Where ELD Rules Fit in 49 CFR

The current federal motor carrier regulations appear in Title 49, Subtitle B, Chapter III. Part 395 covers hours of service of drivers, including the ELD provisions and technical specifications referenced by FMCSA’s notices.

Part 395 is one part of a larger framework. Part 390 contains general federal motor carrier rules. Part 391 addresses driver qualifications. Part 392 covers driving of commercial motor vehicles. Part 393 covers parts and accessories necessary for safe operation, and Part 396 covers inspection, repair, and maintenance.

An ELD records duty-status information. It does not inspect brakes, determine whether cargo was secured, evaluate driver qualifications, or establish why a collision occurred. Those questions may involve other records governed by other parts of Chapter III.

The eCFR is the appropriate source for current regulatory text. Summaries can become stale, and a notice about a device list does not rewrite every hours-of-service rule. The exact rule, effective date, exceptions, and vehicle operation still matter.

What ELD Data Can Show

An ELD is intended to make it easier to track, manage, and share records of driving and off-duty time. Depending on the record and export, the data can help establish duty-status changes, driving time, vehicle movement, date and time information, location information, and annotations or edits.

The information can be compared with dispatch messages, bills of lading, fuel transactions, toll records, GPS or telematics data, and engine information. Agreement across independent sources can strengthen confidence in a trip timeline. Conflicts can identify a question that needs technical review.

Not every difference is evidence of falsification. Time-zone handling, unidentified driving, team-driver assignments, edits, data transfer problems, device malfunctions, and gaps between systems can require explanation. The original output file and supporting records are more useful than a cropped screenshot.

The device identifier is especially important after a removal action. A generic statement that a truck used “an ELD” does not show whether it was one of the 22 devices removed in these two actions, whether the use occurred before or after a deadline, or whether the provider later corrected the deficiency.

What Revocation Does Not Establish

A regulatory removal is not a crash reconstruction. It does not prove that a driver exceeded an hours limit, that a carrier directed excessive driving, that the ELD file was altered, or that fatigue contributed to a collision. Each of those propositions requires evidence tied to the driver, vehicle, trip, and event.

Removal also does not make every earlier output unusable. Records from a revoked device may still contain relevant time, location, status, or diagnostic information. The weight given to the data depends on completeness, technical reliability, corroboration, and the specific deficiency at issue.

The opposite assumption is also unsafe. A device appearing on the registered list does not prove that every log is complete or correct. Registration status, installation, operation, driver entries, edits, malfunctions, and file transfer are separate questions.

FMCSA’s notices provide a starting point for current status. They do not replace a device-specific and trip-specific examination when a record matters.

Crash-Related Documentation Questions

When ELD information is relevant to a crash, the useful record is broader than the daily graph grid. It can include the native output file, records of duty status, edits and annotations, unidentified driving events, malfunction or diagnostic events, driver assignments, device registration details, and instructions used by the carrier.

Supporting records can help explain whether the electronic record matches the trip. Dispatch and load records may show scheduled stops and delivery windows. Fuel and toll records may confirm movement. Vehicle telematics may provide a second location stream. Paper or software logs used during a revocation transition may fill a period when the old device was discontinued.

The May notice specifically instructed affected carriers to revert to paper logs or logging software during the replacement period. That means a transition file may legitimately contain more than one record format. The existence of paper logs during that period is not automatically evidence of evasion.

A careful review keeps status and causation separate. It identifies which device was used, when it was used, what FMCSA listed on that date, what the file contains, what is missing, and whether other records agree.

How to Read FMCSA Crash Statistics Carefully

FMCSA’s Large Truck and Bus Crash Facts is a recurring national report of descriptive statistics for fatal, injury, and property-damage-only crashes involving large trucks and buses. FMCSA says the report draws from NHTSA’s fatal-crash census, a national sample of police-reported crashes, the MCMIS Crash File, and federal highway statistics.

The page currently points to reports by data year and warns that comparisons across the transition from the former General Estimates System to the Crash Report Sampling System should be made with caution. The landing page was last updated October 10, 2025 and lists 2022 as the most recently published report on that page.

That source does not support an undated statement about “current 2026 crash numbers.” Publication year, data year, crash definition, and source system should travel with any number. National descriptive statistics also do not establish what happened in one collision.

The 2026 ELD removals are regulatory events, not crash-count updates. Combining them with an unrelated national statistic can suggest a connection the sources do not establish.

Transition Records and Date-Specific Compliance

The transition periods make date accuracy essential. For a device in the May group, the relevant sequence includes the May 20 removal, the paper-log or logging-software transition, and the July 20 deadline. For a device in the July group, the live FMCSA page identifies September 8 as the replacement deadline.

A carrier may therefore have an ELD record for one part of a trip history and paper or software logs for another. That mixed format can reflect FMCSA’s instructions rather than an attempt to conceal driving time. The records should be reviewed for continuity, driver identity, vehicle assignment, and agreement with independent trip data.

Enforcement treatment also changes by date. The May notice described interim instructions before July 20 and a different consequence for continued use on or after the deadline. An article or report that omits the date may wrongly apply the post-deadline consequence to earlier use.

If a provider later corrects the device and FMCSA restores it, the live list may differ from the original bulletin. Both sources serve a purpose: the dated notice shows the agency action at that time, while the live list shows current registration status.

That distinction matters when records span several months. Status should be checked for the day of use, not only the day someone later reviewed the file. Provider name, model, ELD identifier, removal notice, transition deadline, and any restoration should be recorded separately.

The same date discipline applies to citations: quote the notice that governed the device at the relevant time, then confirm whether the live registry later changed.