A crash mention often sits with logbook and hours trouble

When a previous carrier writes about a crash or damage, the useful next question is not only whether a claim was filed. It is whether the same write-up also talks about a log book, a disconnected ELD, or hours of service. Those two sit together more often than chance. Treat the pairing as one screen before you put someone in a truck, not as two unrelated complaints.

Among the reviews carriers left on CDLScan, 13.7% mention a crash or damage. 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.

Inside that slice, 7.1% also mention logbook and hours problems. Read the denominator before you use the number. It is 7.1% of crash-or-damage reviews, not 7.1% of all reviews, and not 7.1% of logbook reviews. Flip the pair and the share changes: 21.3% of logbook-and-hours reviews also mention a crash or damage. Same overlap, two bases.

That pairing is not random. Logbook and hours problems are 4.6% of all reviews. If a crash mention and a logbook mention showed up together only by chance, you would expect about 4.6% of crash-or-damage reviews to also mention logs. The observed share is 7.1% — about 1.55 times the chance rate. Lift is that multiplier. It is not a probability that the next person you hire will damage a truck and then disconnect the ELD.

Damage, then the logs

The write-ups talk about a damaged truck, a damaged trailer, damaged equipment, a truck trailer, a brand new truck that did not stay that way, an abandoned truck, a left truck, a truck stop, a loaded trailer, always late, went home, home time. On the hours side they talk about a log book, a disconnected ELD, an ELD device, hos rules, how to use the ELD, sometimes a cash advance in the same week. That is the incident register.

Stay away and waste your time are a different register. Those are the author’s recommendation to the next recruiter, not a description of what the driver did. In 32.7% of crash-or-damage reviews the carrier also writes a verdict. In 32.7% of logbook reviews they do the same. That is a fact about how these reviews end, not a fact about the driver. Read the scene. Do not hire off the temperature of the last sentence.

From the crash side, the louder companions dwarf this pair. An abandoned truck sits in 36.7% of crash-or-damage reviews. Aggression or threats sit in 17.2%. Late or missed deliveries sit in 14.2%. Theft sits in 8.8%. Going unreachable sits in 6.0%. A loaded trailer sits in 5.5%. Logbook and hours problems are not the most common companion. They are the one that turns a damage complaint into an hours-and-inspection problem.

From the other side, 36.2% of logbook reviews also mention an abandoned truck. Aggression sits in 22.3%. Late deliveries sit in 17.6%. Theft sits in 15.3%. Always name which base you are standing on.

I keep the logs next to the crash because the packet you already buy is built for recorded crashes and roadside inspections, not for the hours complaint that never became a filing. A crash can leak into PSP if someone actually reported it. A disconnected ELD often cannot, unless an inspection caught it. The logbook trend itself is in logbook mentions that are falling, not gone. The missing-card pairing next to logs is in logbook trouble next to equipment that never returns. Late loads next to hours is a separate pairing; that is late deliveries and logbook hours.

The share of reviews mentioning a crash or damage ran 14.0% in 2018, 12.5% in 2019, 13.3% in 2020, 12.1% in 2021, 12.3% in 2022, 13.1% in 2023, 13.5% in 2024, and 15.1% in 2025. I stop that line at 2025. 2026 is still open. The completed series is slightly up, not a spike. Logbook-and-hours mentions ran 5.0% in 2018, then 3.7% in 2025. How these shares are counted is on the methodology page. Compare percentages inside each year, not year totals.

What the pairing is not

It is not proof that every crash mention is a logbook problem. Most crash-or-damage reviews do not also mention hours. 7.1% is a heavy overlap relative to chance, not a majority.

It is also not a CSA score by itself. Crash or damage in these write-ups is an employment complaint: damaged truck, damaged trailer, damaged equipment. A recorded crash can sit next to them, and that part can show up if it was filed. The log book that was disconnected usually cannot.

