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

Inspectors issuing 392.2IN don't need a breathalyzer or a medical test — they're documenting observable impairment. Red flags include bloodshot or glassy eyes, slurred or incoherent speech, inability to answer basic questions about the route or load, visible head-nodding or micro-sleep at a scale or port of entry, and erratic driving behavior leading up to the stop.

Our inspection records show Iowa accounts for 225 citations in the last 180 days alone, more than double any other state in that window. Illinois (103 citations) and New Mexico (76 citations) follow. Iowa's volume strongly suggests an enforcement culture at weigh stations there that specifically watches for fatigue indicators during after-midnight or early-morning stops. Brief your drivers that in IA, IL, and NM in particular, any indicator of reduced alertness will draw scrutiny beyond the standard Level I inspection.

Build a two-part fatigue-and-illness gate into the pre-trip workflow:

Driver self-assessment (recorded):

• Hours slept in the last 24 hours (require a minimum threshold you define — common practice is 6+ hours)
• Any illness symptoms: fever, dizziness, medication use that causes drowsiness
• Time since last full meal and hydration status

Dispatcher verbal check:

• Dispatcher confirms the driver's voice quality and responsiveness during the dispatch call
• Any dispatch-logged concern triggers a supervisor callback before wheels roll

Vehicle tie-in: Our data shows 392.2IN frequently co-occurs with 393.9 (inoperable required lamp, 40 shared inspections in the last 90 days). A fatigued driver who skipped a thorough pre-trip also missed a burned-out lamp. Use that linkage: a sloppy pre-trip walk-around is itself a fatigue indicator. If the driver can't complete the physical inspection accurately, they shouldn't be dispatched.

Because 392.2IN is a subjective, observation-based citation, documentation is your primary defense lever.

Drivers should carry:

• Completed pre-trip inspection report (signed and dated, timestamped if electronic)
• Current hours-of-service logs showing compliant rest periods immediately before dispatch
• Prescription or OTC medication list, if applicable, signed by a physician confirming it does not impair driving

Carriers must retain:

• Dispatcher call logs or electronic dispatch records noting the driver's condition at assignment
• Any driver self-assessment forms completed that shift
• HOS records for the prior 8 days (regulatory minimum), but retain 30 days internally for pattern analysis
• Medical examiner certificates showing current physical qualification status — particularly relevant given that 391.41A (physical qualification) appeared in 19 shared inspections in the last 90 days alongside 392.2IN

Retention gaps in any of these categories will make a DataQs challenge nearly impossible to win.

Our inspection records from the last 90 days reveal three dominant co-occurrence patterns that point to specific systemic failures:

1. 392.2RG (90 shared inspections): This is the most frequent pairing. 392.2RG and 392.2IN are both fatigue/illness codes — seeing them together at the same inspection suggests inspectors are writing multiple fatigue-related violations on the same event. This indicates the driver's condition was unambiguous and likely severe. Root cause: dispatch pressure overriding fitness-for-duty gates.

2. 396.17C — No proof of periodic inspection (63 shared inspections): A vehicle with no inspection documentation traveling with an impaired driver is a double compliance failure. Root cause: maintenance program gaps that also reflect a broader safety culture problem at the terminal level.

3. 393.9 — Inoperable required lamp (40 shared inspections): An impaired driver skipped or rushed the pre-trip walk-around. Root cause: fatigue presenting before dispatch, not caught by the pre-trip gate. This is a leading indicator — fix the pre-trip process to catch it upstream.

Because 392.2IN is not OOS-eligible (only 8 of 3,021 all-time citations resulted in an OOS order), the driver technically may continue operating after citation. However, returning that driver to the cab immediately without review is a liability and safety exposure.

Minimum return-to-service protocol:

1. Remove the driver from service for the remainder of that shift regardless of OOS status
2. Require a documented rest period of at least 8 hours before the next dispatch
3. Conduct a supervisor-witnessed fitness-for-duty check at the next pre-trip
4. If illness is claimed, require a physician clearance note before the driver operates again
5. Pull and review that driver's HOS logs for the prior 7 days to confirm the rest record matches the claimed rest
6. Document every step — if this driver receives a second 392.2IN citation, that documentation file becomes essential for both FMCSA interaction and internal disciplinary proceedings.

392.2IN carries a CSA severity weight of 8 out of a possible 10, placing it among the more heavily weighted violations in the Unsafe Driving BASIC. A single citation adds 8 severity points to the inspecting driver's record before time-weighting multipliers are applied (most recent violations carry the highest multiplier).

