← All guides
Guide

How do you challenge an inspection or violation with DataQs?

You file a Request for Data Review (RDR) in FMCSA's DataQs system against the specific inspection report, violation or crash record. A state agency adjudicates most requests, not FMCSA, and the burden of proof rests entirely with you.

What DataQs is, and who actually decides

DataQs is FMCSA's online system for requesting a review of federal and state safety data you believe is incomplete or incorrect. FMCSA builds and hosts it, but FMCSA does not decide most cases. You pick a request type and the state where the event happened, and the system routes the request there. State DataQs analysts review and respond to most requests; FMCSA Service Center and Division staff can also respond.

Two programs are the exception. Drug and Alcohol Clearinghouse petitions and Crash Preventability Determination Program requests are reviewed by FMCSA teams trained specifically for those reviews.

Anyone can register for a free account and file. In 2024, DataQs received 8,314 requests on crash data and 63,548 on inspections and violations.

What you can challenge, and what you cannot

Request types cover crash, inspection, investigation and audit records, plus registration, licensing and insurance, household goods complaints, and Clearinghouse petitions. The winnable grounds are factual: a wrong USDOT number or driver name, a crash that is not FMCSA-reportable, a duplicate or missing record, a violation listed in error or listed twice, and crash data that differs from the Police Accident Report.

Three limits save wasted effort.

  • Warnings cannot be challenged. FMCSA records do not contain written or verbal warnings issued on behalf of the state. Inspection records do contain violations noted at the time, whether or not a citation was issued.
  • Fixing the defect does not remove the violation. A fixed violation is not the same as an incorrect violation and will remain on the record. Removal requires proof the violation did not exist, was recorded in error, or was listed multiple times.
  • "Crash could not be prevented" is a dead end as a crash RDR. FMCSA states the request will not be upheld and will be automatically closed. Preventability has its own program.

How a Request for Data Review works end to end

You search for the record, pick a reason, add detail, upload documents, and track status in My DataQs. The decision arrives by email.

If you contested the citation behind a violation, use the citation option rather than arguing the violation itself. An adjudicated citation is one contested through due process in a state, local or administrative tribunal. Not guilty or dismissed is excluded from SMS calculations and from the PSP report. Conviction of a different charge sets the SMS severity weight to 1. Conviction of the original charge keeps the original weight.

As of September 18, 2026, a state's RDR plan must allow for three stages of independent review, used as needed, as a condition of MCSAP grant funding: Initial Review, Reconsideration and Final Review. Reconsideration and Final Review are not automatic. You have to ask for them, within 30 days of the decision you are appealing. At Initial Review the issuing officer cannot be the sole decision-maker on a denial. Reconsideration goes to an independent person or panel with subject matter expertise, not the issuing officer or that officer's immediate supervisor. Final Review escalates to a senior decision-maker or independent panel, and nobody involved in an earlier stage may decide it. After Final Review the state's decision is final to FMCSA. You escalate with "Re-open Request" under Take Action.

Denials have to explain themselves now. An RDR closed "No Data Correction Made" must point to the state's approved DataQs Implementation Plan, name the decision-maker, list the evidence reviewed, give the decision and the specific reasons for it, and — at any stage before Final Review — tell you how to appeal.

What makes a challenge succeed

The burden of proof rests entirely with the requestor, at every stage. An RDR will be rejected without factual or legal justification explaining why the information is incorrect or incomplete. A request with no minimal justification can be rejected procedurally, without a substantive review.

Common supporting documents are the state inspection report, the state crash report, shipping papers and lease agreements. For a crash the PAR is the anchor: FMCSA receives only a subset of PAR fields in MCMIS and no direct access to the PAR itself.

Front-load everything. The appeal stages review the existing record, so new unrequested evidence at Reconsideration or Final Review sends the RDR back to Initial Review. On appeal, address the state's prior reasoning and say why it was wrong; disagreement alone can be summarily rejected. When a state asks for more, you have 14 days.

Filing windows, deadlines, and when the data actually moves

States must accept and conduct a good faith review of inspection RDRs submitted within 3 years of the inspection, and crash RDRs for 5 years from the date of the crash.

The deadlines effective September 18, 2026: open the RDR within 7 days of submission, decide Initial Review within 21 days of submission, decide a Reconsideration within 21 days of the request, and a Final Review within 45 days. You have 30 days to escalate after each decision, and the state's clock pauses for your 14 days to answer an information request. CPDP and Clearinghouse requests run on their own timelines.

