Carrier crash records show reportable crash involvement recorded in federal safety data. They are useful context, but they do not establish fault, legal liability, or the likely outcome of a particular shipment. Review the count with the period, scale of the operation, and the source’s definitions; do not turn a zero or blank display into a “safe” label.
Use HaulFacts lookup to identify the USDOT record before reading the count. Similar company names or a broker record are not a sound basis for interpreting a motor carrier’s crash history.
What the public record means
FMCSA’s SAFER Company Snapshot includes crash information, and the public SMS carrier overview summarizes 24 months of crash history. Its displayed buckets cover reportable crashes involving a fatality, an injury requiring immediate medical treatment away from the scene, or disabling damage requiring a vehicle to be transported away. These are reportable events, not every collision or minor injury. Listed crashes describe involvement, which does not itself assign fault or responsibility.
Before interpreting a count, verify the USDOT record and the reporting window. A raw count without fleet size, mileage, or exposure does not support a simple comparison between a one-truck operation and a large fleet.
A disciplined review sequence
- Confirm the legal entity and USDOT number.
- Record the stated time window and total crash count exactly as shown.
- Identify whether the source calls the events reportable crashes, involvement, or another defined category.
- Consider the count alongside inspection history and any official rating, without combining them into an invented score.
- Apply your company’s documented escalation policy if one exists.
A hypothetical carrier’s SMS overview may show two reportable crash involvements in a 24-month period. A reviewer can record that fact and the source date. The reviewer cannot fairly state that the carrier caused two crashes or is unsuitable for every load without more evidence and an applicable policy.
Why absence is not assurance
No displayed crashes can reflect the time period, the scope of reportable events, reporting timing, or limited available records. It does not verify driver behavior, equipment condition, cargo security, or current insurance. The same logic applies to inspection history: public history is evidence with boundaries.
Safety records also answer a different question than identity. A valid-looking crash history does not prove that the person who emailed a rate confirmation represents the registered company. Use independent contact checks and a pre-pickup process when fraud or diversion is a concern.
Do not use the page to infer a driver’s individual record or make a public allegation. The federal summary is carrier-level information with its own reporting criteria and should stay in that context.
Review inspection history alongside the crash count and use carrier vetting to connect the public record to your decision process.