The Federal Motor Carrier Safety Administration will hold its first hearing on the hours of service proposal May 31- June 1 in Washington, DC.
More hearings will follow in Atlanta, Denver, Los Angeles, Indianapolis, Kansas City, MO, and the Springfield, MA/Hartford, CT, area. Dates will be announced soon, the agency said.
The controversial proposal, which would place new limits on the time truck drivers may work, and would require some truckers to use electronic recorders to track hours, was released last week.
The Washington hearing will be in room 2230 at Department of Transportation headquarters, 400 Seventh Street, SW.
To ask for time to testify at the hearing, call Stanley Hamilton of FMCSA at (202) 366-0665 by May 26. Each speaker will have 10 minutes for his or her presentation, although the agency also will accept written comments.
The agency is specifically interested in comments on the science behind the rule, as well as the particulars of scheduling and the onboard recorder requirement.
Comments on the proposal are posted on the DOT website at http://dms.dot.gov.
More hearings will follow in Atlanta, Denver, Los Angeles, Indianapolis, Kansas City, MO, and the Springfield, MA/Hartford, CT, area. Dates will be announced soon, the agency said.
The controversial proposal, which would place new limits on the time truck drivers may work, and would require some truckers to use electronic recorders to track hours, was released last week.
The Washington hearing will be in room 2230 at Department of Transportation headquarters, 400 Seventh Street, SW.
To ask for time to testify at the hearing, call Stanley Hamilton of FMCSA at (202) 366-0665 by May 26. Each speaker will have 10 minutes for his or her presentation, although the agency also will accept written comments.
The agency is specifically interested in comments on the science behind the rule, as well as the particulars of scheduling and the onboard recorder requirement.
Comments on the proposal are posted on the DOT website at http://dms.dot.gov.
media brand
0 Comments
See all comments