Prevention FAQ — FMCSR 387.403B

Fleet safety guidance for 387.403B citations. Based on 11 all-time citations and co-occurrence patterns with duty-status and fatigue violations, this FAQ covers inspector focus areas, pre-trip protocols, and root-cause analysis.

Severity Weight
N/A
OOS Eligible
No
BASIC Category
General/Admin
Code System
FMCSR
Code:
387.403B
Code System:
FMCSR
BASIC Category:
General/Admin
OOS Eligible:
No
Severity Weight:
N/A

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

Violation Description

Freight Forwarder - No evidence of public liability and property damage insurance

Prevention FAQ for Fleet Managers

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

What specific items do inspectors focus on when checking for 387.403B violations?

Our inspection records show that across 13 million roadside inspections, 387.403B has been cited only 11 times all-time, making it one of the rarest General/Admin violations. In the last 180 days, Illinois accounted for 6 of these citations. Inspectors examining this code are likely scrutinizing records and documentation related to the specific regulatory requirement. Since this violation has never resulted in an out-of-service placement (0.0% OOS rate across all citations), focus is on paperwork completeness and accuracy rather than immediate safety stand-downs. Expect inspectors to review driver logs, vehicle records, and maintenance documentation during the inspection window. The rarity of citations suggests that most fleets maintain adequate compliance, so violations often reflect isolated documentation lapses rather than systemic issues.

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

Given that 387.403B violations frequently co-occur with 387.403A (6 shared inspections in the last 90 days), your pre-trip checklist should include verification that all required administrative records and certifications are current and available in the vehicle. Drivers should physically confirm that documentation files are complete before departure. For fleets operating commercial tractors and trailers (Freightliner units represent 4 of the 11 all-time citations), assign a spotter to verify paperwork before each shift. Create a simple driver sign-off: driver confirms vehicle documents are present, legible, and match the vehicle identification. This takes under two minutes and directly addresses the co-occurrence pattern with 387.403A, suggesting both codes flag related administrative compliance gaps.

What documents must drivers carry, and what should the fleet retain in its records system?

While the co-occurring violations (387.403A, 395.8A-ELD, 387.301A, and 387.301B) appear in 6 shared inspections each in the last 90 days, the pattern suggests a broader administrative documentation standard. Drivers should carry all required proof of compliance documents in the vehicle at all times. The fleet should maintain a digital or physical master file of current certifications, licenses, and compliance records indexed by vehicle and driver. Establish a weekly audit of these files to confirm no gaps. Since KLM 20 LLC (USDOT 4459130) has the highest citation count for this code (2 citations all-time), review whether carriers in similar operating profiles are storing or organizing documents in ways that make them difficult for inspectors to locate during roadside checks. Accessibility and organization matter as much as possession.

Why does 387.403B appear alongside fatigue and duty-status violations? What's the root cause?

Our 90-day data reveals a striking pattern: 387.403B co-occurs with 395.8A-ELD (Failing to keep RODS) and 392.2UCR (Operating while ill or fatigued) in 6 and 5 shared inspections respectively. This suggests that drivers cited for 387.403B often also show gaps in electronic logging device compliance and fatigue management. The likely root cause is insufficient driver training on administrative compliance or rushed pre-trip procedures during fatigue conditions. When drivers are fatigued or running behind schedule, documentation shortcuts increase. Additionally, False record of duty status (395.8E) appears in 4 shared inspections, pointing to intentional or careless record falsification. Address this by linking your fatigue-management training directly to administrative discipline: emphasize that incomplete or inaccurate records during fatigued operations trigger multiple citations and undermine your entire compliance profile.

How should we verify that repairs or compliance actions are complete before a vehicle returns to service?

Since 387.403B citations never result in out-of-service orders (0.0% OOS rate), vehicles cited for this violation remain in service—but the fleet must ensure corrective documentation is complete before the next inspection. Create a remediation checklist: (1) identify the specific documentation or record gap cited; (2) obtain or correct the missing item; (3) have a supervisor independently verify the correction; (4) photograph or scan the corrected records; (5) file in your audit trail indexed by vehicle, date, and citation number. For fleets with Freightliner tractors (4 of 11 all-time citations), implement a post-citation vehicle hold: the vehicle does not resume interstate operations until a manager signs off on the remediation package. This prevents repeated citations and demonstrates due diligence if a DataQs challenge is needed.

