Logbook Falsification Cases
Identifying false and manipulated hours-of-service records through ELD audit trails, supporting documents, and forensic timeline analysis.
Falsification is rarely obvious in the log itself. A well-maintained set of ELD records can look entirely clean on first review. What exposes the problem is everything surrounding the log: the fuel receipts, toll records, GPS data, dispatch messages, and shipper timestamps that should align with what the official record shows. When they don't, the conflict becomes the case.
Forty years of reviewing driver records as a fleet manager, an instructor, and an expert witness gives Bill Collins a clear picture of what legitimate records look like. He knows the patterns that appear in logs built to survive a quick inspection rather than a thorough one.
What Falsification Actually Looks Like
Under 49 CFR 395.8 and 395.30, drivers and carriers are required to maintain accurate records of duty status. Falsification occurs when those records misrepresent actual work, driving activity, or rest in a way that conceals HOS violations or overtime. It is not always a dramatic fabrication. Sometimes it is a duty status that was switched ten minutes before a work activity began. Sometimes it is a rest period that started on paper before the truck stopped moving.
The standard for identifying falsification is not proving intent. The standard is demonstrating that the official record conflicts with what the available evidence shows actually occurred. That process starts with the records the ELD preserves and works outward through every corroborating document.
The ELD Audit Trail
Original records are preserved after edits under 49 CFR 395.30(f). That means every version of a log entry: the original, any revised versions, and the final certified record, is available for forensic review alongside the edit history showing who made changes, when, and what annotation was provided.
Annotations are required under 49 CFR 395.30(c)(2) to explain the reason for any edit. Generic explanations, vague notes, or a series of identical annotations across multiple entries should be cross-checked against dispatch records and location data from the same time period. An annotation that says "driver correction" on an edit made three days after a crash, with no driver recertification, tells a different story than one with a specific and verifiable explanation.
Timing matters. Edits clustered around the date of a crash, or edits that consistently convert on-duty time to off-duty across a pattern of runs, are worth examining in detail. The edit history is not just procedural: it is a record of decisions made about what the log should say.
Drive Time and What Cannot Be Reclassified
Automatically recorded CMV movement is driving time under FMCSA's editing and annotations guidance. It cannot be converted to a non-driving status through an edit. What does appear in falsification disputes is driving assigned to the wrong account, movement left in unassigned status, and the use of personal conveyance or yard move designations to absorb actual drive time that would otherwise create a violation.
Unassigned driving records are among the most significant documents in a log falsification review. Under FMCSA Editing and Annotations guidance Q14 and Q15, vehicle movement not claimed by any driver account must be reviewed by the carrier and either assigned or explained. Unassigned events that align with the relevant time period, that GPS or fuel records place near the relevant route, or that the carrier cannot explain consistently deserve serious attention.
Fuel Receipts, Toll Records, and the Paper Trail
Supporting documents are often more reliable than the log in falsification cases precisely because they are generated independently of the driver. Fuel transaction records place the truck at a specific location at a specific time. Toll records do the same. Weigh station receipts, truck stop transactions, and bills of lading create a parallel timeline that should match what the official log shows.
When a fuel receipt timestamps activity during a period logged as sleeper berth, or a toll record places the vehicle moving through a corridor the driver logged as off-duty, the discrepancy is documentable. The analysis is not speculative: it is a factual comparison of independent records against the official duty status. Supporting documents do not prove every case of falsification. What they do is make it very difficult to explain away conflicts that the log alone would never surface.
GPS Conflicts with Recorded Duty Status
GPS and telematics data show where the truck was and how it was moving at specific times. Cross-referencing that data against ELD duty status events is standard in log falsification analysis. A vehicle showing continuous movement through a known freight corridor during a period logged as a ten-hour rest break presents a factual conflict that demands an explanation.
GPS conflicts should be built into a minute-by-minute timeline, not treated as isolated anomalies. A single data point can be explained. A sustained pattern of movement contradicting logged status across hours of a claimed rest period is a different matter entirely. Dispatch records and load appointment data are reviewed alongside GPS to establish whether the movement served a commercial purpose consistent with active driver duty.
Carrier-Requested Edits and What They Indicate
Under 49 CFR 395.30(d)(1), carriers may request edits to driver records. The driver must review, accept or reject, and recertify. A driver who rejected a carrier-proposed change, or who never recertified after an edit was made, creates a dispute in the record itself.
Multiple post-crash edits requested by carrier staff, without adequate annotation or driver recertification, can support questions about whether the record was being adjusted rather than corrected. That analysis requires the full edit history with timestamps, user identities, and all associated annotations. Context matters. Not every carrier edit reflects an attempt to conceal a violation. What drives the analysis is whether the edited status is consistent with every other source of information about what the driver was actually doing at that time.
Paper Logs
Paper records require more external corroboration than ELD data because they lack automatic movement capture. A driver filling out a paper log manually at the end of a shift has more flexibility to reconstruct what the log shows. Under 49 CFR 395.8, those records must still be accurate, and the same cross-referencing process applies.
Fuel receipts, toll records, and GPS data are reviewed against the paper duty status entries. Bills of lading and shipper records establish pickup and delivery times that should align with the log. Where they don't, the conflict is the same in a paper case as in an ELD case: it just requires assembling more pieces to build the picture.
Multiple ELD Systems and Equipment Replacement
Drivers who moved between carriers, or who operated equipment fitted with different ELD systems during the relevant period, create a records challenge. Under FMCSA Editing and Annotations guidance Q10 and Q11, incompatible ELD systems may not transfer data between them. The driver and carrier are still responsible for accurate current records and prior seven-day history regardless of what systems were in use.
Equipment replacement and ELD resets present similar issues. FMCSA guidance Q12 addresses what is required when an ELD is replaced or reset. These events deserve close attention when they occur shortly before or after a crash, or coincide with periods under examination. A reset does not erase the carrier's obligation to produce accurate records, and the gap between what should exist and what was produced is itself a forensic question.
Questions Attorneys Ask About Logbook Falsification
How do you prove a log has been falsified?
Falsification is established by demonstrating that the official record conflicts with what independent sources show actually occurred. Fuel receipts, toll records, GPS data, dispatch messages, shipper records, and the ELD edit history are cross-referenced against the duty status entries. The analysis identifies specific factual conflicts and documents them against the applicable regulatory standard. A single conflict may have an innocent explanation. A pattern of conflicts across multiple records from the same period is harder to account for.
Can ELD data actually be manipulated?
Automatically recorded drive time cannot be reclassified through an edit. What can be manipulated is the assignment of driving to accounts, the use of personal conveyance or yard move designations to absorb drive time, and the editing of non-driving status entries. The audit trail under 49 CFR 395.30 preserves original records, and the edit history records who made changes and when. Whether edits represent legitimate corrections or record adjustments is determined by comparing what was changed against every other available source.
What are ghost logs?
Ghost logs refer to situations where a driver or vehicle was active under an account or status that does not reflect what actually occurred. The concept covers unassigned driving left unclaimed, driving assigned to a secondary account, or in paper log cases, records that were created or altered after the fact. Identifying ghost log patterns requires corroborating the official record against movement data, transaction records, and dispatch instructions from the relevant period.
What if the carrier produced edited logs after the crash?
Post-crash edits are a recognized issue in trucking litigation. The timing, volume, and content of edits following a crash are all forensic questions. Edits made promptly with specific annotations reflecting legitimate driver corrections are different from bulk edits made by carrier staff with vague notes and no driver recertification. The full edit history with timestamps and user identities is the starting point for that analysis.
Do paper log cases still get filed?
Yes. Smaller carriers and some owner-operators still operate under paper log requirements or short-haul exemptions. Paper log analysis requires the same cross-referencing process as ELD analysis, relying more heavily on transaction records, GPS, and shipper documentation to build the comparison timeline.
What if records are missing or incomplete?
Missing records are their own issue in litigation when the carrier had control over the evidence and its preservation was foreseeable following the crash. The analysis documents what records were requested, what was produced, and what gaps exist. An incomplete production can raise questions that a complete one would not.
Discuss Your Falsification Case
Bill reviews all submitted materials and responds within one business day.
Plaintiff and defense. All inquiries are confidential.