Prevention FAQ — FMCSR 392.2FT: Fatigue & Illness Behind the Wheel

Inspectors cite 392.2FT when observable evidence suggests a driver's ability or alertness is impaired to the point driving is unsafe — fatigue, illness, or any comparable cause. Common triggers include slurred or slow speech, bloodshot or glassy eyes, difficulty standing steadily, an inability to answer basic questions coherently, or an admission by the driver that they feel unwell or have not slept.

Our inspection records show NC generated 1,544 citations in the last 180 days alone, far outpacing every other state. Illinois followed with 330. That concentration in NC suggests aggressive roadside screening programs where behavioral assessment is built into standard Level I and Level III inspections. Inspectors in those corridors are trained to observe driver demeanor, not just paperwork and equipment. Coach drivers to expect direct questions about recent sleep hours, any illness, and medication use at NC and IL inspection stations.

The pre-trip must go beyond the vehicle — it must include a driver self-assessment and a dispatcher verification step:

Driver self-assessment (required before key-on):

• Hours slept in the last 24 hours (document actual number)
• Current illness symptoms — fever, congestion, medication taken
• Any over-the-counter or prescription medication that carries a drowsiness warning
• Subjective fatigue rating on a 1–5 scale (flag anything above 3 for supervisor review)

Dispatcher or terminal check-out:

• Supervisor verbally confirms driver appears alert and responsive
• HOS records reviewed to confirm adequate off-duty rest before dispatch
• Any driver-reported illness results in documented clearance or reassignment

Make this a signed form retained per trip, not a verbal checkbox. Without a paper trail, there is no defense if a citation is issued.

Drivers should carry:

• Current electronic or paper HOS logs showing off-duty hours immediately preceding the shift
• Any physician clearance letter if the driver has a known managed medical condition
• The completed pre-trip driver self-assessment form for that day

Carriers must retain at the terminal:

• Pre-trip sign-off records (driver and supervisor signatures)
• HOS records for at least 6 months
• Any wellness or fatigue screening documentation tied to that driver's dispatch
• Dispatch records showing the time the driver was assigned and any reported complaints prior to departure

With 392.2FT carrying a CSA severity weight of 8, a well-documented paper trail is your primary post-citation tool. If the inspection record contradicts the documentation you hold — for example, logs show adequate rest — that discrepancy is the foundation of a DataQs challenge.

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

396.17C — No proof of periodic inspection (221 shared inspections): This is the most common pairing. When periodic inspection records are missing, it signals a maintenance and compliance culture gap — the same operations skipping paperwork discipline are also failing driver fitness checks. Audit both simultaneously.

392.2RG — A related fatigue/illness code variant (175 shared inspections): The high pairing rate here suggests inspectors are writing multiple fatigue-related codes in the same stop, indicating the driver's condition was unambiguous. This points to a dispatch or scheduling failure — drivers are reaching the roadside visibly impaired, not borderline cases.

383.23A2 — Operating without a CDL (160 shared inspections): This is a credentialing breakdown paired with fitness concerns. When unlicensed drivers are on the road, they are likely also operating without the fitness oversight a licensed driver program provides. Verify licensure and fitness controls are linked in your driver onboarding process.

Do not treat return-to-service as automatic after the mandatory rest period ends. Build a structured clearance step:

1. Minimum rest verification: Confirm via HOS logs that the driver completed the required off-duty time before any return-to-duty conversation begins.
2. Supervisor interview: A terminal supervisor or safety manager conducts a brief in-person or video call. Document observations — speech clarity, responsiveness, reported energy level.
3. Illness-specific clearance: If illness was cited, require a written self-clearance statement or, for any condition involving a physician-documented diagnosis, a return-to-duty note.
4. Medication review: Confirm no new medications with drowsiness warnings are being taken without a physician's sign-off on fitness to drive.
5. Signed clearance record: File the clearance document alongside the original citation and inspection report.

This process closes the gap that the co-occurrence data suggests — drivers returning to service without any fitness gate.

Run a structured root-cause review within 72 hours of notification:

