Prevention FAQ — FMCSR 392.2C: Driver Illness & Fatigue

Inspectors are looking for observable, in-the-moment indicators that a driver's alertness or physical condition makes continued operation unsafe. Common triggers include bloodshot or glassy eyes, slurred speech, slowed reaction, inability to answer basic questions coherently, or a driver who admits to illness or fatigue during the stop.

Our inspection records show enforcement is heavily concentrated in a small number of states. In the last 180 days, New Mexico generated 1,562 citations — nearly double Iowa's 845 and more than twice Texas's 744. If your lanes run through NM or IA, inspectors in those corridors are clearly active on this code. Brief your drivers on what a "fitness for duty" roadside assessment looks like before they enter those states, so they understand the interaction, not just the regulation.

Build a brief self-certification step into your pre-trip routine — separate from the vehicle walk-around. The driver should confirm:

• Sleep: Minimum 8 hours of off-duty rest, not broken rest in a sleeper.
• Illness: No active fever, nausea, dizziness, or medication side effects impairing alertness.
• Medications: Any OTC or prescription drugs reviewed against a known impairing-substance list.
• Stress/mental fatigue: Recent personal distress that could affect cognitive function.

Have the driver sign or digitally confirm this checklist in your dispatch system before departure. That record creates a contemporaneous log showing the carrier exercised reasonable oversight. It also creates a natural intervention point — if a driver can't honestly check every box, the dispatcher has documented grounds to hold the load.

Carriers cannot produce a document that un-issues a citation, but the right paper trail supports a DataQs challenge and demonstrates a culture of compliance. Retain:

• Pre-trip fitness-for-duty logs signed by the driver, time-stamped at dispatch.
• Hours of Service records (RODs or ELD logs) showing adequate off-duty time before the cited dispatch — our data shows 82 inspections in the last 90 days paired 392.2C with 395.8E (false record of duty status), meaning inspectors cross-check these directly.
• Dispatch notes showing the load was not tendered under coercive scheduling pressure.
• Driver communication records if a driver raised a concern about their condition.

Retain all of the above for at least 12 months. The ELD logs are legally required, but the fitness-for-duty record is your differentiator in any review.

The co-occurrence data from the last 90 days reveals three distinct systemic patterns:

1. Hours of Service breakdown: 392.2C appeared alongside 395.8E (false duty status records) in 82 shared inspections and 395.8A-ELD (failing to keep RODs) in 69 shared inspections. When HOS compliance collapses, fatigued driving follows — these are symptoms of the same scheduling or coaching failure.

2. Vehicle maintenance neglect: 396.17C (no proof of periodic inspection) co-occurred in 121 shared inspections, and 393.9 (inoperable required lamp) in 118. A driver who is not stopping to inspect equipment is also not stopping to assess their own fitness — both point to a skip-the-process culture.

3. Emergency preparedness gaps: 393.95A (fire extinguisher missing/defective) appeared in 85 shared inspections. Carriers seeing this pattern have drivers who are not completing full pre-trip procedures at all, which is a training and accountability problem, not just a fatigue problem.

FMCSR 392.2C carries a CSA severity weight of 8 — one of the higher weights in the Unsafe Driving BASIC. For context, the all-FMCSR average out-of-service rate is 31.4%; this code's OOS rate across all-time records is effectively 0.0% (only 2 of 16,197 citations resulted in OOS placement), so the immediate operational disruption is minimal. However, the severity weight means each citation hits the Unsafe Driving BASIC harder than most codes.

This code ranks #159 out of 3,036 FMCSR codes by citation volume, so inspectors know it well and use it. Peer codes in the same category — particularly 392.2 with 1,208,164 citations — show how broadly the unsafe driving family is enforced. A pattern of 392.2C citations without remediation will push a carrier's BASIC percentile and attract targeted inspections.

Run a structured post-event review within 72 hours of the citation. Cover these five areas:

