Sixty-Two Miles, a Closing Dock, and Ice in the Forecast
It is 4:05 p.m. You came on duty at 5:00 a.m. and have driven 9 hours 15 minutes of your 11-hour limit; your last 30-minute break ended at 9:30 a.m. You are 62 miles from the consignee, whose dock closes at 5:30 p.m. and reopens at 7:00 a.m. The forecast you heard at your 9:30 break calls for freezing rain starting around 5:00 p.m.; it is already 29°F. The route crosses two river bridges and a ridge. Traffic is light. You feel alert, but you have yawned repeatedly in the last 20 minutes and turned up the radio twice. Dispatch messages: "It's an hour - run it, we'll cover any issue." Your steer tires are at 60% tread, the engine brake works, and the truck is at 68,000 lb.
1. Compute the hours-of-service picture. Do the hours alone block this run?
Read the worked answer
Work each clock separately:
- 11-hour driving limit: 9:15 used → 1 hour 45 minutes remaining.
- 14-hour window: on duty since 5:00 a.m. → window closes at 7:00 p.m., so 2 hours 55 minutes remain.
- 30-minute break: last taken at 9:30 a.m.; driving since then is well under 8 cumulative hours, so the break requirement is satisfied.
At 45 mph average, 62 miles is about 83 minutes - arrival around 5:28 p.m., inside both the 11-hour limit and the 7:00 p.m. window. So the hours do not block the run. It is tight but legal.
That matters, because it forces the real issue into the open: if the schedule is legal, the only remaining reasons not to go are the weather and your own fatigue. Those are not paperwork problems, and dispatch's message is aimed squarely at the paperwork.
2. Does the adverse driving conditions exception cover this?
Read the worked answer
No, and it would not help even if it did.
The exception allows up to two additional hours of driving when you hit adverse conditions you could not reasonably have known about. Two limits on that:
- It applies to conditions that are unexpected. Freezing rain was in the forecast you personally heard at 9:30 a.m. A forecast ice event is a known condition, not an unexpected one.
- It never extends the 14-hour on-duty window. Even a valid use of the exception would not push past 7:00 p.m.
Run the numbers as if it applied: at 25–35 mph on ice, 62 miles takes 1 hour 45 minutes to 2 hours 30 minutes. You would arrive between 5:50 and 6:35 p.m. - after the dock closes at 5:30 either way. The exception buys you nothing here; it only extends a decision that should already be made.
Invoking it to cover a forecast storm is the kind of reasoning that turns a late delivery into an investigation.
3. Make the call. What do you tell dispatch, and why?
Read the worked answer
Stop short of the bridges, before the ice arrives, and deliver at 7:00 a.m.
Reasoning to give dispatch, in specifics rather than adjectives:
- Temperature is 29°F and falling, with freezing rain forecast to start at 5:00 p.m. - right as you would be on the bridges and the ridge, which ice first.
- 68,000 lb on steer tires at 60% tread is not a combination to test on a bridge deck.
- Even at a legal and cautious 45 mph you arrive at 5:28, two minutes before the dock closes; any slowdown at all means a closed gate and a truck parked on ice anyway.
- Running it produces a coin flip between a delivery and a jackknife, and the safe outcome and the unsafe outcome both end with you not delivering tonight.
On the fatigue: yawning repeatedly and turning up the radio are warnings, not background. If you push 62 miles on ice and arrive wired, you have also set up a bad drive tomorrow.
Dispatch's "we'll cover any issue" covers a late fee. It does not cover a crash, and it does not sit with the person holding the wheel.