DataQs: Getting a Wrong Inspection or Crash Off Your Record

In 2024, DataQs received 8,314 requests on crash data and 63,548 requests concerning inspections and violations — against the “approximately 3 million inspections, 5 million violations, and over 180,000 vehicles involved in Federally-reportable crashes” FMCSA publishes every year (91 FR 20561, 20562). The older ratio is starker: in calendar 2013, against nearly 3.5 million inspections, “there were fewer than 40,000 RDRs submitted” — about 1.1 percent (79 FR 32491, 32493).

Two things decide whether your filing is one of the ones that works.

The burden of proof is entirely yours, at every stage. Requests “to remove or modify information will be rejected without factual or legal justification explaining why the information is incorrect or incomplete,” and a filing with no minimal justification can be closed without any substantive review at all (91 FR 20561, 20567).

Filing does not take the data down while you argue. FMCSA considered hiding disputed records and refused, because it “creates opportunities for requestors to ‘improve’ their safety records in the short term by submitting frivolous RDRs” (90 FR 28860, 28862). The record stays in your CSA data and on the driver’s PSP report the whole time.

What is DataQs, and why does a State answer instead of FMCSA?

DataQs is FMCSA’s online system for requesting and tracking review of federal and state crash and inspection data, and the individual filing is a Request for Data Review (RDR). Users are “motor carriers, commercial motor vehicle (CMV) drivers, and other interested parties.”

A state officer’s own agency judges your challenge to that officer’s paperwork because of grant law. To qualify for Motor Carrier Safety Assistance Program funds, a State must “ensure the State’s participation in a national motor carrier safety data correction system prescribed by FMCSA” (49 CFR 350.207(a)(12)). That also caps what Washington will do for you: States may consult FMCSA, “but FMCSA will not resolve factual or legal disputes.”

What actually changed in April 2026?

FMCSA published revised DataQs requirements for MCSAP grant funding on April 16, 2026 — a Notice, not a rulemaking, and not a change to the CFR. Docket FMCSA-2023-0190, signed by Administrator Derek Barrs, imposing obligations on States as a condition of grant funding. Four reach a carrier building a filing.

Three stages of independent review. An Initial Review, a Reconsideration and a Final Review, escalating “from the DataQs analyst in the State MCSAP Lead Agency to a responsible decision-maker or panel of subject matter experts.”

Reviewer independence at each stage. The issuing officer cannot be the sole decision-maker on a “Closed—No Data Correction Made” outcome, Reconsideration cannot be decided by that officer or the officer’s immediate supervisor, and Final Review cannot involve anyone who touched either earlier decision (91 FR 20561, 20567).

Reasoned, signed denials. Every “Closed—No Data Correction Made” response must carry six elements: a link to or description of the State’s approved Implementation Plan, the decision-maker’s name and title, the evidence reviewed, the decision, the specific reasons for it, and how to appeal. Procedural closures such as “Closed—No Requestor Response” or “Closed—Insufficient Information” are exempt — they “do not constitute a substantive decision on the merits.”

Published filing windows. States must accept and conduct a good faith review of inspection RDRs filed within 3 years of the inspection date, and crash RDRs within 5 years of the crash date.

Is any of it in force yet?

Not automatically, and this is the part trade coverage skips. FMCSA’s own words introducing the schedule are “FMCSA proposes the following implementation schedule.”

The 150-day date has not arrived as of this review, and no Federal Register document published since April 16, 2026 announces the release. Until a State’s plan is approved, practice varies — FMCSA notes that “every State that does not have a multi-level review process in place will need to incorporate one.” Approved plans get posted publicly on dataqs.fmcsa.dot.gov, so you can read how your own State says it will handle your filing. Do that before you file.

One scope boundary: the new requirements cover State-owned data only — not federally-owned data, which FMCSA lists as Crash Preventability Determination Program requests, Drug and Alcohol Clearinghouse petitions, or other FMCSA offices (90 FR 28860, 28863). FMCSA set no equivalent deadline on its own side, saying only that it “is currently evaluating” one.

What are the real timelines?

There is no 45-day cap on the whole process. That figure is circulating widely and it is wrong. The 45 days applies to Final Review alone. Everything below is in calendar days — FMCSA chose them because they are “simple to track and uniform nationwide.”

Three mechanics sit behind that table. Your 14 days do not count against the State, which “may only request additional information that is relevant and material to the disposition of the review”; when you answer, “the clock will resume (not restart back at day one of the review).” The State’s own delays do count against it — when the Lead Agency has to ask the issuing officer’s agency or another local agency for information, “the clock will keep running.” Missing your 14 days closes the file as “Closed—No Requestor Response” unless the State can already decide on the record. Supplying the information reopens it, but note where it lands: a reopened request “will not be escalated; instead, it will be reviewed at the level it was closed,” with the full allotted time for that stage running again.