What should our post-citation review process look like?

When a driver or vehicle receives a 387.403B citation, initiate a three-part review within 48 hours. First, determine the exact documentation that triggered the violation and verify it is now corrected and accessible. Second, conduct a brief driver interview to understand whether the gap was caused by lack of training, poor organization, vehicle issue, or time pressure. Third, check whether the same vehicle or driver has any citations in the prior 24 months for 387.403A, 395.8A-ELD, or 387.301A/B (the most common co-occurring codes). If yes, escalate to a refresher training session and a fleet-wide audit of similar vehicles. Since only 8 citations occurred in the last 12 months across all fleets, a single citation is notable and warrants focused investigation rather than dismissal as minor.

Does 387.403B affect our CSA Vehicle Maintenance BASIC or safety profile?

At 11 all-time citations, 387.403B is ranked #2167 of 3,036 FMCSR codes by enforcement volume—making it statistically rare. The national average out-of-service rate across all FMCSR codes is 31.4%; 387.403B's 0.0% OOS rate means it is categorized as a General/Admin violation with no direct severity in roadside enforcement. However, CSA scoring depends on your carrier's BASIC composite calculations, which aggregate violation severity and frequency across multiple inspection events. A single 387.403B citation is unlikely to materially impact your Vehicle Maintenance BASIC. That said, the co-occurrence with fatigue (392.2UCR, 5 shared inspections in 90 days) and false duty records (395.8E, 4 shared inspections) can harm your Hours of Service or Vehicle Maintenance profiles. Focus remediation on preventing the co-occurring codes, not the 387.403B citation itself.

What training topics should drivers complete to prevent 387.403B citations?

Given that the top three co-occurring violations are 387.403A (6 shared inspections), 395.8A-ELD (6 shared inspections), and 387.301A (6 shared inspections), your driver training should integrate administrative compliance as a core topic. Include: (1) a walkthrough of required documents and where they belong in the vehicle; (2) step-by-step ELD compliance and duty-status record accuracy; (3) pre-trip checklist execution with supervisor sign-off; (4) time-management tactics to prevent rushing and documentation shortcuts; (5) what an inspector will ask and where they will look. For fleets operating Freightliner and Hyster equipment (which account for 5 of 11 all-time citations), add vehicle-specific document-storage walkthroughs during onboarding. Use your 387.403B citation as a case study: show drivers the actual violation, explain the fix, and reinforce the link between thorough pre-trip checks and clean inspections.

When should we consider filing a DataQs challenge against a 387.403B citation?

DataQs challenges are appropriate when the citation is factually inaccurate or the inspector documented the violation incorrectly. For a 387.403B administrative violation, a challenge may be warranted if: (1) the cited document was actually present and legible in the vehicle but the inspector missed it or recorded it incorrectly; (2) the inspector failed to follow proper examination procedures; or (3) your fleet has documented evidence (photos, logs, maintenance records) proving compliance at the time of inspection. Since 387.403B citations are extremely rare (11 all-time, 8 in last 12 months), a citation is worth reviewing for accuracy. However, do not challenge merely to avoid the minor compliance correction. If the violation is factual, correct the documentation and move forward. Challenge only if you have clear evidence the inspector erred.

How often should we self-audit for 387.403B compliance issues?

Our 90-day enforcement trend shows 6 citations; in the last 12 months, 8 citations occurred across all fleets. This is a low-frequency violation, suggesting that most administrative documentation practices are sound. However, implement a quarterly self-audit (every 90 days) for fleets with 20+ vehicles and an annual audit for smaller fleets. During each audit, randomly select 5–10 vehicles, conduct a full roadside-style document inspection, and verify all required records are present and current. If you discover gaps, correct immediately and brief drivers on the issue. The data suggests that once a vehicle is cited for 387.403B, the problem is resolved; we see no patterns of repeat citations on the same vehicle or carrier (only KLM 20 LLC has 2 citations, all-time). Use the quarterly cadence as a preventive measure rather than a response to frequent violations.

Last updated: 2026-04-20T16:47:46.455Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 387.403B is most commonly cited (last 180 days)

1. Illinois
14
OOS 0.0%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.