What's Really in Your PSP Report? | ATDSA Guide

Your PSP report is FMCSA (opens in a new tab)'s own file on you, and it's not a mystery box. It shows five years of crash history and three years of roadside inspection history, pulled straight from the federal Motor Carrier Management Information System (MCMIS). You can order your own copy from FMCSA for a small fee, or get it free through a FOIA request. FMCSA's 2013 safety impact study found that carriers using PSP as a hiring screen averaged an 8% lower crash rate and a 17% lower driver out-of-service rate than carriers that didn't use it. That's the whole reason this report exists, and it's why you need to know what's in yours before a hiring desk pulls it.

At ATDSA, we review PSP and inspection records for professional drivers every week, and the mistake we see most often is waiting until a job offer falls through to find out something on that record is wrong. By then you're not fixing a data error, you're explaining a gap in employment to the next carrier. Pull your own record now. Know what's accurate and what isn't, and handle any dispute before it costs you a seat.

What Information Does a PSP Report Actually Contain?

A PSP report contains two things, and only two things: your DOT-reportable crash history for the past five years, and your roadside inspection history for the past three years, as recorded in MCMIS. FMCSA's own program page says it plainly — it's a crash and inspection snapshot, nothing more. The crash data covers any DOT-reportable crash you were involved in, meaning one involving a fatality, an injury treated away from the scene, or a vehicle towed for disabling damage, as defined under 49 CFR 390.5T (opens in a new tab). It doesn't matter who was at fault. If it met that threshold and got reported, it's in there.

The inspection side shows every roadside inspection on file, including any violations cited, whether you or the vehicle got placed out of service, and even clean inspections with no driver-related violations. FMCSA updates the data monthly from the same MCMIS extract carriers and state agencies feed into. So if you got inspected last week in another state, it might take a cycle or two before it shows up on your report.

What's Not on a PSP Report?

Here's where a lot of drivers get confused, and it matters. A PSP report does not contain your state driving convictions. It doesn't contain your license status, points, suspensions, or anything else that lives on your state Motor Vehicle Record (MVR). Those are two completely separate systems. Your MVR comes from your state licensing agency. Your PSP record comes from federal MCMIS data on crashes and inspections only.

Carriers still have to pull your MVR separately, and federal rules require it. Under 49 CFR 391.23 (opens in a new tab), a motor carrier has to request a driver's MVR from every state where that driver held a license in the preceding three years before hiring them. Under 49 CFR 391.25 (opens in a new tab), that carrier has to pull and review your MVR again at least once every twelve months while you're employed. Those records, along with your application and safety performance history, get filed under 49 CFR 391.51 (opens in a new tab) in your driver qualification file. A PSP report doesn't replace any of that. It's an add-on screening tool, not a substitute for the MVR check carriers are legally required to run.

It's also worth knowing that CDL disqualification for things like DUI or certain traffic convictions runs under 49 CFR Part 383.51 (opens in a new tab), and that process goes through your state driving record and CDLIS, not through PSP. If you're dealing with a conviction or disqualification issue, that's a different fight than correcting a PSP data error, and it needs a different approach.

Does a Carrier Need My Permission to Pull It?

Yes. Federal statute (49 U.S.C. 31150 (opens in a new tab)) requires that your crash and inspection data get compiled into PSP, but a prospective employer has to get your written consent before actually using that report to screen you for a job. FMCSA's driver factsheet, "Just the Facts for Drivers," says it straight: carriers can only use PSP as a pre-employment screening tool to see your five-year crash and three-year inspection history, and they need your consent before they can pull it. A carrier also can't use PSP to screen a current employee's driving record — only new hires at the pre-employment stage. If a carrier ran a PSP report on you without consent, that's worth flagging, not something to let slide.

How Do I Get My Own PSP Report?

You've got two ways to see exactly what a hiring carrier sees. The fast option is ordering it yourself at psp.fmcsa.dot.gov. FMCSA's own driver factsheet lists the fee at $10 per report, straight from the source, not a guess. You get it almost instantly, and you can see exactly what's showing up before anyone else does.

The free option is a Freedom of Information Act (FOIA) request submitted through FMCSA's FOIA portal. It costs nothing, but it moves slower, sometimes weeks slower, which doesn't help if you've got a job offer sitting on the table right now. If you're between jobs or just want a baseline check, FOIA works fine. If you're actively applying and need to know what a carrier's hiring desk is about to see, pay the $10 and get it today.

This is usually the point where a driver realizes they haven't looked at their own record in years, and that's exactly the gap we built the ATDSA Driver Compliance Bundle to close. We help you pull your file, read it the way a hiring carrier reads it, and flag anything that needs a second look before it costs you a job.

What If My PSP Report Has an Error on It?

If something on your PSP report is wrong, incomplete, or doesn't belong to you, you challenge it through FMCSA's DataQs (opens in a new tab) system, not by calling FMCSA directly. DataQs lets drivers, carriers, and other parties file a Request for Data Review (RDR) when MCMIS crash or inspection data looks wrong. FMCSA's Federal Register notice on its revised DataQs requirements lays out the scale of what gets processed. The agency publishes roughly 3 million inspections, 5 million violations, and over 180,000 crash-involved vehicles into the system every year, and in 2024 alone DataQs took in 8,314 crash data requests and 63,548 inspection and violation requests.

FMCSA overhauled the DataQs process in 2025 as part of a broader package of trucking reforms. States now have to follow a defined three-step independent review process with strict deadlines, and they're required to review requests filed within three years of an inspection and within five years of a crash — the same windows that match what shows up on your PSP report in the first place. The FMCSA Administrator said the changes were meant to "guarantee due process by ensuring drivers who challenge an inspection or crash record receive an independent, unbiased, and completed review in a timely manner," according to FMCSA's newsroom announcement on the DataQs upgrade.

These 2025 DataQs changes, including the three-step review and the three- and five-year windows, may change. Check the DataQs site for the current rules before you file.

Here's the honest part, though. Filing a DataQs request starts a review, it doesn't promise a result. The data on your PSP report was originally reported by a state agency, and FMCSA can't unilaterally change a state's record without that state's agreement, a point state DOT guidance pages echo directly. Some disputes get resolved in your favor. Some don't. What you control is whether you catch the error early and build a clean, documented case, instead of finding it mid-hiring-process when there's no time left to fix anything.

How ATDSA Helps You Manage Your PSP Record and DataQs Disputes

When a member sends us a PSP report, the first thing we do is pull it apart line by line and check it against what actually happened: date, location, violation code, and whether it even got reported correctly in the first place. We've overseen more than 650,000 citations and directed over 10,000 Safety Fitness Determination upgrades over 25-plus years in this business, so we know what a legitimate data error looks like versus a record that's accurate but just needs context.

From there, we tell you plainly whether something's worth disputing through DataQs, help you put together the documentation that actually moves a request through state review, and track it until it resolves. We also fold your PSP record into ongoing CDL monitoring, so instead of finding out about a problem the day a carrier's hiring desk flags it, you know about it the day it hits MCMIS. That's the whole point of CSA (opens in a new tab) score monitoring and DataQs support done right: catching it early, not reacting late.

Don't wait for a carrier's hiring desk to flag it. Get your PSP report in front of us through the ATDSA Driver Compliance Bundle, and we'll tell you exactly what's worth disputing and what's just part of the job.