Do not read the State-side numbers as a personal entitlement. FMCSA measures timeliness as “the percentage of requests at each review level that are addressed in the respective timelines,” and it will not grant an RDR because a State ran late: “Decisions must be based on the validity of the claim.” It has published no average resolution time, and plans to publish State timeliness measures on the DataQs website once enough data exists. That will be the number to plan around — not a vendor’s average. Corrections that do land are not instant either: FMCSA calculates SMS results monthly (89 FR 91874, 91880), so a correction granted on the 3rd moves nothing on the 4th.

What is actually challengeable?

Records that are incomplete or incorrect. Not records you wish were different. In the 2023 notice proposing the federal appeal it later abandoned, FMCSA published worked examples of requests it said it would not accept for review, each with its stated reason (88 FR 63195, 63198). That appeal never came into being, so read the table as FMCSA’s published reasoning about what these filings lack rather than as a State’s disposition rule. The defects it names cover most of the wasted filings a safety department produces.

Reportability is settled by definition, not argument. Under 49 CFR 390.5, an accident is an occurrence involving a CMV on a highway in interstate or intrastate commerce resulting in a fatality, bodily injury to a person who immediately receives medical treatment away from the scene, or one or more motor vehicles incurring disabling damage requiring a tow. Three outcomes. No fault test. Your accident register runs off the same definition and is separate from anything in DataQs: 49 CFR 390.15(b) requires it be kept for 3 years after the date of each accident.

Reportability filings that do work look nothing like a fault argument. FMCSA guidance holds that a motorist striking a deployed attenuator truck at a construction site is not an accident under 390.5 as to the carrier operating that attenuator truck, and tells that carrier to file an RDR “as a no reportable crash” (80 FR 15913) — a documented rule saying this event is not what the record says it is.

How do you build an RDR that survives?

FMCSA declined to define adequate documentation, saying the circumstances surrounding each RDR “can vary widely” and that “States are best suited to decide on a case-by-case basis if the documents received are sufficient for a given request” (91 FR 20561, 20566). So there is no checklist to satisfy. There is a strategy.

How do you challenge a violation the court threw out?

With certified court documentation, and only if the dismissal came without money attached. This is the most mechanical category of RDR, and the one carriers most often file wrong (79 FR 32491, 32495):

The third row is definitional. “Conviction” in 49 CFR 383.5 and 390.5 includes “the payment of a fine or court cost,” regardless of whether the penalty is rebated, suspended or probated. So “when an RDR indicates that a court dismissed a citation while still imposing a fine or punitive court cost, the outcome will be recorded in MCMIS as a conviction.”

Not every fee counts, though, which is worth checking before you abandon a file. FMCSA excludes incidental expenses “uniformly imposed on all persons that appear before a particular court or tribunal regardless of case outcome” — scheduling fees, the cost of a certified copy of the docket, attorney fees. A court cost becomes a fine “when the amount charged exceeds the amount generally imposed for court costs and is akin to a penalty.”

What to upload: scanned certified documentation from the court or tribunal — “certified records of the docket entry, the order of dismissal, or entry of a ‘not guilty’ determination” — or a link to an official court website showing the result. Two limits: the policy applies only to inspections occurring on or after August 23, 2014, and while a citation is still pending the RDR gets held rather than decided — FMCSA confirmed in 2026 that such requests “can be held while pending with the relevant jurisdiction for adjudication and should only proceed once resolved,” but “should not remain open indefinitely” (91 FR 20561, 20565).

What about a crash you cannot get removed?

Then the question stops being reportability and becomes preventability, which runs on a separate FMCSA-owned track inside DataQs. The Crash Preventability Determination Program covers 21 eligible crash types for crashes on or after December 1, 2024; earlier crashes are judged under the May 2020 criteria, and the program reaches back only to crashes on or after August 1, 2019 (89 FR 96269; 85 FR 27017).

The December 2024 expansion added a catch-all: type 21 is “any other type of crash, not listed above, where a CMV was involved and a video demonstrates the sequence of events of the crash.” The wrong-direction type stayed narrow — FMCSA declined to allow partial crossing of the center line, so a partial-crossing case gets in only through that catch-all. Four conditions then decide whether the filing goes anywhere.

