Prevention FAQ — FMCSR 392.2WG: Ill or Fatigued CMV Operation

Inspectors are looking for observable signs that a driver's ability to operate safely is compromised — bloodshot or glazed eyes, slurred speech, unsteady gait, inability to answer basic questions coherently, or a driver who admits to feeling ill or exhausted. They may also review Hours of Service logs on the spot for evidence of insufficient rest before the run began.

The enforcement pressure is real: our inspection records show 392.2WG ranks #172 out of 3,036 FMCSR codes by citation volume, with 8,972 citations written in just the last 12 months. New York alone generated 1,891 citations in the last 180 days, far outpacing every other state. Florida (388), Alaska (367), and Wisconsin (197) round out the top tier. If your fleet runs lanes through those states, your drivers are operating in the highest-scrutiny corridors for this specific code. Brief drivers accordingly before dispatching into NY-heavy routes.

Add a driver fitness self-certification section to your pre-trip form. It should require the driver to affirmatively answer — and sign — each of the following before departure:

• Hours of consecutive off-duty time prior to dispatch (minimum 10 hours documented)
• Any prescription or OTC medication taken in the last 12 hours that carries a drowsiness warning
• Current illness symptoms (fever, nausea, vertigo, respiratory distress)
• Sleep quality rating for the prior rest period (flag anything self-rated below acceptable)
• Hydration and meal status

The terminal dispatcher or safety supervisor should conduct a face-to-face or video check-in before departure — not just a phone call — so a trained observer can assess visible fatigue indicators. Pair this with your existing vehicle inspection so it becomes a single integrated stop rather than an afterthought. Our data shows 392.2WG citations are running at 1,653 in the last 90 days, so this is an active enforcement area, not a theoretical risk.

Drivers must carry:

• Current ELD or paper log showing compliant off-duty time before the trip
• Medical examiner's certificate confirming fitness for duty
• Any physician's note if returning from illness or injury

Carriers must retain:

• Completed pre-trip driver fitness self-certification forms (retain minimum 6 months; longer if your SMS BASIC is under scrutiny)
• Dispatch records showing scheduled vs. actual departure times — these can demonstrate a driver was not pressured into a fatigued start
• Any wellness or fitness-for-duty screening records
• For post-event defense: driver interview notes taken within 24 hours of the citation, ideally by a safety manager, not the dispatcher

Because 392.2WG carries a CSA severity weight of 8, every citation leaves a mark in your SMS profile. Clean documentation gives you the factual basis for a DataQs challenge if the citation was written without adequate evidentiary support.

The last 90 days of co-occurrence data reveals three high-signal patterns:

1. Seat belt and lane-related unsafe driving codes (392.2-SLLSR: 258 shared inspections; 392.2-SLLIFTA: 207 shared inspections): When fatigued-driving citations pair this frequently with other unsafe driving codes, it points to a driver who has already been observed by the inspector exhibiting erratic behavior before the stop — weaving, late braking, or failure to maintain lane. Root cause: your dispatching process is releasing drivers who are not fit to operate. Fix: pre-departure fitness checks with supervisor sign-off.

2. No proof of periodic inspection (396.17C-PI: 184 shared inspections): This pairing suggests inspections are happening at carriers where compliance culture is broadly weak — not just fatigued driving in isolation. Root cause: systemic documentation gaps. Fix: audit your periodic inspection file completeness immediately.

3. CDL validity issues (383.23A2-LCDLN: 93 shared inspections): Fatigue citations alongside CDL possession violations indicate some drivers in this pattern are operating outside authorized parameters entirely. Root cause: driver qualification file gaps. Fix: monthly MVR pulls and license expiration alerts in your DQF system.

392.2WG is a driver condition violation, not a vehicle defect, so there is no mechanical repair to verify before return to service. However, the co-occurrence data signals that cited inspections frequently include equipment-related violations alongside the fatigue citation — notably inoperable required lamps (393.9A-LIL: 88 shared inspections) and tire load limit violations (393.75G-TAOW: 91 shared inspections).

Before returning any driver to service after a 392.2WG citation:

1. Pull the full inspection report and verify every co-cited violation is corrected and documented on a DVIR.
2. Confirm the driver has taken adequate off-duty time and completes a new pre-trip fitness certification.
3. Have a supervisor — not a dispatcher — authorize the return-to-service decision in writing.
4. If any vehicle defect was cited in the same inspection, retain the repair order with the citation file.

