When a commercial motor vehicle is involved in an accident, the regulatory clock starts immediately. Before the scene is cleared, before the insurance adjuster is called, before the driver completes a post-trip inspection — the documentation obligation has already begun. Carriers who misunderstand this sequence don’t just face civil liability exposure. They face federal enforcement action with direct consequences to their Safety Measurement System (SMS) scores, their safety rating, and their operating authority.

This post breaks down exactly what 49 CFR 390.15 requires, which documents are auditor priorities, and where carriers consistently fail.

---

What 49 CFR 390.15 Actually Requires

Section 390.15 mandates that every motor carrier maintain an accident register — a record of each accident, as defined under 49 CFR 390.5, involving a commercial motor vehicle operated under that carrier’s authority. The definition of “accident” under 390.5 is specific and non-negotiable: it includes incidents resulting in a fatality, a bodily injury requiring immediate medical treatment away from the scene, or disabling damage to any vehicle requiring tow-away.

The accident register must be retained for three years from the date of each accident and must be made available to any authorized federal, state, or local enforcement official upon request.

What the Register Must Contain

The minimum required data elements for each accident register entry are:

• Date of accident
• City or town, and state, where the accident occurred (or closest city/town)
• Driver’s name
• Number of injuries
• Number of fatalities
• Whether hazardous materials were released

This is the floor, not the ceiling. FMCSA compliance reviews routinely expect carriers to produce supporting documentation beyond the register itself — and auditors cross-reference register entries against police reports, insurance records, and driver logs to identify discrepancies.

---

Post Accident Documentation Requirements: The Full Document Set

Regulatory minimum compliance and audit-ready compliance are not the same standard. FMCSA investigators examining a carrier’s accident history under a Compliance Review or Focused Audit will request the accident register and then drill into supporting records. The following document set represents what a carrier should have on file for every qualifying accident.

Primary Incident Documents

• Police/law enforcement crash report — The official report establishes the regulatory definition of whether the event qualifies as an accident under 390.5. Carriers that fail to obtain these create a verification gap that auditors exploit.
• Driver’s written statement — A contemporaneous account from the driver, completed within 24 hours when possible, documents the driver’s perspective and provides a baseline for comparing against ELD data.
• Post-accident drug and alcohol testing records — Under 49 CFR 382.303, drivers involved in fatal accidents must be tested. For non-fatal accidents, testing is required when the driver receives a citation or when a tow-away or injury occurs. Testing records must link directly to the accident register entry.
• ELD/HOS records for the 8-hour window preceding the accident — Hours of service compliance immediately before an accident is one of the first things an auditor checks. These records must be preserved exactly as they existed at the time of the accident.
• Vehicle inspection records and maintenance logs — Pre-trip and post-trip inspection reports for the vehicle involved, plus any recent repair records, establish whether mechanical failure was a contributing factor and whether the carrier had notice of any defects.

For a complete framework of which documents must be maintained across all operational categories, review the DOT compliance documents the complete list truck drivers must maintain.

Supporting and Secondary Records

Beyond the primary documents, carriers should preserve photographs of the scene and vehicle damage, witness statements collected at the scene, towing and recovery documentation, cargo manifest if hazardous materials were involved, and any communication records between dispatch and the driver in the period surrounding the accident. Regarding that last category — what gets said over dispatch channels and what drivers communicate at the scene can become evidence. Understanding what to say and what not to say to an enforcement officer applies equally to post-accident interactions with investigators.

---

How Accident Records Feed Into Enforcement Actions

Accident data doesn’t stay in a filing cabinet. It flows directly into FMCSA’s Motor Carrier Management Information System (MCMIS), where it affects a carrier’s BASIC scores under the CSA methodology. The Crash Indicator BASIC is one of the seven BASICs, and carriers above the intervention threshold face increased roadside inspection scrutiny, potential investigations, and, ultimately, rating actions. FMCSA’s public data portal allows anyone — including brokers and shippers — to review a carrier’s crash history.

The Rating Consequence Carriers Underestimate

A carrier with incomplete accident documentation faces a compounding problem during a Compliance Review. Missing or inconsistent records don’t just result in a documentation violation — they can shift the interpretation of the accident itself. An auditor who cannot verify that post-accident drug testing was conducted on time, or who finds that the accident register entry doesn’t match the police report date, has grounds to treat corrective action as an open issue. This is one pathway through which documentation failures contribute to conditional or unsatisfactory ratings. Understanding what a satisfactory safety rating means and why it’s not a guarantee is critical context for any carrier that assumes clean prior reviews provide ongoing protection.

Inspection Data Upload Timelines Matter

For accidents that generate a roadside inspection (which many do, particularly when law enforcement is involved), that inspection data enters MCMIS on a defined timeline. How roadside inspection data is uploaded to MCMIS and how long it takes affects when and how carriers can challenge inaccurate entries. Missing the DataQs challenge window because accident documentation wasn’t preserved correctly is an avoidable and costly error.

---

Retention Timelines and Where Carriers Get Caught

The statutory minimum under 390.15 is three years. However, because accident records interact with drug and alcohol testing records (49 CFR Part 382), driver qualification files, and vehicle maintenance records — each with different retention clocks — a single accident can generate documents with retention obligations ranging from one year to the life of the driver’s employment plus three years. For a consolidated reference on how these timelines interact, the DOT recordkeeping and document retention guide is the place to start.

Common violation patterns identified in FMCSA audit narratives include:

• Accident register entries with missing or incorrect dates (violation of 390.15(b))
• No post-accident drug test records linked to qualifying accidents (violation of 382.303)
• ELD records not preserved in tamper-evident format following an accident
• Police report not obtained or not retained
• Accident register not produced within reasonable time during a compliance review

---

Before the Next Review

Documentation gaps discovered during an audit are far more expensive to address than documentation gaps discovered during an internal audit. Every qualifying accident should trigger a standardized documentation checklist, completed within 72 hours, and filed in a dedicated accident record package — separate from but cross-referenced with the driver’s qualification file and the vehicle maintenance file.

Prepare for your next compliance review: DOT Audit Preparation Bundle — The Trucker Codex

---

Data sourced from 49 CFR 390.15 and FMCSA public records. Verify current enforcement thresholds at fmcsa.dot.gov.