Your Carrier Checks Out. The Driver Has Four Crashes in Three Years.

The load was 42,000 pounds of pharmaceutical product on a reefer. MC-1247893 / DOT-3567102. No BASIC alerts in any category. Satisfactory rating dated 2022. OOS rate well below the national average for both vehicle and driver. Insurance verified against the FMCSA L&I database. I'd tendered to them once before without a problem.

The driver they put on that load had four crashes in three years before he was ever hired by this carrier. Two involved injuries. One fatality. All of it was in the FMCSA's Pre-Employment Screening Program database, visible to any carrier who paid the $10 fee and asked.

The carrier apparently didn't ask. And I didn't know because I was vetting the carrier — not the person behind the wheel.

That's the gap I want to talk about today.

The PSP Database: What It Is and What It Shows

The Pre-Employment Screening Program (PSP) is an FMCSA-maintained database of individual commercial driver safety records. You access it at psp.fmcsa.dot.gov. Carriers enroll in the program and request reports during the hiring process — with the driver's written consent. A single report costs roughly $10.

Each PSP report contains five years of crash data and three years of inspection violations tied to that specific CDL. Not the carrier. Not the fleet. The person. If a driver had a crash in Ohio while working for one carrier, then left, then got hired by your carrier and crashed again, both crashes are in the PSP. The state MVR — the motor vehicle record from a state DMV — won't show you the federal inspection history. It captures license status, state-level violations, DUI records. It doesn't pull the roadside inspection from Georgia where the driver was found in violation of hours-of-service rules, or the brake defect violation flagged during a Level I inspection in Texas.

PSP gets you the FMCSA side of the ledger: the inspections, the violations, the crashes recorded in the federal database regardless of which state they happened in. It's the only way to see how a driver has actually performed across their entire commercial driving history under federal oversight.

Why Carrier-Level BASIC Scores Miss This

Here's the mechanical problem. Every BASIC score is a carrier-level aggregate. The algorithm takes violation and crash data from inspections and incidents across the fleet, weights them by time and severity, and produces a percentile compared to peer carriers. When a carrier runs 40 trucks, one driver's history gets averaged into the whole fleet. A clean fleet can absorb one dangerous driver without pushing a single BASIC into alert territory.

Small carriers are actually more exposed to this problem, not less. A 6-truck operation where one driver had three crashes in 24 months might sit in the 65th percentile on the Crash Indicator BASIC — elevated but not flagged, not in alert. Because FMCSA normalizes crash data against estimated vehicle miles traveled, and a small fleet runs fewer miles, the denominator is small and the math gets messy. From the outside: a carrier with some crash exposure. From the inside: one person who has no business driving that equipment, and five others who drive fine.

There's also a timing problem. FMCSA BASIC data runs about 60 days behind real time — inspections and crashes have to be reported, processed, and incorporated into the monthly recalculation. A crash that happened six weeks ago may not have moved the needle yet. PSP has its own update lag, but individual driver records tend to update faster than the carrier-level percentile recalculations.

None of this is an argument to stop checking BASICs. They matter. But they're a carrier-level instrument. They're telling you about the fleet, not about the driver your freight depends on.

The Regulatory Basis: §391.23 and §391.25

49 CFR § 391.23 requires carriers to investigate each driver's safety performance history before putting them on the road. That investigation must include employment history from prior DOT-regulated employers for the preceding three years, plus driving record from every state where the driver held a license during that period. The PSP report is the tool FMCSA built specifically for this purpose — it gives carriers the FMCSA-side inspection and crash history that no state MVR can provide.

Carriers aren't legally required to name PSP by name in their compliance records. But § 391.23's purpose is clear: you're supposed to actually know something about this person's driving history before you hand them the keys. A carrier that skips the PSP and relies only on a state MVR has a plausible compliance argument — an MVR does satisfy some of § 391.23's requirements — but they're working with an incomplete picture. They're not seeing the inspection violations, the out-of-service orders at the driver level, the crash history that didn't result in a state conviction.

§ 391.25 requires an annual review of each driver's driving record. If a carrier is doing these correctly, they're not filing a piece of paper and calling it done. They're looking at whether the driver's record has changed since hire. Someone who had two clean years and then two crashes in year three should be triggering that annual review process — and if the carrier is current on PSP, those crashes show up.

A carrier that neither runs PSP at hire nor does real annual reviews has a compliance gap. Under § 391.23 and § 391.25, they're required to know their drivers' histories. If they don't know — because they didn't look — that's not a technicality. That's the kind of gap that plaintiff's counsel will highlight in discovery.

PSP vs. Clearinghouse: They're Not the Same Thing

