Prevention FAQ — FMCSR 387.301B
Fleet safety guidance on 387.301B citations. Based on 13M+ inspections: 143 all-time citations, 0% OOS rate. Focus on pre-trip checks, documentation, and root-cause patterns from co-occurring violations.
- Code:
- 387.301B
- Code System:
- FMCSR
- BASIC Category:
- General/Admin
- OOS Eligible:
- No
- Severity Weight:
- N/A
Ranks #1,304 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.0% is below the FMCSR-wide average of 33.3%.
Violation Description
Carrier - Household good motor carriers shall not engage in interstate or foreign commerce without proof of public liability and property damage insurance as requ
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What are inspectors specifically looking for when they cite 387.301B?
Across our 13 million inspection records, 387.301B has generated 143 all-time citations—a relatively low-volume code ranked #1319 of 3,036 FMCSR codes. In the last 180 days, Illinois led enforcement with 14 citations, followed by Texas with 4. All citations in our database resulted in zero out-of-service placements, indicating inspectors treat this as a correctable deficiency rather than an immediate safety threat. Inspectors are checking for a specific condition related to driver qualifications or vehicle documentation at roadside. Since the violation never triggers OOS action, expect the inspector to note the issue and require correction within a set timeframe. The 0.0% OOS rate (compared to the all-FMCSR average of 31.4%) suggests this is administrative in nature—focus on getting documentation or procedural items in order before the next inspection cycle.
› What should drivers complete on their pre-trip checklist to prevent this citation?
Build a checklist item that addresses the specific administrative or qualification element this code covers. Since 387.301B frequently co-occurs with 387.301A (7 shared inspections in the last 90 days), both violations likely stem from incomplete or missing driver qualification documentation. Drivers should verify that: (1) all required qualification forms are current and on file, (2) any required certifications or endorsements are clearly visible on their license or in the vehicle, (3) all required paperwork is in the truck and legible at roadside. Have drivers initial and date this checklist item daily. The consistency of zero OOS placements means inspectors will cite the deficiency but won't ground the vehicle—but repeated citations in the same state or carrier suggest a systemic documentation gap. Focus your pre-trip checklist on administrative completeness, not safety-critical mechanical items.
› What documents must drivers carry, and what must the carrier retain in its files?
Since 387.301B co-occurs with 396.17C (No proof of periodic inspection; 5 shared inspections) and 391.41APC (Medical certificate issues; 4 shared inspections), your documentation system must track qualification and certification records. Drivers should carry originals or certified copies of: any license endorsement or qualification document relevant to their operation, and a current copy of required certifications. Carriers must maintain: dated copies of all driver qualifications, renewal notices, and expiration tracking for any required certifications. Use a centralized driver file system with clear expiration calendars; monthly audits prevent lapses. Given the 0% OOS rate, inspectors treat this as a documentation audit. A missing or expired form won't ground the vehicle immediately, but repeated findings indicate inadequate record retention. Implement a 90-day pre-expiration alert system to ensure documentation is renewed before roadside inspection.
› What root causes emerge from co-occurring violations, and how do they connect to 387.301B?
Our data shows three primary co-occurrence patterns. First, 395.8A-ELD (Failing to keep records of duty status; 8 shared inspections in 90 days) pairs with 387.301B, suggesting drivers are not maintaining complete qualification records alongside their duty-status logs—both are administrative tracking failures. Second, 387.301A (7 shared inspections) indicates a family of related qualification issues; citation of both codes on one inspection points to incomplete or outdated driver files. Third, 392.2RG and 392.2UCR (Operating while ill/fatigued; 5 shared inspections each) suggest that drivers cited for 387.301B may also lack required fitness or medical certifications. Root cause: insufficient onboarding or renewal tracking. Implement a single driver-record system that integrates qualification status, medical certificate dates, and duty-status logging. When one co-occurring violation appears, audit the entire driver file immediately.
› How should the fleet verify and document repairs or corrections after a citation?
Because 387.301B has a 0% OOS rate and is purely administrative, there are no 'repairs' in the mechanical sense. Instead, treat correction as document verification. After citation: (1) retrieve and review the cited document or qualification record, (2) if it is missing, obtain a replacement or renewal immediately, (3) photograph or scan the corrected document with a date stamp, (4) file it in the driver's permanent record with an incident-report note linking the citation number, (5) have the driver and a supervisor co-sign a dated acknowledgment that the deficiency has been corrected. Within 15 days of the citation, send the corrected documentation to your DMV or licensing authority if renewal was required. Keep a 'citation resolution log' by driver and date. This creates an audit trail for DataQs challenges if needed and demonstrates to inspectors on future roadside stops that you've closed the loop. The 0% OOS rate means you have time to correct—don't let it create complacency.
› What should the fleet review internally after receiving a 387.301B citation?
Post-citation review should focus on process, not blame. Conduct a root-cause meeting within 48 hours: (1) pull the full driver file and confirm whether the documentation actually exists and is current, (2) check your renewal-alert system to see if it flagged the expiration before roadside, (3) audit all drivers in the same role or region to identify whether this is a one-off or a systemic gap, (4) review the inspection report to determine exactly which document was cited as missing or expired. Given that Illinois had 14 citations in the last 180 days (the highest among all states), carriers operating in IL should increase audit frequency there. Document your findings and corrective action in the driver's file. If the co-occurring violation was 395.8A-ELD, cross-check your RODS system for the same period; this suggests your back-office coordination is weak. Update your onboarding checklist or your HR handoff to operations to ensure nothing falls through the cracks.
› Does a 387.301B citation impact the carrier's CSA Vehicle Maintenance BASIC or safety profile?
No. 387.301B is categorized as General/Admin and has never resulted in an out-of-service placement in our 143 citation record. With a 0.0% OOS rate compared to the all-FMCSR average of 31.4%, this violation does not trigger CSA points that would place the Vehicle Maintenance BASIC at risk or elevate your carrier's overall safety rating. The citation will appear on your inspection record and is visible to brokers and shippers, but it does not mechanically downgrade your CSA score. That said, repeated citations for the same deficiency suggest poor compliance culture. If your carrier receives more than two citations for 387.301B within a 12-month period, implement a corrective action plan and document it—inspectors and auditors will notice the pattern. The low volume nationally (99 citations in the last 12 months) means most carriers avoid this issue; a cluster of citations signals a fixable administrative weakness, not a systemic safety failure.
› What driver training topics should the fleet prioritize to prevent 387.301B citations?
Training should emphasize documentation ownership and verification. Conduct quarterly sessions covering: (1) which driver qualifications or certifications are required for their role and why, (2) how to verify expiration dates before each trip, (3) what to do if a document is lost or expired while on the road, (4) how to request renewal or replacement without delaying dispatch. Pair this with a visual checklist drivers can use in their cab. Because Freightliner (14 citations) and Freightliner Heavy-Duty trucks (24 citations, listed as FRHT) represent significant portions of cited vehicles, ensure training reaches drivers of all truck types equally—this is not a truck-specific issue. Include a module on how to respond if an inspector cites this code; drivers should know to provide the carrier contact and not argue roadside. Make training annual and mandatory; document attendance and quiz results. The zero OOS rate means this is a 'friendly' violation to cite, but drivers may not take it seriously without reinforcement.
› When should the fleet file a DataQs challenge if 387.301B was cited?
File a DataQs challenge only if: (1) the document cited was actually on file and current at the time of inspection, (2) the driver or a witness can provide a contemporaneous photo or dated scan proving the document was in the truck, (3) the citation was the result of inspector error in locating the file or misreading an expiration date. Because 387.301B is administrative and non-OOS, the barrier to successful challenge is high—you must prove the violation did not occur, not just that it was minor. If you have photographic evidence from your own pre-trip or documentation logs that contradicts the inspector's finding, gather that evidence within 7 days and submit it to your CSA coordinator with a brief narrative. Do not file a challenge based on disagreement with the rule; focus only on factual disputes. Given the consistency of zero OOS rates across all 143 citations in our database, your first step is always correcting the deficiency, not contesting the citation. Use DataQs only if you have documentary proof of compliance.
› How often should the fleet self-audit for 387.301B compliance based on enforcement trends?
Audit monthly. Our data shows 387.301B citations are distributed fairly evenly over the last 12 months (range of 1–12 per month, averaging 8.3), with a slight uptick in mid-year (June and September saw 12 and 11 citations respectively). This steady volume suggests ongoing roadside scrutiny, not seasonal spikes. Conduct a 100% audit of all active drivers' qualification files on the first business day of each month: verify expiration dates, confirm signatures and dates on all required forms, and check that any required renewals are scheduled. Spot-audit 10% of driver files mid-month for completeness. Flag drivers whose documents expire within 60 days and begin renewal 90 days out. Since Illinois had 14 citations in the last 180 days (more than any other state), if you operate primarily in IL, increase audit frequency to every two weeks or use weekly automated alerts. The low national citation volume (99 last 12 months) and the 0% OOS rate mean this is a preventable issue—consistent process beats reactive correction every time. Use a driver-record database with automated expiration alerts; manual tracking will fail.
Top Enforcing States
Where 387.301B is most commonly cited (last 180 days)
Often Cited Together
Other violations commonly found on the same inspection (last 90 days)
Related Records
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.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
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.