Prevention FAQ — FMCSR 392.2W: Driver Illness & Fatigue

Inspectors cite 392.2W when observable driver condition raises a safety concern — bloodshot or glassy eyes, slurred speech, difficulty following instructions, or visible disorientation. They are not diagnosing a medical condition; they are documenting that the driver appeared unsafe to operate the vehicle at that moment.

Our inspection records show Texas alone accounts for 18,174 citations in the last 180 days, making it by far the highest-volume enforcement state for this code. With that concentration, inspectors at Texas ports of entry and weigh stations are actively watching cross-border operators. Illinois follows at 185 citations in the same window, and North Carolina at 30.

Key inspector triggers:

• Driver unable to produce coherent answers during Level I inspection
• Physical signs of fatigue: micro-sleep during the inspection itself, head-drooping
• HOS logs showing minimal or no off-duty time before the current shift
• Admission by the driver that they feel unwell or exhausted

Coach drivers never to self-report fatigue during an inspection without understanding the consequences. The better policy: if a driver is too fatigued to drive safely, they should park and rest before an inspector ever approaches the cab.

A pre-trip checklist for fatigue and illness prevention should operate at the dispatch stage, not just at the truck. Build these gates into your dispatch workflow:

Before dispatch authorization:

• [ ] Driver self-certification of sleep: minimum 8 consecutive hours in the prior 24 hours (document the time)
• [ ] Driver confirms no OTC medications, alcohol, or substances that warn against operating machinery
• [ ] Dispatcher verbal wellness check — not a formality, a 60-second conversation
• [ ] HOS log review: verify no split-sleeper irregularities that mask actual rest deficit
• [ ] Confirm driver has not reported illness to any supervisor in the past 48 hours

At the vehicle:

• [ ] Driver performs a full walk-around — fatigue degrades attention to vehicle condition, which is why our data shows 392.2W co-occurring with equipment defects like inoperable lamps (1,019 shared inspections) and windshield defects (553 shared inspections) in the last 90 days
• [ ] Driver signs and dates the pre-trip section of the DVIR acknowledging fit-for-duty status

Any unchecked box should be a hard stop. Dispatchers need authority — and backing from management — to hold a driver without penalty.

Drivers must carry at time of inspection:

• Current HOS logbook or ELD record showing all on-duty, off-duty, and sleeper berth entries for the current day and prior 7 days
• Current medical examiner's certificate (valid, unexpired)
• Any physician-issued fitness clearance if the driver recently returned from illness or injury

Carriers must retain:

• Signed pre-trip DVIR for the trip in question, with fit-for-duty attestation
• Dispatch records showing assigned start time vs. actual driver availability
• Driver wellness check logs or supervisor sign-off records at dispatch
• ELD data export for the 8-day window surrounding the citation date
• Any internal communications (text, app message) between driver and dispatch regarding fatigue or illness concerns

Retention period: keep all of the above for at least 12 months beyond the citation date. If a DataQs challenge is filed, you will need the full evidentiary package. Carriers without dispatch wellness-check documentation have almost no basis to contest a 392.2W finding, because the citation is based on inspector observation, and the only counter-evidence is a contemporaneous record showing the driver was assessed as fit before departure.

The co-occurrence data from our last 90 days of inspection records points to three systemic patterns that fleet managers should address as interconnected, not isolated:

Pattern 1 — Deferred maintenance culture (393.9 / 393.78 / 393.47E) The most frequent co-occurring code is 393.9 (Inoperable Required Lamp) at 1,019 shared inspections, followed by 393.78 (Windshield condition defective) at 553, and 393.47E (Slack adjuster defective) at 312. When fatigued drivers are on the road, pre-trip inspections are cursory or skipped entirely. The vehicle defects and the impaired driver arrive at the inspection together because the same root cause produced both: inadequate pre-trip discipline.

Pattern 2 — Maintenance documentation gaps (396.17C) 396.17C (No proof of periodic inspection) appeared in 396 shared inspections. Fleets that lack organized maintenance records often also lack structured driver management — the disorganization is systemic.

Pattern 3 — Mechanical neglect under schedule pressure (396.5B / 393.53B) Fuel system leaks (396.5B, 328 shared inspections) and worn steering components (393.53B, 289 shared inspections) suggest vehicles are being pushed past service intervals. That same scheduling pressure is likely what puts fatigued drivers behind the wheel.

Address all three patterns as one program, not three separate write-ups.

Because 392.2W carries a 0.1% OOS rate across 64,257 all-time citations, most cited drivers are not placed out of service at the inspection site — but that doesn't mean they should immediately continue the trip. The citation itself is evidence that an inspector found the driver's condition concerning.

Immediate steps after a citation:

1. Mandatory rest stop: Require the driver to take a documented off-duty rest period before continuing. Minimum 10 consecutive hours, logged in the ELD.
2. Supervisor call: A safety supervisor — not dispatch — speaks with the driver to assess condition. Document the time, participants, and outcome.
3. Medical clearance if illness was cited: If the inspector noted illness rather than fatigue, require a physician fit-for-duty letter before the driver re-enters service.
4. Second driver option: For time-sensitive loads, evaluate whether a team driver or replacement driver is faster than the litigation and CSA cost of a second incident.

Document every step in the driver file. The return-to-service record is your proof that the fleet took the citation seriously — relevant if the driver is ever cited again and the pattern comes under FMCSA scrutiny.

Run a structured post-event review within 72 hours, before memories fade and before the inspection report closes in your CSA portal.

