How do I dispute a crash on my record in DataQs?

Chapter 01

Why does a wrong crash record hurt, and who fixes it?

A crash record starts as a police report. The State sends some of its details to FMCSA. Those details appear in your safety scores, the list of your crashes that anyone can see, and your driver’s work history report (FMCSA’s 2023 notice). A wrong entry hurts in all three places. To fix the facts, you file in DataQs, and the State that reported the crash decides. FMCSA runs the website and sets the rules, but it will not settle a dispute about the facts (the April 2026 rules).

Consider this example. Say you run three trucks under your own USDOT number. On August 14, 2026, one of them is stopped at a red light in a town two States from home. A car hits it from behind. The car’s front end is crushed, and a tow truck takes it away. Your truck has a bent bumper and drives on to deliver its load. The car’s driver says her neck hurts. But she turns down the ambulance, and a relative drives her home. A city police officer writes the crash report, and your driver sends you a copy that night.

On October 5, you log in to FMCSA’s safety score website to check on your company. You find that crash listed twice, and both entries count it as an injury crash. There is also a third crash you have never heard of. It is a tow-away crash from September 2, in another State, in a truck you sold in May. So one real crash has turned into three on your record.

Why does that matter? FMCSA gives each crash points in a crash score (FMCSA’s scoring manual). A tow-away crash gets 1 point. A crash with an injury or a death gets 2. If hazardous materials were released, it gets 1 more. Those points count three times over for the first six months. They count twice until the crash is a year old, and once until it drops out after 24 months.

Now add up yours. The real crash, counted right, is a tow-away crash: 1 point multiplied by 3 gives 3. But your record shows two entries classed as injury crashes at 2 points each, times 3. That makes 12. Add the sold truck’s crash, and you are at 15 instead of 3. The score then divides your points by the size of your fleet, adjusted for miles driven. So in a small fleet, each point weighs a lot. And the crash score only ranks carriers with two or more crashes that count. With one crash, you would have no crash ranking at all. With three, you do. For most truck carriers, a ranking of 65 or higher triggers a warning symbol. FMCSA uses those symbols to pick carriers for letters and investigations (the scoring manual).

Who sees it? The crash score itself is not public. You see it when you log in, and so do FMCSA and the police. But the list of your crashes is public (FMCSA’s 2020 notice). So any broker or shipper who looks you up sees three crashes, not one. A crash also goes on the driver’s work history report, called PSP, for 5 years. Other carriers check that report before they hire a driver.

So who fixes it? The State that reported the crash. Every State must have a contact for crash requests and must take them for 5 years after the crash (the April 2026 rules). Your real crash goes to the State where it happened. The sold truck’s crash goes to the other State. Since September 13, 2026, crash requests follow the same three review stages and deadlines as any other request. Our main guide to DataQs explains those steps. This page stays with what is different about crashes. The first question is what exactly is wrong with yours.

Chapter 02

What can be wrong with a crash record, and does it count at all?

DataQs can fix any fact on a crash record that you can prove is wrong. That includes the date, the place, the truck, the driver, and whether anyone was hurt or killed, or a vehicle was towed. It can remove a copy of a crash that was entered twice. It can also remove a crash that does not meet the federal test. But a crash that meets the test stays on your record, even if the other driver caused it. So first check whether your crash meets that test.

The test is short. Under the federal definition, a crash involving a commercial truck on a public road counts in three cases. Someone dies, then or within 30 days. Someone is hurt and “immediately receives medical treatment away from the scene”. Or a vehicle has damage so bad that it must be towed away. The rule calls that “disabling damage”. It means the vehicle cannot drive off in its usual way, even after simple repairs. A flat tire alone does not count. Neither does a broken headlight or taillight, or damage fixed at the scene without special tools or parts. Some events are not crashes under this test at all. One happens only while cargo is loaded or unloaded. Another happens only while someone gets into or out of a parked truck.

Compare your crash with that definition, one fact at a time. Did anyone get treatment away from the scene right away? No. The police report says the other driver turned down the ambulance and went home. So the injury on your record does not meet the test, and it is wrong. Was a vehicle towed because of damage? Yes, the car was. Here is the trap. Your truck drove away, but the test counts any vehicle in the crash, not just yours. So this crash counts, and asking to remove it would fail. Ask the State to keep one entry and classify it as a tow-away crash without a qualifying injury.

DataQs makes you pick a reason for each request, from a list. FMCSA’s help page shows that list, last updated March 17, 2026 (the DataQs Help Center). We read a copy of that page from September 8, 2026, before the site’s September 13 update, so your screen may differ a little. On the list, the duplicate entry fits “Crash—Duplicate (same crash is listed multiple times)”. The injury fits “Crash report contains incorrect information”. That reason is for a federal record that does not match the police report, which is exactly your case.

Many owners try one more thing at this point. Say your insurer writes a letter that says you were not at fault. It will not help with this request. FMCSA says its crash records are “based on vehicle involvement, and fault is not a consideration” in whether a crash counts (FMCSA’s 2023 notice). FMCSA’s help page says the same: reportable crashes count “without any determination of responsibility” (the DataQs Help Center). This request corrects the facts in the record. The final section explains the separate review of whether your driver could have prevented the crash.

