← All articles Compliance

Hours of Service, fatigue and the limits of the logbook

A truck at a warehouse loading dock

Hours-of-Service rules are the backbone of fatigue regulation for commercial drivers, and they do real work. But they answer a narrower question than most people assume. A clean logbook proves a driver was permitted to be driving. It does not prove the driver was fit to be driving. The gap between those two is where fatigue lives.

The rules, briefly

For property-carrying commercial drivers in the US, the core limits are (FMCSA, 49 CFR Part 395):

  • 11-hour driving limit after 10 consecutive hours off duty.
  • 14-hour window: no driving beyond the 14th consecutive hour after coming on duty, and off-duty breaks do not extend that window.
  • 30-minute break required after 8 cumulative hours of driving.
  • 60/70-hour limit over 7 or 8 consecutive days, with a 34-hour restart to reset the clock.

These have been refined over decades, most recently in the 2020 final rule that added sleeper-berth flexibility and expanded the short-haul exception. Electronic logging devices now make compliance largely automatic to record and audit.

What the logbook can't see

Here is the limit. The clock treats all eleven hours as equivalent, but the body does not. As we have written elsewhere, being awake for around 17 hours impairs performance to roughly a 0.05% blood-alcohol level (Dawson & Reid, 1997). A driver can be perfectly inside their 11 and 14-hour limits and still be dangerously impaired at 4am, because the regulation counts hours driven and fatigue depends on hours awake and the time on the clock.

The prevalence data makes the gap concrete: even with HOS in force, drowsiness shows up in roughly 9% of all crashes in naturalistic studies (AAA Foundation, 2018). Compliance is necessary. It is not sufficient.

The logbook tells you a driver was legal. It cannot tell you they were awake.

Compliance plus monitoring

This is not an argument against Hours of Service, it is an argument for pairing it with something that measures the thing the logbook can't: actual driver state. HOS sets the outer boundary. In-cab monitoring watches what happens inside that boundary, the eye-closures and microsleeps that a fully compliant shift can still produce, and flags the specific hour and driver that need intervention. One is a legal floor. The other is a real-time safety net. Fleets that lead on safety run both.

Sources

  1. FMCSA, Summary of Hours-of-Service Regulations, 49 CFR Part 395. fmcsa.dot.gov
  2. Dawson & Reid, Nature, 1997. nature.com
  3. AAA Foundation, drowsy-driving prevalence, 2018. aaafoundation.org

See inside the boundary the logbook sets

FleetScout adds real-time fatigue monitoring on top of compliance, so a legal shift is also a safe one.

Open Control Panel