Prevention FAQ — FMCSR 385.337B

Fleet safety guide for 385.337B citations. Pre-trip checklists, documentation requirements, root-cause patterns from 13M inspections, and self-audit cadence.

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

Ranks #1,157 of 3,146 FMCSR codes by citation frequency • OOS rate of 94.6% is above the FMCSR-wide average of 33.3%.

Violation Description

Operating in violation of FMCSA Operational Out of Service order for Failure to permit a Safety Audit

Prevention FAQ for Fleet Managers

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

What specific areas do roadside inspectors focus on for 385.337B violations?

Our inspection records show that 385.337B citations spike in North Carolina, Texas, Iowa, and New Mexico—NC and IA alone account for 26 of the last 180 days' citations. Inspectors in these high-enforcement states are flagging this violation at a 100% out-of-service rate in NC and IA, compared to the all-FMCSR average of 31.4%. This intensity suggests inspectors in these regions are conducting deeper documentation audits during roadside stops. Train your drivers on the specific state-by-state inspection profiles: NC (17 citations last 180 days) and TX (16 citations) are your highest-risk corridors. Brief your fleet on what triggers an extended inspection in these states before routing through them.

What should our pre-trip checklist include to prevent this violation?

Build your checklist around the co-occurring violation patterns we see in our database. Six of the last 90 days' shared inspections paired 385.337B with proof-of-inspection gaps (396.17C), and another six involved CDL or fatigue documentation failures (383.23A2, 392.2RG). Your pre-trip must verify: (1) all periodic inspection paperwork is present and current; (2) driver credentials are valid and in cab; (3) driver has logged adequate rest. The data shows Freightliners (64 all-time citations of this code) and Fords (31 citations) are most frequently involved—these fleets should implement a specific checklist line-item for documentation completeness before every dispatch.

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

Because 385.337B pairs with 396.17C (proof of periodic inspection) in 6 of the last 90 days' co-occurring inspections, drivers must carry physical or digital proof of the most recent periodic inspection in the cab. Carriers must retain originals for a minimum of one year in their records system and ensure digital access to dispatch and roadside. Additionally, because this code co-occurs with CDL and fatigue violations, drivers must have current CDL, medical certificate, and Hours of Service records available. The 94.3% out-of-service rate (versus 31.4% all-FMCSR average) underscores the severity: documentation gaps don't just result in citations—they result in immediate vehicle impound. Establish a centralized document-management system that syncs with your driver onboarding and pre-trip workflow.

What root causes does the co-occurring violation data reveal?

Across the last 90 days, we identified a clear pattern: 385.337B appears with proof-of-inspection gaps (396.17C, 6 instances), operator credential failures (383.23A2, 6 instances), and fatigue/illness issues (392.2RG, 6 instances). This suggests three systemic roots: (1) inadequate document-control processes allowing inspection records to leave the vehicle; (2) insufficient pre-dispatch credential verification; (3) fatigue-risk policies that don't prevent unsafe operation. Five of the last 90 days' inspections also involved brake defects (393.48A, 393.45B2UV), hinting that vehicles cited for 385.337B may simultaneously lack maintenance documentation. Root-cause analysis should examine whether your fleet is missing periodic preventive-maintenance sign-offs, which fuels both mechanical failures and documentation audits.

How should we verify repairs before returning a vehicle to service after a citation?

If the citation involved a mechanical defect (as seen in 5 of the last 90 days' inspections involving brake issues), require a certified shop inspection and written sign-off before the vehicle re-enters service. For documentation-only violations, the recovery process is faster: retrieve missing records, digitize them, and upload to your compliance system. Because emergency equipment defects (393.95A, 393.95F) also co-occur with 385.337B, include a full emergency-equipment audit in your post-citation repair checklist. Require the driver to sign off that all documentation is complete and correct before the vehicle is dispatched. If the violation was out-of-service, notify your insurer and review the citation details with your safety team before clearance.

What should our fleet review immediately after a 385.337B citation?

Conduct a root-cause review within 48 hours of the citation. Pull the inspection report and identify the specific documentation gap: was it proof of periodic inspection, CDL/medical certificate, Hours of Service logs, or vehicle-maintenance records? Cross-reference with our data: 124 citations in the last 12 months and 21 in the last 90 days show this violation is actively cited. Check whether the same driver, vehicle, or dispatcher was involved in prior violations. Because this code has a 94.3% out-of-service rate, review whether the vehicle was correctly placed OOS and ensure your recovery workflow restored full compliance. Document your corrective action (retraining, system upgrade, scheduling change) and communicate it to all drivers within one week.

How does this violation affect our CSA Vehicle Maintenance BASIC score?

385.337B is ranked #1166 of 3,036 FMCSR codes by citation volume—a mid-range violation—but its 94.3% out-of-service rate (versus 31.4% all-FMCSR average) indicates inspectors view it as a serious compliance failure. While not a top-tier Vehicle Maintenance issue, the severity of the OOS outcome means even a single citation can trigger audits and carrier review. More importantly, the co-occurring violations—brake defects (393.48A), lamp failures (393.9), emergency equipment gaps (393.95A, 393.95F)—directly impact your Vehicle Maintenance BASIC. A single 385.337B citation often arrives with 2–3 mechanical defects; address the root system, not just the immediate violation.

What training should we roll out to close the gap?

Focus training on three pillars: (1) Documentation management—teach drivers the inspection protocols and where each piece of paper or file must live. (2) Pre-trip procedures—make it mandatory and time-boxed; the data shows documentation gaps (396.17C) are the #1 co-occurring issue in 6 of the last 90 days' inspections. (3) Regional enforcement awareness—driver briefings for NC (17 citations last 180 days), TX (16 citations), and IA (9 citations) should highlight that these states enforce this code at 87–100% OOS rates. Tailor training by vehicle make: Freightliners (64 all-time citations) and Fords (31 citations) should receive platform-specific document-stowage guidance. Use real citations from your fleet as case studies in quarterly safety meetings.

When should we challenge a citation through DataQs?

Challenge only if the citation is factually incorrect—e.g., the driver did carry proof of inspection, and you have timestamped photographic or system evidence. Because 94.3% of 385.337B citations result in OOS placements, inspectors are applying this code conservatively and with high confidence. Frivolous challenges waste resources and may flag your carrier for closer scrutiny. However, if the inspector failed to note a document that was present, or if timing records prove the driver was not violating the code at the time of inspection, DataQs is appropriate. Consult your FMCSA liaison before filing; our database shows only 244 all-time citations for this code, so a challenge stands out.

How often should we self-audit for this violation?

Our 90-day data shows 21 citations, while the 12-month total is 124—an average of about 10–11 per month. This indicates steady enforcement. Conduct a monthly audit of all vehicle documentation compliance, focusing on proof of periodic inspection (the #1 co-occurring gap) and driver credentials. For your highest-risk fleets (those with Freightliners or Fords, or those routing through NC, TX, IA, or NM), implement a weekly document-verification spot-check. Because the last 90 days' citation count (21) is lower than the preceding 90-day period (May–July averaged ~15 citations monthly), enforcement may be plateauing, but do not relax—this is still a high-OOS-rate violation, and systematic compliance prevents both citations and vehicle impounds.

Last updated: 2026-04-20T15:01:18.641Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

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

1. Texas
18
OOS 88.9%
2. North Carolina
11
OOS 100.0%
3. Iowa
3
OOS 100.0%
4. New Mexico
3
OOS 100.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.