JackRick Logistics

FMCSA Accident Register: What's Recordable and How to Keep It

The short answer

FMCSA requires every motor carrier to maintain an accident register of recordable accidents — defined by fatality, off-scene medical treatment for injury, or tow-away disabling damage, regardless of fault — kept as a single continuous record generally for three years. Investigators cross-check it against claims and look for preventability reviews and corrective actions, not just a list. Record generously, review every crash for preventability, and document what you changed. Per FMCSA — verify current requirements against official sources.

Lapis-blue and gold illustration of an open logbook with accident entries beside a semi truck
The accident register is a factual log with a three-year memory — complete, honest, and paired with action.

Tucked into the FMCSA regulations is a recordkeeping requirement that carriers violate constantly without knowing it: the accident register. Every motor carrier must maintain a register of its recordable accidents — and 'recordable' has a specific federal definition that does not match what most people mean by 'accident.'

The register is not just paperwork. Investigators review it in compliance reviews, plaintiff attorneys subpoena it after crashes, and insurers read it at renewal. A complete, honest register with documented follow-up is a safety-program asset. A missing or sanitized register is a finding — or worse, evidence of a cover-up.

Per FMCSA — verify current requirements against official FMCSA sources. This guide covers the framework as it generally works.

What Counts as a Recordable Accident

FMCSA defines a recordable accident with three alternative triggers: a fatality, bodily injury to a person who receives medical treatment away from the scene, or disabling damage to a vehicle requiring it to be towed away. If any one of the three occurred in an incident involving your commercial motor vehicle on a public road, it goes in the register.

Note what the definition does not require: it does not require your driver to be at fault, it does not require a citation, and it does not require significant damage. A minor collision where the other driver goes to urgent care 'just to be checked' is recordable. A tow-away of your trailer after a tire blowout with no other vehicle involved can be recordable. When in doubt, record it — over-inclusion never hurt a carrier, and under-inclusion has.

The common miss is the injury trigger. Drivers report 'no one was hurt' because no one was hurt at the scene — then the other party seeks treatment the next day and the carrier never updates the record. Build a follow-up step into your accident procedure: check back on injury and tow status before closing the file.

What the Register Must Contain

For each recordable accident, the register must record: the date and location, the driver's name, the number of injuries and fatalities, whether hazardous materials were released, and — critically — the carrier's documentation of the accident. The regulation requires specific data elements; a spreadsheet with 'date, driver, what happened' may not satisfy it. Check the current regulatory text for the exact required fields.

Keep the register as a single, continuous record — not scattered across emails, claim files, and someone's memory. Whether it is a bound log, a spreadsheet, or your safety software's module, it should be one place where every recordable accident lives in chronological order, maintained at your principal place of business where an investigator can review it.

Separate the register from your internal investigation files. The register is the factual log; your preventability review, witness statements, and corrective actions are supporting documentation. Both matter, but they serve different purposes — the register proves you recorded, the investigation file proves you learned.

Retention: How Long to Keep It

Accident register records must generally be retained for three years from the date of the accident — longer than many carriers assume. Supporting documentation (police reports, photos, investigation files) should be kept at least as long, and your insurer or attorney may advise longer retention for serious crashes where litigation is possible.

The three-year clock runs per accident, not per register. When you archive old entries, keep them retrievable — an investigator asking about a crash from two and a half years ago will not accept 'we purged the old spreadsheet.' Calendar the retention per entry if your system does not handle it automatically.

Do not confuse the register retention with other record periods: driver logs, maintenance records, and drug testing records each have their own retention rules. The accident register's three-year period is specific to the register — verify current requirements for each record type rather than applying one rule to everything.

The Register in Compliance Reviews

The accident register sits inside the Accident factor of a compliance review, and investigators read it skeptically. They compare your register against other sources — insurance claims, roadside inspection crash indicators, news reports — looking for accidents you did not record. A crash that appears in your insurer's loss runs but not in your register is a finding and a credibility problem.

Investigators also look for the follow-up: preventability determinations, driver retraining or discipline, and systemic corrective actions. A register that lists six rear-end collisions in a year with no documented response reads as a carrier that records crashes and learns nothing. Our DOT audit preparation checklist covers how the Accident factor is evaluated.

The best defense is a register that is complete, honest, and paired with visible action. Record every recordable accident, review each one for preventability promptly, document what you changed, and file the review with the register entry. That is what a working safety program looks like on paper.

Preventability Reviews and Countermeasures

For each recordable accident, conduct a preventability review: could the driver have done something reasonable to avoid it, regardless of legal fault? Preventability is a safety concept, not a legal one — a driver can be legally not-at-fault and still have a preventable accident (following too closely when the other driver stopped short, for example). Document the determination and the reasoning.

Match the response to the finding. Non-preventable: document and close. Preventable: retraining, ride-along evaluation, policy review, or discipline per your safety policy — documented in the driver's file. Pattern preventable accidents across drivers: systemic countermeasures like speed-governor review, following-distance campaigns, or route changes.

Track your accident data over time: frequency by driver, by type, by location, by time of day. The register is raw material for a safety program that actually improves — carriers that analyze their own crash data prevent the next one instead of just recording it. Share trending (not names) with drivers; nothing changes behavior like seeing the pattern.

Building the Accident Procedure

Write the procedure drivers follow at the scene: ensure safety and call 911, do not admit fault, photograph everything, collect the other parties' information, notify dispatch immediately, and take a drug and alcohol test as your post-accident testing policy requires. Laminate the card and put it in every truck — drivers in shock do not improvise well.

Build the office procedure behind it: who receives the driver's call, who decides on testing, who preserves the ELD and dash-cam data, who opens the register entry, and who conducts the preventability review within days, not months. Assign every step to a name, with a backup name.

Review the procedure annually against your actual accidents: did the notifications happen, was data preserved, were reviews timely? The procedure that works on paper and fails in practice is worse than no procedure — it proves you knew what to do and didn't. Test it with a tabletop walkthrough once a year.

Key takeaways

  • Recordable means fatality, off-scene medical treatment, or tow-away — fault is irrelevant.
  • When in doubt, record it; over-inclusion never hurt a carrier.
  • Keep one continuous register, generally retained three years per accident.
  • Investigators cross-check your register against claims — gaps are credibility problems.
  • Pair every entry with a preventability review and documented corrective action.
  • Analyze your own crash data; the register is raw material for prevention.
FAQ

Questions carriers ask

What makes an accident 'recordable' under FMCSA rules?

Any one of three triggers: a fatality, bodily injury requiring medical treatment away from the scene, or disabling damage requiring a vehicle to be towed. Fault, citations, and damage amount do not matter — if a trigger occurred, record it.

How long must I keep the accident register?

Generally three years from the date of each accident. Keep supporting documentation at least as long, and longer for serious crashes where litigation is possible.

What information goes in the register?

The date, location, driver name, injury and fatality counts, hazmat release information, and the carrier's accident documentation for each recordable accident — maintained as a single continuous record at your principal place of business.

Does a not-at-fault crash go in the register?

Yes, if a recordability trigger occurred. The definition does not consider fault — a crash where your driver did nothing wrong but someone was injured away from the scene is still recordable.

What do investigators look for in the register?

Completeness (cross-checked against claims and other sources), honest recording, and evidence of follow-up: preventability reviews, corrective actions, and systemic countermeasures — not just a list of crashes.

Where do I verify current register requirements?

FMCSA's official site (fmcsa.dot.gov) publishes the accident recordkeeping regulations. Verify the exact required data elements and retention there — requirements change.

Call or text Get started