FMCSA publishes every DOT-registered carrier's crash record on the public safety profile, but raw crash counts routinely mislead brokers in both directions. A single crash doesn't disqualify a carrier; zero crashes doesn't clear one. This guide shows you how to find the data, read each field correctly, calculate the rate that makes crashes comparable across fleet sizes, and identify the signal combinations that should trigger a deeper review or a hard pass.
A carrier's crash history — trailing 24 months — is public on FMCSA's SAFER system and on Knowhaul. What matters isn't the raw count: divide crashes by the carrier's power unit count and multiply by 100 to get the crash rate per 100 trucks. A rate above roughly 1.5 crashes per 100 power units over 24 months puts a carrier in the elevated range. Layer that rate against the Unsafe Driving BASIC percentile and any out-of-service orders — stacking signals are the real red flag.
FMCSA collects crash data from state law-enforcement agencies through the Motor Carrier Management Information System (MCMIS). The public profile shows total crashes for the trailing 24 months, broken down into three severity tiers: fatal crashes (at least one fatality), injury crashes (bodily injury requiring medical treatment away from the scene), and tow-away crashes (a vehicle could not be driven from the scene).
FMCSA does not adjudicate fault. The record does not say whether the carrier was responsible — it records that a commercial vehicle registered to that DOT was involved in a reportable event. A carrier rear-ended at a red light by a distracted driver shows the same entry as a carrier whose driver ran the light.
This matters for how you interpret the data: crash count alone is not a guilty verdict, but it is a data point that demands context — specifically fleet size, violation history, and the severity breakdown.
FMCSA crash data comes from state police reports and records only that a CMV was involved — not who caused the crash. Always pair crash count with the Unsafe Driving BASIC and inspection violation history before drawing a conclusion.
A crash enters the FMCSA record when a commercial motor vehicle in interstate commerce is involved AND at least one of three federal thresholds is met: a fatality, a bodily injury requiring off-scene medical treatment, or a vehicle tow-away. Minor fender-benders where no one is injured and the truck drives away are not reportable — which means every entry on a carrier's public record represents a real-severity event.
State-only intrastate carriers may show lower crash counts than their actual exposure because state participation in MCMIS varies. If you are vetting a carrier that operates exclusively within a single state, the public record may undercount their crash exposure. Interstate carriers operating under federal authority have higher reporting completeness.
Crash records are submitted by states on varying timelines — a recent crash may not appear in the federal system for 30 to 60 days after the event. When timing matters (a carrier with a very recent crash close to the edge of your risk threshold), a direct check of state DOT records can surface events not yet in the federal system.
Raw crash count is nearly meaningless without fleet size context. A 200-truck carrier with 3 crashes over 24 months is far safer than a 5-truck carrier with 1 crash over the same period. The metric FMCSA's Safety Measurement System uses for peer comparison is crash rate: (crashes ÷ power units) × 100, expressed as crashes per 100 power units.
As a rule of thumb, a crash rate above roughly 1.5 crashes per 100 power units over 24 months places a carrier in the elevated range worth investigating. Above 2.0 is a hard look before any tender. These thresholds come from FMCSA's SMS national peer-group benchmarks; the exact numbers shift quarterly as the dataset updates, but the order of magnitude is stable.
The Crash Indicator BASIC percentile, visible on a carrier's SMS Safety Profile, performs this comparison automatically — adjusting for miles driven rather than just fleet count. A percentile above 65–70% is FMCSA's internal alert threshold. If you see a high percentile, the raw-count math above will tell you why.
Fleet size on a carrier profile comes from the most recent MCS-150 filing, which carriers must update only every 24 months. A rapidly growing carrier with outdated paperwork looks riskier on a crash-rate basis than it really is. Cross-check the filed count against inspection-observed power unit counts for a more accurate denominator.
Not every elevated crash count is equal. Certain combinations turn a yellow flag into a strong signal to investigate before tendering — or to decline outright:
Any single one of these flags is a reason to ask questions before tendering a load. Two or more stacking is a hard pass until you have direct answers from the carrier and have re-verified their insurance and authority status.
FMCSA's CSA BASIC scores are driven by roadside inspection violations — not crash records. Crashes feed into a separate Crash Indicator BASIC that compares a carrier's crash rate to peer carriers with similar miles-driven exposure. The two data streams are related but distinct, and reading them together is more powerful than either alone.
A carrier can have a clean inspection record and still carry a high Crash Indicator BASIC. Conversely, a carrier with an elevated Hours-of-Service or Unsafe Driving BASIC but no crashes yet is a leading indicator — the behavior that causes crashes is already documented, even if a crash hasn't happened in the measurement window.
The most concerning profile is a carrier with both an elevated Crash Indicator BASIC and high Unsafe Driving or HOS violations: the underlying behavior is documented in inspections AND it has already produced crashes. That combination warrants either additional vetting documentation (driver qualification files, maintenance records) or a routing decision to a different carrier.
Neither data point is sufficient alone. A high Crash Indicator BASIC with a clean inspection record might reflect bad luck; a clean crash history with a 90th-percentile Unsafe Driving BASIC is a carrier that hasn't crashed yet. Use both together.
Here is the six-step sequence for reviewing a carrier's crash profile before a tender decision. It takes under two minutes once you have the carrier's DOT number in front of you.
If all signals are clean, note the date and move on. If signals stack, escalate: require a certificate of insurance refresh, request driver qualification documentation, or route to a different carrier and note the reason in the file.
The public FMCSA crash record covers the trailing 24 months from the current date. Crashes older than 24 months roll off the live public profile, though FMCSA retains them internally for enforcement and compliance review purposes. The 24-month window is what drives the Crash Indicator BASIC percentile calculation.
No. FMCSA crash data is sourced from state-filed police reports, which record that a commercial motor vehicle was involved — not who caused the crash. A carrier that was rear-ended at a stop light appears in the system identically to a carrier whose driver caused a head-on collision. Fault-at-fault is not a valid DataQ challenge ground; the record only logs involvement.
Inspections are proactive safety checks — a carrier can accumulate serious Hours-of-Service or equipment violations without any crash. Crashes are reactive: they record what happened after a safety failure (or misfortune) occurred on the road. Both matter for vetting, and neither is a substitute for the other. A carrier with heavy inspection violations but no crashes yet is a leading indicator; a carrier with crashes but clean inspections may have been unlucky.
Yes, through FMCSA's DataQ system (fmcsa.dot.gov/DataQs). A carrier can challenge a crash entry if the report was filed in error, the crash does not meet the federal reportable threshold, or the CMV was misidentified. Successful challenges result in removal from the record. However, challenging fault is not grounds for removal — DataQ disputes are limited to whether the crash should be in the system at all, not who was responsible.
FMCSA's SMS publishes quarterly national peer-group benchmarks. As a practical rule of thumb, a rate above roughly 1.5 crashes per 100 power units over 24 months places a carrier in the elevated range worth investigating; above 2.0 is a hard look before tendering. The Crash Indicator BASIC percentile (which adjusts for miles driven rather than just fleet count) gives a more precise comparison — FMCSA's internal alert threshold is a percentile above 65–70%.
Generally yes. Commercial auto and cargo insurers underwrite based on loss history, and FMCSA crash records are part of that picture. A carrier with multiple recent crashes may face higher premiums, higher deductibles, or restricted coverage terms. This is one reason why verifying that a carrier's insurance is currently in force — not just that they had it at the time of onboarding — matters at every tender, not just the first.
Paste an MC, DOT, or VIN to verify a carrier in one card. Free, no signup.
Free, no signup. Paste a DOT, MC, or VIN — verify right away.
CSA BASIC scores rank a carrier's safety against peers across seven behavior categories. Learn what each BASIC measures, how the percentile and intervention thresholds work, and how to read them when vetting a carrier.
Roadside inspection records decoded for brokers — inspection levels, violation severity, OOS conditions, and how to read the inspection list as a near-real-time signal of carrier health.
The out-of-service rate is the share of a carrier's inspections that put a vehicle or driver out of service. Learn how it's calculated, how to read it against the national average, and why it's a leading safety signal.
Open one of these profiles in a new tab to see how the checklist applies to a live carrier record.
Crash count, severity breakdown, fleet size, BASIC scores, and safety rating — all from the live FMCSA record, in one tab.