A late log is an hours problem. A false log is a records problem, and the inspector is looking at something different. Here is how I read 395.8(e), what the numbers in our data show, and what I check before a trip so the paperwork never becomes the citation.
What the code covers
Our reference lists 395.8(e) as "False report of drivers record of duty status." It falls under the Hours-of-Service Compliance BASIC, sits in the False Log violation group, and carries a severity weight of 7. The code is used in SMS calculations. It does not carry an out-of-service indicator on its own.
The rule is about the accuracy of the record, not the clock. A driver can be well within hours and still get cited if the log that shows it is wrong. A driver who is over hours but logs honestly has an hours violation. Keeping those two apart matters, because the fix is different: one is a scheduling problem, the other is a documentation integrity problem. The regulation text is on eCFR under 49 CFR 395.8. The violation record itself, with its counts and weights, is on the 395.8(e) violation page.
The numbers
The stats are as of October 20, 2026. The dataset records 166,066 violations under this code, and 82,225 of those were out-of-service. That gives the 49.5% OOS rate in the data (82,225 divided by 166,066 is 0.495).
That rate deserves a careful read. The code is not flagged as out-of-service by itself, yet it ends out-of-service about half the time. The fields alone don't explain why. Before I drew any conclusion about shutdowns, I would read the inspection narratives for the cases in question, because the outcome often depends on what else was found during the same inspection.
What makes a log false
Most false logs I have seen fall into a few patterns:
- Duty status that doesn't match what the driver was doing, such as off-duty time recorded while the truck was moving.
- Edits that remove or shift time without an annotation explaining why.
- Logs completed after the fact to fill a gap in the day.
- Entries that place the truck somewhere the trip records, fuel receipts, or GPS data say it was not.
- Identical or copied days that don't match the actual trip.
Inspectors cross-check. The log is one document among several, and a roadside audit compares it against the records the carrier already keeps. When they conflict, the log loses.
Why the weight matters
The severity weight is 7. In the VioCodes calculator, time weights run 3 for violations 0 to 6 months old, 2 for 6 to 12 months, 1 for 12 to 24 months, and 0 beyond 24 months. Severity contribution is capped at 30 per inspection per BASIC, so a single bad inspection cannot grow without limit.
The practical effect is that a false log cited last month counts for far more than one cited two years ago. I won't reduce the full formula to prose here, because the calculator shows the inputs side by side and is easier to test against a real inspection.
What I check before a trip
- Reconcile daily. Check the log against fuel receipts and load documents at the end of each day, not at the end of the week.
- Annotate every edit. Each change should have a reason the driver can explain in one sentence.
- Don't let logs fall behind. Late logs are where false logs start.
- Watch the pressure. If the office asks for a clean log the trip doesn't support, that request is the problem. It usually comes from the office, not the cab.
Key takeaways
- 395.8(e) is about record accuracy, not hours alone.
- The data shows 166,066 violations, 82,225 out-of-service, and a 49.5% OOS rate, even though the code carries no OOS flag.
- The severity weight is 7, and time weights step down from 3 to 0 over 24 months.
If you want to see how a single citation under this code moves a score over time, run the scenario through the calculator.