Prevention FAQ — FMCSR 392.2: Operating While Ill or Fatigued

Inspectors are looking for observable signs that a driver's ability or alertness is compromised to the point that continuing to operate is unsafe. Common triggers include slurred speech, bloodshot or heavy-lidded eyes, slow or confused responses to questions, admission of extended hours without sleep, or a demeanor inconsistent with being fit for duty. Our inspection records show 392.2 is the #1 most-cited FMCSR code out of 3,036 — 1,208,164 all-time citations — which tells you inspectors are well-practiced at identifying these cues. North Carolina and New Mexico are currently the highest-enforcement states (348 and 332 citations respectively in the last 180 days), so drivers operating in those corridors should expect heightened scrutiny. The key coaching point: how a driver presents at the window during any stop — not just weigh stations — is itself an inspection trigger.

Build a short fitness-for-duty gate into your pre-trip process, separate from the vehicle condition check:

1. Sleep verification: Driver self-reports hours of sleep in the preceding 24 hours. Flag anyone under 6 hours for dispatcher review before departure.
2. Medication review: Driver declares any prescription or OTC medication taken that carries a drowsiness or impairment warning.
3. Illness declaration: Driver confirms no fever, nausea, or acute symptoms that could impair reaction time.
4. Hours-of-service sync: Confirm ELD record matches driver's stated rest period before wheels roll — this directly connects to the 395.8 log falsification issues that co-occur with 392.2 in our database (25 shared inspections in 90 days).
5. Dispatcher sign-off: Require a named dispatcher to acknowledge the driver cleared the fitness check in your TMS or a timestamped log entry.

This checklist creates an audit trail and shifts detection upstream, before a roadside officer does it for you.

Drivers must carry current, accurate records of duty status (RODS) accessible on the ELD. Our data shows 392.2 co-occurs with 395.8A-ELD (failing to keep RODS) in 23 shared inspections and with 395.8E (false record of duty status) in 25 shared inspections within just the last 90 days — meaning incomplete or falsified logs are a compounding liability, not just a separate violation.

Carriers should retain:

• Pre-trip fitness-for-duty declarations (minimum 12 months recommended)
• ELD data exports covering the 72 hours preceding any cited inspection
• Driver qualification files including current medical certificates
• Dispatch logs showing assigned start times and loaded miles
• Any written driver communication requesting relief from dispatch due to fatigue

Retaining these records gives you a factual foundation for a DataQs challenge if the citation lacks supporting documentation, and they are the first thing FMCSA will request in a compliance review triggered by CSA score deterioration.

Across the last 90 days, three co-occurrence patterns stand out:

1. 392.2C and 392.2RG (63 and 62 shared inspections): These are sub-variants of the same fatigue cluster, meaning inspectors are citing multiple fatigue-related behaviors in a single stop. Root cause: drivers are operating well past impairment thresholds — this is a dispatch pressure or HOS planning failure, not a one-time lapse.

2. 396.17C — No proof of periodic inspection (44 shared inspections): A fatigued driver operating a vehicle without current inspection documentation suggests a systemic maintenance compliance gap. Fleets with poor PM tracking also tend to have weak driver oversight.

3. 383.23A2 — Operating without a CDL (29 shared inspections): When unlicensed drivers are behind the wheel, the driver qualification process has broken down entirely. These drivers are also more likely to be unfamiliar with HOS rules and fatigue management practices.

Address each with targeted corrective action: HOS audit for dispatchers, PM record audits, and a full DQ file review for the implicated driver pool.

392.2 carries a CSA severity weight of 8 — one of the highest possible scores under the BASIC system. Every citation adds to your Unsafe Driving BASIC, and because violations are time-weighted, recent citations hit harder than older ones. With 392.2 ranked #1 out of 3,036 FMCSR codes by citation volume at 1,208,164 all-time citations, FMCSA is well aware of how frequently this code appears, and it is a known intervention trigger.

The OOS rate for 392.2 is 0.8%, which is far below the all-FMCSR average OOS rate of 31.4%. That low OOS rate means most cited drivers keep rolling — but the citation still posts to FMCSA's Safety Measurement System and counts against your BASIC. Fleets that accumulate multiple 392.2 citations across a short window can cross the Unsafe Driving BASIC threshold that triggers an FMCSA warning letter or investigation. Build a citation tracking dashboard that flags any 392.2 citation within 24 hours of posting.

