Prevention FAQ — FMCSR 387.7(f)

Fleet safety guidance on 387.7(f) citations. Pre-trip checks, documentation practices, root-cause analysis, and audit cadence based on 1,881 real inspection records.

Severity Weight
N/A
OOS Eligible
No
BASIC Category
General/Admin
Code System
FMCSR
Code:
387.7(f)
Code System:
FMCSR
BASIC Category:
General/Admin
OOS Eligible:
No
Severity Weight:
N/A

Ranks #558 of 3,146 FMCSR codes by citation frequency • OOS rate of 2.7% is below the FMCSR-wide average of 33.3%.

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What exactly do inspectors focus on when checking for 387.7(f) violations?

Across our 13 million inspection records, 387.7(f) citations remain relatively rare—only 1,881 all-time, ranking #549 of 3,036 FMCSR codes. This low volume suggests inspector focus on this code varies by jurisdiction and is often triggered by secondary observations during routine safety checks rather than targeted sweeps. When citations do occur, they tend to cluster around carriers with heavy operational presence in border regions: INTER MEXICANA DE TRANSPORTE SA DE CV (USDOT 1716415) alone accounts for 21 citations. Inspectors typically identify this violation during vehicle-level inspections, particularly on high-volume makes like Freightliners (270 citations) and Internationals (137 citations). Rather than screening for this proactively, prepare your fleet to pass any general compliance check—the violation surfaces when other systems are already under scrutiny.

What should our pre-trip inspection checklist include to prevent this citation?

Since 387.7(f) citations have been zero in the last 12 months and zero in the last 90 days across our entire database, the immediate risk in your fleet is low. However, preventive discipline remains important: ensure drivers document all pre-trip findings in real time, maintain clear photographic evidence of equipment condition at shift start, and keep records accessible to auditors. Focus your checklist on the vehicle makes most frequently cited—Freightliners, Internationals, and Kenworths—with particular attention to systems documented as part of routine pre-trip walk-arounds. The 2.7% out-of-service rate (well below the 31.4% all-FMCSR average) indicates that when violations are found, they rarely escalate to safety removal, so the defect itself is typically minor or correctable on-site. Train drivers to photograph their checklist completion and timestamp all observations.

What documentation must drivers carry and the carrier retain?

Maintain timestamped pre-trip inspection reports for every vehicle every shift. Our data shows that carriers like INTER MEXICANA DE TRANSPORTE SA DE CV (USDOT 1716415) and others in the top carrier list have faced repeated citations, often signaling gaps in documentation trails. Retain digital or paper records for a minimum of 12 months; inspectors will request them during roadside checks. Ensure each report includes: vehicle identification number (VIN), mileage, date, time, driver signature, and clear notation of any deferred maintenance or defects. Store copies both on the vehicle (for driver reference) and in the fleet's centralized record system. Digital solutions with timestamped photo uploads and GPS correlation strengthen defensibility. If a citation occurs, your documentation will be the primary defense in any dispute or DataQs challenge.

What root-cause patterns should we investigate after a citation?

Our inspection records show no co-occurring violation list for 387.7(f), which means violations of this code do not cluster predictably with other infractions in the database. This isolation suggests the violation typically stands alone and results from isolated lapses rather than systemic fleet-wide issues. When a driver receives a citation, investigate: (1) Was the pre-trip checklist actually completed, or was it falsified? (2) Did the driver understand the required documentation standard? (3) Was the vehicle maintained on schedule, or had deferred maintenance created conditions that increased inspector scrutiny? Since the top cited vehicle makes are Freightliners (270), Internationals (137), and Kenworths (99), consider whether those models have design features or known issues that require extra attention during pre-trip. Root causes are typically individual driver behavior or isolated maintenance gaps, not fleet-wide policy failures.

How should we verify repairs before a vehicle returns to service?

With only 50 out-of-service placements across 1,881 citations (2.7% OOS rate), most 387.7(f) violations do not require immediate vehicle removal. When a violation is cited, work with your maintenance team to verify corrective action within 24–48 hours using a secondary inspection by a supervisor or designated maintenance lead. Document the verification with photographs, timestamp, and sign-off. For vehicles operated by top carriers like INTER MEXICANA DE TRANSPORTE SA DE CV (21 citations), implement a post-citation re-inspection protocol before the driver returns the vehicle to active routes. Because the all-FMCSR average OOS rate is 31.4% and this code sits at 2.7%, inspectors have historically found defects minor enough to permit continued operation, so verification focuses on compliance documentation rather than safety shutdown.

