Prevention FAQ — FMCSR 385.13(d)

Fleet safety guidance on 385.13(d) citations, root causes, prevention checklists, and audit protocols based on 10 all-time citations across 13 million inspections.

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

Ranks #2,215 of 3,146 FMCSR codes by citation frequency • OOS rate of 80.0% is above the FMCSR-wide average of 33.3%.

Violation Description

Failing to comply with an Unsatisfactory Out of Service Order

Prevention FAQ for Fleet Managers

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

What exactly do roadside inspectors focus on when checking for 385.13(d)?

Across our 13 million inspection records, we see 10 all-time citations for this code—a rare violation that ranks #2191 of 3,036 FMCSR codes. Our data shows this code has been cited in North Carolina and Texas in the past 180 days (1 citation each). When present, it triggers an out-of-service rate of 80.0%, compared to the all-FMCSR average of 31.4%, indicating inspectors view this violation as serious enough to ground vehicles at a much higher frequency than typical citations.

Inspectors typically verify documentation completeness, carrier compliance with recordkeeping requirements, and proper driver qualification file maintenance. The rarity of citations suggests most carriers maintain adequate compliance, but when inspectors do find violations, they immediately place vehicles out of service in 8 of 10 cases. Focus your inspection preparation on document organization and file accessibility.

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

Build a compliance checkpoint into your pre-trip routine that covers three areas: (1) driver qualification file status—verify the file exists, is current, and contains required certifications; (2) record accessibility—ensure documents are organized and can be produced within minutes during an inspection; (3) driver self-certification—confirm the driver has reviewed their own file status before departing.

While this code itself accounts for only 1 citation in the past 90 days, the 80.0% out-of-service rate when cited means prevention saves significant downtime. Create a laminated checklist card drivers carry that references key file elements: valid CDL, medical certificate, driving history review, and violations log. Weekly spot-checks by safety staff on 10% of your fleet's driver files will maintain alignment.

What documentation must drivers carry and what must the carrier retain?

Drivers must carry a valid CDL and current medical certificate in their possession at all times. The carrier must maintain and produce on demand: the complete driver qualification file (49 CFR Part 391), including application, certification of driving record, medical certificate, and any required endorsement records.

All records must be retrievable within minutes during a roadside stop. Our data shows that when 385.13(d) is cited, 8 of 10 citations result in out-of-service placement, typically because inspectors cannot quickly locate required documentation. Implement a digital backup system (scanned PDFs) in addition to physical files, stored both at the carrier location and accessible via secure cloud. This redundancy eliminates the most common citation trigger: missing or inaccessible paperwork.

What root causes appear behind this violation in our co-occurring violation patterns?

Our inspection records show this code frequently appears alongside specific driver and vehicle defects. In the past 90 days, co-occurring violations include: Disqualified driving status (391.15A-NSIN, 1 shared inspection)—suggesting incomplete driver qualification monitoring; Operating while ill/fatigued (392.2FT, 1 shared)—indicating poor driver fitness certification tracking; and Brake system defects (393.47C/47E, multiple instances)—implying carriers may not be cross-checking vehicle maintenance records with driver files.

The pattern suggests root causes cluster in two areas: (1) failure to validate driver qualification status before or during operation, and (2) poor coordination between driver file maintenance and vehicle inspection teams. Implement monthly audits linking driver files to assigned vehicles and maintenance schedules. When a brake violation is cited, automatically trigger a review of the assigned driver's file currency.

How should we verify repairs or compliance before a vehicle returns to service after a citation?

If a driver or vehicle is cited for 385.13(d), the compliance action is documentation correction, not mechanical repair. Before returning to service: (1) obtain a signed statement from the driver acknowledging they have reviewed their complete qualification file; (2) have safety staff verify all required documents are present and current in the file; (3) create a dated audit log entry noting which documents were verified and their expiration dates; (4) cross-reference the driver's file with the vehicle assignment and maintenance schedule to confirm no conflicts exist.

