What 385.13A2 means in plain language
385.13A2 is a general administrative violation under FMCSR Part 385. While the regulation itself is narrow in scope, citations under this code typically relate to documentation, reporting, or procedural compliance issues that fall outside the core safety categories like braking, lights, or driver qualifications.
If you've been cited for 385.13A2, the inspector found a deficiency in how you or your carrier handled a required administrative task—whether that's a form, record, notification, or other compliance element tied to vehicle operation or carrier responsibility. The specifics depend on the context of your inspection, but the underlying theme is always the same: a required process or document wasn't completed or submitted correctly.
This is not a safety-critical code like brake or lighting violations, which is why it's not eligible for out-of-service placement by regulation. However, as you'll see in the data, inspectors still place vehicles out of service when 385.13A2 is cited—which suggests the citation often appears alongside other violations that do trigger OOS status.
What our enforcement data actually shows
Across our 13 million+ inspection records, 385.13A2 is extremely rare. We've recorded 12 all-time citations for this code, with 6 citations in the last 12 months and 2 in the last 90 days. This ranks 385.13A2 at #2132 out of 3,036 FMCSR codes by citation volume—meaning you're in a very small group.
But here's what matters: of those 12 all-time citations, 9 resulted in out-of-service placement. That's a 75.0% OOS rate, which is dramatically higher than the all-FMCSR average of 31.4%. Even though the regulation itself doesn't allow OOS eligibility, inspectors are placing vehicles out of service in three out of every four 385.13A2 cases we see. This almost always means the citation co-occurred with a violation that does trigger OOS—such as driver qualification issues, vehicle defects, or operational violations.
Over the last 12 months, the citation trend has been sporadic: one in September 2025, one in October 2025 (not OOS), two in December 2025 (both OOS), one in January 2026, and one in February 2026. No clear seasonal pattern, but when it does appear, the OOS outcome is the norm.
Who gets cited most
Our inspection records show that 385.13A2 citations are concentrated in a few states. Texas leads with 3 citations in the last 180 days, all three resulting in out-of-service placement (100% OOS rate). North Carolina follows with 1 citation, also out of service. These two states account for all recorded 385.13A2 enforcement in our recent data.
At the carrier level, our data shows fleets such as Rapido & Furioso Logistics LLC (USDOT 4150252) and Coqueto Trucking LLC (USDOT 3870746) with 2 citations each, all-time. The remaining citations are distributed across single-truck operations and smaller carriers. None of these patterns suggest systemic negligence—rather, they reflect the randomness of a very low-frequency violation.
How severe is this compared to similar codes
385.13A2 sits in the General/Admin category alongside codes like 390.21(a) (Vehicle marking requirements), which has racked up 25,872 citations with a 0.0% OOS rate. That's a stark contrast: marking violations are common but rarely result in out-of-service placement, whereas 385.13A2 is rare but frequently results in OOS when cited.
Other peer codes in the same category show even higher citation volume. 390.21TB2-DOT has 74,663 citations, 390.21T(b) has 61,097, and 390.21TB1-MC has 59,189—all with 0.0% OOS rates. 390.21(b) (USDOT number not displayed) has 13,244 citations and also 0.0% OOS. The pattern is clear: administrative codes typically don't trigger out-of-service status. The fact that 385.13A2 does 75% of the time indicates it's almost always paired with a more serious violation.
How to avoid it
Because 385.13A2 is so rare and typically co-occurs with other violations, prevention starts with broad compliance practices:
-
Maintain current CDL status and language proficiency documentation. Our data shows 383.23A2 (Operating without a CDL) and 391.11B2-Q (English language proficiency) co-occurred with 385.13A2 in recent inspections. Before every run, confirm your license is valid and your medical certificate is current.
-
Keep proof of vehicle inspection on hand. Code 396.17C (No proof of periodic inspection) appeared in a co-occurring inspection. Carry documentation that your vehicle has passed its required periodic inspection and inspection report.
-
Perform a thorough pre-trip inspection. Vehicle marking (390.21(a)) and tail lamp function (393.9T) were also co-occurring violations in our data. Walk around your vehicle, check that all required markings are visible and legible, test all lights, and document any defects before you depart.
-
Ensure your carrier has up-to-date licensing and operating authority. Administrative violations often stem from carrier-level documentation gaps—expired authority, missing filings, or incomplete registration. Work with your fleet manager to confirm all paperwork is current.
-
Verify the vehicle make and model alignment with your load and route. Our data shows Freightliners (FRHT) as the most-cited vehicle make under 385.13A2. This likely reflects their prevalence in the fleet, but it's a reminder to know your vehicle's specifications and limitations.
-
Never operate while ill or fatigued. Code 392.2RG (Operating while ill or fatigued) was co-cited in recent 385.13A2 cases. Your physical fitness to drive is non-negotiable and often the trigger for a detailed roadside inspection where administrative gaps are uncovered.
The bottom line: 385.13A2 is uncommon, but when it appears, something else is usually wrong too. Stay on top of licensing, maintenance records, pre-trip checks, and carrier compliance. If you've been cited, work with your carrier and legal counsel to understand what triggered it and prevent it next time.