In this article:
- What the adverse driving conditions exception allows
- What counts as adverse driving conditions
- The "not known before" test
- A worked example of the 2-hour extension
- What the exception does not change
- Adverse driving conditions vs emergency conditions vs emergency declarations
- How to annotate adverse driving conditions on an ELD
- Fleet checklist: using the exception without abusing it
- Related questions
The adverse driving conditions exception lets a driver who runs into snow, ice, sleet, fog, other bad weather, or unusual road or traffic conditions that weren't known when the day started drive up to 2 extra hours. It also stretches the driving window by up to 2 hours. A truck driver gets up to 13 hours of driving inside a 16-hour window. A bus driver gets up to 12 hours of driving inside 17 hours on duty.
That is the rule as of October 2026, in 49 CFR 395.1(b)(1). It is a final rule and has been in effect since September 29, 2020. Below: the exact text, what qualifies and what doesn't, a worked example, the limits it leaves alone, and how to annotate it on an electronic logging device (ELD).
What the adverse driving conditions exception allows
The exception covers a driver who "encounters adverse driving conditions... and cannot, because of those conditions, safely complete the run" within the normal limits. That driver may drive "not more than two additional hours beyond the maximum allowable hours" in 49 CFR 395.3(a) (trucks) or 395.5(a) (buses). The purpose is limited: "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" (395.1(b)(1)).
| Limit (as of October 2026) | Normal rule | With the adverse driving conditions exception |
|---|---|---|
| Property-carrying driving time | 11 hours (395.3(a)(3)(i)) | Up to 13 hours |
| Property-carrying driving window | 14 consecutive hours after coming on duty (395.3(a)(2)) | Up to 16 hours |
| Passenger-carrying driving time | 10 hours (395.5(a)(1)) | Up to 12 hours |
| Passenger-carrying on-duty limit for driving | 15 hours on duty (395.5(a)(2)) | Up to 17 hours |
The 2-hour window extension is the newer half. FMCSA added it in its 2020 hours-of-service final rule (85 FR 33396, June 1, 2020). In FMCSA's words: "This rule would not allow an increase in driving time, but it would increase the driving window from 14 to 16 hours when an adverse driving condition is encountered." Before 2020 the 2 extra driving hours had to fit inside the normal 14-hour window.
What counts as adverse driving conditions
Adverse driving conditions are defined in 49 CFR 395.2 as "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" at the right moment (see the next section).
FMCSA explained the boundaries in the 2020 rule's preamble (85 FR 33415–33416). The exception "covers only situations that occur after a driver started her or his trip." It "does not cover detention time, breakdowns, or enforcement inspections," which FMCSA calls "factors that are to be anticipated in the industry." Road construction and detours count only when they "could not reasonably be known before the driver started driving, such as accidents that significantly interfere with traffic movement."
This decision table is built only from that text.
| Situation | Qualifies? | Basis |
|---|---|---|
| Freezing rain develops after the driver leaves, not forecast at the start | Yes | "adverse weather conditions" not known (395.2) |
| A crash closes the interstate ahead and traffic stops for hours | Yes | An accident that "significantly interfere[s] with traffic movement" (85 FR 33416) |
| Dense fog rolls in on a mountain pass mid-run | Yes | "fog" (395.2) |
| A forecast storm the driver or dispatcher knew about before the run | No | The condition was known, or could reasonably be known |
| A 3-hour wait at the shipper (detention) | No | Detention is excluded (85 FR 33416) |
| A flat tire or engine problem | No | Breakdowns are excluded |
| A roadside inspection | No | Enforcement inspections are excluded |
| A construction zone posted on the state's road-closure map before dispatch | No | Construction counts only if it couldn't reasonably be known |
FMCSA also refused to widen the definition in 2020. Commenters asked to add detention, loading delays and breakdowns. FMCSA "declines to make the definition applicable to specific sectors of the industry or to cover situations not contemplated by the current definition" (85 FR 33415).
The Off Duty Brief
Get FMCSA hours-of-service rule changes the week they're final.
Plus one practical guide a month. Free, and one click to leave.
The "not known before" test
The timing test is where most disputes land. Under 395.2, the condition must not have been known, and could not reasonably have been known:
- to the driver immediately before beginning the duty day, or
- to the driver immediately before beginning to drive after a qualifying rest break or sleeper berth period, or
- to the motor carrier immediately before dispatching the driver.
The driver half is the 2020 change. The old definition looked only at what "the person dispatching the run" knew. FMCSA said the new wording "makes it clear that the driver should be involved in the decision-making" (85 FR 33436). It also tied the change to technology, noting "the common availability and use of technology that can provide motor carriers and drivers notice of adverse weather" (85 FR 33416). A forecast on the driver's phone at 5 a.m. is something the driver could reasonably know.
A worked example of the 2-hour extension
Illustrative example built from 49 CFR 395.1(b)(1) and 395.3(a). Not a real driver or fleet.
A property-carrying driver takes 10 consecutive hours off and comes on duty at 5:00 a.m. The forecast she checked at 4:45 a.m. showed clear roads. She takes a 30-minute break after 8 hours of driving.
| Time | What happens | Normal limits | With the exception |
|---|---|---|---|
| 5:00 a.m. | On duty; the window starts | Window closes 7:00 p.m. | Window can run to 9:00 p.m. |
| 4:00 p.m. | 9 hours of driving done | 2 driving hours left | 4 driving hours left |
| 4:00 p.m. | An ice storm the forecast missed hits; she slows to 25 mph | Can't finish the run by 7:00 p.m. | May drive until she has 13 driving hours or reaches 9:00 p.m., whichever comes first |
| 7:30 p.m. | Reaches a safe truck stop, 12.5 hours of driving | Would have been a violation after 6:00 p.m. driving / 7:00 p.m. window | Within limits |
| 7:30 p.m. on | 10 consecutive hours off before driving again | 395.3(a)(1) | Unchanged |
The exception gave her room to slow down, which is the point FMCSA made in 2020: drivers would have "up to 2 additional hours to either complete their run or to reach a safe location" without breaking the window (85 FR 33414).
What the exception does not change
- The 60/70-hour limits. The exception refers only to 395.3(a) and 395.5(a). It doesn't add hours to the 60-hour/7-day or 70-hour/8-day limits in 395.3(b) and 395.5(b). Every extra hour counts toward the weekly total.
- The required rest before the next shift. A truck driver still needs 10 consecutive hours off before driving again; a bus driver needs 8.
- The 30-minute break for truck drivers. Nothing in 395.1(b)(1) waives the break in 395.3(a)(3)(ii).
- Safety. The exception permits extra time only when the driver "cannot... safely complete the run." It never requires anyone to keep driving into the conditions.
- Alaska. Alaska has its own version. A driver in Alaska who meets adverse driving conditions may drive "for the period of time needed to complete the run," then must take 10 hours off (property) or 8 (passenger) (395.1(h)(3)).
Adverse driving conditions vs emergency conditions vs emergency declarations
Three different rules get confused in winter.
| Rule (as of October 2026) | What triggers it | What it does |
|---|---|---|
| Adverse driving conditions, 395.1(b)(1) | Weather or unusual road or traffic conditions not known in advance | Up to 2 more driving hours and 2 more window hours |
| Emergency conditions, 395.1(b)(2) | "any emergency" on a run | The driver may complete the run "if such run reasonably could have been completed absent the emergency" |
| Emergency declarations, 390.23 | A declared emergency, for carriers giving direct assistance | Regional or FMCSA declaration: relief from 395.3 and 395.5 for the emergency or 30 days, whichever is less. Local declaration: up to 5 days |
The declaration rule changed this month. A final rule effective October 5, 2026 lengthened the automatic relief after a regional declaration by a governor or FMCSA from 14 days to 30 days (91 FR 63156). That relief applies only to carriers and drivers "providing direct assistance" to the emergency, not to every truck in a storm.
How to annotate adverse driving conditions on an ELD
The ELD rule covers it. A driver operating under any exception in 395.1 that isn't a special driving category "must annotate the driver's ELD record to explain the applicable exemption" (49 CFR 395.28(c)). FMCSA expected exactly that in 2020. Drivers using the exception "would routinely annotate their RODS," and "a law enforcement officer could investigate the merits of the claimed exception" (85 FR 33414).
A useful annotation answers what an officer or auditor will ask:
- What the condition was ("freezing rain, road glazed").
- Where and when it started (highway, mile marker, time).
- Why it wasn't known (forecast checked at a stated time showed no ice).
- Where the driver stopped, or that the run was completed.
Some ELDs have a dedicated adverse-conditions option and some rely on a free-text note. Either way, the annotation is the record.
Fleet checklist: using the exception without abusing it
FMCSA said the exception is "mainly meant to cover situations outside a driver or motor carrier's control" and that it does "not expect it to be invoked frequently" (85 FR 33416). A fleet policy can hold to that.
- Log the weather check at dispatch. The carrier's knowledge "immediately prior to dispatching the driver" is part of the test.
- Never plan a load around the exception. A run that needs 13 hours of driving in good weather doesn't qualify.
- Make stopping the default. The rule allows reaching "a place offering safety." It doesn't require continuing.
- Watch the coercion rule. Under 49 CFR 390.6, a carrier, shipper, receiver or intermediary "may not coerce a driver" to break the hours-of-service rules.
- Audit annotations monthly. Repeated use by one driver or lane is a sign the planning, not the weather, is the problem.
- Check the weekly hours. Extra hours today come out of the 60/70 total.
Related questions
How often can the adverse driving conditions exception be used? The regulation sets no limit. In 2020 FMCSA declined "to limit its use to a fixed frequency" (85 FR 33416). Each use must meet the definition on its own facts.
Does adverse weather that was forecast count? No, if the driver or carrier knew or could reasonably have known it at the start, after a qualifying rest break, or at dispatch.
Is there a new adverse driving conditions rule for 2026? No. A Federal Register search on October 20, 2026 found no FMCSA rule changing 395.1(b)(1) since the 2020 final rule. For the rest of the daily limits, see our guide to hours of service rules, the facts on the new 14-hour rule, the 8/2 vs 7/3 sleeper berth split, and how passenger carrier hours of service differ.
Off Duty Not Driving Rewards is a rewards program for trucking fleets. Contact our team to learn more.
This article is general information, not legal advice. Confirm requirements against the current regulation text and with your compliance counsel.
The Off Duty Brief
FMCSA rule-change alerts plus one practical guide a month, for fleet safety and retention.
Checked against the regulation text before it goes out. One click to unsubscribe.