Step 1 — Collect the record set Pull the inspection report, ELD export for the prior 8 days, dispatch assignment records, and any pre-trip DVIR signed before the cited trip.

Step 2 — Timeline reconstruction Map the driver's actual off-duty hours against assigned start times. Identify whether dispatch scheduled a departure that was mathematically incompatible with adequate rest.

Step 3 — Interview the driver Ask specifically: Did you tell anyone you were tired before departure? Did dispatch acknowledge it? Was there pressure to continue despite fatigue? Document verbatim answers.

Step 4 — Co-violation audit Review the inspection report for any co-occurring violations. Our data shows that in the last 90 days, 392.2W frequently appears alongside equipment defects — use this as a prompt to audit the specific vehicle for deferred maintenance.

Step 5 — Root-cause classification Categorize the event: scheduling failure, driver behavior, illness onset, or vehicle-condition-related inspection escalation. Each category has a different corrective action.

Step 6 — Corrective action memo File a written corrective action plan in the driver's file and route a copy to the safety director. This is the foundation of any future DataQs challenge.

392.2W carries a CSA severity weight of 8 — one of the higher weights in the Unsafe Driving BASIC. Citations in the Unsafe Driving BASIC receive time-weighting (more recent citations score higher) and are among the most visible to shippers, brokers, and FMCSA intervention staff.

Our inspection records rank 392.2W #44 out of 3,036 FMCSR codes by citation volume, with 64,257 all-time citations and 40,495 in just the last 12 months. That volume means FMCSA has extensive comparative data — fleets that generate multiple citations for this code within a 24-month window will draw percentile scores that invite intervention.

For context within the same violation family: the parent code 392.2 has 1,208,164 all-time citations at a 0.8% OOS rate. 392.2W's 0.1% OOS rate is well below the all-FMCSR average of 31.4%, meaning inspectors are not routinely grounding drivers for this — but they are writing it up, and every write-up lands on the CSA scorecard with full severity-weight impact.

Fleets operating near the Unsafe Driving BASIC intervention threshold should treat a single 392.2W citation as a five-alarm event, not a minor notation.

Our inspection records show the top cited vehicle makes for 392.2W are Freightliner (16,688 citations), Kenworth (13,620), and Peterbilt (10,694). These are the dominant long-haul platforms, confirming this is primarily a long-haul and regional OTR issue rather than a local delivery problem. Training programs should be calibrated to that population.

Required training modules:

1. Fatigue science basics — What 18–20 hours of wakefulness does to reaction time; why drivers underestimate their own impairment
2. HOS rules as a floor, not a ceiling — Legal hours do not equal safe hours; the driver still owns the fit-for-duty decision
3. Pre-trip fit-for-duty self-assessment — A structured 5-question self-check before every shift; train drivers to take it seriously, not treat it as a checkbox
4. Illness reporting without fear of penalty — Drivers who fear dispatch retaliation will not call in sick; this must be a policy with teeth, not a poster on the break room wall
5. Medication awareness — OTC antihistamines, cold medications, and sleep aids are among the most common hidden impairment sources; provide a reference card for common medications and their warning labels

Run this training annually with a signed completion record in every driver file.

DataQs challenges for 392.2W succeed in a narrow set of circumstances, because the citation is based on inspector observation of driver condition — which is inherently subjective and difficult to rebut with paper records alone.

Challenge is appropriate when:

• The inspection report contains a factual error (wrong driver name, wrong vehicle, wrong date/time)
• The driver has a contemporaneous physician record or ELD-verified rest record that directly contradicts the inspector's stated basis
• The citation was issued alongside violations that were later successfully challenged, and the 392.2W was clearly derivative of those errors
• Duplicate entries exist for the same inspection event

Challenge is unlikely to succeed when:

• The only counter-argument is "my driver says he wasn't tired"
• There is no pre-trip documentation showing a fit-for-duty assessment was performed
• The post-event review (see above) turned up HOS records showing inadequate rest

Given the citation's severity weight of 8 and its #44 national rank by volume, a successful challenge removes a high-impact data point from your CSA percentile. It is worth investing the time in the factual analysis — but do not file without a documented evidentiary basis. Unfounded challenges waste safety staff time and do not succeed.

Our inspection records show 8,943 392.2W citations in the last 90 days against 40,495 in the last 12 months — meaning the last 90 days account for roughly 22% of the annual volume. Monthly data shows a sustained plateau: citations ranged from 3,096 to 4,043 per month from December 2025 through March 2026, with no sign of seasonal decline.

This sustained, high-volume enforcement pattern argues against annual auditing. The recommended cadence is quarterly internal audits, aligned to the 90-day inspection window that governs CSA time-weighting.

Each quarterly audit should include:

• Pull all 392.2W citations received in the prior 90 days from the FMCSA SMS portal
• Cross-reference each citation against dispatch records and ELD exports to identify scheduling patterns (specific routes, specific dispatch windows, specific drivers)
• Review co-occurring violations on each cited inspection — any repeat appearance of 393.9, 396.17C, or 396.5B alongside 392.2W signals a systemic vehicle or dispatch problem, not a one-off driver issue
• Audit pre-trip DVIR completion rates for the prior quarter; completion below 95% is a corrective action trigger
• Review driver wellness check compliance by dispatcher

Document the audit in writing. If FMCSA ever initiates a compliance review, a trail of self-audits with corrective actions demonstrates a functioning safety management system.