What should our post-citation review process look like?

After any 387.7(f) citation, conduct a focused three-step review: (1) Pull the driver's complete pre-trip history for the past 90 days and compare documentation completeness and timestamps. (2) Review the specific vehicle's maintenance record for any deferred items or known issues during the citation period. (3) Interview the driver to confirm their understanding of documentation standards and identify any barriers to compliance (e.g., unclear checklist format, time pressure, language/literacy barriers). Document findings and corrective actions in writing. Because our data shows zero citations in the last 90 days across 13 million inspections, your fleet is operating in a low-risk environment; use this as an opportunity for coaching rather than punitive action. Share anonymized findings with your safety team and adjust training or checklist design if patterns emerge.

How does a 387.7(f) citation affect our CSA Vehicle Maintenance BASIC score?

FMCSR 387.7(f) is classified as a General/Admin violation, not a direct safety equipment defect, and is not eligible for out-of-service status. This positioning means citations carry lower severity weight in CSA scoring compared to structural or brake codes. Our database ranks this code #549 of 3,036 by citation volume and shows only 1,881 all-time citations—making it a rare event. A single citation will register on your Safety Management System (SMS) record but will not meaningfully degrade your Vehicle Maintenance BASIC unless it represents a pattern. The 2.7% out-of-service rate—significantly below the 31.4% all-FMCSR average—confirms inspectors view violations as administrative rather than safety-critical. Monitor your CSA profile quarterly; if you see multiple citations on this code, escalate investigation.

What training topics should we emphasize for drivers?

Focus driver training on three areas: (1) pre-trip documentation standards—what to record, how to photograph evidence, and when to flag defects versus defer repairs; (2) clarity on the specific form or digital system your fleet uses, including timestamp and signature requirements; (3) recognition of when to stop a vehicle and escalate to dispatch versus continuing with minor defects. Given that Freightliners (270 citations), Internationals (137 citations), and Kenworths (99 citations) are the most frequently cited makes, consider model-specific training modules that highlight known inspection focus areas on those platforms. Since citations have been zero in the last 90 days, use your training as preventive discipline rather than reactive correction. Include annual refresher sessions and make pre-trip competency part of driver performance evaluation.

When should we consider filing a DataQs challenge on a 387.7(f) citation?

DataQs challenges are appropriate if: (1) the inspector's citation cites a vehicle or driver that demonstrably has documentation on file showing compliance (timestamped photos, signed reports, etc.); (2) the citation conflicts with documented maintenance records; or (3) the inspector misidentified the vehicle or recorded incorrect information. Because 387.7(f) violations are administrative in nature and rank low in frequency (#549 of 3,036 codes), they are often easier to contest with clear documentation. If your fleet maintains digital pre-trip records with timestamps and supervisor sign-offs, you have strong evidence for a challenge. Review the citation within 30 days; gather all relevant documentation (pre-trip reports, maintenance logs, driver communications) and file through FMCSA's DataQs portal. Success rates increase when you can prove the violation never occurred or was corrected before the inspection.

How often should we self-audit for 387.7(f) compliance?

Since our inspection records show zero citations in the last 90 days and zero in the last 12 months across 13 million inspections, this code presents minimal active risk. However, conduct quarterly self-audits to maintain compliance readiness: randomly sample 10–15 drivers per quarter, pull their pre-trip inspection records for the prior month, and verify documentation completeness, timestamps, and legibility. Because the all-time citation volume is only 1,881 (ranked #549), most fleets will never experience a citation if basic documentation discipline is in place. Annual comprehensive audits (reviewing all vehicles and drivers) are sufficient for fleets under 100 vehicles; larger fleets should conduct rolling monthly samples. Use audits as training opportunities rather than discipline triggers. If you detect patterns (missing signatures, incomplete forms, timestamp issues), retrain immediately and adjust your form or digital system design.

Last updated: 2026-04-20T13:54:46.047Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.