Hours of service and driver fatigue

Fatigue does not leave skid marks. What it leaves is a duty record, a dispatch history, and a delivery window that could not be met legally — and those are documents. This is general information, not legal advice.

What Part 395 does

Part 395 of the federal motor carrier safety regulations is titled "Hours of Service of Drivers." It caps how long a driver may drive and be on duty, requires rest between shifts, and limits accumulated on-duty time over consecutive days. Subpart B covers electronic logging devices.

The specific limits depend on the type of operation and change from time to time, so the applicable version has to be established rather than assumed. The structure does not change: there is a ceiling on driving, a ceiling on the working day, a required rest period, and a weekly cumulative cap.

Sources: 49 C.F.R. Part 395, "Hours of Service of Drivers" (subpart B, Electronic Logging Devices); Part 391 (driver qualification); Part 392 (driving of commercial motor vehicles).

What an electronic logging device records

An ELD connects to the engine and records automatically rather than depending on what a driver writes in a book. It typically captures date and time, engine hours, vehicle miles, location at intervals, and duty status changes — with an identification of the driver and the vehicle.

Two features matter for a claim. Edits are recorded rather than substituted, so the original entry and the change both survive. And driving time that is not assigned to a logged-in driver is captured as unassigned driving, which is where time gets hidden when it is hidden.

How logs get manipulated anyway

• Unassigned driving time, left unclaimed so it belongs to nobody.
• Duty status editing — recharacterising driving as on-duty-not-driving or off-duty.
• Personal conveyance, a legitimate category, claimed for what was really revenue movement.
• Credential sharing, where a second driver runs under another's login.
• Exemption claims asserted to keep an operation outside the ELD requirement.
• Paper logs, still permitted in limited situations and far easier to write to suit.

Checking the log against the world

The reliable method is to compare the duty record against records the driver had no hand in creating. Each carries a time and a place:

• Fuel purchases, with card timestamps and locations.
• Toll transponder crossings.
• Weigh station and roadside inspection records.
• Bills of lading, delivery receipts, and gate or dock timestamps.
• Dispatch and messaging records between carrier and driver.
• Cell site and device location data.
• Engine control module data, which records its own picture of the run.

Where the log and these disagree, the log is the document that loses. And the carrier is required to keep the supporting documents precisely so this comparison is possible.

Black box and ECM data · FMCSA violations as evidence.

The case against the carrier, not just the driver

Fatigue is usually a scheduling decision before it is a driving decision. A delivery window that cannot be met within the legal limits is a decision the carrier or the shipper made, and it can support a claim against the company independent of anything the driver did at the wheel — through dispatch records, the rate confirmation, the appointment time, and the pattern of that driver's prior runs.

Who is liable in a truck case.

Act early or lose it

ELD data, supporting documents, and dispatch records all sit on retention schedules, several of them short. A written preservation demand naming these categories has to go out at the start rather than once the claim is worked up.

Why these cases move fast.

Common questions

What are the hours-of-service rules for?

Fatigue. Part 395 of the federal motor carrier rules caps driving time and requires rest, because a tired driver reacts like an impaired one. The limits are a floor for safety, not a target to be driven to.

Can a driver still falsify a log?

It is much harder than it was. Electronic logging devices connect to the engine and record driving time automatically rather than relying on what the driver writes. Manipulation still happens — unassigned driving time, editing duty status, running under another driver’s credentials — and those leave their own traces.

How do you prove the log was wrong?

By checking it against records the driver did not create. Fuel purchases, toll transponder crossings, weigh station records, delivery and dispatch timestamps, and cell location data all carry times and places. A log that shows a driver resting while a fuel receipt puts them three hundred miles away answers itself.

Is fatigue really provable, or is it just an argument?

It is provable more often than people expect, because it leaves a documentary trail. Duty records, dispatch pressure, the delivery window, and the absence of braking before an obvious hazard together make a case that does not depend on the driver admitting anything.