I would not read the last sentence of these reviews as the finding. Carriers reach for stay away. That is their recommendation to the next desk, not a category of behavior.

Why the packet you already buy stays quiet

PSP, an MVR, and the Clearinghouse hold what someone filed: a roadside inspection, a recorded crash, a failed test, a license action. A crash can leak into that packet if someone actually reported it. A disconnected ELD, a log book that looks wrong, hos rules the last desk could not get the driver to follow — those are employment complaints. They are not a query result unless an inspector wrote them down.

Previous-employer forms are not much better. Eligible for rehire can come back blank while the same desk will later write that the driver damaged a truck and disconnected the ELD. The behavior lives in carrier-to-carrier memory. Most of that memory never becomes a query result.

A clean packet on Monday morning does not tell you whether Friday’s unit came back with a dent and a log that does not match the trip. Those are different claims.

I am not going to pretend this is an independent study. CDLScan is the source, and I write from the data they share. Crash mentions are common enough in what carriers bother to write down, a logbook mention rides along above chance, and the packet you already run is designed for the filing, not for the hours complaint sitting next to it.

What was visible before you handed over the keys

The pattern I’d watch for is a previous carrier who already used damaged truck, damaged trailer, log book, disconnected ELD, or hos rules, plus a hole between two recent jobs. Those words are not a violation code. They are a reason to look the name up before you issue a unit.

Typical sequence, built from how these reviews cluster, not from one person’s file: they start. The truck takes a hit, or the trailer does. The logs look wrong, or the ELD gets disconnected. Then they go home, or they leave the truck, or they stop answering. Sometimes always late sits in the same week. People who left cleanly can usually tell you where the unit is and whether the damage was reported. People who are about to walk often skip the report and jump to home time.

None of that is a reason to treat every crash mention as an hours falsification. It is a reason to run the name before you issue either.

Aggression next to hours is a separate pairing; that is aggression and logbook hours. Theft next to hours is another; that is theft and logbook hours. Do not collapse them into one crash story.

What to do before you issue the unit

Look the name up in what previous carriers already wrote. If you see a crash or damage and a logbook problem in the same history, treat the first week as a supervised start, not as a full issue of keys and a solo dispatch.

Ask how they ran logs at the last carrier, whether any damage was reported, and what that desk will say about the unit. Then make the call. Five open questions beat a rehire box.

If you already issued a truck, freeze the next dispatch until someone has looked. Check the name on CDLScan first. It takes less than a minute, and it is where that pairing actually sits.

Frequently asked questions

Does 7.1% mean a crash mention usually comes with a logbook problem?

No. 7.1% is the share of crash-or-damage reviews that also mention logbook and hours problems, among reviews carriers left on CDLScan. Most crash write-ups do not include that companion. The pairing is above chance. It is not a majority.

Why is the other share 21.3%?

Because the base changed. 21.3% of logbook-and-hours reviews also mention a crash or damage. Same overlap, counted from the other side. Always name the denominator.

What does lift 1.55 mean here?

Logbook and hours problems are 4.6% of all reviews. Seeing them in 7.1% of crash-or-damage reviews is about 1.55 times the chance rate. Lift is that multiplier, not the odds on your next hire.

Will PSP or an MVR warn me?

Sometimes about the crash, if something was filed. Not about the logs, unless an inspection caught them. Those reports hold inspections, recorded crashes, and license events. A disconnected ELD that never became a filing is usually not there.

Is this the same problem as an abandoned truck?

Nearby, not the same. An abandoned truck sits in 36.7% of crash-or-damage reviews and in 36.2% of logbook reviews. Screen the walk-off separately. This pair is damage plus hours.

What should I ask before I issue a unit?

How they ran logs at the last carrier, whether any damage was reported, and what that desk will say about the truck. Then read the write-ups.

Where do I check the name?

On CDLScan, before you issue the unit. Previous carriers already wrote this pairing down. You should read it while the truck is still yours.