1. HOS audit: Pull the cited driver's RODs or ELD logs for the 7 days prior. Look for short off-duty windows, split-sleeper patterns, or any indication the dispatch system pushed a load that compressed rest time.
2. Fitness-for-duty record: Did the driver complete a pre-trip self-certification? If not, that is a policy gap, not just a driver failure.
3. Dispatcher review: Was the load tendered on a timeline that made adequate rest impractical? Review the dispatch notes.
4. Co-occurring violations: The cited inspection report will show any additional violations. Cross-reference against the known co-occurrence patterns — particularly HOS and equipment maintenance codes — to identify whether this was an isolated incident or a systemic breakdown.
5. Driver interview: Conduct a candid, non-punitive conversation. If the driver knew they were impaired and drove anyway, that is a coaching issue. If they felt pressure to drive, that is a management issue.

Our inspection records show Freightliner (FRHT) accounts for 5,514 of all-time 392.2C citations — by a wide margin over the next-highest makes (UTIL at 1,977 and KW at 1,733). Freightliner is the most common heavy truck make on American roads, so the volume reflects fleet size, but it also means your Freightliner operators are statistically the most likely to face this citation. Tailor training delivery to where your drivers actually sit.

Core training topics:

• Recognizing personal fatigue signs before they become a roadside event.
• The legal right — and obligation — to refuse dispatch when unfit.
• Medication awareness: a structured review of OTC and prescription drugs that impair CMV operation.
• HOS rules as a fatigue-prevention tool, not just a compliance box.
• How a roadside fitness-for-duty assessment unfolds, so drivers know what to expect and how to respond professionally.

Our database shows 1,822 citations in the last 90 days versus 8,908 in the last 12 months — meaning the last 90 days represent roughly 20% of the annual total, which is consistent with a sustained, year-round enforcement pattern rather than a seasonal spike. Monthly counts peaked at 1,121 in July 2025 and were still 741 in March 2026, confirming this is not a weather-season or enforcement-campaign phenomenon.

Recommended cadence:

• Monthly: Pull your fleet's HOS exception reports and any internal fitness-for-duty log gaps. Review any 392.2C citations from the prior 30 days.
• Quarterly: Full audit of pre-trip fitness-for-duty compliance rates by terminal or dispatcher. Cross-reference against HOS violations to identify the co-occurrence pattern in your own data.
• Annually: Refresh driver training on fatigue recognition and medication awareness. The consistent 90-day volume justifies treating this as a standing program item, not a one-time corrective action.

A DataQs challenge is appropriate when the cited inspection record contains a factual error or when the citation was issued without observable, documented basis. Specific grounds to evaluate:

• Contradicted by HOS records: If the driver's ELD logs show a full 10-hour off-duty period immediately before the inspection, and the inspector's notes rely solely on subjective observation with no corroborating evidence, that record is challengeable.
• Clerical or jurisdictional errors: Wrong driver, wrong vehicle, incorrect USDOT number, or the inspection occurred outside the state's jurisdiction.
• No supporting documentation in the inspection report: A 392.2C citation requires the inspector to document the specific indicators observed. If the report lacks that detail, challenge it.

Note: the code's 0.0% OOS rate across 16,197 citations means inspectors are writing these citations without pulling drivers off the road — which can indicate the evidentiary standard in the report is thin. That makes DataQs review particularly worthwhile for this specific code.

Because 392.2C is not an OOS-eligible code — all-time records show only 2 out of 16,197 citations resulted in an out-of-service order — there is no federal reinstatement requirement. However, that absence of a mandatory process is not a green light to immediately redispatch.

Establish an internal return-to-service protocol:

1. Safety manager review: The citation should trigger a hold on the driver's next dispatch until a supervisor has reviewed the inspection report and spoken with the driver.
2. Rest verification: Confirm the driver has taken a full, uninterrupted off-duty period before the next dispatch — documented in the ELD, not estimated.
3. Medical clearance if illness was cited: If the inspector's notes reference illness rather than fatigue, require a written medical clearance before the driver returns to a CMV.
4. Dispatcher acknowledgment: The assigning dispatcher should log that they reviewed the prior citation before tendering the next load.

This process creates an audit trail and closes the loop between the roadside event and your dispatch system.