Now change one fact. Say the car had driven away too, and nobody was treated away from the scene. Then the crash would not meet the test at all, and you could ask the State to remove it. A police report that shows no tow and no one treated away from the scene would be your proof. The tow must also be because of damage. A car towed away only because its driver was arrested does not fit the rule’s words. On FMCSA’s list, that reason is called “Crash is not an FMCSA-reportable crash” (the DataQs Help Center).

Other facts go wrong too, and each needs documents that show the correct information. A wrong date or place is fixed with the police report and your ELD records, which show where the truck was and when. A wrong truck is fixed with the report and the truck’s registration. A hazardous materials release that never happened is worth fixing, because it adds a point (the scoring manual). When the federal record differs from the police report, all of these go under “Crash report contains incorrect information”. FMCSA’s own examples for it are wrong death counts, injury counts and vehicle details (the DataQs Help Center).

Before disputing a duplicate, compare the two records carefully. FMCSA’s help page warns that some crashes only look like copies (the DataQs Help Center). A second crash can happen after the first one is over, and it counts on its own. And FMCSA counts crashes by vehicle, not by event. So if two of your trucks were in the same crash, two entries can be right. Compare the date, the time, the place, the truck, the driver and the police report number. Each entry also has its own FMCSA report number, which may differ from the police report’s. If everything else matches, the copy should go. The scoring manual has no step that spots copies, so each one counts in full (the scoring manual).

An inspection after a crash can create another problem. Say an officer had inspected your truck after the crash. Problems the crash caused should not count against you. The scoring manual uses only problems the truck had before the crash. Violations marked as caused by the crash, or marked unknown, are left out (the scoring manual). If crash damage was marked as a problem the truck already had, that is a mistake on the inspection report. You dispute that inspection the same way as any other.

As with any DataQs request, the proof is up to you, and our main guide explains how that works. For a crash, the police report comes first. FMCSA’s crash record holds only some of the details in the police report, and FMCSA does not see the report itself (FMCSA’s 2024 notice). So the report tells the fuller story, and the State can compare the two. You should already have a copy. Federal rules make you keep a list of your crashes for 3 years, with the date, place, driver, injuries and deaths. You must also keep copies of the crash reports (the accident register rule). The rules do not list which papers are enough. FMCSA said each State decides that case by case (the April 2026 rules).

Then you write the request. Keep it short, and point every claim to a paper. Yours could read like this. Fill in the parts in brackets with your own details.

Request to correct crash records. Crash of August 14, 2026. USDOT [your number].

What is wrong. This crash appears twice on our record. Both entries show the same date, time, place, truck, driver and police report number [number]. Both also list an injury. No one was hurt and treated away from the scene.

The proof. The police report (1) shows the other driver turned down the ambulance and left with a relative. It shows one vehicle towed: the other car. Our accident register (2) lists this one crash.

What we ask. Please remove the duplicate entry. On the entry that stays, please remove the injury and keep the tow-away.

Notice what it does not ask. It does not ask the State to remove the crash, because the tow makes it count. It asks only for what the papers prove.

Then the clock runs as it does for any request, with a first answer due in 21 days (the April 2026 rules). One thing is different for crashes. The crash report may come from a city or county police department, not from the State agency that decides your request. If the State has to ask that department something, its clock keeps running. FMCSA also said some hard cases may need more time, and it will work those out with each State. One more thing to get right when you file. You name the State where the crash happened, not your home State. FMCSA’s help page warns that naming your home State sends the request to the wrong office first (the DataQs Help Center). How to open the request, attach the papers and track it is in our guide to filing in DataQs. That leaves the third crash on your list, the one that was never yours.

Chapter 03

What if the crash is not mine at all?

Then you ask the State to take it off your record. You prove that the truck, or the driver, was not working for you at that moment. This happens with a truck you sold, a truck leased on to another carrier, a rented truck, or the wrong driver’s name. The supporting document shows who was running the truck on the day of the crash, and it carries a date. If it shows someone else, the crash is on the wrong USDOT number, and you can prove it.

Go back to the third crash on your list. It happened on September 2, in another State, in the truck you sold on May 20. The buyer runs it under his own authority now. But the crash landed on your USDOT number. Nobody may ever tell you how.

Your proof is the paper trail of the sale. The bill of sale shows the date. The title or the registration in the buyer’s name shows ownership had passed to the buyer. Your insurance schedule shows the truck came off your policy. Your ELD records show none of your drivers drove it after May. You file under “Crash—Company and/or USDOT Number is listed incorrectly on crash report” (the DataQs Help Center). And you send it to the State where the September crash happened, since that State reported it.

This crash teaches one more lesson. The name and USDOT number on a truck’s doors must be those of the carrier running it (the marking rule). So when you sell a truck, or a lease ends, take your name and number off it.

