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

Fleet safety guidance on preventing 392.2DH citations. Inspector focus areas, pre-trip protocols, documentation, root-cause analysis, and self-audit cadence based on 13M+ inspection records.

Severity Weight
3
OOS Eligible
No
BASIC Category
Unsafe Driving
Code System
FMCSR
Code:
392.2DH
Code System:
FMCSR
BASIC Category:
Unsafe Driving
OOS Eligible:
No
Severity Weight:
3
Violation Group:
Misc Violations

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

Violation Description

Headlamps - Failing to dim when required

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when citing 392.2DH?

Our inspection records show 16 citations for 392.2DH in the last 12 months across the entire database. Iowa and Illinois account for 6 of those—Iowa with 4 citations and Illinois with 2—making them the primary enforcement zones. Inspectors focus on observable driver impairment: slow reaction times at the scale house, difficulty maintaining lane control, drooping eyelids or nodding during the inspection, slurred speech, or admission of illness. Unlike some violations, 392.2DH requires an officer's direct observation of impairment; it is not a mechanical defect. Pay particular attention to long-haul freight operations (FRHT vehicles represent 15 of 41 all-time citations in this code), where fatigue risk is highest. Inspectors will note the time of day, recent service hours, and driver statements about rest and health.

What should the pre-trip driver checklist include to prevent this citation?

Build a fatigue and health attestation into your daily pre-trip form. Require drivers to document: (1) hours slept in the last 24 hours; (2) current medications or symptoms affecting alertness; (3) time elapsed since last break; (4) any planned stops for rest before the next 100 miles. Include a self-assessment question: "Are you physically able to operate this vehicle safely?" with a required yes/no signature. Pair this with a driver-facing fatigue scale (e.g., 1–5 alertness rating). Do not treat this as a checkbox exercise—train drivers that honest reporting prevents citations and crashes. Review flagged responses before dispatch. This upstream control aligns with the regulation's intent: making the decision to operate unsafe vehicles impossible.

What documentation must drivers carry and carriers retain?

Retain the signed daily attestation described above for a minimum of 3 years. Pair it with electronic logs (ELDs): they show hours of service, driving time, and off-duty rest in an auditable format. If a citation is issued, the ELD record becomes your first defense—it proves whether the driver had adequate rest. Also document any medical incidents: if a driver reported illness or medication that day, retain copies of clinic visits, prescriptions, or communications about "not fit to drive" determinations. Train dispatchers to flag drivers who reported symptoms in the pre-trip; do not dispatch them without medical clearance or reassessment. In a post-citation review, compare the citation timestamp against ELDs, pre-trip forms, and any trip notes. This trail shows whether the violation was systemic (inadequate scheduling, ignored fatigue warnings) or isolated (undisclosed driver medical condition).

What root causes should a fleet investigate after a 392.2DH citation?