I want to be clear about this because brokers conflate them. The FMCSA Drug & Alcohol Clearinghouse shows drug and alcohol program violations: failed tests, refusals, return-to-duty status, prohibited determinations. It tells you whether a driver is currently prohibited from operating a CMV and whether they've completed the return-to-duty process. It does not show crash history. It does not show inspection violations.

PSP shows crash data and inspection history. It does not show Clearinghouse information.

A complete driver screening program uses both. Clearinghouse for the drug and alcohol side. PSP for the crash and inspection side. State MVR for license status and state violations. Together, those three sources give you a reasonably complete picture of a driver's history. Any one of them alone is a partial view.

When you ask a carrier about their driver screening process, the answer should involve all three. "We run Clearinghouse queries and pull the state MVR" is not a complete answer. Ask specifically about PSP.

What You Can Actually Ask

Brokers aren't going to pull PSP reports on drivers. The program is designed for carriers making hiring decisions, the driver's written consent is required, and you typically don't know who's assigned to a load when you tender it. That's not your job.

What is your job is asking whether the carrier does this as part of their normal hiring process. The question is direct: "Do you run PSP reports on drivers before hire?"

Most carriers will say yes. The honest answer for most established carriers is yes, even if execution is inconsistent. What matters is the follow-up: "Do you keep those reports in your driver qualification files?"

49 CFR § 391.51 sets out what a DQ file must contain. PSP reports aren't enumerated by name — the regulation predates the program — but the underlying documentation requirement is there. A carrier that runs PSP at hire, documents the results, and can produce those records if a DQ file is ever subpoenaed has a paper trail showing they took § 391.23 seriously. A carrier that runs PSP but doesn't retain the reports has a documentation gap. A carrier that doesn't run PSP at all is doing driver hiring with incomplete information.

For new carriers I haven't worked with before, I ask the question during the initial carrier setup conversation, not just at the first load tender. It's one of the things that separates carriers I'll run freight with regularly from carriers I'll use once and not again.

The High-Value Load Variation

On pharmaceutical loads, high-value electronics, anything where cargo value exceeds $150K, I ask for the driver's CDL number before pickup. Not because I'm going to pull their record — I can't without consent — but because the question tells me something.

A carrier whose dispatcher can immediately provide a CDL number is working with a system that knows which driver is assigned to which load. They have driver information organized and accessible. That's a carrier running an operation, not improvising. A dispatcher who says "we'll have a driver by pickup, I don't know who yet" at 8 AM on a load that picks up at noon is a different scenario.

Asking for the CDL also opens the door to the PSP conversation naturally. "We confirm CDL number and carrier verifies they've run PSP on the assigned driver" is a defensible documentation note. It's not foolproof — but it shows a process.

For freight above $200K or for pharmaceutical, hazmat, or specialty cargo where a loss isn't just expensive but potentially catastrophic, I'd want more. An explicit written confirmation from the carrier that the assigned driver's PSP was reviewed at hire and that no subsequent disqualifying violations have appeared. That's a reasonable ask for a load that serious.

What Montgomery Changes About This

Before Montgomery v. Caribe Transport II, LLC, the preemption argument gave brokers some cover: federal law preempted state negligent-selection claims, so there was a structural limit on liability regardless of what the broker knew or didn't know. The Supreme Court ended that on May 14, 2026, unanimously. Negligent selection claims now survive in state court.

Which means the question "what did the broker do to vet the carrier?" now includes the question "did the broker ask whether the carrier actually vets its own drivers?" A plaintiff's lawyer who can show that the driver had a documented history of crashes — a history the carrier had access to and chose not to look at — and that the broker never asked about the carrier's driver screening process has a story. The broker hired the carrier without knowing the carrier hired the driver without looking.

That's not a complicated theory of liability. It's a chain of "nobody asked."

How I Document This

For every new carrier, I add a line to the carrier qualification notes:

"Confirmed carrier runs PSP reports on drivers at hire per § 391.23 and maintains driver qualification files per § 391.51. [Date]. [Contact name and title]."

One line. Takes 30 seconds. Creates a record that I asked and got an answer.

For established carriers on high-value lanes, I add a note at the per-load level when I confirm the load assignment: "Carrier confirmed driver assigned, CDL on file, PSP reviewed at hire."

That's the whole protocol. It's not an audit. It's not a certification. It's the difference between a broker who thought about whether the driver was qualified and a broker who didn't.

One more thing. If a carrier tells you they don't need PSP because "we know our drivers" or "we've run their routes for years," that's exactly the answer that should make you uncomfortable. The carriers most confident they don't need a formal process are often the ones with the least documentation when something goes wrong.

— Mason Lavallet

Founder, DOTScreener.com