Interrupted Sleeper Berth Period: What an On-Duty Break Does to Your Split

"Consecutive" is doing a lot of work in that sentence. One interruption is the difference between a legal split and a 14-hour violation at the scale house.

What the rule actually requires

The longer period of a pairing must include at least 7 consecutive hours in the sleeper berth (395.1(g)(1)(ii)(B)). Consecutive means uninterrupted berth time — the clock counts your longest unbroken run inside the stretch:

• On duty inside the stretch — fueling, an inspection, BOL paperwork, a dock bump — ends the run.
• Off duty inside the stretch — getting out of the berth for anything — also ends it, because the requirement is berth hours specifically.
• What survives: the longest continuous berth run on either side of the interruption. 4 h berth, 30 min work, 4 h berth = a 4-hour run. No pairing survives on 4 hours.

The recoverable interruption

Interruptions at the very start are often survivable: 30 minutes of work, then 7 h 40 m of berth — the remaining run still clears 7 consecutive hours, and the 30 minutes simply doesn't count toward the pairing. It is the same logic as fractional splits: the floor is about the berth run, not the total block. But an interruption at hour 4 leaves two 2-hour fragments — dead.

Dock days: the classic killer

Long wait at the shipper, in the berth — great, that's berth time. Then a dock bump, or you climb out to check paperwork: if that happens inside your planned 8-hour stretch, your consecutive run is now however long since the interruption. Two ways drivers handle it:

1. Put the interruption outside the stretch. Take the 8 hours cleanly, then handle the dock work — the interruption becomes ordinary on-duty time in your recalculated window.
2. Let the dock time be the shorter period. If you'll be off duty/berth at the dock for 2+ hours, that stretch can pair with a ≥7 h berth run elsewhere — that stretch can pair with a ≥7 h berth run elsewhere in the day — the worked examples show dock-built pairings.

Log it honestly, whichever way it lands

The record must show the truth: berth time as sleeper-berth status, the interruption in its actual status. A log that "cleans up" the interruption manufactures the exact mismatch that produces false — or true — violations. If the interruption broke the pairing, recalculate: often the longest clean berth run plus a fresh 2-hour-plus period still makes a legal pairing, just on a different anchor.

All guides · The rule explained · The rule explained · Common mistakes · Contact
Rule basis: 49 CFR 395.1(g)(1)(ii) via eCFR.