Run a structured post-event review within 72 hours of receiving notice of a 392.2WG citation. Include: safety director, the cited driver, the dispatcher who approved departure, and the driver's direct supervisor.

Review agenda:

1. Reconstruct the 72 hours before the stop — hours worked, rest taken, dispatch timing, any known illness.
2. Pull ELD data and compare logged off-duty time against the dispatch schedule.
3. Interview the driver: was fatigue communicated to dispatch? Was departure pressure applied?
4. Review the pre-trip form for that day — was a fitness self-certification completed?
5. Identify which process gate failed (self-reporting, supervisor check, dispatch policy) and assign a corrective action owner with a deadline.

Document the entire review. If this driver or terminal appears in the top carrier citation patterns visible in TruckCodex data, escalate to a broader terminal audit rather than treating it as an isolated event.

392.2WG sits in the Unsafe Driving BASIC and carries a CSA severity weight of 8 — one of the higher severity weights in the category. Every citation accrues points against your Unsafe Driving BASIC score, with time-weighting applied (citations in the most recent 6 months carry the heaviest penalty).

Our inspection records show 8,972 citations written in the last 12 months for this code alone, and the monthly trend has been running above 600–900 citations per month for most of that period. At that enforcement volume, fleets with high mileage in states like New York — which generated 1,891 citations in 180 days — face meaningful BASIC exposure if pre-departure fitness screening is not systematic.

Because 392.2WG is not OOS-eligible (only 5 out of 14,811 all-time citations resulted in OOS placement, a 0.0% rate), the citation does not stop the vehicle. But it does accumulate in SMS, and the Unsafe Driving BASIC is one of the two that FMCSA and shippers watch most closely for intervention thresholds.

Our database shows Kenworth units account for 3,425 all-time 392.2WG citations and Peterbilt for 2,593 — together representing the two most-cited makes by a significant margin. These are predominantly long-haul tractor platforms, which confirms that the exposure is concentrated in over-the-road operations with irregular sleep schedules, not local or regional short-haul.

Priority training topics for OTR drivers operating those platforms:

1. Fatigue physiology — how sleep debt accumulates across multi-day runs and why 10 hours off-duty does not always equal 10 hours of sleep
2. Self-assessment techniques — validated alertness self-checks (psychomotor vigilance indicators) drivers can use before a shift
3. Medication interaction awareness — OTC cold, allergy, and pain medications that impair alertness and trigger 392.2WG exposure
4. Speaking up without fear — dispatcher-driver communication protocols so drivers can call off a run without career consequences
5. Sleep hygiene in the cab — blackout strategies, temperature management, noise reduction for quality rest

Challenge when you have documented evidence that contradicts the inspector's basis for the citation. Specific grounds:

• ELD records show compliant rest and the driver's pre-trip fitness form was signed — the inspector had no observable impairment evidence beyond a subjective impression
• The citation was written in conjunction with equipment violations (which our co-occurrence data shows is common — e.g., 88 shared inspections with inoperable lamps, 91 with tire violations) and the fatigue finding appears to have been added without independent evidentiary support
• Factual errors in the inspection report: wrong date, wrong driver, wrong vehicle

Do not challenge on the grounds that the driver was merely tired — that will not succeed. Challenge only when you can present affirmative documentation: ELD logs, pre-trip certification, supervisor check-in record, and if available, dashcam footage showing normal driving behavior in the minutes before the stop. Given the CSA severity weight of 8, a successful DataQs challenge removes real BASIC exposure.

Run a monthly self-audit of your driver fitness and pre-departure screening compliance. The trend data justifies this cadence: our inspection records show 392.2WG generated 8,972 citations over the last 12 months but 1,653 in just the last 90 days — meaning enforcement has been running hot in the most recent quarter. Monthly reviews let you catch process drift before it compounds into BASIC threshold exposure.

The audit should cover:

• Random sample of pre-trip fitness certifications (10% of departures minimum)
• Dispatch logs for evidence of departures scheduled with less than 10 hours off-duty preceding them
• Any driver self-reported illness or fatigue calls logged by dispatch — are they being honored or overridden?
• Terminal-level citation counts pulled from your SMS dashboard

For terminals operating heavily in New York (1,891 citations in 180 days) or Florida (388 citations), increase audit frequency to bi-weekly for those specific locations until pre-departure screening compliance reaches 100% documentation rate.