In terms of enforcement volume context, 392.2IN ranks #439 out of 3,036 FMCSR codes by all-time citation count, with 3,021 total citations in our database. That's a moderately cited code — not among the most common violations inspectors write, but the severity weight means each citation punches well above its frequency. For high-mileage carriers where drivers accumulate inspections quickly, two or three 392.2IN citations in a 24-month window can materially move a carrier's Unsafe Driving BASIC toward intervention thresholds. Fleet managers should treat each citation as a high-value event warranting root-cause review, not just a single-driver corrective action.

Run a structured debrief using this sequence:

1. Pull the inspection report and confirm the inspector's stated observable indicators. Were they accurately documented? Are there factual errors suitable for a DataQs challenge?
2. Interview the driver — document in writing what the driver reports about sleep, illness, and the hours leading up to the stop
3. Cross-reference HOS logs against the driver's stated rest. Discrepancies between logs and the driver's account are a red flag requiring deeper review
4. Review the dispatch record — who assigned this load, when, and was any fitness concern raised or ignored?
5. Check for co-occurring violations — if 396.17C (no periodic inspection proof) or 393.9 (inoperable lamp) also appeared on the same inspection report, escalate to a maintenance program audit, not just a driver counseling session
6. Document findings and corrective actions in the driver's safety file with a completion date for each action item
7. Brief the driver's dispatcher on findings — dispatcher behavior is frequently the upstream cause of a driver fatigue event

Our inspection records show Freightliner (FRHT) vehicles account for 713 all-time 392.2IN citations — more than double the next highest make, International (INTL) at 336 citations. Peterbilt (PTRB, 278) and Kenworth (KW, 263) also appear prominently. If your fleet runs predominantly Freightliner or International equipment, your drivers represent the most-cited population and should be prioritized in training cycles.

Core training topics to cover:

• Recognizing personal fatigue warning signs before they become impairment (not just hour limits — subjective self-assessment)
• The right to refuse dispatch when unfit, and how to report without fear of retaliation
• HOS rules as a floor, not a ceiling — legal hours don't equal safe hours
• Medication awareness: OTC drugs (antihistamines, cold medicines) that impair driving and require a physician consult before operating
• Pre-trip inspection rigor as a proxy for fitness — a thorough walk-around requires the alertness to complete it accurately

Tie training records to the specific vehicle makes in your fleet so you can demonstrate targeted intervention to FMCSA reviewers.

A DataQs challenge on 392.2IN is appropriate only when there is documentable factual error — not when the driver simply disagrees with the inspector's subjective assessment.

Pursue a challenge when:

• The inspection report contains an incorrect USDOT number, driver license number, or vehicle ID
• The date, time, or location recorded is demonstrably wrong (contradicted by ELD data or dispatch records)
• The driver's HOS logs and ELD data clearly show a compliant rest period immediately preceding the stop, directly contradicting the impairment finding
• A physician clearance note issued within 24 hours of the stop documents no impairment-causing condition

Do not pursue a challenge when:

• The only evidence is the driver saying they felt fine
• No contemporaneous documentation of adequate rest or fitness exists

Note that with a 0.3% all-time OOS rate across 3,021 citations, the vast majority of 392.2IN stops end without an OOS order — meaning the citation stands on the record but the driver continued operating. The CSA severity weight of 8 still applies, making accurate challenges worth pursuing when the facts support it.

Our inspection data shows a clear seasonal pattern that should drive your audit calendar. Citations spiked to 162 in June 2026, 156 in May 2026, and 148 in July 2026 — a sustained summer peak. The last 12 months total 1,222 citations nationally, while the last 90 days show 230 citations, indicating the code remains actively enforced.

Recommended audit cadence:

• Quarterly deep audits aligned to the seasonal spike: run your most thorough review in April–May ahead of the summer enforcement peak, then again in September to close out summer exposure
• Monthly spot checks during May–August: pull a random sample of 10–15 pre-trip inspection forms and cross-reference against HOS logs for that shift to verify rest compliance was documented before dispatch
• After any citation event: trigger an immediate unscheduled audit of that driver's terminal covering the prior 30 days of dispatch records and pre-trip logs

The jump from 57 citations in April 2025 to 162 in June 2025 — nearly a 3x increase in 60 days — means fleets that aren't auditing in spring are already behind by the time summer enforcement peaks.