Quote:
Originally Posted by Rev.Vassago
Wrong again, golfhobo.
What you are likely mistaking for this regulation is the interpretation:
Although I'm sure you'll claim that since the "examples" given didn't include any off duty activities, they didn't "intend" for it to include those. But since you're still hung up on the word "fork" as opposed to "bracket", it's understandable that you can make that kind of error.
|
Why the large type? I'm not blind.
First, it will come as no surprise that I DON'T agree that I am wrong.
Second, I am NOT confused by the only slightly relevant "interpretation" that you mentioned. It doesn't apply to this discussion.
Third, yes... that is EXACTLY what I am claiming as support for my interpretation of the exact reg and para you quoted.
Although they said those were "examples," and I suppose there COULD be others, they clearly didn't mention any change from line one to line 2. And there is a good reason.
It's NOT because no Off Duty activities were mentioned. Some were IMPLIED by such things as "reporting to work" and "being released from work." And the very fact that these two "changes" to or from an OFF DUTY status can occur at different locations is why they must be flagged.
First, one must agree and understand that the purpose of flagging IS to show the location of a duty status change. No explanation of the activity is required...just the location.
Second, one must understand that (unless you are teaming) it is impossible to change from line 1 to line 2 directly (or vice versa) without BEING in the same location one was at the last time one flagged going OFF DUTY (either in the sleeper or on line 1.)
Third, "bracketing" is not a requirement. One can show just a single flag through the time element that the duty status changed (along with the location,) and it is understood that one is still at that location, regardless of duty status, until another flag shows a different location...or you begin line 3 (driving.)
This is consistent with and proved by the instructions for J.J. Keller's scannable logs. Scannable logs interface directly with DOT computers. I'm sure any "failure" to follow the rules would result in a warning if not a company and/or driver violation.