OOSC, Part I, Item 9. - Driver's Record of Duty Status - U.S., a. False Record of Duty Status

There are questions relating to placing drivers out of service for a false log when “…in an apparent attempt to conceal a violation of an hours-of-service limitation” cannot be documented and a driver has since been re qualified. Secondly, if a driver takes a 34 hour reset after a false log should he be placed out of service.

To develop current and consistent guidance and enforcement.

1. A driver uses personal conveyance outside of the definition by utilizing it to enhance the operational readiness of a motor carrier by moving closer to the next loading station. By way of footnote 13 in the OOS criteria the use of PC in this manner would be deemed a false log: Paragraph 6 of the OOS criteria states: In relation to placing the vehicle OOS the last sentence “…in an apparent attempt to conceal a violation of an hours-of-service limitation.” Becomes important. Take for example a driver utilizes the personal conveyance improperly, however there is no indication that an hours of service violation would have occurred even if he had logged the PC driving time as on-duty driving time. All mileage ranges, time frames before and after are within tolerance and the driver takes the required ten hours off prior to any violation or possible violation based on all documentable evidence. The question is in this instance would the driver be placed out of service for a false log? There is no doubt that the log is false based on footnote 13 but some question on whether the driver would be placed OOS due to the previously identified sentence. 2. A driver is identified as having a false log on day 2 of his 8 days. During his 4th and 5th days he obtains a valid 34 hour reset and based on all available evidence there is no reason to doubt this 34 hour reset. 395.3 states “(2) Any period of 8 consecutive days may end with the beginning of an off-duty period of 34 or more consecutive hours.” Since the driver took a valid 34 hour reset after the identified false log would the driver be placed out of service for that false log? It appears that he would still be in violation of a false log but not placed OOS.