Crash-record errors that aren't about fault: wrong carrier, non-recordable, duplicates.

Gut check: fault question or fact question?.

Before you do anything, sort the crash into one of two buckets.

Here is the line that keeps you out of trouble: fault and reportability have nothing to do with each other. A crash you could not possibly have prevented can still be a perfectly valid, correctly recorded crash. So if your real complaint is "this wasn't my fault," stop — that's the CPDP, not this. This lesson is only about records that are factually wrong.

Is it even a reportable crash?.

This is the one most owners miss. A crash only belongs on your federal record if it clears two bars at once — a vehicle test and a severity test. Miss either one, and it should not be there.

"Disabled" has a specific meaning: damage that keeps the vehicle from leaving in its normal way after simple repairs. A fender that bends back so you can drive off is not disabling damage. A car that has to ride away on a flatbed is.

Common ones that quietly fail the test: a driver who was off duty, a truck running bobtail on personal business, personal use of the vehicle, or an errand the driver ran after the contracted job was already done. A personally owned vehicle used for personal reasons is not a recordable crash either.

The error types — and the proof that wins each.

Once you know it's a fact question, find your error type. Each one has a document that does the heavy lifting. And across all of them, one paper sits at the center: the Police Accident Report, the PAR. It's the source record for almost every crash dispute, so get a clean copy first.

On the contractor trap

One trap on the wrong-driver type: a leased or contracted driver still counts as yours. Federal definitions treat an independent contractor as an "employee" of the carrier, so "he's a contractor, not my employee" is not a defense. The off-duty angle, though, is real — if the driver genuinely was not on duty under the federal on-duty-time definition when the crash happened, that is a legitimate fact challenge.

On the document clock

Keep these documents. The rule requires carriers to hold crash and inspection supporting documents for at least six months. You will be glad you did when the dispute comes in weeks after the incident.

What gets it denied.

A few things sink an otherwise good crash dispute.

• Filing a fault argument dressed as a fact error. "It wasn't my fault" belongs in the CPDP, not here — file it as a data error and it goes nowhere.

• Missing the Police Accident Report. The PAR anchors the whole case; without it, a reviewer has little to work from.

• Calling a contractor "not my driver." The federal employee definition closes that door — a leased driver is the carrier's.

• Thin proof on wrong-carrier. A bare assertion will not move a USDOT number; the lease, shipping papers, log, and registration are what reassign the crash.

• Filing outside the window. States must review crash records for 5 years from the date of the crash. Inside that window the state must look; outside it, review is discretionary. File while the crash is fresh.

Checklist: reportable-crash test + error-type proof.

Use these two tables as a reference before you file. The first tells you whether a crash belongs on federal record at all. The second maps each error type to the proof that closes it.

Is this even a reportable crash?

Error type → proof checklist

If you need to build the evidence file for a specific error type, the evidence-that-wins lesson goes deeper on what documents actually move each category. And if the crash dispute turns out to be a fault argument — not a data error — the CPDP lesson walks the preventability path. The DataQs hub maps the whole topic.