Prevention FAQ — FMCSR 387.307

Across our 13 million inspection records, 387.307 citations are extremely rare—only 3 all-time in our database, with zero in the last 12 months. This low volume means inspectors encounter this violation infrequently, but when they do, they're checking for compliance with a specific administrative or documentation requirement tied to carrier operations. Since this code ranks #2551 of 3,036 FMCSR codes, focus your pre-inspection briefing on the exact regulatory language rather than expecting high inspector familiarity. Ensure your safety manager reviews the precise requirement with drivers before roadside encounters. The fact that no violations were placed out of service suggests the violation is documentary or procedural in nature, not a direct safety defect.

Given the low citation volume, your pre-trip checklist should focus on administrative completeness rather than mechanical systems. Work with your compliance team to identify the exact documentation or record-keeping element that 387.307 covers, then create a driver-facing checklist item that confirms that item is present, legible, and up to date before departure. For example, if the code relates to driver qualifications or logbook setup, add a specific checkbox that the driver verifies this element meets requirements. Since only 3 citations exist in our records, treat this as a due-diligence item—low-frequency but high-consequence if missed during a full roadside inspection. Include it in your standard pre-trip routine even though the likelihood is low.

Our data shows 3 citations across carriers including J B HUNT TRANSPORT INC, U S GLOBAL INC, and GHOTRA XPRESS INC, indicating no carrier is immune. Establish a document-retention policy that covers whatever administrative requirement 387.307 specifies—likely driver qualification files, logbook setup records, or vehicle assignment documentation. Drivers should carry proof of compliance (e.g., updated qualifications, correct logbook entries, or required authorizations) in their cab. Retain originals in your fleet management system for at least 36 months to support any post-inspection defense or DataQs challenge. The zero out-of-service rate across all 3 citations suggests inspectors are issuing warnings or minor citations that don't remove vehicles; nevertheless, documentation completeness is non-negotiable for fleet-wide compliance and audit readiness.

With only 3 citations in our database, co-occurrence patterns are limited; however, peer codes in the General/Admin category offer insight. Administrative violations like 390.21(a) (vehicle marking requirements) and 390.21(b) (USDOT number display) together account for 39,116 citations at 0.0% out-of-service rates—suggesting that 387.307 likely shares a pattern of incomplete or improperly maintained records. Root causes typically include: (1) inconsistent document-management practices across drivers, (2) gaps between policy and execution at the terminal, or (3) training lapses when hiring or onboarding. Conduct a post-citation review asking whether the cited driver received the same training as others, whether your document-control system flagged the issue, and whether supervisors spot-checked compliance before dispatch.

Since 387.307 citations are administrative rather than mechanical—evidenced by the 0.0% out-of-service rate—'repair' means correcting documentation or compliance gaps, not vehicle defects. After a citation, require the driver and a supervisor to jointly complete the missing or erroneous item (e.g., updating a record, re-signing a form, or re-entering correct information). Document this corrective action with date, time, and signatures in your fleet management system. Assign a compliance manager to verify the correction matches the citation and inspector's note. Only then re-authorize the vehicle for revenue service. This administrative verification step is as critical as a mechanical repair—incomplete corrections invite repeat citations during the next roadside stop.

After any 387.307 citation, your safety manager should: (1) interview the cited driver to understand how the administrative lapse occurred, (2) pull that driver's file and compare it to your policy and three other drivers' files to identify system-wide gaps, (3) review your document-management system logs to see whether supervisors received or acted on compliance alerts, and (4) assess whether your pre-trip or pre-dispatch checklist caught the issue (or why it didn't). Document findings in your fleet's safety record, then close the loop with a corrective action—whether it's retraining the driver, fixing a checklist item, or improving your document-tracking system. Even though 387.307 citations are rare, each one signals a process failure worth investigating.

Our data shows 387.307 ranks #2551 of 3,036 FMCSR codes—among the lowest citation frequencies in the database. With only 3 all-time citations and zero in the last 12 months, this violation is unlikely to materially impact your CSA Vehicle Maintenance BASIC score. However, CSA scoring is cumulative and includes all violations; if your fleet receives multiple citations across different codes, even low-frequency violations add points. Monitor your BASIC closely via your CSA portal. If you do receive a 387.307 citation, ensure it doesn't reflect a broader pattern of neglected documentation or administrative compliance—that pattern could signal vulnerabilities in other administrative codes and invite increased inspection focus.

Our citation data shows 387.307 violations across three different carriers (J B HUNT TRANSPORT INC, U S GLOBAL INC, and GHOTRA XPRESS INC) and multiple vehicle makes (2 FRHT, 1 HYTR, 1 WANC), indicating no single driver type is at fault. Design training that covers: (1) the specific administrative requirement tied to 387.307, (2) when and how to complete or verify the required documentation, (3) what to do if a document is missing or incorrect before dispatch, and (4) how to respond if an inspector questions the item at roadside. Include a walkthrough of your pre-trip checklist item so drivers understand why it matters. Because this violation is rare, drivers may not encounter it in their peer discussions—make your training explicit and include it in new-hire onboarding.

Given the extremely low citation frequency—only 3 in our 13 million-record database—any 387.307 citation warrants close scrutiny for accuracy. Review the inspector's written description against your documentation and your understanding of the requirement. If you believe the inspector misinterpreted the regulation, misread your records, or cited you in error, file a DataQs challenge with FMCSA within 30 days of the citation. Include your documented evidence (e.g., photos, dated records, policy documentation) that shows compliance. Since 387.307 violations are so uncommon, inspectors may be less familiar with the requirement—an error or interpretation gap is plausible. A successful DataQs challenge removes the citation from your safety record and CSA scores.

Our data shows zero citations in the last 90 days and zero in the last 12 months, despite the code existing in our database. This suggests the violation is either extremely uncommon or has been largely phased out of enforcement. Nevertheless, include a 387.307 compliance check in your annual audit cycle—not monthly or quarterly, but once per year as part of your broader administrative-compliance review. During that audit, confirm that 100% of your drivers have the required documentation in place and that your pre-trip checklist covers the item. If you do receive a citation, escalate to a monthly spot-check for 60 days to ensure it was an anomaly and not a systemic gap. The rarity of this violation means it's a low-priority focus but should not be ignored entirely.