Picture a roadside inspection where the ELD shows the driver off duty since 6:00 a.m., with hours to spare. The inspector pulls the fuel receipts from the cab. One is timestamped 9:40 a.m. at a station roughly 200 miles from where the log puts the truck. Nobody has to prove the driver exceeded a limit. The record itself is now the problem.
That is the territory of violation 395.8E-HOSPD, described in the data as "HOS (Property) - No driver may make a false report in connection with a duty status." The code is about whether the record is true, not whether the hours were legal.
What the code covers
Under 49 CFR 395.8, a driver has to keep an accurate record of duty status, and the false-report prohibition bars a driver from making a false report in connection with that status. The "E" in the code points to that paragraph of the section.
In practice, inspectors see this in a few recurring patterns:
- Logging off duty while doing work the regulation treats as on duty.
- Recording sleeper-berth or off-duty time that did not actually happen.
- Editing entries after the fact so the timeline fits the clock instead of the day.
- Paper logs that conflict with what the truck, the receipts, or the dispatch record show.
Note that the citation attaches to the driver's report. A carrier that pressures a driver into bad entries creates its own exposure, but this code is written against the driver.
Why it is weighted heavier than it looks
Our data gives this code a severity weight of 7. In the calculator, that base is adjusted by a time weight tied to how recent the violation is: 3 for 0 to 6 months, 2 for 6 to 12 months, 1 for 12 to 24 months, and 0 beyond 24 months. Any single BASIC's severity contribution from one inspection is capped at 30.
The weight reflects what a false entry does to the rest of the file. An inspector who finds one falsified entry has no reason to trust the other entries, and that doubt spreads to every hours calculation on the same log.
Out-of-service status
The OOS indicator for this code is off in our data, so it is not an automatic out-of-service violation. That does not make it harmless. In the same data set, the code appears in 79,443 inspections across 136,858 recorded violations, and about 8.8 percent of those recorded instances (12,049 of them) ended in an out-of-service result. Read that as a rate, not a rule: the code does not put a truck out of service on its own, but it is far from a footnote.
How inspectors check it
Roadside checks rarely rely on the ELD alone. Inspectors compare the log against:
- Fuel receipts, with time and location.
- Toll and weigh-station records.
- GPS or telematics location history.
- Bills of lading and delivery appointments.
- The ELD's edit and annotation history.
When the log says the truck was somewhere it could not have been, or the timeline has edits that cluster around an inspection, the inspector has grounds to write this code.
What to do about it
For drivers, the practical rule is simple: log duty status when it happens, not at the end of the day from memory. If an entry is wrong, correct it through the ELD's proper edit or annotation function and explain the reason. An honest annotation is a far better record than a clean timeline that doesn't match the receipts.
For carriers, review edit logs regularly, look for patterns in who edits and when, and make sure dispatch never asks a driver to show time that did not happen. A driver who can say "I logged it wrong and here is the fix" is in a much better position than one whose record and receipts disagree.
Key takeaways
- 395.8E-HOSPD is about falsity in the duty-status record, independent of hours.
- Its severity weight in our data is 7, and it is subject to the calculator's time weighting and per-BASIC cap.
- The OOS indicator is off, but about 8.8 percent of recorded instances still ended out of service.
- Inspectors check the log against receipts, location data, and edit history.
- Corrections belong in the ELD's annotation or edit function, documented honestly.
If you want to see how this code sits alongside hours violations on the same inspection, the calculator lays out how the weights combine. The underlying rule is in the eCFR text of 49 CFR 395.8, and the glossary defines the terms like duty status that the rule depends on.