Although co-occurring violation data for 392.2DH specifically is limited due to its low citation volume (41 all-time, ranked #1687 of 3,036 codes), the broader 392.2 family (operating while ill/fatigued) shows patterns. Inspect scheduling practices: are drivers being assigned back-to-back loads without 10-hour breaks? Audit medication/health policies: are drivers disclosing medications that impair alertness, or hiding symptoms to avoid off-duty time? Review dispatch transparency: do trip planners know current driver fatigue levels, or are they assigning miles based only on freight deadlines? Check compliance culture: are drivers penalized for reporting fatigue, or rewarded for honesty? The 0.0% OOS rate for 392.2DH (versus the all-FMCSR average of 31.4%) suggests these citations reflect driver-level impairment rather than vehicle failure, pointing to hiring, training, or scheduling root causes rather than equipment.

How should fleet managers verify driver fitness before the vehicle returns to service after a citation?

Do not redeploy the cited driver without a documented medical assessment and a mandatory off-duty period of at least 10 hours (the FMCSR minimum). Require the driver to undergo a DOT physical or a fitness-for-duty evaluation if illness was the reason. For fatigue citations, mandate completion of fatigue awareness training and a signed pledge to report future fatigue without penalty. Have the driver re-sign your pre-trip attestation acknowledging the citation reason. At dispatch, assign a follow-up inspection window within 7 days: have a supervisor or DOT-trained observer monitor the first two legs of the driver's next run. Use this observation to confirm the driver is alert, reactive, and maintaining proper lane position. Document the clearance in the driver's file. This approach transforms a citation into a coaching moment rather than a purely punitive event.

What should the fleet's post-citation review process look like?

Within 48 hours of citation, pull: the inspection report, the driver's ELD record for the 72 hours prior, pre-trip attestations, dispatch logs, and any communication with the driver about rest or health that week. Schedule a 30-minute interview with the driver (and the dispatcher if scheduling is suspected). Ask: Had you reported fatigue or illness before the inspection? Were you offered a break or sent home? Did dispatch know your condition? Document answers. Cross-check the ELD: if the driver had only 4 hours rest but dispatch assigned a 10-hour drive, the root is scheduling. If the driver hid symptoms and had adequate rest, the root is driver honesty/selection. Classify the citation as "preventable" (dispatch error, ignored fatigue flags) or "unpreventable" (driver concealment, medical emergency). Feed preventable citations into your dispatch training and scheduling review. This rigor—done for all 41 all-time citations in this code—ensures you're identifying and fixing the actual systemic weakness.

How does a 392.2DH citation affect the carrier's CSA metrics and Safety BASIC scores?

FMCSR 392.2DH carries a CSA severity weight of 8, placing it in the middle tier of safety violations. Although it is ranked #1687 of 3,036 codes by citation volume (low frequency), each citation counts toward your Unsafe Driving BASIC in the CSA program. A single citation contributes less to your percentile than a high-frequency code, but fatigue/illness violations are high-profile in the eyes of insurers, brokers, and regulators because they directly cause crashes. The all-FMCSR average OOS rate is 31.4%; 392.2DH's 0.0% OOS rate means inspectors view it as a driver state issue, not a vehicle defect issue. Carriers see the greatest reputational and underwriting impact from clustering: if you rack up 3–4 in a year, brokers will flag your fatigue management practices even if your raw CSA percentile remains acceptable. Prevention here is about both compliance and market perception.

What training topics should be mandatory after a 392.2DH citation?

Require all drivers (not just the cited driver) to complete: (1) Fatigue Recognition & Management: teach sleep physiology, circadian rhythm impacts, and the 10-hour rule; (2) Medication & Health Disclosure: explain which OTC and prescription drugs impair alertness, and establish a no-penalty reporting process; (3) Recognizing Impairment in Yourself: self-check strategies (pull over every 2 hours, use the ALERT acronym—Awareness, Listening, Engagement, Reaction time, Thinking); (4) Dispatch Communication: empower drivers to say "I'm not safe to drive" without job jeopardy. Pair this with dispatcher training on fatigue-aware scheduling: teach them to build in buffer time and recognize driver signals. Because FRHT (Freightliner) vehicles represent 15 of 41 all-time citations and long-haul fleets are overrepresented, tailor training to multi-day trip operations. Make fatigue a safety conversation, not a compliance checkbox.

When should a fleet consider filing a DataQs challenge on a 392.2DH citation?

Challenge the citation if: (1) the inspection report contains factual errors (wrong vehicle ID, wrong driver name, incorrect timestamp); (2) the officer's observations contradict objective records (the ELD shows the driver had 9+ hours rest, but the report claims "nodding off"); (3) the driver was assessed by a medical professional during the inspection window who cleared them as fit to drive; or (4) the citation was issued in error (e.g., the driver was riding as a passenger, not operating). Do not challenge on the grounds that fatigue "is subjective"—officers have broad authority to assess impairment. If your ELD, pre-trip forms, and medical clearances are clean and well-retained, you have a strong evidentiary basis for a DataQs appeal. File within 120 days of citation. Weak or missing documentation (no pre-trip form, no ELD data) makes challenges unlikely to succeed. Invest in documentation discipline—it pays off when citations are contestable.

How often should the fleet audit for 392.2DH risk?

Establish a monthly self-audit of fatigue and fitness risks. Review the last 30 days of: (1) pre-trip attestations flagged for fatigue or illness; (2) dispatch patterns (are drivers being assigned excessive consecutive days?); (3) ELD trends (are any drivers consistently driving near the 11-hour limit?); (4) driver feedback or sick reports; (5) near-miss safety events involving driver alertness. Our inspection records show 2 citations in the last 90 days and 16 in the last 12 months, indicating an average rate of about 1.3 per month. While 392.2DH is a rare citation, its prevention is high-value because it directly prevents fatigue-related crashes. If your fleet exceeds 2 citations in a rolling 90-day window, escalate to a quarterly deep dive with executive attendance. This cadence is proportional to the violation's rarity (ranked #1687) but acknowledges its severity (CSA weight 8) and crash risk.

Last updated: 2026-04-20T18:45:39.963Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

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

1. Iowa
1
OOS 0.0%
2. Illinois
1
OOS 0.0%

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.