Fatigue and Hours of Service Cases
Connecting HOS violations, dispatch pressure, and timeline evidence to driver fatigue in commercial vehicle litigation.
Fatigue cases don't start with a tired driver. They start with a schedule that couldn't be completed legally, a rest period that wasn't what it looked like on paper, or a carrier that kept pushing work into time logged as off-duty. Proving fatigue in commercial vehicle litigation means building a timeline from the records outward and identifying where the legal framework broke down.
Bill Collins has operated under Hours of Service rules for 51 years and taught them to commercial drivers for 28. A fatigue case built on records he has reviewed will either support the theory or tell you clearly and early why it doesn't.
How Fatigue Gets Proven
No single document proves fatigue. The strongest cases layer timeline conflicts, insufficient rest patterns, and supporting records that contradict the official log. Under 49 CFR 395.3, property-carrying drivers are limited to 11 hours of driving following 10 consecutive hours off duty. The 14-hour window closes any opportunity to drive once 14 consecutive hours on duty have elapsed, regardless of how much driving time remains. Both limits are provable from ELD records. What the records sometimes conceal requires additional work.
Dispatch schedules, load appointment windows, and trip plans are reviewed alongside the ELD timeline. If the assigned run couldn't be completed within legal HOS limits given the driver's available hours at departure, that calculation becomes part of the analysis. Fuel receipts and toll records create independent timestamps placing the driver at specific locations. Phone records may document carrier contact during periods logged as off-duty. This is the core of forensic HOS and log analysis.
The 14-Hour Window
Under 49 CFR 395.3(a)(2), once a driver has been on duty for 14 consecutive hours, driving is prohibited regardless of time remaining in the 11-hour limit. The clock starts when the driver begins any on-duty activity. Short breaks and meal periods do not reset it.
Identifying a 14-hour violation requires knowing when the duty period actually started, not just when the ELD shows the first driving event. Detention at a shipper, pre-trip inspections, and time spent waiting for dispatch all count as on-duty under 49 CFR 395.2 when the driver has not been relieved from responsibility. A log showing a first driving event at hour twelve of the duty period may still conceal a violation if earlier on-duty time was understated or misclassified.
The 11-Hour Driving Limit
Violations of the 11-hour limit under 49 CFR 395.3(a)(3) can be obscured when non-driving on-duty activities are misclassified, when unassigned driving events are not counted, or when personal conveyance designations mask additional drive time. A full timeline review accounting for all available movement data usually resolves those questions.
Driving that appears across multiple ELD accounts, or vehicle movement left in unassigned status, adds complexity to the count. The total driven hours are what matter under the regulation, not just what appears under the primary driver account. Patterns of this kind also surface in logbook falsification review.
Rest Periods, What 10 Hours Actually Requires
Ten consecutive hours off duty resets the driving clock. The requirement under 49 CFR 395.3(a)(1) is clear on paper. The forensic question is whether the off-duty block was genuinely restorative.
Location data during claimed rest periods matters. A driver logged as sleeper berth off-duty who GPS shows active through a fuel stop or moving through a truck stop facility was not fully at rest. Dispatch messages, satellite communications, and phone records can establish whether carrier contact occurred during required rest time. Under 49 CFR 395.2, repeated interruptions during an off-duty period are relevant to fatigue analysis, particularly when those interruptions were carrier-initiated and tied to the next assignment.
Detention Time and the HOS Clock
Detention at shippers and receivers is one of the most frequently misrepresented issues in HOS compliance. Under 49 CFR 395.2, time spent waiting at a facility counts as on-duty when the driver is required to remain in readiness or has not been relieved from responsibility. Drivers waiting at a dock for hours before loading often record that time as off-duty. Whether the classification holds depends on what the shipper records, gate logs, and dispatch instructions actually show.
Long detention delays can push the 14-hour window toward its limit before a driver has traveled a mile. Shipper and receiver records are among the first documents to request in fatigue cases involving extended loading waits.
Dispatch Pressure and Carrier-Created Fatigue
Under 49 CFR 390.6, coercion of drivers to violate safety regulations is prohibited. The practical analysis of carrier scheduling pressure in fatigue cases doesn't always require a formal coercion argument. Unrealistic schedules can tell the same story.
A load appointment requiring departure before legal rest could be completed, a dispatch pattern that consistently pushed drivers to their HOS limits, or a pay structure rewarding mileage above all else can support arguments that the carrier contributed to unsafe fatigue conditions. Dispatch records, trip planning documents, load appointment windows, and pay records are the evidence base for that analysis. Carriers that ignored their own drivers' HOS history while assigning the next run create a different liability picture than those where the problem was isolated. This overlaps directly with carrier liability analysis.
Personal Conveyance and Sleeper Berth Disputes
Personal conveyance claimed after a delivery, used to reposition toward the next load, is a recurring issue in fatigue cases. FMCSA guidance is direct: movement that serves the carrier's commercial interests is not personal use, regardless of what the ELD shows. GPS data placing the truck on a route toward the next dispatch point during claimed personal conveyance time raises questions about whether the off-duty period qualified under the guidance.
Split sleeper berth arrangements under 49 CFR 395.1(g) allow drivers to break the required rest period under specific conditions. The regulations are technical, and compliance depends on the exact length of each segment and what occurred between them. Fatigue analysis involving split berth records requires careful timeline review to confirm required minimums were met and that the rest was genuinely uninterrupted.
Connecting the Timeline to the Crash
Proving fatigue in court requires more than an HOS violation. The analysis connects the timeline to what happened on the road. ECM data showing late or absent braking, dashcam footage showing lane drift or failure to respond to changing conditions, and the crash report itself are reviewed alongside the duty status records.
A driver 13 hours into a duty period, with a prior rest period interrupted twice by dispatch messages, presents a factually different picture from one whose records are clean. Bill's analysis integrates the HOS timeline with available crash data to explain what the records show about the driver's condition at the time of the event. Opinions are stated in terms of what the evidence actually supports. Where the records are ambiguous or incomplete, that is stated directly. An initial case review identifies what evidence to preserve before retention windows close.
Questions Attorneys Ask About Fatigue Cases
What evidence proves truck driver fatigue?
Fatigue cases are built from a combination of sources. ELD timelines, dispatch records, GPS and telematics data, fuel receipts, shipper and receiver check-in logs, and phone records are reviewed together. The most compelling evidence is usually not one document but the conflict between what the official log shows and what the supporting records reveal about actual activity during claimed rest time.
Does detention time count toward HOS limits?
It depends on the circumstances. Under 49 CFR 395.2, on-duty time includes any period when a driver is not relieved from all responsibility for the load or the vehicle. Drivers waiting at a shipper dock who are required to remain available are generally in an on-duty status. Whether a specific waiting period was on-duty is a factual question that shipper records, gate logs, and dispatch instructions help answer.
Can dispatch pressure support a fatigue liability argument?
Yes. Dispatch records and load scheduling showing a driver was assigned work that required movement before legal rest could be completed, or that consistently generated HOS pressure across multiple runs, can support arguments that the carrier contributed to unsafe fatigue conditions. The analysis looks at the schedule that was built, not just what the driver ultimately chose to do.
Can a logbook that appears compliant still support a fatigue argument?
Yes. A log showing ten consecutive off-duty hours can still be examined when GPS, phone records, or dispatch messages show the driver was not actually resting during that period. A legally adequate break on paper is different from one where the driver was in contact with dispatch, fueling, or moving through a facility.
Can prior HOS violations in the driver's history be used in a fatigue case?
Prior violations documented in roadside inspection records and prior RODS can be relevant to pattern evidence and carrier supervision arguments. Their significance depends on what the carrier knew about the history and what action, if any, was taken before the crash.
Do you work fatigue cases for both plaintiff and defense?
Yes. Some fatigue cases involve HOS violations and dispatch pressure that clearly contributed to a crash. Others involve records that hold up when the full evidence set is reviewed. The analysis follows the records in either direction.
Discuss Your Fatigue Case
Bill reviews all submitted materials and responds within one business day.
Plaintiff and defense. All inquiries are confidential. Or visit the contact page.