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

Fleet safety guidance on 392.2FC citations, pre-trip protocols, co-occurrence patterns, and audit cadence based on 13M+ inspection records.

Severity Weight
8
OOS Eligible
No
BASIC Category
Unsafe Driving
Code System
FMCSR
Code:
392.2FC
Code System:
FMCSR
BASIC Category:
Unsafe Driving
OOS Eligible:
No
Severity Weight:
8

Ranks #714 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.1% is below the FMCSR-wide average of 33.3%.

Violation Description

Operating a commercial motor vehicle while the driver's ability or alertness is so impaired through fatigue, illness, or any other cause as to make it unsafe for the driver to begin or continue to operate the vehicle.

Prevention FAQ for Fleet Managers

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

What specific behaviors do roadside inspectors cite for 392.2FC?

Across our inspection records, 392.2FC citations spike in Iowa (64 in the last 180 days), Texas (40), and Illinois (38), suggesting inspectors in these states actively screen for signs of impairment: swerving, erratic lane control, slow reaction to traffic, nodding off, or admission of fatigue during roadside interaction. Our data shows 476 citations over the last 12 months nationally. Inspectors don't require a positive drug or alcohol result—they document observable signs that the driver's alertness is compromised. Train your dispatch and safety team to recognize these warning indicators before a vehicle leaves the yard, not after an inspector catches it on the road.

What must a pre-trip checklist include to prevent fatigue citations?

Your pre-trip should go beyond vehicle condition and include a driver wellness gate: (1) Did the driver sleep ≥6 hours in the last 24? (2) Is there a known illness, medication side effect, or injury affecting alertness? (3) Has the driver consumed alcohol or used substances in the past 8 hours? (4) Is there fatigue from a recent long haul or insufficient rest day? Document each yes/no answer and have the driver sign. If any answer is 'yes,' hold the vehicle. This is especially critical given that 392.2FC frequently co-occurs with 392.2RG (14 shared inspections in the last 90 days)—a signal that the same driver impairment is being cited under variant codes, indicating systemic fatigue management gaps.

What records must drivers carry and the fleet retain for 392.2FC defense?

Maintain three documentation layers: (1) Driver logs & ELDs: 395.8A-ELD violations co-occur 4 times in the last 90 days with 392.2FC, showing inspectors correlate poor RODS records with fatigue claims. Ensure ELD data is accurate and retained for 2 years. (2) Medical clearance: If a driver has a known condition (sleep apnea, diabetes, medication), keep medical fitness-for-duty certificates on file. (3) Dispatch & routing records: Show hours between trips, actual rest periods, and whether the assignment was realistic. If cited, these records are your first line of defense in a DataQs challenge or carrier safety review.

What root causes do our co-occurrence patterns reveal?

Our last 90 days show three critical patterns: (1) Speeding paired with fatigue: 11 co-occurrences with 392.2-SLLS1 (speeding 1–5 mph over). Fatigued drivers often unconsciously accelerate or fail to adjust for conditions—inspect dispatch incentives that reward speed over safety. (2) Maintenance gaps enabling fatigue: 10 co-occurrences with 396.17C (no proof of periodic inspection). Poor vehicle maintenance can exhaust drivers through rough handling or breakdowns mid-trip. (3) Vision obstruction + fatigue: 9 co-occurrences with 393.9 (inoperable lamps). Tired drivers struggle more with reduced visibility—ensure headlights, marker lights, and wipers are always road-ready. Address root cause, not just the citation.

How should a fleet verify repairs or fitness after a 392.2FC citation?

A 392.2FC citation is not a vehicle repair issue—it's a driver fitness issue. The corrective action is driver retraining and medical evaluation, not a shop visit. Post-citation protocol: (1) Pull the driver's ELD for the 14 days prior to the citation; verify hours logged vs. actual rest. (2) Schedule a medical evaluation if the driver has sleep disorders, chronic illness, or medication changes. (3) Have the driver complete DOT-mandated fatigue awareness training (FMCSA-approved module). (4) Review dispatch for that driver's route complexity and load assignment. Only release the driver back to road operation once medical clearance and training are documented and signed.

