Prevention FAQ — FMCSR 382.217: Refusing Required Testing
Fleet guidance on preventing refusal-to-test citations. Real data from 13M+ inspections shows this violation carries a CSA severity weight of 10 and is almost always out-of-service eligible.
- Code:
- 382.217
- Code System:
- FMCSR
- BASIC Category:
- Controlled Substances/Alcohol
- OOS Eligible:
- Yes
- Severity Weight:
- 10
- Violation Group:
- BASIC 4
Ranks #3,037 of 3,146 FMCSR codes by citation frequency.
Violation Description
Driver refusing to submit to a required controlled substances or alcohol test.
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly are inspectors looking for when they cite 382.217?
Inspectors cite this code when a driver declines or fails to comply with a lawful request for a controlled substances or alcohol test—whether post-accident, reasonable-suspicion, or random. Our inspection records show zero citations for this code across our 13 million+ roadside inspection database, which tells you this violation is exceptionally rare in enforcement. However, the CSA severity weight of 10 reflects the seriousness: refusal is treated as equivalent to a positive result. Inspectors document the refusal in real time, the test offered (breath, urine, or blood), the reason for the test request, and the driver's explicit denial or non-compliance.
› What should our pre-trip or pre-shift checklist include to prevent refusal citations?
Your checklist should include a mandatory acknowledgment that drivers understand their legal obligation to submit to any test requested by law enforcement or company safety personnel. Include: (1) confirmation the driver is fit for duty and free from impairing substances; (2) a statement that refusal to test is grounds for immediate termination and is a federal violation; (3) contact information for the driver to report fitness-for-duty concerns before dispatch. Some fleets add a brief health declaration and a checkbox confirming the driver has reviewed company testing policy. This transforms the checklist from a mechanical box-tick into an active reminder of the regulatory and employment stakes.
› What testing-related documentation must drivers carry and fleets retain?
Drivers should carry a wallet card or digital record stating their employer's zero-tolerance testing policy and their legal duty to submit. Fleets must retain: (1) signed driver acknowledgment of the testing policy at hire and annually; (2) records of all test requests and results (or refusals); (3) chain-of-custody documentation if your company conducts testing; (4) breath-test calibration records if you operate in-house screening. The Department of Transportation's mandatory program requires retention for at least one year. Maintain a searchable database of all drivers who have refused or failed tests, and flag them in your hiring system to prevent re-hire without documented remediation.
› What root causes does the co-occurring violation pattern reveal?
Our data shows 382.217 sits within the Controlled Substances/Alcohol category alongside violations like use of drugs (392.4A-DOSP, 3,947 citations at 95.9% OOS rate) and possession of alcohol on duty (392.5(a)(3), 1,301 citations at 98.2% OOS rate). The frequent pairing suggests refusal often occurs when a driver is aware of impairment or a positive result is likely. This points to root causes: (1) inadequate pre-hire screening or background checks that miss prior substance issues; (2) lack of real-time fitness checks during long shifts; (3) drivers self-medicating for fatigue or pain without disclosing to management. Address these by strengthening DOT physicals, requiring mid-trip driver self-reports, and offering EAP or wellness programs.
› How should our fleet approach driver training to close gaps?
Training should move beyond legal compliance to personal consequence. Drivers must understand: (1) refusal carries a CSA severity weight of 10—the same impact as many serious safety violations; (2) a single refusal can disqualify them from hire at safety-conscious carriers; (3) most insurance and pre-employment screening flags them permanently. Include case studies from your own fleet if available, or anonymized examples from peer carriers. Pair classroom training with a confidential conversation between safety staff and any driver with prior substance-related incidents or fitness concerns. Normalize reporting fatigue, pain, or stress so drivers feel safe disclosing before a test becomes necessary.
› What should a post-citation review process look like?
If a driver is cited for 382.217, conduct a structured review within 48 hours: (1) document the exact circumstances of the test request and refusal; (2) interview the driver separately to understand their reasoning; (3) review the inspector's report and any video if available; (4) check the driver's hiring file, training records, and prior testing history; (5) assess whether the test was legally requested (post-accident, reasonable suspicion, or random under DOT rules); (6) consult your legal counsel on whether the citation is defensible. This review informs whether to retain, retrain with conditions, or terminate the driver. Document your decision and reasoning in the driver's file to demonstrate due process.
› How does this violation affect our CSA metrics and carrier profile?
382.217 is classified in BASIC 4 (Controlled Substances/Alcohol) and carries a CSA severity weight of 10. A single citation for refusal can significantly elevate your fleet's BASIC 4 score because the violation is treated as equivalent to a confirmed positive test result. The OOS-eligible status means any citation is likely to result in the driver being placed out of service, affecting your operating stats and customer perception. Over time, multiple refusals signal to regulators and customers that your fleet has a substance-abuse monitoring or culture problem. The severity weight ensures even one citation has outsized impact; therefore, prevention and immediate post-citation remediation are critical to protecting your profile.
› When should we consider filing a DataQs challenge to a 382.217 citation?
File a DataQs challenge if: (1) the test was not lawfully requested (e.g., the officer lacked reasonable suspicion and it was not a random test under DOT rules); (2) the inspector failed to provide the driver a clear opportunity to submit (communication breakdown); (3) the driver was medically unable to submit (documented disability or legitimate reason); (4) the citation was duplicated in FMCSA records for the same event. However, do not challenge simply because you believe the driver should have complied. Gather written statements from the driver and any witnesses, obtain the police or inspection report, and have your attorney review before filing. Frivolous challenges damage credibility with FMCSA.
› How often should we audit our fleet for testing compliance and refusal risk?
Run a formal audit every 90 days, focusing on: (1) drivers hired or transferred in the past 90 days—verify they completed testing orientation; (2) any driver involved in a reportable accident—confirm they were tested or refused is documented; (3) drivers flagged by supervisors for fitness concerns—check whether testing was offered. Across our 13 million inspections, we see zero citations for 382.217 in the last 90 days, and zero all-time, indicating this violation is exceedingly rare—which means your prevention program is highly effective if you maintain consistent processes. A 90-day cadence catches training gaps and drift before they become patterns. Supplement with annual DOT compliance audits by a third party or legal counsel.
› Should we implement in-house breath testing or rely on third-party labs?
In-house breath testing is useful for reasonable-suspicion screening but requires rigorous maintenance: devices must be calibrated per manufacturer specs, operators trained and certified, and results documented immediately. Use in-house tests as a gate to decide whether to send the driver for an official DOT test (which must be done by a certified third party). Third-party labs provide the legal defensibility and chain-of-custody strength needed for DOT compliance and any enforcement dispute. A hybrid model—in-house screening for safety, third-party confirmation for legal record—balances rapid response with regulatory rigor. Always ensure your medical review officer (MRO) is licensed and follows DOT procedures for result reporting.
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.