The adverse-driving-conditions exception applies only to conditions not known—and not reasonably knowable—to the driver immediately before the duty day or to the motor carrier before dispatch. When it applies, preserve the context supporting the decision.
What this means for your fleet
Use a pre-duty and dispatch-time weather and route check, a driver escalation point, and a written annotation standard. A foreseeable delay should not be relabeled after the fact merely because the trip ran late.
What the exception changes—and what it does not
For property-carrying drivers, the federal exception can extend both the 11-hour driving limit and the 14-hour driving window by up to two hours. The condition must have been unknown—and not reasonably knowable—to the driver immediately before the duty day or to the motor carrier before dispatch. It is not a blanket bad-weather extension. Preserve the dispatch-time route and forecast, when the condition became known, the affected segment, and the driver’s annotation.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Record pre-duty and dispatch-time route and forecast | Retain the pre-trip route, dispatch plan, forecast or road information available before the run, and review timestamp. |
| 2. Identify the unexpected condition | Document the specific weather or traffic condition, location, time encountered, and why it was not reasonably known earlier. |
| 3. Note when it became known | Preserve the first driver or dispatch communication that identifies the condition and when the fleet learned of it. |
| 4. Confirm the applicable HOS window | Calculate the original and adjusted driving/window limits under the cited provision and obtain qualified review. |
| 5. Retain dispatch communications | Keep the message thread, route change, ELD events, annotations, and final disposition for the affected trip. |
Common failure modes
- Using the provision for routine congestion.
- Assuming bad weather automatically qualifies.
- Omitting an annotation and supporting context.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- Current 49 CFR Part 395 text covering HOS limits, exceptions, RODS, supporting documents, ELD duties, and technical requirements — Office of the Federal Register and U.S. Government Publishing Office.
- Editing, annotation, certification, and original-record preservation — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review the exact operation
Bring the driver, vehicle, trip, jurisdiction, current official rule, and original ELD record for a qualified determination. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.