How Independent Location Data Exposes Hours-of-Service Fraud in Commercial Trucking
GPS data tells the truth about where a truck was. Logbooks tell the story the driver wrote down. When the two do not match, the discrepancy is not a recordkeeping error. It is evidence that a driver was operating a commercial motor vehicle while claiming to be off duty, resting, or parked—and that the carrier either did not notice or did not care. In crash litigation, a gap between a truck’s GPS trail and the driver’s recorded hours of service is among the most powerful categories of evidence available, because it establishes not just a regulatory violation but a pattern of conscious disregard for a rule designed to prevent fatigue-related crashes.
Federal hours-of-service regulations exist for a single reason: fatigued driving kills. The rules limit how long a commercial truck driver may drive and how much rest the driver must take before driving again.1 Falsifying the records that document compliance with those rules is a federal violation that carries its own penalties and, in crash litigation, can support a claim for punitive damages. The evidence that proves the falsification most often comes not from the logbook itself but from independent data sources (GPS telematics, fuel card transactions, toll transponder records, and weigh station timestamps) that place the truck at locations incompatible with what the driver’s logs recorded.
The Hours-of-Service Framework
The federal hours-of-service regulations are found in 49 C.F.R. Part 395.2
For property-carrying drivers, the core rules impose the following limits:3 4
These limits are enforced through the driver’s record of duty status, which must account for every hour of every 24-hour period.
The record divides each day into four categories:
Under 49 C.F.R. § 395.8, every driver who operates a commercial motor vehicle must record this duty status for each 24-hour period.5 Making a false report in connection with a duty status is a federal violation under § 395.8(e), which states that no driver or motor carrier may make a false report in connection with a duty status.6 The same provision prohibits disabling, deactivating, jamming, or otherwise tampering with an ELD so that the device does not accurately record and retain required data.7
Motor carriers bear independent obligations. Under 49 C.F.R. § 395.8(k), carriers must retain records of duty status and supporting documents for each driver for at least six months.8 Under 49 C.F.R. § 395.11, carriers must also retain supporting documents—including bills of lading, dispatch records, expense receipts, electronic mobile communication records, and payroll records—that can be matched to the driver’s record of duty status to verify accuracy.9 A carrier that fails to collect or review these documents, or that ignores discrepancies between the documents and the driver’s logs, is not merely negligent in its paperwork. It has failed to exercise the oversight the regulations require.
The ELD Mandate and Its Limits
The electronic logging device mandate, which took full effect on December 16, 2019, was designed to make log falsification harder. Under 49 C.F.R. Part 395, Subpart B, most drivers required to keep records of duty status must use a registered ELD that automatically records driving time by connecting to the vehicle’s engine control module.10 The ELD captures when the engine is running, when the vehicle is moving, and the vehicle’s location at specified intervals, creating an electronic record that the driver cannot simply fabricate.
The mandate reduced some forms of log fraud, but it did not eliminate all of them.
Several categories of drivers remain exempt from the ELD requirement:11
These exempted drivers may still use paper logs, which are susceptible to the same falsification that the ELD mandate was intended to prevent.
Even among drivers using ELDs, manipulation is possible:
Under § 395.8(e)(2), no driver or motor carrier may reengineer, reprogram, or otherwise tamper with an ELD so that the device does not accurately record and retain required data.12
The regulatory prohibition on tampering is explicit, but enforcement depends on detection. And detection most often comes from comparing ELD or logbook entries against independent data that the driver and carrier cannot control.
Where GPS Data Comes From
GPS data in commercial trucking comes from multiple independent sources, each generating its own record of where the truck was and when.
Fleet telematics systems are the most comprehensive source. Carriers that use telematics platforms, such as Omnitracs, Samsara, Motive, or Verizon Connect, receive GPS pings from each truck at regular intervals, typically every few minutes or upon specified events. These pings record latitude, longitude, speed, heading, and timestamp. The telematics provider stores this data on its servers, often for a year or more, creating a continuous location trail that can be mapped against the driver’s log entries.
Fuel card transaction records provide timestamped proof that the truck was at a specific fuel stop at a specific time. Most carriers issue fuel cards (Comdata, EFS, or fleet-specific cards) that record the date, time, location, and fuel quantity for each purchase. If a driver’s log shows the driver off duty and resting at a truck stop in Nashville at 2:00 a.m. but the fuel card shows a purchase in Memphis at 2:15 a.m., the discrepancy is self-evident.
Toll transponder records document every passage through a toll facility. E-Z Pass, PrePass, and state-specific toll systems log the transponder identifier, the toll plaza location, and the date and time of passage. A driver whose log claims a 10-hour rest break but whose toll transponder shows the truck passing through three toll plazas during that period has created a record that directly contradicts the claimed rest.
Weigh station and inspection records provide additional location anchors. Many states use PrePass or Drivewyze bypass systems that log when a truck approaches and clears a weigh station, even if the truck is not required to stop. These records, like toll data, are maintained by third-party systems and are available through subpoena.
The critical characteristic shared by all of these sources is independence. The driver cannot alter the fuel card company’s transaction log, the toll authority’s passage records, or the telematics provider’s GPS database. When these independent records conflict with the driver’s log, the conflict is not a matter of interpretation; it is a factual contradiction documented by systems the driver does not control.
How Discrepancies Are Identified
In crash litigation, identifying GPS-versus-logbook discrepancies is a methodical process. The investigator obtains the driver’s records of duty status, whether paper logs or ELD data, for the days and weeks preceding the crash.
The investigator then obtains the independent GPS and transaction records from every available source:
- The telematics provider
- The fuel card company
- The toll authority
- Weigh station records
- Any other system that logged the truck’s location
The two datasets are then plotted on a timeline. Each entry in the driver’s log (off duty, sleeper berth, driving, on duty not driving) is compared against the GPS trail for the corresponding period. If the log shows the driver off duty from 10:00 p.m. to 8:00 a.m., but the GPS shows the truck moving continuously along an interstate during that window, the driver was driving while logged as resting. If the log shows a 10-hour break at a specific location but the GPS shows the truck never stopped for more than 45 minutes during that period, the required rest break was never taken.
The analysis extends beyond the day of the crash. A pattern of discrepancies across multiple days or weeks establishes that the falsification was not an isolated mistake but a habitual practice. A driver who routinely logged 10-hour rest breaks that GPS data shows lasted 5 or 6 hours was chronically short on rest—precisely the condition the hours-of-service rules are designed to prevent. If that driver caused a crash, the chronic sleep deficit becomes a central fact in the causation analysis, and the falsified logs become evidence that the driver knew the rules and deliberately circumvented them.
The Carrier’s Exposure
When GPS data contradicts a driver’s logs, the carrier’s liability extends beyond the driver’s conduct. Motor carriers have an independent duty under 49 C.F.R. § 395.8(e) not to make or permit false reports.13 Under 49 C.F.R. § 395.8(k), carriers must retain supporting documents that could reveal discrepancies.14 Under 49 C.F.R. § 392.3, a motor carrier may not require or permit a driver to operate a commercial motor vehicle while the driver’s ability or alertness is so impaired through fatigue that it is unsafe for the driver to operate the vehicle.15
A carrier that has telematics data showing its trucks moving during periods logged as rest, and that never compared that data against driver logs, has failed in its oversight obligations. A carrier that received fuel card records showing purchases at times and locations inconsistent with reported rest breaks, and that never flagged the inconsistency, has the data to detect the fraud and chose not to look. A carrier that pressured drivers to meet delivery schedules that were mathematically impossible to achieve within legal hours has created the incentive for the falsification it was obligated to prevent.
This is why GPS-versus-logbook discrepancies frequently support claims for punitive damages. The evidence does not merely show that a driver was fatigued. It shows that the driver lied about being fatigued, that the carrier had independent data proving the lie, and that both allowed the driver to continue operating an 80,000-pound vehicle while impaired by sleep deprivation. In many jurisdictions, conduct that reflects a conscious disregard for the safety of others meets the threshold for punitive damages, and systematic hours-of-service fraud documented by GPS data is difficult to characterize as anything less.
Preservation and Admissibility
GPS and supporting transaction data are subject to the same preservation and admissibility requirements as any electronically stored information in federal litigation. A litigation hold letter should specifically demand preservation of telematics data, fuel card records, toll transponder records, ELD data and supporting files, dispatch records, and all driver qualification file materials. The hold should be directed to the carrier, the telematics provider, the fuel card company, and any third-party toll or weigh station system that maintains relevant records.
Retention periods vary by source. Telematics providers typically retain data for one to three years depending on the service agreement. Fuel card companies may retain transaction data for several years. Toll authorities retain passage records on their own schedules. ELD data and supporting documents must be retained by the carrier for at least six months under § 395.8(k).16 If the data needed is older than six months, it may be available from the telematics or fuel card provider even after the carrier’s minimum retention period has passed.
Under Federal Rule of Civil Procedure 37(e), a party that fails to preserve electronically stored information that should have been preserved faces sanctions ranging from curative measures to adverse inference instructions or case-dispositive sanctions if the loss was intentional.17 A carrier that purges telematics data or fuel card records after a crash involving a fatality or serious injury, particularly after receiving a preservation demand, risks a finding of spoliation.
Sources
- [1] Federal Motor Carrier Safety Administration, "The Truck Driver's Guide to Hours of Service,".
- [2] 49 C.F.R. Part 395 (Hours of Service of Drivers),.
- [3] Federal Motor Carrier Safety Administration, "Summary of Hours of Service Regulations,".
- [4] Id.
- [5] 49 C.F.R. § 395.8(a),.
- [6] 49 C.F.R. § 395.8(e)(1),.
- [7] 49 C.F.R. § 395.8(e)(2)-(3),.
- [8] 49 C.F.R. § 395.8(k),.
- [9] 49 C.F.R. § 395.11,.
- [10] 49 C.F.R. § 395.20,.
- [11] Federal Motor Carrier Safety Administration, "Who Is Exempt from the ELD Rule?" (FMCSA-ELD-395-Q17) (guidance rescinded Mar. 10, 2022 as duplicative of 49 C.F.R. Part 395, Subpart B; underlying regulatory exemptions unchanged),.
- [12] 49 C.F.R. § 395.8(e)(2),.
- [13] 49 C.F.R. § 395.8(e),.
- [14] 49 C.F.R. § 395.8(k), supra note 8.
- [15] 49 C.F.R. § 392.3,.
- [16] 49 C.F.R. § 395.8(k)(1),.
- [17] Fed. R. Civ. P. 37(e),.