Why official reports miss a driver going unreachable

A clean PSP does not mean the last desk could still reach them. Stopping answering, ignoring calls, or going unreachable on a live load is an employment event, not a filing, and no federal hiring packet is built to hold a dead phone. The packet comes back quiet because nothing in it was ever designed to make a noise about that.

Among the reviews carriers left on CDLScan, 8.0% mention going unreachable. That figure describes those reviews, not drivers in general: carriers write after a bad run, so the share tells you what shows up once someone bothers to report it. Some of that slice sits next to an abandoned truck. A lot of it never becomes a report at all. Treating a quiet packet as a character reference is how you dispatch a load and then read the review.

A recruiter who has already pulled PSP, an MVR, and a Clearinghouse query can still be looking at a dull file. That is not a failure of those reports. It is what they were designed to do.

What those reports actually hold

PSP is a crash-and-inspection product. It gives you about five years of crash data and about three years of roadside inspections. If the driver put the truck into a wall and it was recorded, you may see it. If a trooper wrote a violation, you may see that too. Stopped answering, never answered, stopped responding, ignored calls — none of that is a roadside inspection. It is not a crash unless someone filed it as one.

An MVR is a state driving record. Tickets, suspensions, license actions. It is useful for the thing it is. It will not tell you that dispatch called for two days and the phone stayed dead.

The Clearinghouse holds drug and alcohol program events: positives, refusals, actual knowledge, return-to-duty status. A dead phone is not a test result. A clean query answers a real question. It does not answer whether the last desk could still reach them on a live load.

Previous-employer history — the DAC-style employment check, the safety-performance request — is the closest official place this should appear. Sometimes it does. Often it does not. The last carrier answers what they are required to answer, or they answer slowly, or they answer “eligible for rehire” with a blank where the story actually is. Going unreachable is usually treated as an employment mess, not as a filing. Nobody sends it to FMCSA. How we treat these shares is on the methodology page.

So a clean packet is not a lie. It is an incomplete sentence. The missing clause is what previous carriers bothered to write when they were no longer being polite.

Why the write-up stays off the page

The language in those reviews is the phone, not a code. Stopped answering. Answering phone. Answering calls. Stopped responding. Answer phone. Phone calls. Never answered. Calls messages. Calls texts. Answer calls. None of that maps onto a violation you can buy.

The companions in the same write-ups tell you why the official systems stay quiet so often. In 35.2% of unresponsive reviews the carrier also mentions an abandoned truck — so the dead phone and the walk-off are often one recovery, not two random insults. Drugs or alcohol sit in 17.8%. Paid travel with no arrival sits in 11.6%. Late or missed deliveries sit in 10.8%. A crash or damage sits in 10.3% — and that slice is the one most likely to leave a mark on PSP. The rest often will not. Aggression sits in 9.6%. A no-show sits in 8.7%. Those are operational facts. They live in dispatch notes and in the next recruiter’s phone call, not in a state record.

Stay away and waste your time are a different register. In 38.1% of these reviews the carrier also writes a verdict. That is heat at the end of the write-up, not a filing. Read whether the phone went dead.

The share of reviews mentioning going unreachable rose from 4.7% in 2018 to 9.6% in 2025. I stop that line at 2025. 2026 is still open. The problem climbed in what carriers write down. It still rarely becomes a filing. That is exactly the gap a clean packet hides.

I would not drop PSP because of this. I would stop treating a quiet PSP as proof the last desk could still reach them.

What was visible before you spent

The pattern I’d watch for is not a code on a report. It is a short stint, a hole between two carriers, and a previous desk that already used the same words: stopped answering, never answered, stopped responding, left the truck. Those words show up in carrier write-ups. They do not show up as “unreachable” on an MVR.

Ask the candidate to walk the last two exits without help. When did dispatch last reach them. What happened to the phone. What will the previous carrier say if you call. People who had a dead zone can usually name the stretch of road. People who went unreachable often skip the phone and jump to home time or a family reason.

Typical sequence, built from how these reviews cluster, not from one person’s file: the application is thin. References are slow. Official reports are dull. You dispatch a load. Answers get shorter. Then the language in the next review is stopped answering, abandoned truck, left the truck. That sequence does not generate a Clearinghouse hit.

The pairing with a no-show is in going unreachable and a no-show. The pairing with paid travel is in paid travel and going unreachable. The longer read on the category is in unresponsive driver reviews. The words carriers actually reach for are in how they write about going unreachable. The questions that pull this out of an application are in what to ask before going unreachable. Why the walk-off itself stays off PSP is in why official reports miss an abandoned truck.

What to do with a clean packet

Keep running the reports. They catch the class of problem they were built for. Then add the check they cannot do: what previous carriers already wrote about this name.

If the last carrier will only confirm dates, that is not a pass. It is a reason to read what other carriers put on the record when they were not filling out a form. Check the name on CDLScan before you dispatch a live load. It takes less than a minute.

A clean PSP means the filed crashes and inspections are clean. A dead phone on a live load is usually not filed. Those are different claims. Only one of them is in the packet you already buy.

I am not going to pretend this is an independent study. CDLScan is the source, and I write from the data they share. Going unreachable is common enough in what carriers bother to write down, and a quiet packet is not a substitute for reading that sentence.

Frequently asked questions

If PSP, MVR, and Clearinghouse are clean, is the driver safe to hire?

They are clean on the items those systems store. Going unreachable sits in 8.0% of the reviews carriers left on CDLScan, and that behavior is rarely filed. A quiet packet is necessary. It is not sufficient.

Is a DAC or previous-employer check enough?

It is the right official place to look, and it still misses a lot. Carriers answer slowly, narrowly, or not at all. The same desk that returns “eligible for rehire” will later write that they stopped answering.

Does a clean PSP mean they never went unreachable?

No. PSP holds recorded crashes and roadside inspections. A dead phone on a live load is usually an employment event. It becomes a PSP item only if someone also recorded a crash or a roadside violation.

Should I skip official reports and only read carrier reviews?

No. Reviews do not replace a license check, a crash history, or a Clearinghouse query. They cover the class of problem those reports were never built to hold.

What should I ask the previous carrier if they will not give a story?

Ask whether dispatch could still reach them, and when the phone went dead. If they will only confirm dates, go read what other carriers already wrote about the name.

Why do so many unresponsive write-ups never become a record?

Because nobody is required to file “they stopped answering” the way they file a crash or a positive test. The next employer only sees it if the last one bothers to say it.

Where do I look first if the packet is already clean?

The name, in what previous carriers wrote. Start on CDLScan, then call. Do not dispatch a live load first and look later.