The adverse driving conditions exception lets a driver who runs into snow, ice, fog or unusual road or traffic conditions that could not have been known in advance drive up to 2 more hours, and extend the duty window by up to 2 hours, to finish the run or reach a safe place. It is in 49 CFR 395.1(b)(1), with the definition in 395.2. It does not cover conditions that were forecast or routine, such as rush hour, detention or a breakdown.
The rule
Section 395.1(b)(1): "a driver who encounters adverse driving conditions, as defined in § 395.2, and cannot, because of those conditions, safely complete the run within the maximum driving time or duty time during which driving is permitted under § 395.3(a) or § 395.5(a) may drive and be permitted or required to drive a commercial motor vehicle for not more than two additional hours beyond the maximum allowable hours permitted under § 395.3(a) or § 395.5(a) to complete that run or to reach a place offering safety for the occupants of the commercial motor vehicle and security for the commercial motor vehicle and its cargo."
Three conditions sit in that sentence:
- the driver encounters adverse driving conditions as defined;
- because of them, the driver cannot safely complete the run within the normal limits;
- the extra time is used to complete that run or to reach a safe place, and no more than two hours of it.
The definition
Section 395.2: "Adverse driving conditions means snow, ice, sleet, fog, or other adverse weather conditions or unusual road or traffic conditions that were not known, or could not reasonably be known, to a driver immediately prior to beginning the duty day or immediately before beginning driving after a qualifying rest break or sleeper berth period, or to a motor carrier immediately prior to dispatching the driver."
The weight is on the last half. It is not enough that it snowed. The snow, or the crash that closed the highway, must have been unknown and not reasonably knowable at the moments named: when the driver started the duty day, when the driver started driving again after a qualifying rest break or sleeper period, or when the carrier dispatched the driver.
How much extra time
| Normal limit | With the exception | |
|---|---|---|
| Property carrier: driving | 11 hours (395.3(a)(3)(i)) | Up to 13 hours |
| Property carrier: duty window | 14 hours (395.3(a)(2)) | Driving allowed up to the 16th hour |
| Passenger carrier: driving | 10 hours (395.5(a)(1)) | Up to 12 hours |
| Passenger carrier: on-duty limit for driving | 15 hours (395.5(a)(2)) | Driving allowed up to the 17th hour |
| 60/70-hour weekly limit | 395.3(b), 395.5(b) | Not extended: the rule refers only to 395.3(a) and 395.5(a) |
The extension of the window is new since 2020. Before the hours-of-service final rule of June 1, 2020 (85 FR 33396, effective September 29, 2020), the exception gave 2 more hours of driving but not a longer window, so a driver who hit weather late in the day often could not use it. The 2020 rule "expands the driving window during adverse driving conditions by up to an additional 2 hours." FMCSA stressed that the change "will not increase the driving time available during adverse driving conditions. By increasing duty time without increasing driving time, this change will provide the drivers with more non-driving options to safely respond": for example, to slow down or wait out the weather and still finish.
The two hours are a maximum, not an entitlement. The time can only be used to complete that run or reach a safe place, so if the safe place is 40 minutes away, the exception covers 40 minutes.
What qualifies and what does not
FMCSA addressed this directly in the 2020 rule, while declining to widen the definition. Its words: "The exception does not cover detention time, breakdowns, or enforcement inspections," which it called "factors that are to be anticipated in the industry." And: "Nor does it cover things such as road construction or detours except when they could not reasonably be known before the driver started driving, such as accidents that significantly interfere with traffic movement." It added: "The exception is mainly meant to cover situations outside a driver or motor carrier’s control, and the Agency does not expect it to be invoked frequently."
| Situation | Usually qualifies? | Why |
|---|---|---|
| Unforecast freezing rain begins mid-route | Yes | Adverse weather not known at the start of the duty day or dispatch |
| A crash closes the Interstate ahead after you started driving | Yes | An unusual traffic condition that could not reasonably be known; FMCSA’s example |
| A snowstorm forecast the night before | No | It was known, or could reasonably have been known, before the duty day |
| Normal rush-hour traffic in a city you run through daily | No | Not unusual, and known in advance |
| A long-scheduled construction zone | No | Could reasonably be known before driving |
| Four hours of detention at a shipper | No | Named by FMCSA as not covered |
| A breakdown or a roadside inspection | No | Named by FMCSA as not covered |
The honest answer to "does traffic count" is: unusual traffic that could not have been known does; ordinary congestion does not.
Driver knowledge versus dispatcher knowledge
The 2020 rule also changed whose knowledge counts. The old definition looked only at what the carrier knew at dispatch. The current definition looks at both: the driver immediately before the duty day or before resuming driving after a qualifying rest break or sleeper berth period, and the carrier immediately before dispatch. FMCSA explained that drivers on the road "can evaluate situations that could not be foreseen before dispatch or the start of a duty day." In practice, if either the driver or the carrier knew, or could reasonably have known, the condition does not qualify.
That has a consequence for drivers who check weather apps before starting: a forecast storm on the route at the start of the day is something the driver could reasonably have known. The exception is not a way to drive through bad weather that was on the map; it is a way to deal safely with what was not.
How to record it
There is no special duty status for adverse conditions. The driving is recorded as driving. What the regulations require is an explanation: 49 CFR 395.28(c) says a driver operating under any exception in 395.1 who is not covered by the personal-use or yard-move categories "must annotate the driver’s ELD record to explain the applicable exemption." On paper, the remarks section of the log (395.8(d)(8)) serves the same purpose. A good annotation names the condition, where and when it was met, and why it could not have been known: "I-80 closed by crash at MM 212, 16:40, not reported at dispatch; used adverse conditions to reach truck stop at exit 205."
Keep supporting evidence: a screenshot of the road closure or the state DOT alert, the time you learned of it. The exception is judged on facts after the event, and 395.8(e)(1) forbids false reports in connection with duty status.
Worked examples
Example 1, applying 395.1(b)(1). A driver starts at 06:00 after 10 hours off, clear weather forecast. At 17:30, with 10 hours 15 minutes driven and 2 hours 30 minutes left in the window, fog rolls in so thick the driver slows to 25 mph. The planned truck stop is 40 miles away. At normal speed it would have been reachable within the 11 hours; at 25 mph it will take about 1 hour 36 minutes, which runs past 11 hours of driving. The fog was not forecast. The driver may drive up to 2 more hours beyond the 11 (to 13) and past the 14-hour window to the 16th hour, but only as far as needed to reach a safe place. If a safe rest area appears after 50 minutes, that is where the exception ends.
Example 2, not covered. Same driver, but the fog advisory was issued the evening before for the whole region. The condition could reasonably have been known before the duty day, so the exception is not available. The driver must plan the day to stop within the normal limits.
Example 3, not covered. A driver is held 5 hours at a receiver, runs short on the window, and wants to use the exception to reach home. Detention is named by FMCSA as not covered. The options are the normal limits, or personal conveyance to the nearest safe resting place if the carrier allows it (see personal conveyance).
A four-question check in the cab
When conditions change late in the day, the rule reduces to four questions, all taken from 395.1(b)(1) and 395.2:
- Is it weather, or an unusual road or traffic condition? Snow, ice, sleet, fog, other adverse weather, or something unusual on the road. A slow unload or a mechanical problem is neither.
- Could I or my carrier reasonably have known about it? At the start of the duty day, when I last came out of a qualifying rest or sleeper period, or when I was dispatched. If yes, the exception is not available.
- Does it actually stop me finishing safely within the normal limits? If the run can still be completed, or a safe place reached, inside 11 and 14, the extra time is not needed.
- Where is the nearest place that offers safety for me and security for the truck and cargo? The extra time ends there, and never goes past 2 hours.
If all four answers support it, drive on, annotate the record, and keep the evidence. If any one fails, the normal limits apply, and the choice is to stop where you are safely able to.
Related exceptions that are easy to confuse
- Emergency conditions, 395.1(b)(2). "In case of any emergency, a driver may complete his/her run without being in violation" of Part 395, "if such run reasonably could have been completed absent the emergency." This is a different provision and is not limited to two hours.
- Alaska, 395.1(h)(3). A driver in Alaska who encounters adverse driving conditions may drive for the time needed to complete the run, and then must be off duty for at least 10 consecutive hours (property) or 8 (passenger) before driving again.
- Short-haul, 395.1(e)(1). The adverse conditions exception extends the limits in 395.3(a) and 395.5(a). It does not mention the short-haul condition that the driver be released within 14 hours, so a short-haul driver who is released after 14 hours has not met 395.1(e)(1)(ii) that day and needs a record of duty status for it. See the short-haul exemption.
Common mistakes
- Using it for known weather. The definition turns on what was knowable at the start of the day, after a rest, or at dispatch.
- Using the full two hours automatically. The extra time ends when the run is complete or a safe place is reached.
- No annotation. 395.28(c) requires one on an ELD.
- Expecting it to extend the 60/70. It extends only 395.3(a) and 395.5(a).
- Using it for detention, breakdowns or inspections. FMCSA has said it does not cover them.
The underlying limits are on the hours of service rules page, and the HOS calculator shows how much of the 11 and 14 is left when conditions change. When weather closes in, the truck parking list shows the nearest public spaces.