Loading carrier records…
Free case review
Loading carrier records…
Truck Safety Research organizes official FMCSA data into readable carrier reports. We do not assign our own overall safety score or determine fault.
Names, USDOT numbers, reported fleet size, registration, and available federal ratings come from the Company Census File. The registration form and safety rating dates are shown separately. Active registration does not establish that every type of operating authority is active.
The SMS AB PassProperty dataset provides 24-month inspection totals for active interstate and intrastate hazardous-material carriers. It does not cover every intrastate carrier. Driver and vehicle inspection counts overlap. Out-of-service rates equal the relevant out-of-service inspection count divided by inspections of that type. Rates with no inspections or missing inputs are unavailable.
We query the public FMCSA Crash File for the two-year window ending on the report query date. We include complete records marked federally recordable. Reports for the same carrier, report state, number, date, and time are grouped to avoid counting multiple involved vehicles as separate collisions. Severity categories use the highest reported severity: fatal, then injury, then tow-away.
These are site-calculated counts from raw reported data. They may differ from official SAFER and SMS summaries because of reporting periods, filters, corrections, and publication schedules. Reporting delays may leave recent events absent. A crash record documents involvement; it does not establish fault.
Dataset publication dates are taken from the DOT portal’s last row-update metadata. They are not exact measurement cutoff dates. Retrieval dates show when our site fetched the data. We never substitute retrieval dates for an agency rating or registration date.
Supabase checks every five minutes for saved queries due for an update. Carrier reports and dataset metadata target a six-hour refresh; searches and directories target one hour. State and featured city directories are refreshed even without visitors. New carrier queries are fetched when first requested and remain eligible for background refresh for 30 days after the latest request. The schedule refreshes the public data used by this site; it does not mirror the entire national raw database. FMCSA publication schedules and reporting delays still govern when new official records become available. During an outage, saved data no older than seven days may be shown with a warning. If no usable result is available, the report shows an unavailable state rather than a zero.
When a carrier report is opened, the site database retains successful company and inspection source results with their original retrieval dates. These may come from the automatically refreshed Supabase service or a last-good source fallback. Retention does not capture every background refresh or reconstruct earlier records. One latest observation per UTC day is retained, up to 90 observations per source within one year. Rolling totals may change because of corrections or records leaving the measurement window, so subtracting rows does not count new events.
Inspection benchmarks divide the public SMS dataset’s summed out-of-service inspections by summed inspections of that type. Only complete, positive totals with valid out-of-service counts are included. This weighted benchmark describes dataset coverage and is not a matched fleet-size peer group, the SAFER national average, or a crash-risk score.
Some property-carrier SMS measures, including the Crash Indicator BASIC, are not public. We do not display hidden measures or infer an overall safety rating from inspections. See FMCSA’s SMS explanation.
Each carrier report links to SAFER and SMS. For an official data review, consult FMCSA DataQs. A current record may differ from the carrier’s record on the date of a collision.
No. FMCSA crash records document involvement in reported events. They do not determine fault, liability, or whether you have a legal claim.
No. A carrier may have no rating in the public feed. Missing inspections, crash records, or rating data must not be treated as a favorable result.
Yes. Start the case-review form and select that the carrier is unknown. Existing police records, truck photographs, or insurance information may help identify it later.
Supabase checks for due updates every five minutes. Reports target a six-hour refresh and search and directory results target one hour. FMCSA publication and reporting delays still govern when official records become available.
No. This is an independent information service. A case-review inquiry goes to the site operator and its intake services and does not create an attorney-client relationship.
Use the USDOT number to match the company’s federal record. Match the cab’s identifier and incident paperwork rather than assuming a trailer brand is the operating carrier.
A record may list a legal company name and a separate trade or DBA name. Either can help your search, but compare the USDOT number before treating a name match as confirmed.
No. Registration status and operating authority describe different things. Verify the current authority through official agency records when it matters to your inquiry.
Fleet and driver figures come from source records and can reflect information supplied at an earlier time. They are not a live count of vehicles or employees at the collision scene.
Some inspections include driver checks, some vehicle checks, and some both. The categories overlap, so adding them does not produce a reliable total of distinct inspections.
A percentage cannot be calculated with a zero denominator. The report shows “Not enough data” rather than a 0% rate or a favorable safety conclusion.
An inspection finding concerns the inspected driver or vehicle. It is distinct from a company-wide agency order. Do not infer a company-wide shutdown from an inspection rate.
No. This site uses complete records marked federally recordable in its specified query window. Reporting delays, coverage and corrections can affect what appears.
The report displays public carrier-level information and limited event fields. It does not identify every affected person or publish this site’s private intake inquiries.
Source coverage, query dates, rolling windows, corrections and counting rules can differ. Use the methodology and official links to investigate a difference rather than treating either number as interchangeable.
No. It is an inspection-weighted aggregate of valid counts in the public SMS feed. It is not a fleet-size matched peer group, the SAFER national average or a prediction of crash risk.
No. Each row contains rolling totals as retrieved on that date. Corrections and inspections leaving the window can change a total without representing new inspections.
History begins with actual source observations retained by this site. It keeps one latest observation per UTC day, up to 90 per source within one year; older unobserved records are not reconstructed.
Opening a report retains available company and inspection results with their original source retrieval dates. Supabase refreshes the underlying data separately; retention does not capture every background refresh.
Use Print or save PDF and keep the source dates with the saved file. A saved browser link opens a current report later and should not be treated as a permanent copy of today’s page.
A site copy cannot change an agency record. Verify the source and use FMCSA DataQs for an official data-review request when appropriate.