The Adverse Driving Conditions Exception

Weather and road conditions do not always cooperate with a log. A snowstorm moves in faster than forecast. A crash closes the interstate for hours. The adverse driving conditions exception gives drivers limited extra time to get somewhere safe when the unexpected happens.

It is also one of the most misused exceptions in hours of service. Here is how it actually works.

What the exception allows

The exception is in 49 CFR 395.1(b)(1). When a driver encounters adverse driving conditions, they may extend their limits by up to 2 hours.

For property-carrying drivers, that means:

  • Up to 13 hours of driving, instead of 11.
  • Driving up to the 16th hour after coming on duty, instead of the 14th.

For passenger-carrying drivers, a similar two-hour extension applies to their driving and on-duty limits. Check 49 CFR 395.1(b) for the details for passenger operations.

The exception does not change the 60- or 70-hour weekly limits. The 30-minute break rule and required off-duty periods still apply.

What counts as adverse driving conditions

The definition is in 49 CFR 395.2. Adverse driving conditions means:

  • Snow, sleet, fog or other adverse weather conditions, or
  • A highway covered with snow or ice, or
  • Unusual road or traffic conditions.

The key is timing. The conditions must not have been known, or reasonably knowable, to:

  • The driver immediately before beginning the duty day, or immediately before beginning driving after a qualifying rest break or sleeper berth period, or
  • The motor carrier immediately before dispatching the driver.

In plain terms: if the conditions were apparent before the trip, or before the driver started driving again, the exception does not apply.

What does not qualify

Some situations come up again and again that do not meet the definition:

  • Normal rush-hour traffic. Congestion that happens every weekday is expected.
  • Forecast storms. If the snowstorm was in the forecast when the load was dispatched, it was known.
  • Known construction zones. Planned roadwork that was posted in advance is not unusual.
  • Loading or unloading delays. Waiting at a shipper or receiver is not a road or weather condition.
  • Poor trip planning. Running out of hours because the schedule was too tight is not adverse conditions.

A good test is to ask: could a reasonable person have known about this before the trip or before the driver got back behind the wheel? If yes, do not use the exception.

Using it the right way

The exception is meant to let a driver complete the run or reach a safe place, not to squeeze in more miles. Good practices:

  1. Use only what you need. Up to 2 hours is a maximum, not a target.
  2. Stop somewhere safe. If the conditions make driving unsafe, the driver should not keep going just because the exception exists.
  3. Remember driver fatigue rules. Under 49 CFR 392.3, a driver may not operate while their ability or alertness is impaired by fatigue, illness or any other cause.

Dispatchers should never pressure a driver to use the extension. The decision is about getting safely to a stopping point.

Documenting it

On an ELD, drivers typically indicate use of the exception with an annotation on the log. The annotation should explain what happened, where, and roughly when. For example: “Unexpected closure on the interstate due to a multi-vehicle crash. Traffic stopped for about 90 minutes.”

Supporting information helps:

  • Road closure alerts or DOT traffic notices.
  • Weather alerts issued after the trip began.
  • Photos, if safe to take.
  • Dispatch notes showing what was known at the time of dispatch.

During a compliance review or roadside inspection, an officer may ask why the driver went over 11 or 14 hours. A clear annotation and supporting records make that conversation short.

Safety managers should review every use of the exception. If one driver uses it far more often than others, find out why. DOT Compliance Watch helps you keep HOS and ELD records organized by driver, so reviewing these patterns is easier.

Quick checklist

Before using the exception, ask:

  • Were the conditions unknown at dispatch and before the driver started or resumed driving?
  • Is this weather, snow or ice, or truly unusual road or traffic conditions?
  • Is the extra time needed to finish the run or reach safety?
  • Will the driver stay within 2 extra hours?
  • Is the log annotated with a clear explanation?

If a situation is borderline, check the regulation or ask FMCSA. Our DOT regulations reference has the relevant sections.

Handle the unexpected with confidence

Used honestly, this exception keeps drivers safe when conditions change. Used as a scheduling tool, it becomes a violation. See which plan fits your fleet and keep your HOS records ready for review.

Share this article: 𝕏 Twitter Facebook LinkedIn
RC
Robert Caldwell
Founder, DOT Compliance Watch · 30 Years in Trucking

Robert drove trucks for over a decade before building a 22-truck fleet. He survived four DOT audits, two consent agreements, and more roadside inspections than he can count. Now he builds software to make compliance manageable for every carrier.

← Previous The FMCSA Clearinghouse: Carrier Queries Explained

Ready to make compliance effortless?

14-day free trial. 14-day free trial.