1. Pull the full inspection report — note all co-occurring codes. With 221 shared inspections pairing 392.2FT with 396.17C (no proof of periodic inspection), check whether your vehicle maintenance documentation was also deficient at that stop.
2. Review the driver's HOS for the prior 7 days — identify whether the schedule itself created the fatigue condition.
3. Audit dispatch records — was there pressure to depart despite the driver flagging tiredness? Were layovers cut short?
4. Interview the driver — document what they experienced and whether they attempted to report fatigue before dispatch.
5. Review peer drivers on similar routes — if one driver is fatigued on a given lane or schedule, others likely are too.
6. Generate a corrective action memo — specify schedule adjustments, dispatcher training, or checklist revisions with a 30-day completion target.

File all of this. It demonstrates good faith compliance culture if a pattern of citations ever draws regulatory attention.

392.2FT sits in the Unsafe Driving BASIC — the highest-scrutiny category for FMCSA intervention. It carries a CSA severity weight of 8, which is near the top of the severity scale. Each citation is time-weighted, meaning recent citations (last 6 months) carry the most impact on your percentile.

Our inspection database ranks 392.2FT at #245 out of 3,036 FMCSR codes by citation volume, with 8,732 all-time citations. Citation volume has accelerated sharply — 4,541 in the last 12 months alone, meaning more than half of all historical citations were written in the past year. That trajectory signals increased enforcement focus, not a stable background rate.

Because this code is in Unsafe Driving, even a small number of citations can push a carrier's BASIC percentile into intervention territory. Unlike equipment codes where OOS removals dominate the risk picture, here the severity weight alone drives the CSA impact.

The top vehicle makes cited — Freightliner (2,113 citations), Kenworth (937), Peterbilt (910), and International (715) — represent the dominant long-haul and regional fleet platforms. These are not coincidental: they are the trucks on the routes and schedules most exposed to fatigue risk. Training should be built around the reality of those operations:

1. Sleep science fundamentals: How sleep debt accumulates over multi-day dispatch cycles and why 'I feel fine' is an unreliable self-assessment.
2. HOS strategy, not just compliance: How to use off-duty time for actual recovery, not administrative tasks or unpaid loading.
3. Illness and medication decision-making: Practical guidance on which OTC medications disqualify a driver from operating — not just a list, but a decision tree.
4. How to refuse a dispatch: Give drivers language and a process to report fitness concerns without fear of penalty. Pair this with a documented no-retaliation policy.
5. What inspectors look for: Walk drivers through the observable signs that trigger 392.2FT so they can self-assess honestly before reaching the scale.

A DataQs challenge is worth pursuing when your documentation directly contradicts the basis of the citation. Specific scenarios:

• HOS logs show adequate rest: If the driver's logs clearly document the required off-duty hours immediately before the inspection and no illness was present, the factual basis for the citation is weak.
• Inspector observation inconsistency: If a dashcam or body cam (where legal) shows normal driver behavior at the stop and the narrative relies solely on subjective inspector assessment, challenge it.
• Clerical or code error: Confirm the correct sub-code was written. With multiple 392.2 variants in active use — 392.2RG appeared in 175 shared inspections in the last 90 days, 392.2IRP in 150 — miscoding does occur.
• Medical clearance in hand: If the driver held a current physician fitness certification and was cited for illness, that documentation supports a challenge.

Do not challenge citations where the driver's own statements, HOS violations, or co-occurring code record undermines your position. A failed challenge does not remove the citation and wastes administrative resources.

Our inspection records show a sharp spike to 727 citations in March 2026, compared to a range of 197–514 in prior months of the trailing 12-month period. The 90-day window shows 1,112 citations, confirming that enforcement intensity is at or near its highest point in the dataset. This is not a stable background rate — it is accelerating.

Given that pattern, a monthly self-audit cadence is appropriate for any fleet with more than 20 drivers. Quarterly is no longer sufficient given the citation velocity. Each monthly audit should include:

• Random review of 10% of driver pre-trip self-assessment forms
• HOS compliance check for drivers on the longest or most time-sensitive lanes
• Dispatcher interview on any instances where a driver reported tiredness and was still dispatched
• Cross-reference of any 396.17C (no proof of periodic inspection) findings — this code appeared alongside 392.2FT in 221 inspections in the last 90 days, suggesting fleets with maintenance paperwork gaps are the same fleets getting fatigue citations

Schedule a deeper quarterly review specifically for NC-operating drivers given the state generated 1,544 citations in the last 180 days.