PUBLIC RECORDPossible case foundUSDOT · date · state
✓ Crash Review Desk for US motor carriers
FMCSA can exclude a Not Preventable crash
from your Crash Indicator.
Crash Review Desk finds crashes that may qualify for CPDP and handles the police report, evidence file, and DataQs administration for one authorized case.
You approve the case and its facts. FMCSA makes the final determination.
AUTHORITYCarrier authorizes one crashOne case, in writing
✓ EVIDENCEReport and facts assembledNarrative · diagram · video
✓ DATAQSCase prepared and trackedPrepared · approved · monitored
✓ current CPDP crash types
FMCSA reviews these specified eventspolice report required
The public crash row is not enoughNot Preventable crashes excluded
FMCSA excludes them from this calculationSource: FMCSA CPDP FAQs
Two sources for one crash
We find the crash. The police report shows whether it merits review.
FMCSA's public data lets us identify the carrier and event. It cannot show who struck whom or whether the crash fits CPDP. We use the complete police report to review the narrative, vehicle movements, diagram, and point of impact.
Public record identifies the event
+Carrier and USDOT number
+Crash date and state
+Public report reference
+Recorded severity and citation fields
Complete report shows collision facts
✓Police narrative and diagram
✓Unit movements and point of impact
✓Exact vehicle and event match
✓Relevant conflicting or supporting facts
How it works
We manage the work around one crash
You appoint one carrier contact and approve the facts. Crash Review Desk handles the report, evidence, CPDP review, and DataQs administration.
One crashFive managed steps from public record to DataQs follow-up.
- 01
We spot a possible case
We monitor public FMCSA crash data and identify one event that may fit the Crash Preventability Determination Program.
A public record starts the review. It does not prove fault or eligibility. - 02
You authorize one crash
You confirm the carrier contact and approve a crash-specific report request.
No police report request begins without written authority. - 03
We obtain the right report
We use an approved state or police-agency route, then match the complete report to the FMCSA event.
A missing, incomplete, or mismatched report stops the case. - 04
We build and review the evidence
With your approval, we collect the driver's account and relevant supporting evidence. We compare the complete file with FMCSA's current crash types.
You receive a written recommendation before a request is prepared. - 05
We manage the DataQs work
When the evidence supports a request, we prepare the case, coordinate your approval, and monitor follow-up.
You approve the facts. FMCSA makes the determination.
What you delegate
One case owner for the report, evidence, and DataQs work
Hand off the administrative work that begins when a crash reaches FMCSA's public record. One case owner keeps the report request, evidence, and agency follow-up together.
/ IDENTIFY
Find cases worth checking
We watch the public FMCSA record and bring one specific crash to the carrier for review.
/ DOCUMENT
Handle the evidence chase
We request the police report, confirm the match, and collect the carrier-approved driver account and supporting evidence.
/ MANAGE
Keep the DataQs work moving
We prepare the case, track messages, and coordinate responses. The carrier approves any submission and keeps control of government authentication.
Build the evidence file
A public crash row finds the event. Evidence supports the request.
FMCSA requires a police accident report and may ask for other evidence. We match the report to the public event, collect carrier-approved facts, and review the complete file against current CPDP types.
Initial-contact boundaryPolice reports can contain sensitive information. Do not attach one to a first-contact email or submit one through this website.
A decision before filing
We give you a clear recommendation before preparing a request
The written review tells you whether to proceed, collect one missing item, or stop. An unavailable report also closes the case.
/ A
Prepare the request
Both reviewers find that the complete evidence maps to a current CPDP crash type.
/ B
Collect missing evidence
The report leaves a material question open. We name the evidence needed before a filing decision.
/ C
Do not file
The available facts do not support a current CPDP crash type. We explain the reason and recommend stopping.
/ D
Close the case
The approved route did not produce a complete matching report, so we cannot assess the crash.
Crash Review Desk finds the case and manages the administrative work. You approve the facts. FMCSA decides.
Document-firstHuman-reviewedCarrier-controlled
The official benefit
FMCSA excludes a Not Preventable crash from the Crash Indicator BASIC.
The crash remains listed in the Safety Measurement System. FMCSA excludes it from the carrier's Crash Indicator BASIC calculation and notes the determination on the driver's PSP record.
CPDP does not decide legal fault, negligence, insurance coverage, a safety rating, or operating authority. FMCSA controls eligibility and the final determination.
Read the FMCSA CPDP rulesFAQ
Know what you delegate before sharing a crash
You can use DataQs without us. Crash Review Desk is the managed alternative when you want one person accountable for the case administration.
Is Crash Review Desk part of FMCSA or DataQs?
No. Crash Review Desk is an independent commercial service. FMCSA, DataQs, Login.gov, and police agencies do not endorse or operate it.
What work does Crash Review Desk handle?
We identify a possible case, obtain the police report with written authority, organize the evidence, review the case against current CPDP types, prepare the request, and track follow-up.
How can you find a crash before I contact you?
FMCSA publishes carrier and crash identifiers. We use that public information to identify a specific event and contact the carrier. The public record does not show fault or prove that the crash qualifies.
Why do you need the police report?
FMCSA requires a police accident report for a CPDP request. The report may contain the narrative, diagram, vehicle movements, and point of impact needed to compare the crash with a published type.
Can my carrier file through DataQs without this service?
Yes. DataQs is the government's direct route and does not require a purchase from Crash Review Desk. The service exists for carriers that choose to delegate the report, evidence, and case administration.
Will you interview our driver?
The carrier must approve the interview and the agreed case process applies. We do not ask for a driver name, statement, or police report in the public form or first email.
Do you guarantee a Not Preventable determination?
No. FMCSA controls eligibility, classification, timing, and the final determination.
Will you ask for my Login.gov or DataQs credentials?
No. Keep your password, MFA codes, recovery codes, FMCSA PIN, and authenticated sessions private.
How do I start?
Send the carrier name, USDOT number, crash date, and crash state. We will confirm whether we can handle the case and explain the scope, fee, report cost, and next step before you authorize any work.
Start with one crash
Ask us to review one crash
Send the carrier and crash identifiers. We will confirm whether we can handle the case before requesting authority, a police report, or driver information.
- Carrier name and USDOT number
- Crash date and state
- No report or credentials in this form
- Scope and cost confirmed before work begins
Send identifiers firstKeep the police report, signature, driver information, Login.gov credentials, MFA code, and DataQs password out of the public form and first email.
Crash review requestNo payment · no upload