Prevention FAQ — FMCSR 387.301(b)
Fleet safety guidance on 387.301(b) based on 230 all-time citations. Pre-trip checks, documentation, root-cause analysis, and self-audit cadence.
- Code:
- 387.301(b)
- Code System:
- FMCSR
- BASIC Category:
- General/Admin
- OOS Eligible:
- No
- Severity Weight:
- N/A
Ranks #1,197 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.4% is below the FMCSR-wide average of 33.2%.
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly do inspectors focus on when checking for 387.301(b) violations?
Our inspection records show 230 all-time citations for this code, with only 1 resulting in an out-of-service order (0.4% OOS rate). This low OOS rate compared to the all-FMCSR average of 31.4% indicates inspectors treat these violations as administrative rather than safety-critical. Inspectors are primarily verifying compliance during routine roadside checks. The fact that enforcement has dropped to zero citations in the last 12 months suggests the issue has largely been addressed across the fleet, or inspectors are focusing resources elsewhere. When this code does appear, it typically occurs in isolation rather than as part of a cascading violation pattern.
› What should our pre-trip checklist include to prevent this violation?
Since 387.301(b) is an administrative/general code with minimal enforcement activity in recent years, a dedicated pre-trip checklist item is low priority relative to mechanical and safety items. However, include a line verifying that all required documentation and compliance records are aboard the vehicle and accessible. Cross-reference this against your carrier's document retention policy. The Freigthliner, Volvo, and Freightliner models (which account for 32 of the top 10 vehicle makes cited) should receive standard compliance-verification procedures. Focus your pre-trip effort on the mechanical and operational codes that drive the majority of roadside violations.
› What documentation must drivers carry and what should the carrier retain?
The code addresses administrative requirements. Drivers must carry any documentation specified by the regulation and keep it accessible during inspection. Carriers should retain records of compliance verification at the time of vehicle dispatch and any corrective actions taken. Given the low citation volume (230 all-time), focus on consistent document organization rather than elaborate redundancy. Establish a single source of truth—driver logbooks, vehicle registration, insurance, and any required permits—organized in a consistent location in the cab. Retain copies of these records at the carrier office for at least 3 years. This baseline approach aligns with general DOT recordkeeping standards and prevents gaps.
› What are the common root causes of this violation?
With zero citations in the last 90 days and none in the last 12 months, root-cause analysis is difficult. However, historical patterns suggest this violation arose from administrative oversight or incomplete documentation practices rather than driver behavior or mechanical failure. The small carrier cohort (Knowles Trucking LLC with 3 citations, Major Transportation Services Inc and TMT Trucking LLC with 2 each) suggests the issue was isolated to a few operations. If your fleet has never been cited for this code, focus prevention resources on the high-frequency violations that appear in your inspection profile. If you do encounter a citation, audit your documentation workflow and driver training on compliance record management.
› How should we verify repairs or compliance corrections before returning a vehicle to service?
Since 387.301(b) is administrative (not mechanical), there is no repair process. If cited, the correction involves verifying that required documentation is complete, properly organized, and accessible in the vehicle. Assign a compliance officer to review the cited vehicle's documentation package, confirm all required forms are present, and certify that the driver understands the storage and accessibility requirements. Document this sign-off in your maintenance or compliance system. Have the driver acknowledge receipt of corrected documentation. This administrative closure removes the violation and prevents recurrence. No road test is required.
› What post-citation review should our fleet conduct?
If your fleet receives a citation for 387.301(b), initiate a brief compliance audit: (1) Review the specific documentation cited as missing or inaccessible; (2) Check whether other vehicles in the same terminal or assigned to the same driver have similar gaps; (3) Confirm your documentation checklist covers all required items; (4) Retrain the driver and supervisor on proper organization and accessibility. Document this review in your safety file. Given that zero citations occurred in the last 90 days nationwide, the issue is likely rare. If you do receive one, treat it as a low-severity administrative correction rather than a system-wide overhaul.
› How does this citation affect our CSA Vehicle Maintenance BASIC score?
387.301(b) is ranked #1178 out of 3,036 FMCSR codes by citation volume and carries a 0.4% all-time OOS rate—significantly below the all-FMCSR average of 31.4%. This indicates the code is weighted as a minor administrative violation, not a mechanical safety issue. Vehicle Maintenance BASIC scores are driven by mechanical and equipment failures, not administrative compliance. A single 387.301(b) citation will have minimal impact on your BASIC. Focus your CSA improvement efforts on codes with higher citation volumes and OOS rates, such as brake, lighting, and tire violations.
› What training topics should we cover with drivers to close compliance gaps?
Given the administrative nature of 387.301(b) and zero citations in the last 12 months, driver training should be brief and focused: (1) Document organization: how to store registration, insurance, permits, and logbooks so they are immediately accessible during inspection; (2) Inspection protocol: what the officer will request and where to direct them; (3) Driver responsibilities: understanding that incomplete or inaccessible documentation delays inspections and creates violations. Tailor training to your fleet's most common citation codes. If vehicle mechanical violations dominate your inspection records, prioritize pre-trip inspection and maintenance training over administrative compliance.
› When should we challenge a 387.301(b) citation via DataQs?
DataQs challenges are appropriate if: (1) the citation is factually incorrect (e.g., documentation was present and accessible; the inspector overlooked it); (2) the violation code was misapplied to a different compliance issue; (3) you have contemporaneous evidence (photos, driver testimony, dispatch records) proving compliance at the time of inspection. Given the low citation volume and administrative nature of this code, false citations are rare. Before filing a challenge, review the inspection report, consult with the cited driver, and verify your documentation standards. If the citation is accurate, accept it, correct the documented gap, and move forward.
› How often should we self-audit for this violation?
Conduct annual self-audits of documentation compliance rather than quarterly or monthly checks. Our inspection records show zero citations in the last 90 days and zero in the last 12 months, indicating this is a low-frequency issue. Include a documentation checklist review in your annual safety program renewal. Verify that all vehicles carry required paperwork and that drivers know where to find it during inspection. If your fleet has never been cited for this code, allocate audit resources to high-frequency violations instead. Scale up documentation audits only if you receive a citation or your inspection profile indicates a compliance gap.
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.