Level 1. OOS

With Keep Truckin on the normal home screen that I see today it goes all the way back to January 22. Once I switch it to Inspection Mode then it shows only 8 days but with all the info required with the output files.

 

This is the problem with elogs. Now that Leo has a harder time catching you on things, they are nit picking over trivial bs. Really? OOS cuz you stopped driving as a team because you were sick?? Ridiculous. As far as false logs due to showing constant sleeper birth.....that’s ridiculous as well. Do you know how often I use sleeper birth? Hardly ever. Off duty 8 or 10 hours. Prove I was in the bunk. I was at a friends house. I have friends everywhere. I met a girl on tinder, went to her place. It’s really none of their business what I do while off duty!! And before any of you start with the “technically illegal” comments......are you dot? Or just trolls?? Sniff sniff......I smell them coming already.

 

I agree as a team driver you better show your minimum 8 in the bunk. But this case is very chicken #### move on dot. Ppl don’t get sick? Come off it. You know why he didn’t issue a ticket? Cuz he knew it probably wouldn’t stick. Much harder to fight the OOS without a ticket. Where I run I have very limited encounters with dot/MTO. But I once demanded a ticket when MTO was gonna issue a warning. Suddenly the warning disappeared altogether. Funny how calling their bluff works sometimes.

 

D,

I just saw this tag so I know I am late to the party. I believe you are on to something about the log not properly recording a team driver, although this issue happened outside the 8 day window so roadside should not have even asked about it. It does not matter where he went off-duty as long as he had enough off-duty time to be legally back on-duty, which he did, and he had his previous 7 days in his possession.

Doing the driveaway work I currently do my logs have this issue all the time. Once I drop a truck I am off-duty in that city until I begin travel to my next pickup or actually pickup another truck. It is very common for me to log off in Greencastle, PA then take a rental car home to Scranton, stay home for a few days then fly down to Gainesville, GA to pickup a car hauler for a customer. My log will show off-duty in Greencastle then on-duty at home in Hawley with about 5 hours on-duty not driving time for my flight and Uber up to Cottrell.

Even with this being the same truck he was last driving as long as he had a plausible reason for why he logged off in CA and didn't log back on for a few weeks later it is none of the officer's business where he was or what he was doing in an off-duty status.

I would DataQ this with the explanation of what happened, the co-driver's logs for the trip home from CA and any other proof he was not driving. Now, if the ELD records were not showing him as co-driver on the other driver's logs, and the other driver's name on his log then don't even bother as that is a legitimate false log to not have the co-driver listed in a team operation. Although the officer should not have seen the logs from 8 days past, without having the co-driver properly recorded they will not be used as evidence to reconsider the OOS.

As much of a pain as it was, and the 10 hours OOS sucks, it would have been better to have been cited. Then a reasonable Judge could have dismissed it and the OOS would have to removed from the CSA score. If it were not for the damage that an OOS does to the CSA score I wouldn't even worry about this violation, just chalk it up to a lesson about making sure co-driver ELD records are properly synced and signing off-duty properly on your device.

 

the Garmin ELD will show the day and time when last time it was powered on. sometimes that day is 2-3 month old

 

I wouldn't be surprised at all if an ELD didn't function properly & spilled it's guts to a DOT. Heck, Verizon's app doesn't highlight/mark edits or violations.