A plaintiff’s investigator is standing in a tow yard with a laptop, a Nexiq cable, and a preservation letter that went out to the carrier the same afternoon of the crash. Before anyone talks about black ice, cell records, or the driver’s logbook, one number comes off that truck’s engine computer: the top speed the fleet configured it to run. Whatever that number is, it’s the opening move in the case.
The federal push to force that number down into the 60s has, for the moment, collapsed. The way courts, insurers, and reconstructionists treat the setting has not. Whether a carrier capped a truck at 65, at 75, or left it wide open is a decision the ECU remembers, and it’s one of the first things a serious truck accident lawyer asks about after a fatal wreck.
The Federal Mandate That Isn’t Coming
A federal speed cap on heavy trucks looked inevitable for nearly a decade, and much of the industry planned around it. But in a Federal Register notice issued July 24, 2025, FMCSA and NHTSA formally withdrew both the 2016 joint proposal and the 2022 supplemental notice that together would have required trucks over 26,000 pounds to be governed somewhere between 60 and 68 miles per hour.
The withdrawal doesn’t undo anything a carrier has already done to its own fleet. The choice stays with the carrier. Some run their trucks at 62 for fuel economy. Some run at 70 with adaptive cruise and automatic emergency braking layered on top. Some don’t cap at all. Each of those choices is now either a defensible position or a target, depending on what happens next.
The ECU Remembers What the Driver Won’t
Modern heavy-truck engine control modules keep a rolling record of what the truck was doing: second-by-second road speed, engine RPM, throttle position, brake switch state, cruise engagement, and hard-braking snapshots when a threshold event trips.
The maximum vehicle speed parameter sits right next to that event data. It tells the reconstructionist two things at once: what the truck was physically capable of doing in the seconds before impact, and what the carrier decided was acceptable behavior for that unit. Those are separate questions, and juries hear them as separate answers.
Four Configurations Produce Four Different Cases
The setting itself doesn’t win or lose a case. It frames the argument each side has to make. A few common configurations, and where each one lands:
- Capped at 65 with AEB and adaptive cruise. A common configuration among safety-conscious large fleets, and it plays well to a jury. The carrier can show it voluntarily gave up top-end speed and layered on crash-avoidance tech. The plaintiff still has plenty to work with on following distance and driver attention, but the speed narrative is largely defused.
- Capped at 68, no driver-assist stack. A middle ground that looks reasonable on paper and worse under cross-examination. If the truck was governed but the fleet skipped the sensors that prevent rear-end crashes, the plaintiff’s expert will spend a long time on why the carrier picked the cheaper half of the safety package.
- Capped at 75 to match posted limits. Legal in the states that allow it and consistent with the argument that a truck moving with traffic is safer than one holding up a lane. It also means the ECU shows the fleet knowingly authorized speeds well above the range federal regulators once contemplated, and that framing tends to travel with the jury.
- No governor at all. Rare on line-haul fleets, common on smaller operations and owner-operators. The defense is that the driver, not the truck, controls the speed. But the ECU still logs how fast the truck was actually driven, and a pattern of runs above the posted limit turns the missing cap into an inference about the whole safety culture.
Preserve the Data or Lose the Case
ECU data is not permanent. Trip records roll over, hard-brake snapshots get overwritten as new events occur, and a truck that goes back into service can lose the relevant window within days. That’s why plaintiff firms send preservation letters within 24 to 48 hours of a serious crash, naming the ECM download, the ELD file, telematics feeds, and dispatch messages by category. Carriers that ignore those letters risk adverse-inference instructions, monetary sanctions, and in the worst cases a default on liability.
For families on the other side of a crash, the practical takeaway is short. Do not wait for the police report. Get counsel involved fast enough that the letter goes out while the truck is still in the yard and the module still holds the seconds that matter.
The Configuration File Is Now a Policy Statement
Crash reconstruction used to lean on skid marks, crush profiles, and whatever the driver was willing to say. The engine computer changed that.
Once a carrier’s own hardware can testify to what the truck was allowed to do and what it actually did, the configuration file stops being an IT setting and becomes a policy statement. The federal government decided not to make that decision for the industry. The industry now gets to explain each unit’s number, one crash at a time.
