Prevention FAQ — FMCSR 392.2-ML: Operating While Ill or Fatigued
Fleet safety guidance on preventing 392.2-ML citations. Covers inspector focus areas, pre-trip protocols, documentation, root-cause analysis using real co-occurrence data, and audit cadence based on 13M+ inspection records.
- Code:
- 392.2-ML
- Code System:
- FMCSR
- BASIC Category:
- Unsafe Driving
- OOS Eligible:
- No
- Severity Weight:
- 8
Ranks #740 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.2% 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 focus on when citing 392.2-ML?
Our inspection records show this code is cited in only 58 cases over the last 90 days nationwide—making it a rare citation relative to other unsafe driving violations. However, when inspectors do cite it, they are evaluating observable signs: bloodshot or glassy eyes, slurred speech, slow reflexes, inability to maintain lane discipline, or driver admission of exhaustion or illness. In Iowa, the enforcement leader with 46 citations over the last 180 days, inspectors are clearly calibrated to detect and document these conditions. The 0.2% out-of-service rate (only 2 of 950 all-time citations resulted in OOS) suggests inspectors cite this code primarily when the driver is deemed unsafe but the violation does not warrant immediate vehicle impound. Train your safety team to recognize that inspectors are looking for documented observable impairment, not speculation.
› What should be on our pre-trip driver checklist to prevent this violation?
Build a mandatory daily self-assessment that includes: (1) hours of sleep in the last 24 hours—drivers must affirm ≥5 hours; (2) current health status—fever, dizziness, medication side effects, or illness mandates off-duty rest or replacement driver; (3) medication review—OTC cold/allergy products with drowsiness warnings must be flagged; (4) caffeine and meal timing—no long haul on empty stomach or after large carb load without protein. Have drivers initial and date this sheet; retain for 30 days minimum. This creates an early detection gate: drivers who self-report fatigue or illness before dispatch prevent citations and reduce crash risk. Pair this with a 'no-shame' policy: drivers who call in fatigued are commended, not penalized.
› What documentation must drivers carry and what should the carrier retain?
Drivers should carry a copy of their most recent medical certification (DOT physical) and any current medications with a brief summary of known side effects. Carriers must retain: (1) driver logbooks or ELD records for 12 months—these show sleep patterns and identify chronic fatigue trends; (2) driver self-assessment sheets (mentioned above) tied to dispatch dates; (3) driver training records on fatigue recognition; (4) any incident reports where a driver self-reported fatigue or illness before dispatch. When a citation occurs, pull the driver's logbook for the 7 days prior to the inspection and the medical cert expiration date. This documentation bundle allows you to reconstruct the context and identify systemic issues—e.g., dispatch pressure, inadequate break scheduling, or medical non-compliance.
› What root-cause patterns do your data reveal for this violation?
Our records show three critical co-occurring issues in the same inspections: First, 392.2RG (the fatigue/illness code variant) appears 6 times in the last 90 days, suggesting inspectors sometimes cite multiple fatigue-related codes when documentation is ambiguous—investigate whether your ELD or logbook practice is unclear. Second, 395.8E (false duty-status records) appears 4 times alongside 392.2-ML, indicating drivers may be logging falsely to hide fatigue or skipping required rest. Third, 395.22G (ELD not visibly mounted) appears 4 times, suggesting driver distraction and poor time management. The pattern points to three root causes: inadequate pre-dispatch screening, pressure to meet tight schedules, and poor visibility into real driver state. Address these through mandatory crew-rest policies, ELD training, and dispatch accountability.
› How should we verify a driver is safe to return to service after fatigue or illness?
Establish a documented off-duty recovery protocol: (1) Driver must rest for a minimum of 10 continuous hours off-duty before returning to any driving duty. (2) Upon return, driver completes the pre-trip self-assessment again, affirming adequate sleep and no active illness symptoms. (3) For illness-related returns, require a note from a healthcare provider if the illness involved fever, chest symptoms, or prescribed medication. (4) For fatigue-related incidents, require the driver to log actual sleep time for the 48 hours prior to return. Document all of this in the driver's file. Do not allow a driver to self-certify as 'rested enough'—require objective evidence (sleep log, medical clearance, or documented rest period).
› What should we review with a driver after a 392.2-ML citation?
Immediately after citation, conduct a structured post-event review: (1) Interview the driver on the circumstances: What sleep did they get? Were they sick? Were there dispatch pressures? (2) Pull their logbook for the 7 prior days and check for pattern fatigue (short nights, long consecutive driving days). (3) Review their medication list and any recent health changes. (4) Examine the specific inspector notes—what observable signs triggered the citation? (5) Check whether the citation was issued after dispatch or during a scheduled load—this indicates your planning failed to account for driver state. (6) Document findings and corrective action: retraining, schedule adjustment, or medical evaluation. This review transforms a citation into a data point that prevents the next one.
› How does 392.2-ML affect our CSA scores and fleet safety rating?
This code carries a CSA severity weight of 8 out of 10, placing it among the more serious violations despite being ranked #729 of 3,036 FMCSR codes by citation volume. For context, across all FMCSR violations, the average out-of-service rate is 31.4%, but 392.2-ML has a 0.2% OOS rate—meaning inspectors almost never impound the vehicle, but they do record a meaningful safety event. Even a single citation on your fleet record signals to DOT auditors, insurance carriers, and shippers that fatigue management is not controlled. In CSA's Unsafe Driving BASIC, this violation counts as a serious data point. To minimize impact: keep citation count low through prevention (our data shows only 319 in the last 12 months across all carriers), and if you receive one, demonstrate rapid corrective action in your safety documentation.
› What driver training topics should we prioritize to prevent this violation?
Focus on four areas: (1) Fatigue Recognition: Train drivers to self-identify early warning signs—difficulty tracking road markings, missing exit signs, or microsleep episodes—and teach them that pulling over for a 15–20 minute nap is safer than pushing through. (2) Medication Awareness: Review the most common OTC and prescription medications known to impair alertness, and require drivers to consult their medical provider before taking any new medication. (3) Sleep Hygiene: Teach drivers realistic sleep strategies for road life—consistent sleep time, dark sleeper cabs, and meal timing. (4) Logbook Honesty: Emphasize that falsifying duty-status records to hide fatigue (which our data shows co-occurs 4 times with this violation) destroys the driver's credibility and increases crash risk. Use real inspection stories to show consequences.
› Should we file a DataQs challenge if we believe a citation is incorrect?
Yes, if the inspector's observation contradicts documented evidence in your favor. Examples: (1) You have a logbook showing the driver had 10+ hours of continuous sleep the night before inspection, yet the inspector cited fatigue—this is challengeable if your ELD or manual log is clear and signed. (2) The driver has a current DOT medical certification with no restrictions and was not taking impairing medication—absence of medical grounds for the citation may warrant challenge. (3) The inspector notes are vague (e.g., 'driver appeared tired') without specific observable signs (bloodshot eyes, slurred speech). However, do not challenge if the driver admits fatigue or if the inspection notes describe concrete impairment symptoms. Our data shows only 2 of 950 all-time citations were OOS decisions, meaning most drivers were deemed unsafe but still operable—a weak challenge is rarely won.
› How often should we self-audit for fatigue and illness risk in our fleet?
Conduct quarterly audits. Our 12-month trend shows 319 total citations nationally, with May 2025 as the peak (47 citations) and lower volume in winter months. However, the last 90 days averaged 19.3 citations per month, indicating sustained baseline risk year-round. Set your audit cadence to quarterly reviews of: (1) Driver logbooks—identify any driver with a pattern of short sleep or back-to-back long days. (2) Dispatch scheduling—confirm no route is planned without adequate recovery time. (3) Driver self-assessment sheets—check completion rate and any flagged health issues. (4) Citation history—any driver with prior fatigue citations gets immediate evaluation. A quarterly cycle allows you to catch fatigue patterns before they become citations. If you operate in Iowa, North Carolina, or New Mexico (the top three citation states with 46, 33, and 29 citations respectively over 180 days), increase audit frequency to monthly.
Top Enforcing States
Where 392.2-ML is most commonly cited (last 180 days)
Often Cited Together
Other violations commonly found on the same inspection (last 90 days)
Related Records
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.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
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.