US Federal Motor Carrier Safety Regulations (49 CFR Parts 350 to 399)
Parts 396 to 399: Inspection, repair and maintenance, hazardous materials driving and parking, and migrant and employee safety – US Federal Motor Carrier Safety Regulations (49 CFR Parts 350 to 399)

US Federal Motor Carrier Safety Regulations (49 CFR Parts 350 to 399) 396.11-13: Driver vehicle inspection reports at the end of each day for defects on the listed items, carrier review and repair certification before the next dispatch, the driver's pre-trip review of the last report, and three-month retention (396.11, 396.13)

What does 396.11-13 require?

Every driver (except in driveaway-towaway operations) must prepare a written report at the completion of each day's work on each vehicle operated, listing any defect or deficiency discovered that would affect the safety of operation or result in a mechanical breakdown, covering at least the service brakes including trailer brake connections, parking brake, steering mechanism, lighting devices and reflectors, tires, horn, windshield wipers, rear vision mirrors, coupling devices, wheels and rims and emergency equipment; a report is required only when a defect is found (for property carriers), and passenger carriers must prepare one daily in all cases. The carrier must repair any defect likely to affect safety before the vehicle is next operated, certify on the report that the defect was corrected or that correction is unnecessary, and retain the report and certification for three months. Before driving, the driver must be satisfied the vehicle is in safe condition, must review the last driver's report, and must sign to acknowledge the review and the certification of repairs where defects were noted (396.13).

Maintained by Gerard Blokdyk

Other controls in Parts 396 to 399: Inspection, repair and maintenance, hazardous materials driving and parking, and migrant and employee safety – US Federal Motor Carrier Safety Regulations (49 CFR Parts 350 to 399)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.