Prevention FAQ — FMCSR 383.93: CDL Restriction Violations

Fleet safety guidance on preventing CDL restriction violations. Pre-trip protocols, documentation requirements, root-cause analysis, and audit cadences based on real inspection data.

OOS Eligible
Severity Weight
6
OOS Eligible
Yes
BASIC Category
Driver Fitness
Code System
FMCSR
Code:
383.93
Code System:
FMCSR
BASIC Category:
Driver Fitness
OOS Eligible:
Yes
Severity Weight:
6
Violation Group:
BASIC 3

Ranks #3,037 of 3,146 FMCSR codes by citation frequency.

Violation Description

Operating a CMV in violation of a restriction on the CDL (air brakes, manual transmission, etc.).

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when checking for 383.93 violations?

Inspectors verify that a driver's actual vehicle operation matches the restrictions coded on their CDL. This includes air brake restrictions, manual transmission restrictions, and other endorsement limitations. During a roadside inspection, the officer will cross-check the vehicle's equipment (automatic vs. manual transmission, air brake type) against the driver's license restrictions. A mismatch—such as a driver with an air brake restriction operating an air-brake-equipped vehicle—triggers a citation. Your pre-deployment checklist should confirm the restriction matrix for each driver before assignment to any route or vehicle.

What should be on our pre-trip checklist to catch restriction mismatches before the road?

Create a matrix pairing each driver to their CDL restrictions and approved vehicle types. The checklist must include: (1) driver name and CDL number; (2) listed restrictions (e.g., "No air brakes," "Manual transmission only"); (3) vehicle VIN and transmission/brake type; (4) dispatcher signature confirming the match. Use dispatch software to enforce this pairing—flag any assignment that violates the restriction. Run this check every time a driver is assigned a vehicle. Consider a weekly audit of all active assignments to catch mid-week reassignments that may have been missed.

What documentation must drivers carry and what should we retain in our files?

Drivers must carry a current, valid CDL showing all restrictions. Fleet files should include: (1) a copy of each driver's CDL, updated annually; (2) the vehicle-to-driver restriction matrix, signed by dispatcher; (3) audit logs showing which vehicles were assigned to which drivers and when; (4) training sign-offs confirming drivers understand their restrictions. Store CDL images in your driver qualification file (DQF). Maintain assignment logs for at least 3 years. When a driver is reassigned to a different vehicle class, document the reason and re-verify the restriction match before the first trip.

What root causes typically lead to 383.93 violations based on co-occurring violations?

Our inspection records show that 383.93 violations frequently co-occur with driver qualification and medical certificate gaps (codes 391.41APC and 391.41(a) represent 98,809 citations across both). This suggests a systemic issue: when driver file management is poor, restriction verification is also likely to be missed. The pattern indicates that violations cluster in fleets with weak onboarding processes. Additionally, the high out-of-service rates on related CDL codes (383.23(a)(2) at 98.4% OOS) show that restriction mismatches are treated as critical safety failures. Root-cause analysis should focus on: (1) dispatcher training gaps; (2) lack of automated matching in assignment systems; (3) driver reassignment without verification.

How should we verify a vehicle's equipment before assigning it to a restricted driver?

Establish a pre-assignment vehicle inspection protocol that documents transmission type (manual vs. automatic), brake system configuration (air, hydraulic, or combination), and any air brake-specific components. Create a vehicle profile sheet for each asset listing its equipment. Before a restriction-bearing driver is assigned, the maintenance or dispatch team must sign off that the vehicle matches the driver's restrictions. Document this sign-off with date, inspector name, and vehicle odometer reading. Any modification to a vehicle's equipment (e.g., retrofit of air brakes) requires immediate notification to dispatch and re-verification of all assigned drivers. Consider quarterly physical spot-checks of vehicle equipment against stored profiles.

What should we review after a driver is cited for a 383.93 violation?

Conduct a post-citation review covering: (1) how and why the driver was assigned to that vehicle (pull the dispatch log and assignment form); (2) whether the dispatcher verified the restriction match; (3) whether the driver acknowledged understanding the restriction; (4) the vehicle's equipment specification and any recent changes; (5) whether the driver had been reassigned without re-verification. Interview the dispatcher and driver separately to identify the failure point. Document findings in a corrective action record. Determine whether the root cause was human error, system failure, or lack of training. Re-train all dispatch staff on the restriction matrix within 5 business days. Update your assignment system to prevent the same pairing going forward.

How does a 383.93 citation impact our CSA Driver Fitness BASIC score?

FMCSR 383.93 carries a CSA severity weight of 6, indicating a serious violation that significantly impacts your Driver Fitness BASIC category. The peer codes in the same Driver Fitness group show that related violations (such as 383.23(a)(2) — operating without the proper CDL class) generate tens of thousands of citations annually and result in out-of-service rates above 98%. Although our inspection records show zero citations for 383.93 in the last 12 months, the severity weight and peer-code patterns mean even a single citation will harm your safety profile. Prioritize prevention to keep your Driver Fitness BASIC score competitive.

What training topics should we emphasize to prevent drivers from causing 383.93 violations?

Conduct annual driver training covering: (1) how to read and understand their CDL restrictions; (2) consequences of operating outside their restrictions; (3) their responsibility to report a vehicle assignment that violates their restriction; (4) the difference between vehicle types and how transmission/brake systems affect their eligibility. Use real examples from your own fleet assignments. Require drivers to sign a certification stating they understand their personal restrictions and have verified the assigned vehicle matches. Make this a mandatory part of onboarding for all new hires. Include restriction-matching scenarios in your dispatcher and driver-manager training as well, emphasizing that the fleet, not the driver, bears primary responsibility for preventing mismatches.

When should we consider filing a DataQs challenge on a 383.93 citation?

File a DataQs challenge if: (1) your records clearly show the driver's restriction and the vehicle's equipment did match at the time of the roadside inspection; (2) the driver had obtained a CDL waiver or exemption for the restriction (e.g., waiver from the state); (3) the inspection report contains factual errors about the vehicle's equipment; (4) documentation in your DQF proves dispatcher sign-off and verification occurred. Gather the driver's CDL image, your vehicle profile sheet, the dispatch log, the assignment form, and any maintenance records showing equipment configuration on the violation date. Submit within 90 days of the citation. Do not challenge simply because you believe the violation was unintentional—FMCSA evaluates the factual accuracy of the equipment match, not intent.

How often should we audit for 383.93 risk given our enforcement data?

Conduct audits at least quarterly (every 90 days). Our inspection records show zero citations for 383.93 in the last 90 days and zero all-time citations in our 13 million+ roadside inspection database. This absence does not indicate low risk—rather, it reflects the high cost and severity of the violation when it does occur (peer codes show OOS rates exceeding 98%). The zero-citation pattern suggests fleets are successfully preventing the violation, but also means you have no internal historical baseline to track. Quarterly self-audits—pulling all active driver-to-vehicle assignments and verifying restriction matches—will establish your preventive baseline and catch creep before an inspector does. Use a random sample approach: audit 20% of active drivers each quarter, rotating through your entire driver base annually.

Last updated: 2026-04-20T18:14:53.865Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

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.