Daylight savings time

Why not X out 0200-0300 ? I'm curious why you X'd out 0500-0600 instead although it measures up to the same thing the actual time change occurs at the 0200 o'clock hour.

 

You are correct, but the HOS don't require you to record that event. You only need to update the log when you change duty status. A time change is like midnight. Even though the date changes, you don't have to pull over and scribble in the book. But when you change status, that's when you account for date change. You only need to document adding or subtracting an hour to get in sync with the clock at home terminal. My practice is to make the adjustment in any duty status except Driving. I prefer to look for a long period just so the adjustment isn't crowded in the remarks section

 

I randomly picked 5-6 to not crowd the item in the remarks section, show it doesn't have to 2am, and emphasize you don't need to pull over or wake up to note the event. My preference was to always find a long period of not driving, sleeper or off-duty. For my sake I adjusted what time I picked (examples & real life) so the overlap or missing hour was contained in 1 duty status.

 

You're right. But I see no requirement to log it only by adjusting that hour. For clarity & to avoid losing or adding hours on the drive line I've always picked whatever hour fits on Off-Duty or Sleeper. Others may not agree with how I do it. I'm ready to learn a better way.

 

Leave a gap between 2 a.m. and 3 a.m.

 

Here's mine.

Daylight savings by rabbiporkchop posted Mar 11, 2019 at 1:14 PM

 

We ran whatever the clock said on the owner's desk in whichever time zone it was. We never in our paper days made allowances for DST or whatever. Whatever the clock said is what we drew a line to. Come to think of it, it's fortunate the auditors were smart enough in the office not to flag problems as a violation.