Run a structured five-step review within 72 hours:

1. Pull ELD records for the cited driver covering the 72 hours before the inspection. Look for HOS violations, short rest periods, or unusual on-duty time patterns.
2. Interview the dispatcher who assigned the load. Determine whether the driver requested relief or flagged fatigue before departure.
3. Review the pre-trip fitness declaration for that day. If none exists, that is its own corrective action item.
4. Check for co-occurring citations on the same inspection report — particularly 395.8E, 395.8A-ELD, or 396.17C, which our data shows frequently pair with 392.2. Each co-occurring violation needs its own root-cause thread.
5. Document findings in a corrective action report tied to the driver file, with a named responsible party and a completion date for each action item.

Forward the review summary to your safety director and retain it for at least 12 months in case the citation is used in a future compliance review.

Core training topics should include: recognizing personal fatigue signs before they reach impairment, understanding the biological limits of HOS rules (legal ≠ safe), sleep hygiene for irregular schedules, and how to communicate fatigue to dispatch without fear of penalty.

Our database shows FRHT-branded vehicles (109,090 all-time citations) and Freightliner (53,634) account for the two largest shares of 392.2 citations by vehicle make. If your fleet runs primarily Freightliner or Peterbilt (51,238 citations) equipment, your drivers are operating in the highest-exposure segment. That does not mean those trucks cause fatigue — it reflects where the inspection volume concentrates. Use that as a targeting tool: run your fatigue management refresher first with the drivers assigned to those units.

Also train dispatchers — not just drivers. Dispatch pressure is a documented upstream cause, and a severity weight of 8 per citation means every preventable event is expensive for the BASIC.

Our inspection records show a pronounced seasonal spike: 949 citations in May 2025 and 876 in June 2025, compared to 122 in November 2025 and 161 in December 2025. Citations in the last 90 days total 431, and the last 12 months show 4,378. That seasonal pattern — high spring and early summer, lower late fall and winter — suggests enforcement intensity rises in the same months when driver demand spikes.

Recommended audit cadence:

• Monthly: Pull ELD exception reports for any driver with rest periods under 8 hours on more than 3 shifts in a rolling 30-day window.
• Quarterly: Full HOS compliance audit cross-referenced against dispatch assignment records.
• Pre-summer (April): Targeted fitness-for-duty refresher and dispatcher coaching timed to the May–June enforcement surge shown in our data.

Do not wait for a citation to discover a systemic fatigue problem — by May, enforcement is already running at peak volume.

A DataQs challenge is worth filing when the citation record is factually inaccurate or unsupported by the officer's own documentation. For 392.2, the most defensible challenge scenarios are:

• No supporting documentation in the inspection report: If the officer checked 392.2 but recorded no observable indicators (slurred speech, admission of fatigue, HOS violation, etc.), the citation lacks evidentiary foundation.
• ELD data contradicts the fatigue claim: If the driver had a documented 10-hour rest break immediately before the inspection, and your ELD export confirms it, that is direct counter-evidence.
• Incorrect driver or vehicle identification: Clerical errors in USDOT number, driver CDL, or vehicle VIN can be corrected through DataQs.

With a 0.8% OOS rate on 1,208,164 citations, most 392.2 stops end in a citation without OOS status, which means the officer's subjective judgment is the primary evidence. That creates a meaningful window for challenge when your documentation is clean. Retain all pre-trip fitness declarations and ELD exports for at least 24 months specifically to support these reviews.

Return-to-service after a 392.2 event should follow a documented protocol, not a judgment call at the terminal:

1. Minimum documented rest: Require at least a full 10-hour off-duty period logged on the ELD before any return-to-service conversation begins.
2. Supervisor or safety manager sign-off: The driver should not self-clear. A named supervisor must complete a documented fitness-for-duty reassessment — verbal confirmation is not enough.
3. Medical evaluation if illness was cited: If the driver reported or displayed illness symptoms, require a physician clearance note before return, especially if the driver holds a medical examiner's certificate that may need review.
4. Load reassignment review: Confirm the returning driver is not being reassigned to the same dispatch pattern that produced the fatigue event. If a tight relay schedule caused the issue, repeating it immediately is a corrective action failure.
5. Document everything: The return-to-service sign-off belongs in the driver's file alongside the post-event corrective action report. If FMCSA reviews this citation in a future audit, the return-to-service record demonstrates your safety management system responded correctly.