How to Correct Wrong Data in FMCSA Records (DataQs)

Errors happen in any large administrative dataset — a violation recorded against the wrong carrier, a crash report with an incorrect detail, an inspection result that doesn't match what actually happened. FMCSA provides a formal channel for challenging data it publishes: DataQs. Understanding how it works matters both for carriers correcting their own record and for anyone relying on FMCSA data who wants to understand how disputes get resolved.

What DataQs is for

DataQs is FMCSA's system for submitting a Request for Data Review (RDR) — a formal challenge to specific data FMCSA has published about a carrier, driver, or safety event. It covers things like inspection results, crash reports, and other safety data points a carrier or other party believes are inaccurate or improperly attributed.

Who can file a request

Requests can come from a carrier disputing data about its own operation, or from other parties with a legitimate interest in a specific record's accuracy. The review process routes each request to the agency responsible for the original data — often a state agency that submitted the underlying inspection or crash report — since FMCSA's federal system largely aggregates data submitted by states rather than generating it independently.

What the review process looks like

A submitted request goes to the relevant reviewing agency, which evaluates the challenge against the original documentation and either upholds the record as accurate or corrects it. This isn't an instant process — it involves an actual review by the agency that owns the underlying data, which takes time, and outcomes depend on the specific facts and documentation available for that record.

Why this matters for a carrier's public record

An inaccurate violation or crash attribution doesn't just look bad — it can meaningfully affect a carrier's calculated BASIC scores and out-of-service rates, since those are built directly from this underlying data. A successful DataQs correction updates the source record, which then flows through to any system, including CarrierPedia, that pulls from FMCSA's published datasets on their normal refresh schedule.

What CarrierPedia can and can't fix directly

CarrierPedia mirrors public FMCSA data — it doesn't maintain or control the underlying federal records. If something on a carrier's FMCSA record itself is wrong, DataQs is the correct channel, not a request to this site. If instead a page here doesn't yet reflect a correction FMCSA has already made — which can happen given our own refresh schedule — that's a different, faster fix on our end. See Data Corrections for exactly which situation applies and what to do about it.

A practical note for carriers

Because BASIC scores, out-of-service rates, and crash history all directly affect how a carrier is perceived by brokers, shippers, and insurers, carriers have a real incentive to monitor their own record for errors rather than assuming everything published is correct. Reviewing your own carrier profile periodically — and comparing it against your own inspection and crash records — is a reasonable practice, especially after any inspection or incident you believe was recorded incorrectly.