Prevention FAQ — FMCSR 392.2H: Operating While Ill or Fatigued

Operational guidance for fleet safety managers on preventing 392.2H citations, inspector focus areas, pre-trip protocols, and root-cause analysis based on 17 all-time citations in our database.

OOS Eligible
Severity Weight
7
OOS Eligible
Yes
BASIC Category
Hours of Service
Code System
FMCSR
Code:
392.2H
Code System:
FMCSR
BASIC Category:
Hours of Service
OOS Eligible:
Yes
Severity Weight:
7
Violation Group:
Hours

Ranks #2,037 of 3,146 FMCSR codes by citation frequency • OOS rate of 47.1% is above the FMCSR-wide average of 33.3%.

Violation Description

State/Local Hours of Service

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What specific signs do roadside inspectors use to cite a driver under 392.2H?

Inspectors document observable impairment during the roadside interaction: slurred speech, slow reaction time, difficulty standing or maintaining balance, inability to follow simple instructions, or excessive drowsiness. Our inspection records show only 17 all-time citations under this code, with New Mexico recording 1 citation in the last 180 days at a 100% out-of-service rate, indicating inspectors cite this violation only when the impairment is unambiguous and poses immediate safety risk. The high OOS rate (47.1% across all 392.2H cases versus the 31.4% all-FMCSR average) reflects the serious nature of the observations. Inspectors typically assess alertness during license/documentation review, pre-inspection communication, and vehicle walk-around. Document the specific behavioral observations in your post-citation review rather than relying on vague language.

What should our pre-trip checklist include to prevent drivers from operating while fatigued?

Create a driver self-certification section completed at the start of each shift, separate from vehicle mechanical checklist. Include: (1) hours slept in the last 24 hours (target ≥6 hours), (2) any illness symptoms (fever, severe cough, dizziness, medication side effects), (3) caffeine/stimulant intake in the last 4 hours, (4) estimated trip duration and compliance with HOS rules. Driver signs and dates; dispatch retains copies. Add a checkpoint question: "Are you fit to operate safely?" with explicit permission to answer no without penalty. Train drivers that disclosing fatigue or illness prevents citations and protects lives. Many carriers use mobile apps or QR-code prompts to standardize this. The goal is creating a culture where drivers self-report rather than risk a 392.2H citation during inspection.

What documentation must we keep if a driver reports fatigue or illness mid-shift?

Retain: (1) driver's written or recorded statement of the condition and time reported, (2) dispatch log entry confirming the report, (3) decision record (reassign route, pull driver from service, authorize rest), (4) duration of rest taken before return to duty, (5) any medical evaluation or note if the driver visited a clinic or urgent care. If illness is work-related (e.g., injury from loading/unloading), document incident details separately in your safety record. Inspectors and compliance auditors review these to show your fleet acted responsibly. Lack of documentation can signal negligence in a CSA audit. Establish a standardized form or email template so dispatch consistently records these events. Keep records for at least 12 months to identify patterns (e.g., chronic fatigue among night-shift drivers, seasonal illness clusters).

What root causes typically lead to 392.2H citations based on co-occurring violations?

Our inspection records show 392.2H (17 all-time citations) is rare compared to the broader 392.2 category, which spans over 1.2 million citations. The 47.1% out-of-service rate for 392.2H suggests inspectors cite this code only when impairment is severe. Common contributing patterns include: inadequate scheduling (drivers forced to operate on minimal rest to meet tight deliveries), untreated chronic conditions or unmanaged medication side effects, and peer pressure or compensation incentives that discourage reporting fatigue. Analyze your own citations and near-misses: interview drivers cited for moving violations (speeding, unsafe lane changes, following too closely) to determine whether fatigue was a factor. Driver fatigue amplifies other safety risks; a fatigued driver is more likely to speed or make poor decisions. Build root-cause analysis into your post-citation review process by asking: What shift/route was this? How many hours had the driver worked in the prior 48 hours? Was there adequate rest opportunity?

How should we verify a driver is fit to return to duty after reporting illness mid-shift?

Establish a clear return-to-duty (RTD) protocol. For minor illness (mild cold, headache): driver must rest ≥2 hours, self-report symptom improvement, and confirm alertness before resuming. For moderate illness (fever, dizziness, significant pain): require a clinic visit or telemedicine consultation with documented provider clearance before duty. For severe symptoms: pull driver from service until symptom-free or medically cleared. Document the provider's statement in your safety file. For fatigue, enforce a minimum rest period (typically ≥4 hours) before RTD regardless of driver request; confirm rest with driver check-in call or mobile app geolocation. Never rely solely on driver assertion of fitness. A brief conversation ("Can you drive safely right now?") is insufficient if the driver appeared impaired earlier. This prevents 392.2H citations by ensuring inspectors never encounter a driver who should not be operating.