What should the fleet review after receiving a 392.2FC citation?

Initiate a 5-step post-citation review: (1) Interview the cited driver under neutral conditions—document exact circumstances (time of day, drive duration, medical status, sleep quality). (2) Audit that driver's prior 30 days of ELD data for compliance with 395.8A rules; flag any pattern of short rest periods or repeated early morning departures. (3) Review dispatch assignments for that driver over the same period—were routes realistic for the assigned vehicle and load? (4) Check vehicle maintenance records for the cited unit against 396.17C and 393.9 standards. (5) Flag any repeat offender: if this driver has prior 392.2FC or 392.2RG citations, escalate to mandatory medical clearance and retraining before return to service. Document all findings in your safety management system.

Does 392.2FC impact my carrier's CSA score or Safety BASIC?

Yes. Our inspection records show 392.2FC carries a CSA severity weight of 8, placing it in the mid-to-high range for unsafe driving violations. Although ranked #706 out of 3,036 FMCSR codes by citation volume, each citation contributes to your Unsafe Driving BASIC score and feeds CSA carrier risk profiles reviewed by regulators and brokers. Notably, our all-FMCSR average OOS rate is 31.4%, yet 392.2FC has only a 0.1% OOS rate—meaning inspectors are citing driver impairment without placing vehicles out of service. This signals regulatory confidence in the violation; accumulation of citations will trigger compliance reviews. Proactive prevention is far cheaper than remediating a degraded safety rating.

What driver training topics prevent 392.2FC citations?

Deploy targeted training covering: (1) Sleep hygiene and circadian rhythm: Teach drivers how fatigue impairs reaction time and decision-making, especially for long-haul routes. Use data from your own fleet—show that Freightliner units (367 all-time citations) and Kenworth units (144 citations) dominate the citation mix, often in over-the-road assignments. (2) Medication and illness recognition: Train drivers to self-assess before departure; emphasize that cold medicine, allergy meds, or untreated sleep apnea can trigger citations. (3) Micro-sleep and drowsy driving markers: Cover the physiological signs (head nodding, lane drifting) so drivers can self-correct before an inspector sees them. (4) Dispatcher communication: Empower drivers to request rest without penalty if fatigued. Include this in your safety culture messaging and incentive structure.

When should the fleet file a DataQs challenge on a 392.2FC citation?

DataQs challenges are appropriate if: (1) Inspector observation documentation is vague or missing: If the inspection report does not specify which observable behaviors (swerving, nodding, slurred speech) led to the citation, challenge it on evidentiary grounds. (2) ELD or medical records contradict the violation: If your driver's ELD shows 8+ hours of rest immediately before the cited trip, and medical records show no illness, the citation may not withstand review. (3) Procedural error: If the inspector failed to document the driver's response, medical history, or reason for the stop, cite the procedural gap. However, do not challenge frivolously—our data shows only 1 out-of-service placement across 1,039 all-time citations (0.1% OOS rate), meaning inspectors exercise restraint. A strong challenge requires documentary evidence, not driver disagreement.

How often should the fleet audit for 392.2FC risk?

Audit monthly, with intensity tied to recent trends. Our last 90 days show 77 citations (avg. 25.7 per month), while the last 12 months total 476 (avg. 39.7 per month), indicating seasonal and operational fluctuation. May and September spiked at 67 and 54 citations respectively; April and November were lowest at 22 and 28. Audit cadence: (1) Monthly: Review all drivers assigned to long-haul or multi-day routes; check their ELD compliance and medical status. (2) Quarterly deep-dive: Audit the top states where your fleet operates (Iowa, Texas, Illinois showed 142 combined citations in 180 days). (3) Post-incident: Immediately after any fatigue-related citation or near-miss, conduct a full safety review. Use monthly audits to stay ahead of the seasonal peaks and ensure drivers operate rested and medically fit.

Last updated: 2026-04-20T14:11:39.837Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 392.2FC is most commonly cited (last 180 days)

1. Illinois
45
OOS 0.0%
2. Iowa
32
OOS 0.0%
3. Texas
22
OOS 0.0%
4. New Mexico
12
OOS 0.0%
5. North Carolina
6
OOS 0.0%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.