Accident & Incident Register

Carriers must maintain an accident register (49 CFR 390.15) recording DOT-recordable accidents — those involving a fatality, an injury requiring immediate medical treatment away from the scene, or one or more vehicles towed from the scene due to disabling damage. The register must include date, location, driver, number of injuries/fatalities, and whether hazmat (other than fuel) was released, plus copies of accident reports required by states/other agencies, retained for the specified period (generally three years). It's a required record examined in compliance reviews — but it captures only the most serious outcomes, which is why safety-minded fleets log far more than the minimum.

Because they're the free lessons that predict the serious ones. Near misses and minor incidents occur far more often than recordable accidents and share the same root causes — a following-distance habit causes a hundred near misses before the rear-end collision, a fatigue pattern many close calls before the crash. Logging only recordable accidents means you only learn from the events that already caused serious harm; logging near misses lets you intervene on the causes before they produce a recordable accident. The safety-pyramid principle: address the broad base of minor events and near misses, and the serious events at the top decline. The register's prevention value is in the events that didn't (yet) cause damage.

By revealing patterns and driving corrective action. Logging cause and corrective action for each event (not just recording the damage) turns the register into analyzable data: a cluster of following-distance incidents points to a coaching need; recurring incidents at a location or time point to route or scheduling factors; vehicle-factor events feed maintenance; driver-specific patterns target individual coaching. The corrective-action field closes the loop — each event becomes a prevention opportunity rather than just a cost. A register analyzed for patterns and acted on systematically reduces future accidents; a register kept only for compliance records the damage without preventing the next instance. The difference is whether you log the cause and the fix, and whether anyone reviews the patterns.

Significantly: DOT-recordable accidents feed CSA (Compliance, Safety, Accountability) scores, specifically the Crash Indicator BASIC, affecting your safety rating and inviting scrutiny; insurance costs rise with accident frequency and severity; a poor safety record affects your ability to get business (shippers and brokers check); and serious patterns can trigger interventions or audits. So accident prevention isn't just about avoiding the direct costs of crashes (damage, injury, liability) — it protects your CSA scores, insurance rates, and commercial reputation. The register, used as a prevention tool rather than just a record, is part of managing all of these: fewer accidents through pattern-based prevention means better scores, lower insurance, and a safer, more competitive operation. The compliance requirement and the business case point the same direction.