A win closes as "Data Correction Made," and it will not move your percentile that week. SMS and PSP update monthly from a snapshot taken on the third or last Friday of the month, and processing and validation take about 10 days before results post.

Crash preventability is a separate program

The Crash Preventability Determination Program is where you argue a crash was not preventable. It runs through DataQs, FMCSA adjudicates it, and a Police Accident Report issued by a law enforcement agency is a condition of eligibility. For crashes occurring on or after December 1, 2024, 21 crash types are eligible; earlier crashes are evaluated under the May 2020 criteria.

Not Preventable is excluded from the carrier's Crash Indicator BASIC, still appears on the public SMS website in a separate table, and is the only CPDP result noted on the driver's PSP record. Preventable and Undecided keep counting. FMCSA finds a crash Preventable where evidence shows the driver or carrier could have prevented it, or was prohibited from operating the CMV at the time: out-of-service violations, license violations, Clearinghouse prohibitions. A fatal crash requires proper post-accident drug and alcohol test results, or the required explanation of why testing missed the timeframes in 49 CFR 382.303(d)(1) and (d)(2). A Preventable or Undecided RDR may be re-opened once.

CPDP is voluntary and supports SMS. It does not alter FMCSA's safety fitness standard under 49 U.S.C. 31144 and 49 CFR part 385, and it assigns no fault. FMCSA states that under 49 U.S.C. 504(f) its preventability determinations may not be admitted into evidence or used in a civil action for damages.

  • Struck in the rear, or on the side at the rear
  • Struck on the side by a motorist going the same direction
  • Struck while legally stopped at a traffic control device, or parked, including unattended
  • Struck by a motorist going the wrong direction, or making a U-turn or illegal turn
  • Struck by a motorist who did not stop or slow in traffic, or failed to stop at a traffic control device
  • Struck by a motorist entering the roadway from a private driveway or parking lot
  • Struck by a motorist who lost control of the vehicle
  • Struck because another individual was under the influence, by the legal standard where the crash occurred
  • Struck because another motorist had a contributing medical issue, fell asleep, or was distracted
  • Struck by cargo or equipment from another vehicle, or by debris
  • Crash resulting from an infrastructure failure
  • CMV struck an animal
  • Crash involving a suicide death or suicide attempt
  • Crash involving a non-motorist
  • A crash type that seldom occurs and meets no other eligible type
  • Any other crash type where a video demonstrates the sequence of events

Treat DataQs as a monthly routine

DataQs rewards a standing process, not an annual cleanup. Pull inspections and violations monthly and read each new record against the paper you already hold, while the inspection is inside three years and the crash inside five. Keep the PAR, the repair order, the lease and the license history filed against the record so an RDR takes an hour, not a week. Fleetmule's inspections and CSA workflow syncs inspections and violations, shows what is driving score changes, and surfaces the records worth a dispute; the decision to file stays with your safety team.

Common questions

Who decides a DataQs challenge, FMCSA or the state?

FMCSA runs the DataQs system, but state DataQs analysts review and respond to most requests. The request is routed to the state where the inspection or crash occurred. FMCSA runs the DataQs system, but state DataQs analysts review and respond to most requests, routed to the state where the inspection or crash occurred. Crash Preventability Determination Program requests and Drug and Alcohol Clearinghouse petitions go to FMCSA teams trained for those reviews, and FMCSA Service Center and Division staff can respond to other requests, including those against federal records.

How long does a DataQs request take?

As of September 18, 2026, a state must open an RDR within 7 days of submission and decide an Initial Review within 21 days. A Reconsideration is due within 21 days of the request and a Final Review within 45 days. The state's clock pauses for the 14 days you have to answer a request for more information.

Can a violation be removed because the defect was repaired?

No. FMCSA states that a fixed violation is not the same as an incorrect violation and will remain on the record. Removing it requires proof that the violation did not exist, was recorded in error, or was listed multiple times.

How far back can you dispute an inspection or a crash?

States must accept and conduct a good faith review of inspection-related RDRs submitted within 3 years from the date of the inspection, and crash-related RDRs for 5 years from the date of the crash.

Does a Not Preventable determination take the crash off your CSA score?

It removes the crash from the calculation of your Crash Indicator BASIC, but the crash still appears on the public SMS website in a separate table. Crashes found Preventable or Undecided continue to count in the Crash Indicator BASIC.

Sources