Prevention FAQ — FMCSR 392.5C2: Violating OOS Orders
Fleet safety guidance on controlled substances/alcohol OOS violations. Pre-trip checklists, inspector focus areas, root-cause analysis from 13M inspection records, and audit cadence.
- Code:
- 392.5C2
- Code System:
- FMCSR
- BASIC Category:
- Controlled Substances/Alcohol
- OOS Eligible:
- No
- Severity Weight:
- 10
- Violation Group:
- Alcohol Jumping OOS
Ranks #1,931 of 3,146 FMCSR codes by citation frequency • OOS rate of 86.4% is above the FMCSR-wide average of 33.3%.
Violation Description
Violating OOS order pursuant to 392.5(a)/(b)
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly do inspectors look for when citing 392.5C2?
Inspectors cite this code when a driver operates a CMV after receiving an out-of-service order related to controlled substances or alcohol under 392.5(a) or (b). Across our inspection records, Iowa has led enforcement with 4 citations in the last 180 days, all resulting in out-of-service placements (100% rate). Texas, Illinois, and North Carolina have each recorded 1 citation. The high concentration in Iowa suggests inspectors there are conducting thorough post-order compliance checks, likely at weigh stations or during roadside inspections. Inspectors verify whether the driver was formally notified of the OOS order and then placed the vehicle back in operation without clearance. Documentation of the original order and the violation is critical to the inspector's findings.
› What should our pre-trip checklist include to prevent this violation?
Your checklist must include a driver attestation confirming current OOS status. Specifically, drivers should verify:
- No active OOS orders exist on their CDL or FMCSA record
- They have not been directed to remove the vehicle from service by law enforcement or a medical examiner
- They understand the consequences of operating under an OOS order
Stress that this is a controlled-substance/alcohol safety issue. Include a line-by-line sign-off requiring the driver to confirm they are fit to operate. Given that our data shows 86.4% of citations result in out-of-service placement—far above the all-FMCSR average of 31.4%—the severity of operating under an OOS order is exceptionally high. Implement a secondary check: have dispatch confirm via the state's licensing system that the driver's CDL is valid and free of restrictions before assigning the run.
› What documentation must drivers carry and fleets retain?
Drivers must carry proof of clearance or waiver if they have previously been issued an OOS order related to 392.5 (alcohol/controlled substances). This includes:
- Any written clearance from a medical examiner or employer
- Documentation of completion of required testing or evaluation
- Current medical certificate (if applicable)
- Signed driver acknowledgment of current fitness to operate
Fleets must retain in the driver file:
- Copies of all OOS orders issued to the driver
- Correspondence showing when restrictions were lifted
- Training records confirming the driver understands the prohibition
- Pre-trip attestation forms signed by the driver
Our records show 22 all-time citations for this code; nearly all (19 out of 22) resulted in out-of-service placement. Retain this documentation for the life of the driver's tenure plus three years after separation. This protects you in CSA audits and demonstrates due diligence.
› What root causes emerge from drivers cited for this violation?
Our inspection data reveals three systemic patterns in citations co-occurring with 392.5C2:
CDL validity (383.23A2, 2 shared inspections): Drivers operating without a valid CDL or with a suspended license often do not track OOS restrictions effectively. This suggests gaps in dispatch verification and driver record monitoring.
Fatigue and illness (392.2RG and 392.2C, 3 shared inspections): Impaired judgment from fatigue or illness may lead drivers to ignore or misunderstand OOS notifications. Implement mandatory fitness-to-drive assessment before each shift.
ELD/RODS compliance (395.8A-ELD and 395.30C, 3 shared inspections): Drivers unfamiliar with electronic logging systems may not properly document their status or review system alerts about OOS orders. Strengthen ELD training and require drivers to review alerts before starting the engine.
These patterns suggest that weak pre-dispatch controls and inadequate driver communication are the primary contributors, not ignorance of the rule itself.
› How should we verify repairs or fitness-to-operate before returning a vehicle to service?
This code does not involve vehicle defects; it concerns driver fitness. After an OOS citation for violating a controlled-substance or alcohol order, follow this procedure:
- Suspend the driver from operation immediately upon notification of citation.
- Verify clearance status: Confirm with your legal or compliance team whether the original OOS order has been formally lifted by the issuing authority (state, medical examiner, or FMCSA).
- Medical re-evaluation: If the OOS order was based on a substance violation, require the driver to complete a DOT medical examination and obtain a valid medical certificate before resumption of duty.
- Fitness-to-operate declaration: Have the driver and a supervisor jointly sign off confirming understanding of the violation and commitment to compliance.
- Documentation: Retain all clearance paperwork in the driver's personnel file.
Given that 86.4% of citations result in out-of-service placement, the bar for reinstatement is high. Do not rely on the driver's word alone; verify independently.
› What post-citation review should we conduct after a 392.5C2 finding?
Immediately after receiving a citation for this code, conduct a root-cause review:
- Driver interview: Ask why the driver operated the vehicle after receiving the OOS order. Determine whether the driver understood the order, forgot, or misinterpreted dispatch instructions.
- Dispatch audit: Review communications (text, email, radio logs) between dispatch and the driver on the date of violation. Confirm whether dispatch issued clear warnings.
- Record check: Pull the driver's complete OOS history. Look for prior violations of 392.4 (drug use) or 392.5A/B (alcohol use) that may indicate a pattern.
- Fleet policy review: Verify that your OOS policy was in the driver handbook and that the driver signed acknowledgment.
- Peer comparison: Our data shows Arborscape Enterprises Inc. (USDOT 4007322) has recorded 2 citations for this code—the highest among cited carriers. If your fleet operates similarly, benchmark your controls against industry practice.
Document all findings and corrective action in a formal report.
› How does this violation affect our CSA Vehicle Maintenance BASIC score?
While 392.5C2 is categorized as a Controlled Substances/Alcohol issue rather than Vehicle Maintenance, any citation on your carrier's FMCSA record contributes to overall CSA severity. This code ranks #1898 out of 3,036 FMCSR codes by citation volume, indicating it is not a high-frequency citation nationally. However, its consequence is severe: our records show an 86.4% out-of-service rate compared to the all-FMCSR average of 31.4%—meaning inspectors place vehicles out of service at nearly 3× the baseline rate.
Each citation carries enforcement weight and may trigger increased scrutiny from state inspectors. For your CSA profile, focus on minimizing driver qualification (HOS) and controlled substance/alcohol violations to strengthen your overall safety profile. Even a single 392.5C2 citation signals to auditors that your pre-dispatch controls may be weak.
› What training topics should drivers receive to prevent this violation?
Design driver training around three core topics:
- Understanding OOS orders: Explain in plain language what an OOS order is, who can issue one, and why violating it is a federal offense. Use case studies of real drivers (anonymized) who were cited.
- Recognizing notifications: Train drivers to immediately recognize OOS notifications from dispatchers, medical examiners, or law enforcement. Have them confirm receipt and read back the order to ensure understanding.
- System integration: Our data shows FMCSR 383.23A2 (Operating without a CDL) co-occurs with 392.5C2 in 2 inspections, and ELD issues (395.8A-ELD) in 2 inspections. Teach drivers to check their CDL status in the state licensing portal and to review ELD alerts daily before starting the vehicle.
Conduct this training annually for all drivers and make it mandatory for any driver with a prior substance/alcohol or OOS citation. Use the 17 citations in the last 12 months as evidence of ongoing enforcement priority.
› When should we consider a DataQs challenge for this citation?
A DataQs challenge is appropriate only if the evidence supporting the citation is factually incorrect. Consider a challenge if:
- The OOS order was not valid or had already been lifted at the time the driver operated the vehicle. You must provide written proof from the issuing authority.
- The driver was not notified of the OOS order before being dispatched. Provide dispatch logs and communication records proving the notification did not occur.
- Documentation is incomplete or contradictory in the inspection report itself (e.g., the inspector cites a violation but provides no date or authority for the original OOS order).
DataQs challenges require documentary evidence; verbal disputes are rejected. Given that 19 of 22 all-time citations (86.4%) resulted in out-of-service placement, and most cases appear properly documented, successful challenges are rare. Focus your energy on prevention rather than litigation. Only pursue a challenge if you have contemporaneous written evidence that directly contradicts the citation.
› How often should we self-audit our fleet for 392.5C2 risk?
Conduct audits on a quarterly (90-day) cycle. Here's why: our inspection data shows 3 citations in the last 90 days and 17 in the last 12 months, indicating steady enforcement pressure. A quarterly rhythm allows you to:
- Review all drivers with current OOS restrictions (controlled substance/alcohol related) and verify clearance status every 90 days.
- Audit dispatch procedures to ensure they are actively checking state CDL and OOS databases before assigning runs.
- Spot trends: If two or more drivers are cited in a single quarter, this signals a systemic control failure requiring immediate remediation.
- Update training: Use quarterly audit findings to refresh driver training on OOS recognition and compliance.
Conduct a full annual audit in addition to the quarterly checks. Pull all OOS citations from the past 12 months, map them to drivers and dates, and identify any patterns by vehicle type, route, or dispatcher. Our monthly trend data shows 1–3 citations per month throughout the 12-month period, confirming consistent enforcement. A quarterly audit cadence keeps you ahead of inspector patterns.
Top Enforcing States
Where 392.5C2 is most commonly cited (last 180 days)
Related Records
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.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
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.