Prevention FAQ — FMCSR 392.2WC: Driver Illness & Fatigue

Inspectors cite 392.2WC when observable signs indicate a driver's ability to operate safely is impaired by fatigue, illness, or any similar condition — not just sleep deprivation. Our inspection records show Texas alone accounts for 2,169 citations in the last 180 days, making it by far the highest-enforcement state for this code. That concentration near the southern border aligns with the carrier pattern in our data: the majority of the all-time top-cited carriers are Mexico-domiciled fleets, suggesting long cross-border runs without adequate rest.

Inspectors watch for: bloodshot or glazed eyes, slurred speech, inability to answer basic questions clearly, erratic pre-inspection behavior, cab conditions suggesting the driver slept in the vehicle without adequate rest time, and HOS logs that don't support the claimed rest. Illness symptoms — coughing, fever, visible distress — are also triggers. Prepare drivers to present alertly and respond to inspector questions confidently.

A 392.2WC citation is written against the driver's condition, not the vehicle — so your pre-trip process must include a driver readiness check, not just a vehicle walk-around. Build these into your morning dispatch protocol:

• Sleep confirmation: Driver affirms minimum off-duty hours since last on-duty period (document in dispatch log).
• Self-assessment declaration: Driver checks a box on the DVIR or a standalone form confirming no illness, medication effects, or fatigue that would impair driving.
• Supervisor visual check: For high-risk runs (overnight, multi-day, cross-border), a dispatcher or terminal supervisor does a brief face-to-face or video check before departure.
• Medication disclosure: Remind drivers that OTC medications — antihistamines, decongestants, sleep aids — can impair alertness. Include a medication advisory on the pre-trip form.
• HOS verification at dispatch: Confirm the driver's available hours match the planned run before the truck rolls.

The checklist should be signed and retained — see the documentation FAQ below.

392.2WC is not OOS-eligible — our records show a 0.0% OOS rate across 7,990 citations — but it still carries a CSA severity weight of 8 and will appear on the carrier's safety record. Strong documentation limits your exposure in post-incident review and DataQs challenges.

Drivers must carry:

• Current ELD or paper HOS logs showing compliant off-duty time
• Completed DVIR for the current and previous day
• Any medical examiner's certificate if a health condition is disclosed

Carriers must retain:

• Signed pre-trip driver readiness declarations (recommended minimum 6 months)
• Dispatch logs showing scheduled departure time vs. actual hours available
• Any documented driver self-reports of illness or fatigue that led to a trip reassignment
• Communication records (text/email/portal) confirming supervisor sign-off on driver fitness for long or cross-border runs

Retaining these records creates a documented culture of fitness-for-duty that supports both DataQs challenges and internal root-cause reviews.

The co-occurrence data from our last 90 days of inspections reveals systemic patterns worth addressing directly:

393.9 — Inoperable Required Lamp (399 shared inspections): The most common companion code. When a driver is fatigued, pre-trip lamp checks are the first thing skipped. This pairing strongly suggests your drivers are departing without completing the full vehicle walk-around — a behavioral fatigue indicator before the truck even moves.

392.2RG (244 shared inspections): This code co-occurring with 392.2WC in the same inspection indicates inspectors are citing multiple fatigue-related behaviors simultaneously. This pattern points to drivers who are visibly impaired and whose log or behavioral record confirms it — a training gap around recognizing and self-reporting fatigue before an inspection occurs.

393.78 — Windshield Condition Defective (185 shared inspections): A cracked or obstructed windshield combined with a fatigued driver suggests deferred maintenance culture. Drivers who are too fatigued to report defects or too pressured to delay departure are also driving vehicles with known deficiencies. Address dispatch pressure alongside driver wellness.

Because 392.2WC carries a 0.0% OOS rate in our records — only 2 drivers were placed out of service across all 7,990 citations — inspectors typically allow the driver to continue after issuing the citation. That means the burden of determining fitness falls entirely on your fleet.

After any 392.2WC citation, implement this return-to-service gate:

1. Mandatory rest stop: Require the driver to take a documented 10-hour break before continuing the run, regardless of remaining HOS.
2. Supervisor contact: A manager must speak with the driver by phone or video before the truck moves again. Log the call with a timestamp.
3. Medical clearance if illness is cited: If the inspector noted illness specifically, require a supervisor-approved fitness declaration or, for recurring incidents, a medical clearance from the driver's examiner.
4. Vehicle inspection: Since 393.9 appears in 399 shared inspections with this code, use the stop to complete a full lamp and equipment check before departure.
5. Document everything: Log the hold, the supervisor contact, and the cleared departure time in your fleet management system.

Run a structured post-event review within 48 hours of the citation. Structure it around four questions:

1. How did this dispatch happen? Pull the HOS logs for the 48 hours preceding the citation. Identify whether the driver had adequate off-duty time. If not, trace back to the load assignment and who approved it.
2. Were co-occurring violations preventable? With 393.9 appearing in 399 of the last 90 days of shared inspections, check whether the cited vehicle also had lamp violations. If yes, the pre-trip process failed — not just the driver.
3. Is this driver a repeat? Check the driver's full inspection history for prior 392.2-family citations. Our peer data shows 392.2 (the parent code) has 1,208,164 all-time citations across the FMCSR database — fatigue enforcement is not rare, and repeat patterns matter.
4. Was dispatch pressure a factor? Interview the driver privately. Document their account. If load pressure contributed, that is a systemic issue requiring a policy fix, not just a coaching conversation.

Document the review outcome and corrective action in the driver file.

392.2WC sits in the Unsafe Driving BASIC — the highest-visibility BASIC for enforcement intervention. Its CSA severity weight is 8, which is on the higher end of the severity scale. Citations are weighted by time, with more recent events carrying more weight.

In our database, 392.2WC ranks #257 out of 3,036 FMCSR codes by citation volume — it is not obscure. Enforcement is active and growing: the last 12 months produced 4,896 citations compared to a much lower historical baseline, meaning inspectors are increasingly trained to identify and write this code.

Importantly, the 0.0% OOS rate means these citations accumulate on your CSA record without drivers being pulled from service — they are easy for inspectors to write and do not trigger an immediate operational disruption that might prompt a fleet response. That makes them a slow-burn CSA risk that fleets often underreact to. With a severity weight of 8 per event, a cluster of these citations over 24 months can meaningfully move your Unsafe Driving BASIC percentile.

Our all-time citation data by vehicle make shows Freightliner (FRHT) vehicles account for 2,436 citations — more than double the next-highest make, Kenworth (KW) at 1,092, followed by Peterbilt (PTRB) at 1,005. These three makes represent a significant share of the long-haul fleet population most exposed to fatigue enforcement. Prioritize training delivery for drivers operating these platforms.

Core training topics:

• Fatigue science basics: Sleep debt is cumulative; 6 hours per night for a week produces impairment equivalent to 24 hours without sleep. Use this to reframe HOS compliance as a health issue, not just a regulatory one.
• Self-assessment drills: Teach drivers to run a 60-second self-check before departure — reaction time, eye focus, ability to recall the last leg's route details.
• Medication awareness: OTC drugs are a leading non-fatigue trigger for 392.2WC. Build a medication advisory module into annual training.
• Pre-trip completion discipline: Given the 399 shared inspections with 393.9, reinforce that a skipped lamp check is a visible sign of impairment to an inspector, not just a vehicle defect.

A DataQs challenge is worth pursuing when your documentation directly contradicts the basis for the citation. Grounds that are typically supportable:

• HOS logs show adequate off-duty time and the driver's pre-trip declaration confirms no illness — the inspector's observation may have been mistaken or based on a brief interaction.
• The citation was written alongside vehicle defect codes (e.g., 393.9 or 393.78, both top co-occurring codes in our data) and there is evidence the vehicle issues were the inspector's primary concern, with 392.2WC added without documented driver behavior observations.
• Clerical or jurisdictional errors — wrong USDOT number, incorrect driver identification, or a code applied under the wrong sub-section.

Do not challenge citations where the driver's logs show insufficient off-duty time, where a supervisor contact confirms the driver reported illness before departure, or where the inspector's notes include specific behavioral observations. Unsuccessful challenges waste administrative time and do not remove the citation. Always attach signed pre-trip records, HOS printouts, and any dispatch communications when filing.

Our monthly trend data from the last 12 months shows citation volume has been consistently elevated, ranging from 393 to 478 citations per month across the February 2025–March 2026 window, with no month below 390 citations (excluding the partial April 2026 data). There is no clear seasonal low — enforcement is sustained year-round.

Given that the last 90 days produced 1,026 citations out of 4,896 in the full 12-month period, roughly 21% of the annual volume is occurring in any given quarter. That rate supports a quarterly self-audit cadence at minimum.

Quarterly audit checklist:

• Pull all drivers cited under any 392.2-family code in the period and review their dispatch history for off-duty compliance.
• Review DVIRs from the cited dates for co-occurring vehicle defects.
• Audit dispatch records for runs where drivers were assigned with less than 10 hours off-duty.
• Spot-check pre-trip driver readiness declarations for completeness and supervisor sign-off.

For fleets with cross-border operations — given Texas's 2,169 citations in just 180 days — consider a monthly audit specifically for drivers on TX-corridor runs.