Document this verification in writing and retain it in the driver's file. Since out-of-service placement occurs in 80.0% of citations for this code, treat the return-to-service approval as a management sign-off, not a clerk task. This ensures the deficiency that triggered the citation—likely missing or inaccessible documentation—is permanently corrected.

What post-citation review should we conduct after our fleet is cited for 385.13(d)?

Immediately after a citation, conduct a three-part review: (1) file audit—pull the cited driver's file and identify which specific documents were missing or inaccessible; (2) fleet-wide scan—check 100% of driver qualification files across your fleet for the same gap within 5 business days; (3) root-cause interview—ask the driver and the staff member responsible for file maintenance why the deficiency occurred and what process failed.

Our data shows only 1 citation in the past 90 days for this code, but when cited, 80.0% result in out-of-service placement. This high severity warrants immediate investigation. Create a corrective action plan addressing both the individual file and the broader system. Document the plan, assign responsibility, and schedule a follow-up verification. This prevents the same citation from recurring within 30 days.

How does this citation impact our carrier's CSA Vehicle Maintenance BASIC or safety rating?

While 385.13(d) ranks #2191 of 3,036 FMCSR codes by citation volume, its out-of-service rate of 80.0% is significantly higher than the all-FMCSR average of 31.4%. This means the violation is treated as severe when cited. A single citation appearing on your FMCSR history will be weighted according to the severity of the deficiency.

Driver qualification file violations, though administrative, directly reflect carrier safety management and can negatively influence your Safety Management BASIC score and CSA percentile. Each out-of-service placement creates a documented compliance failure that auditors and shippers review. Preventing even one citation in a 12-month period is more valuable than remediating after the fact. Implement quarterly self-audits of driver files to ensure you catch gaps before an inspector does.

What training topics should we emphasize with drivers to prevent this violation?

Focus driver training on three areas: (1) file accountability—ensure every driver understands that their qualification file is their responsibility and they must notify management immediately if any required document expires; (2) documentation recognition—train drivers to identify which documents belong in their file and why each is required; (3) carrier responsibilities—explain that while management maintains the file, drivers have a duty to report changes in their status (medical condition, violations, etc.).

Our top vehicle makes cited include Pace American, Freightliner, and various trailer types, indicating no single equipment category drives this violation—it is purely an administrative/compliance issue. Annual recertification training should include 15 minutes on driver file contents and driver responsibilities. Use your post-citation review as a teaching case study: share anonymized details of what was missing with your fleet during a safety meeting.

When should our fleet consider filing a DataQs challenge if we believe a citation was issued in error?

Consider a DataQs challenge if: (1) you can prove the cited driver's file was complete and accessible during the inspection, with contemporaneous documentation (photos, time-stamped logs, witness statements); (2) the document the inspector cited as missing was actually present but the inspector overlooked it; or (3) the carrier had corrected the deficiency prior to the inspection date, with evidence of the correction.

Our records show 8 of 10 citations for this code resulted in out-of-service placement, suggesting most citations involve genuine missing documentation rather than inspector error. Before filing a challenge, interview the driver and file staff to confirm the violation did not occur. DataQs challenges require strong documentary evidence and are most successful when they target factual errors (wrong citation date, wrong driver name) rather than disputes about document presence. Consult your safety consultant before filing.

How often should we audit our driver files for compliance with this code?

Our inspection records show 1 citation in the past 90 days and 4 citations in the past 12 months for this code, indicating it is extremely rare but serious when cited. Implement a quarterly self-audit schedule—every 90 days, pull a random sample of 10% of your driver files and verify completeness against the 385.13(d) requirement checklist.

For fleets with fewer than 50 drivers, audit 100% of files semi-annually (every 6 months). For larger fleets, maintain monthly spot-checks on 5% of files. Additionally, conduct a full-fleet audit whenever you hire a new driver file administrator or when you update your driver management system. Because out-of-service placement occurs in 80.0% of citations, the cost of prevention (staff time) is far lower than the cost of a single citation (lost revenue from downtime). Track audit dates and results in a compliance log.

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

Top Enforcing States

Where 385.13(d) is most commonly cited (last 180 days)

1. North Carolina
1
OOS 100.0%

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.