What should our post-citation review process include after a 392.2H citation?

Within 48 hours of a citation, schedule a confidential meeting with the driver (not punitive). Cover: (1) What led to the condition—fatigue, illness, medication, personal stress? (2) Were there warning signs the driver ignored or failed to recognize? (3) Could the driver have safely reported and rested instead? (4) What support does the driver need—modified schedule, medical evaluation, EAP referral? Then conduct a systems review: (1) Was the assigned route unreasonably tight? (2) Do shift patterns or load assignments create chronic fatigue risk? (3) Are HOS compliance practices adequately monitored? (4) Does your dispatcher culture encourage drivers to report fatigue without fear? Document findings and corrective actions in your compliance file. If multiple drivers cite fatigue as a root cause, escalate to management—this signals a scheduling or culture problem requiring systemic fixes, not just driver retraining.

Does a 392.2H citation affect our CSA score or carrier safety ratings?

The 392.2H code carries a CSA severity weight of 8, placing it in the upper-mid range of violation seriousness. Our database ranks 392.2H at #2011 of 3,036 FMCSR codes by citation volume, meaning it is extremely rare. However, when cited, the 47.1% out-of-service rate (compared to the 31.4% all-FMCSR average) indicates inspectors treat this violation as a significant safety event. A single 392.2H citation contributes to your Unsafe Driving BASIC score in CSA, which affects insurance rates, customer audits, and DOT safety ratings. The rarity of citations also means one citation stands out more in a small citation history than in a high-volume history. Prioritize prevention: our records show only 2 citations in the last 12 months nationally, meaning this violation is relatively uncommon but high-impact when it occurs.

What training topics should we require for drivers to reduce 392.2H risk?

Focus training on three areas: (1) Recognizing impairment in yourself: fatigue signs (difficulty focusing, frequent blinking, delayed reactions), illness symptoms requiring duty removal, and medication side effects. (2) Reporting without penalty: explicitly train drivers that disclosing fatigue or illness will not result in disciplinary action and prevents citations, accidents, and liability. (3) HOS compliance and rest strategy: help drivers understand their obligations under HOS rules and how to plan rest effectively rather than pushing through fatigue. Use peer-led discussion (have drivers who've been cited share their experience) rather than generic videos. Include scenario-based training: "You're 3 hours into a 10-hour shift and feeling dizzy. What do you do?" Require annual refresher training with signed acknowledgment. Consider fatigue management and health screening during annual medical certifications. Our inspection records show 17 all-time citations, indicating most drivers operate safely—reinforce the positive safety culture in your fleet.

When should we consider filing a DataQs challenge for a 392.2H citation?

Challenge if: (1) The inspector's observation notes contradict the citation (e.g., driver documented as alert and coherent in interaction notes, but cited for fatigue), (2) The driver has independent evidence of fitness (medical clearance, telemedicine consultation timestamp, HOS logs showing adequate rest), or (3) The citation was issued after an accident/incident, and causality is disputed. Our inspection records show 17 all-time citations, most resulting in out-of-service actions (8 OOS of 17 total). If your driver was NOT placed out of service despite the citation, this may indicate inspector uncertainty—gather that evidence. However, do not challenge if the inspector documented clear observations (slurred speech, inability to follow instructions, excessive drowsiness). Challenges based on "the driver says they were fine" without corroborating evidence are unlikely to succeed. Consult your legal or compliance team; a weak challenge damages your credibility with inspectors. The goal is accuracy, not score-gaming.

How often should we audit our fleet for fatigue and illness risk factors?

Our inspection records show 0 citations in the last 90 days but 2 citations in the last 12 months (August and November 2025), indicating this violation occurs sporadically rather than in clusters. We recommend a quarterly self-audit focused on: (1) Hours-of-service compliance (sample 5–10 drivers' logs each quarter), (2) Driver self-reported fatigue/illness incidents (review your internal incident log), (3) Accident/near-miss review for fatigue or illness as contributing factors, (4) Shift schedule patterns that create chronic fatigue risk. Supplement with an annual comprehensive audit: driver interviews (anonymous survey), schedule review, and fatigue management policy effectiveness assessment. The rarity of 392.2H citations nationally means fatigue and illness prevention works best as a culture and systems issue rather than a reactive compliance program. Use quarterly audits to catch problems before inspectors do.

Last updated: 2026-04-20T16:31:11.262Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.