• A Police Accident Report is a condition of eligibility. FMCSA refused to waive it even where video exists, because the PAR corroborates “other information provided with the RDR.”
• The burden is on you, again. FMCSA “does not have direct access to PARs or other supporting documentation about a crash.” You supply compelling evidence that the crash is eligible and not preventable.
• Fatal crashes require the post-accident testing paperwork — results, or the required explanation of why testing was not done within the timeframes in 49 CFR 382.303(d)(1) and (d)(2). A positive result or a refusal makes the crash Preventable.
• Your own paperwork gap can lose it. FMCSA determines Preventable where the driver “was prohibited from operating the CMV at the time of the crash” — out-of-service violations, license violations, Clearinghouse prohibitions — or was not qualified. A crash you would otherwise have won is lost by a stale driver qualification file.

CPDP runs its own 14-calendar-day document deadline, and missing it “will continue to preclude a ‘Not Preventable’ determination and result in an ‘Undecided’ determination.” A determination is not necessarily the end of it: documents uploaded to an RDR stay accessible in DataQs afterward, and FMCSA has said the RDR “may be reopened if additional information is provided to the Agency.”

What a “Not Preventable” result actually buys

Less than the phrase suggests. The crash is not deleted — FMCSA “will continue to list Not Preventable crashes on the public SMS website,” in a separate table. What changes is the arithmetic: they are excluded from the Crash Indicator BASIC calculation, while Preventable and Undecided crashes stay in it. Only Not Preventable determinations are noted on the driver’s PSP record.

Two boundaries get read wrong in opposite directions. It is not litigation ammunition: determinations “do not establish legal liability, fault, or negligence by any party,” and under 49 U.S.C. 504(f) no part of such a report “may be admitted into evidence or used in a civil action for damages.” And their absence proves nothing: “the absence of a not preventable determination does not indicate that a crash was preventable” — useful when a broker or underwriter reads unmarked lines as fault.

Timing gives the filing its urgency. Crashes stay in SMS for 2 years from the crash date and in PSP for 5 years, “as a result, FMCSA will not review crashes that are more than 5 years old,” and the Crash Indicator BASIC uses the previous 24 months. A crash corrected in month 23 has already done nearly all the damage it will do to your Crash Indicator — and still has three years left on the driver’s PSP, which is the argument for filing on behalf of a driver who was not at fault.

Where does the road end?

At your State. There is no appeal to FMCSA. This is the correction most worth making against outdated content, because a great deal of published material still describes a federal appeal as existing or imminent.

FMCSA proposed exactly that in September 2023, then abandoned it: the initial proposal “would not sufficiently address the due process issues that currently exist with State-reviewed RDRs” (90 FR 28860, 28861). The three-stage structure above replaced it. After Final Review, “the State’s decision will be considered final by FMCSA… Any future or related requests concerning the RDR will be heard at the discretion of the State.”

What DataQs cannot correct at all

Drug and Alcohol Clearinghouse records. Corrections run through a petition under 49 CFR 382.717, on its own clock, and the scope is narrow: petitioners “may request only that administrative errors be corrected (e.g., errors in data entry or a duplicate report of a positive test result); petitioners may not contest the accuracy of test results, test refusals, or other violation information, under this section.”

CDL conviction history. DataQs is FMCSA’s correction system for MCMIS data. CDLIS driver records are posted and maintained by the State licensing agency under 49 CFR 384.225. If the problem is a conviction on the driving record, that is the licensing agency’s system — see the MVR check for how that record is pulled.

What a corrected record still cannot tell you

A clean record means the reportable events were recorded correctly. It does not mean much else. Every entry in a corrected federal file is an event serious enough that somebody was legally required to write it down. The behavior producing those events mostly lives below that threshold. A driver who leaves a loaded trailer at a truck stop generates no MCMIS entry at all — the problem the first 24 hours of an abandonment is really about. A driver who burned three carriers on reliability leaves a pattern only those three carriers know, and none of it reaches a system built to record roadside inspections and tow-away crashes.

That gap is what cdlscan is built for: reviews written by the carriers that actually employed a driver, tied to the period they employed him, capturing observations that never became a reportable event. Our overview of how carrier-written driver reviews work covers the format, and the real cost of a bad hire covers what the gap costs.

Be plain about the boundary. This sits on top of the required record, never in place of it. The MVR inquiry, the safety performance history investigation, the Clearinghouse query and the driver qualification file are legally mandatory and nothing here substitutes for any of them; correcting a wrong inspection through DataQs remains the only way to fix a wrong inspection. If you intend to rely on third-party information about a candidate in a hiring decision, ask the provider which category of information they consider it under the Fair Credit Reporting Act, and confirm the attaching obligations with your own counsel. That call belongs to a lawyer.

Frequently asked questions