A lease works the same way, with its own papers. Suppose one of your trucks is leased on to another carrier. The federal leasing rules say the lease must name the time and date it starts and ends. It must also say that carrier has “exclusive possession, control, and use” of the truck, and takes “complete responsibility for the operation” of it. That carrier must give you receipts with the date and time it took the truck. Its trip papers must show the load was its responsibility (the leasing rules). FMCSA’s help page names lease agreements and shipping papers among the usual supporting papers (the DataQs Help Center). If the crash happened inside the lease dates, those documents show which carrier was operating the truck. The same rules apply when you are the carrier leasing the truck. If an owner-operator’s truck was leased on to you, those papers point to you.

A rented truck can mix things up as well. When a carrier rents a truck for 30 days or less, the truck may keep the rental company’s name and USDOT number on its doors. The rental agreement must then name the carrier renting it and be kept in the truck (the marking rule). So the rental agreement is the paper that shows who was running it.

Sometimes the truck is right and the driver is wrong. Maybe the report names a driver who left you in June. That hurts him most, because a crash stays on a driver’s work history report for 5 years (the DataQs Help Center). Your driver list, your payroll and your ELD records for that day show who was really driving. FMCSA’s list has a reason for this, “Crash—Driver name is listed incorrectly on the crash report”. But its help text says that reason is for the driver whose own name is wrong, so he may need to file it himself. If the federal record simply does not match the police report, “Crash report contains incorrect information” also fits.

So the sold truck’s crash needs a correction to the record. But your August crash is still on your record, and it was not your driver’s doing. That is a different kind of request.

Chapter 04

Should I fix the facts, or ask whether the crash was preventable?

Fix the facts when the record is wrong. Ask about preventability when the facts are right but your driver could not have avoided the crash. These are two separate requests, and two different offices decide them. The State decides the facts. FMCSA decides preventability, through its Crash Preventability Determination Program. That program takes only some kinds of crash. And a “not preventable” finding does not remove the crash. It takes it out of your crash score (FMCSA’s scoring manual).

Your August 14 crash needs both. Ask the State to remove the duplicate and correct the injury classification. But even when fixed, the crash stays on your record, and a car hit your truck from behind at a red light. That is a question of preventability. Being hit from behind by another driver is one of the kinds of crash FMCSA’s program lists (FMCSA’s 2024 notice). The full list, and how to ask, are on FMCSA’s page for the program.

The program works differently from a correction. You ask FMCSA, not the State, and you must send the police report. If FMCSA finds the crash not preventable, it stays on your public list of crashes, in a separate table. But it no longer counts in your crash score, and the driver’s work history report notes that it was not preventable. If FMCSA finds it preventable, or cannot decide, the crash keeps counting (FMCSA’s 2024 notice).

It is also not a ruling on who caused the crash. FMCSA says the finding does not decide fault or legal blame. It cannot be used in a lawsuit over the crash either (FMCSA’s 2024 notice). Use the correct process for each request. FMCSA said that preventability requests sent to a State will be closed (FMCSA’s 2020 notice). And a correction cannot rule on fault, because fault plays no part in whether a crash counts.

Watch the list of reasons, too. One of them is called “Crash could not be prevented”, and it is not the preventability program. FMCSA’s help text says a request under it “will NOT be upheld and will be automatically closed” (the DataQs Help Center). The preventability review is a separate request, and an FMCSA team decides it.

Which one do you need? Ask one question: are the recorded facts wrong, or could your driver not have avoided the crash? A crash on the wrong USDOT number, a copy, or a tow-away marked as an injury is wrong, and that goes to the State. An accurate record can still describe a crash your driver could not have avoided. That goes to FMCSA’s program, if the crash is a kind it takes. Your sold truck’s crash needs only the State. It is not yours, so whether it was preventable does not matter to you.

Say you file both State requests and the preventability request on October 8. Each State owes you a first answer within 21 days (the April 2026 rules). If both agree, the duplicate and the sold truck’s crash are removed. The remaining entry is classified as a tow-away crash without a qualifying injury. The fix then reaches your scores with FMCSA’s monthly update. Its help page says the data is captured on the third or last Friday of each month. Processing then takes about 10 days (the DataQs Help Center). That leaves one crash worth 3 points. With only one crash, you have no crash ranking at all (the scoring manual). If FMCSA later finds it not preventable, it leaves your crash score as well.

Do not wait on any of it. Your crash counts three times over until February 14, 2027, six months after it happened (the scoring manual). The State takes crash requests for five years, but the score only looks back two. A fix filed in year three no longer helps your score, though it still cleans the driver’s work history report.

There are things we could not check. FMCSA’s websites block automated checks, so we could not open the live DataQs screens or FMCSA’s page for the preventability program. The reason names on this page come from a copy of FMCSA’s help page from September 8, 2026. If the September 13 update renamed them, pick the one that means the same thing. We could not confirm the program’s current list of crash kinds. And we found no official guide to how a police department fixes its own report. If the report itself is wrong, ask the department that wrote it.

If you would rather hand this to someone, we pull the papers, write the requests and answer the State: here is what it costs.