Prevention FAQ — FMCSR 390.35: False Record Entries

Inspectors cite 390.35 when they find fraudulent or intentionally false entries in driver logbooks, inspection reports, maintenance records, or pre-trip documentation. Across our 13 million inspection records, we see 640 citations in the last 12 months, with Pennsylvania accounting for 72 of those in the past 180 days—the highest enforcement volume by far. Illinois follows with 42 citations and a 9.5% out-of-service rate, suggesting inspectors there may be escalating when falsification is suspected. In most states (PA, IA, ID, CO, KS) the OOS rate sits at 0%, meaning inspectors typically issue a citation without removing the vehicle. North Carolina is an outlier at 75% OOS rate on just 4 citations—a sign that when falsification is flagged there, conditions warrant immediate removal. Focus your pre-inspection preparation on document authenticity and consistency across all records.

Your pre-trip checklist must explicitly require drivers to verify that all logbook entries, vehicle inspection reports, and maintenance records are accurate and complete before submission. Include checkpoints for: (1) timestamp and odometer consistency across all logs; (2) duty status matching actual vehicle movement and location data; (3) vehicle condition observations that match prior maintenance records; (4) driver signature and date on all documents; (5) legibility and correction procedures (strike-through, initials, date for any changes—never erasure or white-out). Require drivers to flag any discrepancies immediately rather than backfilling or estimating. Make it clear that guessing times, inventing inspections, or altering prior records violates 390.35 and triggers enforcement. Assign one person per shift to spot-check three random logbooks daily for internal consistency before the driver leaves the lot. This preventive step catches errors before inspection.

Drivers must carry originals or legible copies of daily vehicle inspection reports (DVIRs), logbooks (paper or electronic), and pre-trip checklists for the current and prior 7 days. The fleet must retain all of these—plus maintenance records, service logs, and any corrected or amended logbooks—for a minimum of 6 months, searchable by vehicle unit number and driver name. Electronic logging device (ELD) data and any corrections made through the ELD system must be audit-logged with timestamp and reason code. If a driver corrects an entry, it must remain visible in the system with an explanation appended. Do not delete or overwrite original entries. Establish a naming convention and backup protocol so that if an inspector requests the records for a specific date, you can produce them within 5 minutes. Our data shows 27 shared inspections linking 390.35 to 396.17C (no proof of periodic inspection), suggesting incomplete or missing documentation is a common root cause—retain everything, even draft versions, to prove due diligence.

Our inspection records over the last 90 days show three patterns: (1) 390.35 appears alongside 396.17C (no proof of periodic inspection) in 27 shared inspections—drivers or fleet staff are either skipping documented inspections or falsifying completion records. Implement a tied logbook-to-inspection workflow where no vehicle is released until a completed DVIR is attached. (2) 27 inspections pair 390.35 with 392.2 (operating while ill/fatigued), in variants SLLIRP, UCR, and SLLSR—fatigue or impairment may lead drivers to fabricate duty status or inspection details to hide violations. Require fitness-for-duty checks before dispatch and train drivers that reporting fatigue is never a violation, falsifying logs is. (3) 18 inspections link 390.35 to 391.11B2-Q (English language proficiency failure), suggesting language barriers may drive copying or guessing on forms rather than direct, accurate entry. Provide translated checklists, audio guides, or buddy systems for drivers with language constraints. Each pattern points to a systemic gap in training, process, or support—address the upstream cause, not just the citation.

