FMCSR 392.6: Excessive Speed Scheduling — Driver Q&A

No. Across our 13 million inspection records, code 392.6 has never resulted in an out-of-service order. The OOS rate for this violation is 0.0%—all 4 all-time citations resulted in roadside warnings or citations without vehicle placement. Compare that to the national FMCSR average OOS rate of 31.4%, and you'll see this code is treated as a documentation issue rather than an immediate safety risk that grounds equipment.

The specific CSA point value depends on your state's FMCSA scoring rules and whether this was a documented finding. We don't have the exact point weight in our database, but this violation falls under the Unsafe Driving category, which typically carries points in the FMCSA's Unsafe Driving BASIC. The 30-day point multiplier applies based on your state's threshold. Contact your carrier's safety team or your state's enforcement office for the exact CSA hit.

1. Document the stop: Get the officer's name, badge number, and citation number.
2. Review the citation: Confirm the reason—this code means you were scheduled for a run requiring speeds over posted limits, not that you were actually speeding.
3. Notify your dispatcher and safety manager immediately: They need to know before the violation hits FMCSA's system.
4. Request the inspection report: Ensure the findings are accurate and complete.
5. Follow your carrier's appeal process: Ask if they support a DataQs challenge if you believe the citation is incorrect.

No—392.6 is significantly less common than related unsafe driving violations. Across our records, 392.2 (operating while ill or fatigued) accounts for over 1.2 million citations with a 0.8% OOS rate, while 392.6 has only 4 all-time citations and a 0.0% OOS rate. This makes 392.6 one of the rarest unsafe driving codes cited, ranked #2480 out of 3,036 FMCSR codes by enforcement volume. You're unlikely to see this again; focus on the peer codes that actually drive enforcement action.

Yes, you can challenge any citation through FMCSA's DataQs system within a set window (typically 90 days from the roadside inspection). Success depends on the type of finding: documentation errors (wrong dates, misidentified equipment) are easier to overturn than observation-based findings (what the officer witnessed). For 392.6, if the dispatcher's schedule or dispatch records don't support the officer's conclusion that the run necessitated excess speed, that's your strongest argument. Work with your carrier's compliance team to submit supporting dispatch logs.

Rarely. Over the last 12 months, our database shows 0 citations for this code, and 0 citations in the last 90 days. All 4 all-time citations in our 13 million-record database occurred before the past year. This suggests the violation is either not actively enforced or extremely uncommon in real-world operations. Your risk from this code is minimal—focus your safety program on the peer violations like 392.2 that generate thousands of citations annually.

A 392.6 citation follows both the driver and the carrier in FMCSA's CSA system. It appears on your personal record and your carrier's safety profile. However, because this code is so rarely enforced—only 4 all-time citations across 13 million inspections—a single 392.6 is unlikely to significantly damage your hire ability. Prospective carriers will see it, but they'll also see how uncommon it is. Transparency during your next application is best: explain what happened and what you learned about dispatch communication.

Across all roadside inspections in our database, Rich Farms Inc (USDOT 485860), GP Trans Inc (USDOT 1227505), AA&F Transport LLC (USDOT 2895182), and Mahar Trans Inc (USDOT 3566185) each have 1 citation for this code. No single carrier dominates 392.6 enforcement because the violation is so infrequent. If you were cited while leased to one of these carriers, ask your safety manager how dispatch procedures could be clarified to avoid similar findings.