Log Falsification: Penalties and How ELDs Prevent It (2026)

"Fixing" a log to hide driving time is one of the most expensive mistakes in trucking. Here's what counts as falsification, what it costs, and why an ELD leaves almost no room for it.

What counts as falsification

Falsification is knowingly putting false information on your record of duty status. It isn't limited to a paper logbook — it covers any attempt to make your hours look legal when they aren't. Common examples:

Ghost logs — logging off-duty or sleeper time while you're actually driving.
Two sets of books — one log for the office, another for the inspector.
Logging under another driver's account to keep your own clock clean.
Back-dating or rewriting a record to erase an obvious violation.

FMCSA addresses this in its hours-of-service rules (49 CFR 395.8). The key word is knowingly — an honest correction with a note attached is not falsification, but a deliberate cover-up is.

What it costs you

Falsification is treated as a serious violation, not a paperwork slip. The consequences stack up:

Federal civil penalties that can reach into five figures per violation, assessed against the driver and, often, the carrier.
Out-of-service orders — an inspector who spots a false log can shut the driver down roadside until enough off-duty time is logged.
CSA points — false-report violations carry heavy weight in the Hours-of-Service Compliance BASIC, dragging down your CSA score and inviting more inspections.
Lost trust — a falsification finding can cost you contracts, raise your insurance, and follow you to your next carrier.

Why editing isn't the same as falsifying

You're allowed to correct a log. If the system assigns drive time to the wrong status, or a mechanic moved your truck, you can fix it — the rules just require an annotation explaining the change. The line is intent: a documented correction is legal, while erasing a violation to deceive an officer is not. We cover the boundary in can you edit ELD logs.

How an ELD makes falsification nearly impossible

The whole point of the ELD mandate was to take the fiction out of logs. An ELD records driving time automatically from the engine, so you can't log "off duty" while the wheels are turning. Every edit is kept alongside the original record, so a rewrite shows up as an edit rather than a clean replacement. And miles driven with no one logged in become unidentified driving events that an inspector can see. Together those features make the old tricks leave a trail.

How Eagleye ELD keeps you honest — and legal

Eagleye ELD captures drive time straight from engine data, warns you before you hit a limit so you're not tempted to "adjust" a log after the fact, and keeps a clean, annotated edit history for every change. Unidentified driving is flagged for review so nothing hides. The result: logs you can hand to an officer with confidence, no second set of books required.

Keep clean, inspection-ready logs — start for $1 →

Frequently asked questions

Is falsifying a logbook a federal violation?

Yes. Under FMCSA rules (49 CFR 395.8), knowingly entering false information on a record of duty status is a violation that can bring federal civil penalties, out-of-service orders, and CSA points against the driver and carrier.

Can you be put out of service for a false log?

Yes. An inspector who finds a false record of duty status can place the driver out of service, typically until enough off-duty time is logged to bring the driver back into compliance.

Can you still falsify logs with an ELD?

It's far harder. An ELD records driving time automatically from the engine, keeps the original of every edit, and flags unidentified driving — so hidden driving time and after-the-fact rewrites leave a trail.