After any maintenance or correction tied to a prior false-entry citation, require a supervisor witness sign-off on the corrected record. The process: (1) Driver or technician writes the correction in a log correction form (date, reason, corrected data, signature, timestamp). (2) Supervisor reviews the original record, the correction, and any supporting evidence (receipt, photo, technician note). (3) Supervisor approves and signs—this becomes the official amendment, filed with the original. (4) Before the vehicle returns to revenue service, the driver and supervisor jointly review the corrected documents to confirm accuracy and consistency. (5) Scan and back up the signed correction form to your fleet management system. This audit trail proves the fleet did not hide or alter records retroactively. If the original falsification involved a maintenance claim (e.g., driver said brakes were checked when they weren't), require a re-inspection by a third-party mechanic and retain the report. This is especially important given our data shows paired citations with inspection codes—correcting one without verifying the underlying fact invites another citation.

Within 48 hours of a 390.35 citation, run a structured review: (1) Identify the specific false entry (logbook time, DVIR checkbox, maintenance claim, etc.) and the inspector's evidence. (2) Pull the driver's prior 90 days of records and compare them for similar patterns—if one entry is falsified, others may be too. (3) Interview the driver to understand why (fatigue, confusion, pressure, language barrier, system glitch). (4) Check the vehicle's maintenance history against the cited DVIR claim—if the driver claims an inspection was done but maintenance records don't match, that's a process failure. (5) Review what tool or system the driver used (paper logbook, ELD, inspection app) and whether it had built-in safeguards or editing gaps. (6) Document findings and corrective action in writing, signed by driver and supervisor. (7) If this is the driver's second 390.35 in 12 months, escalate to retraining or reassignment. Our data shows 640 citations in the last 12 months; carriers with multiple drivers on this code often have systemic training or process issues, not individual bad actors.

390.35 (false entries) carries a CSA severity weight of 10—well above the all-FMCSR average OOS rate of 31.4%, yet 390.35 itself has a 3.6% OOS rate across our 13 million records. This means inspectors cite it frequently but rarely remove the vehicle, treating it as a compliance violation rather than an immediate safety threat. However, the high severity weight means a single citation contributes significantly to your BASIC score. Nationally, 390.35 ranks #735 by volume—not a top-tier code—so one citation won't dominate your profile, but clusters will. The real risk: false entries in maintenance or inspection records obscure actual safety defects. If a driver falsifies a DVIR (checking boxes for brake inspection when none occurred), and later the brakes fail, you face liability and CSA escalation under the Vehicle Maintenance BASIC for negligent maintenance oversight. Prevent this by auditing a random 5% of DVIRs monthly and cross-checking them against actual service records. One 390.35 citation is a warning; multiple citations in a 12-month window signal a broken record-keeping process that auditors will scrutinize.

Conduct annual training covering: (1) What counts as a false entry: guessing times, backdating logs, copying prior-day entries, leaving blank boxes and filling them later, falsely checking inspection items, or approximating odometer readings. (2) Logbook best practices: real-time entry as duty status changes, correction procedures (no erasure, use official correction form), and what to do if the driver discovers a mistake hours later (strike through with date and initial, append explanation—never rewrite). (3) Inspection integrity: why every DVIR checkbox matters, that reporting a defect is never punished, and how to document actual observations rather than assumed conditions. (4) When to ask for help: if the driver doesn't understand a form, is fatigued, or is unsure if an entry is correct, they must flag it before submission, not fabricate. (5) Consequences: a 390.35 citation affects CSA and hiring, falsification can lead to disqualification, and repeat offenders may face removal. Top vehicle makes cited (FORD 185, FRHT 116, DODGE 91) suggest these vehicles are common in violation fleets—tailor training to address the makes in your fleet. Make training mandatory upon hire and annually; document attendance and comprehension testing.

File a challenge if: (1) The inspector's evidence does not clearly show intent to falsify—honest mistakes or system glitches are not 390.35 violations; (2) The driver has a documented explanation that shows the entry was corrected or clarified in real time, not hidden or altered after the fact; (3) The record itself is legible, signed, and dated, and any amendments are clearly marked with reason codes and supervisor approval—this demonstrates accountability, not fraud; (4) The inspection report lacks specificity (e.g., "driver logbook contains false entries" without citing which entries or what the false claims were). Our data shows a 3.6% all-time OOS rate on 939 citations, much lower than the 31.4% FMCSR average, suggesting inspectors apply this code conservatively. A poorly documented citation may be vulnerable. However, do not challenge frivolously—if the driver admits to guessing or backfilling, the citation is solid. Consult your safety director and legal counsel before filing; DataQs challenges require specificity and supporting documents within the appeal window.

Run audits monthly on a rolling basis. Our 90-day trend shows 118 citations vs. 640 in the last 12 months—roughly consistent monthly volume with peaks in June (74 citations) and lows in April 2026 (5 citations). Given this volatility and the fact that false entries are often discovered during routine inspection, do not rely on annual spot checks. Instead: (1) Each month, randomly select 10–15 drivers' prior 30-day logbooks and DVIRs and cross-check entries for consistency (times, odometer progression, duty status changes). (2) Compare logbook claims (e.g., "vehicle inspected") against actual maintenance records for the vehicle. (3) Flag discrepancies (missing inspections, time gaps, odometer reversals) and interview the driver within 48 hours. (4) Document findings and any corrective actions. (5) Trend the audit results—if the same driver appears multiple times, escalate; if the same vehicle shows repeated inconsistencies, investigate the maintenance program. A monthly audit catches problems before an inspector does and demonstrates due diligence if a citation occurs. Given the high citation load in states like Pennsylvania (72 in 180 days), carriers operating there should audit every 2 weeks during high-enforcement seasons.