Leer este parte en español →

A truck that strikes the back of stopped traffic without slowing is not a case about braking too late. It is a case about a truck that never slowed. In a case like that the question is what the driver was doing in the last ten seconds, and for a while the answer is written down: in the truck, in the company’s files, and sometimes in a stranger’s camera.

The pattern. Traffic on a highway backs up behind something no one at the end of the line can see: a crash, a lane closure, a slowdown. A tractor-trailer comes up on the back of the line at highway speed and strikes it without slowing. Federal law lets a truck on the interstate weigh up to eighty thousand pounds, and when a truck that heavy meets a car, the car takes almost all of the change in speed (Nineteen to One; Delta-V). This page names no one and decides nothing about any crash.

What the Board found once. In a crash the National Transportation Safety Board investigated on an Ohio interstate in 2023, a truck-tractor combination came up on a line of traffic left by an earlier minor crash. The Board found that it “did not slow and crashed into the rear of the traffic queue.” It was traveling “about 72 mph,” and the four vehicles ahead of it were moving “between 3 and 15 mph.” There were “no tire friction marks in advance of the area of initial contact.” Six people died, and more than 40 were hurt. The Board’s report summed up the driver in one sentence: his “lack of evasive action was consistent with being inattentive to the forward roadway, but the reason for his inattention was unknown” (NTSB, Highway Investigation Report HIR-25-05). The Board found “no indication that the driver was fatigued.” His phone records showed he “was not using native calling or regular text messages at the time of the crash,” and the Board could not determine whether data activity on the phone “indicated active use of the cell phone by the driver.” The truck’s control modules, the report says, “were consumed by the postcrash fire and no data could be downloaded.” Unknown is the hardest word in a case like this, and the reason the record matters.

The reach and the stop. At seventy miles an hour a truck covers about a hundred and three feet every second, so a driver who looks away for three seconds travels a little more than the length of a football field, goal line to goal line, with no one watching the road. Then the stopping begins. The commercial driver’s manual adds the driver’s perception and reaction and the half second or more an air brake needs to the braking itself, and puts the total stopping distance at fifty-five miles an hour, for an average driver with good brakes and good traction, at “over 450 feet” (The Air Brake).

What the rules say. Texas asks the same thing of every driver following another vehicle: keep “an assured clear distance” so that the driver “can safely stop without colliding with the preceding vehicle” (Transportation Code Section 545.062). Federal rules add lines about screens for the driver of a commercial truck. “No driver shall engage in texting while driving” (49 CFR 392.80), and texting is defined to include “reading text from” an electronic device as well as typing into one, and a request to open a web page, though not reading a navigation screen (49 CFR 383.5). “No driver shall use a hand-held mobile telephone while driving” a commercial vehicle (49 CFR 392.82), and under both rules the company may not “allow or require” it. A rule written for the age of television still requires a screen for receiving a television broadcast, if it is in the same compartment as the driver, to sit “to the rear of the back of the driver’s seat,” placed so as “not to be visible to the driver” while driving (49 CFR 393.88). And the electronic logging device can be a portable one, which the company must make sure is “mounted in a fixed position” and “visible to the driver” (49 CFR 395.22(g)). So the rules want one screen in the driver’s view, keep a television screen out of it, and forbid texting or a hand-held phone while driving. What the driver was looking at is a question of fact, and most of the facts are electronic. A broken rule is evidence of the standard of care, not a verdict by itself (Negligence Per Se).

The record. Some of it is in the vehicle. An engine controller can keep event records: one described in a federal crash investigation, on a motorcoach, stores a “Last Stop” record with “one minute and 45 seconds of data prior to” the stop, and a “Hard Brake” record when the wheel speed “decelerates at a rate greater than 7 MPH per second.” In that same crash, between a truck and a motorcoach, fire destroyed that controller, and “no event data was recovered”; the truck’s own engine controller was so damaged by fire that “no data could be recovered” (NTSB, Electronic Control Modules factual report). The electronic log keeps the hours (Logbook). A dash camera, where there is one, keeps the road; in the Ohio crash, the Board relied on video from a vehicle traveling behind the truck. The phone keeps its own record (The Phone). And the company’s files run on clocks of their own. The driver’s records of duty status must be kept “for six months from the date of receipt” (FMCSA). The accident register must be kept “for 3 years after the date of each accident,” but the rule asks it to list only the basics: the date, the place, the driver, the number of injuries and deaths, and whether hazardous materials were released, with copies of the accident reports that governments or insurers require. The second-by-second record is not on that list (49 CFR 390.15).

Logbook said the record is the first thing to preserve because it is the first thing that disappears. Here part of the record may be a minute and three quarters inside an engine controller, part is on a device mounted where the driver could see it, and part is in the company’s files on a six-month clock. The letter that asks the company to keep all of it is not a formality. It is the first act of the case, and it is a race (Spoliation).

Sources. The pattern, with no news report linked: the Board’s closed investigation of the November 14, 2023 crash on Interstate 70 near Etna, Ohio, National Transportation Safety Board, Highway Investigation Report HIR-25-05 (September 2025) and the Board’s press release; the engine controller records as described in NTSB, Electronic Control Modules, Specialist’s Factual Report (October 29, 2014). The rules: Tex. Transp. Code § 545.062 (subsection (a)), as posted on FindLaw; 49 CFR § 392.80, § 392.82, § 393.88, § 395.22 (paragraph (g)) and § 390.15 (paragraph (b)), as posted by Cornell LII; 49 CFR § 383.5 (the definition of texting), on eCFR; FMCSA, How long must motor carriers retain records of duty status (RODS) and supporting documents?. The stopping figures are from the commercial driver’s manual as quoted and linked in The Air Brake; the weight limit is from the federal statute as quoted and linked in Nineteen to One. The arithmetic: seventy miles an hour is about 102.7 feet a second, and three seconds is about 308 feet. Text and figures as published at publication.

Dispatch is the Night Docket’s news strand: what happened on Texas roads and in Texas courts, reported from credible outlets and agency releases, with no names and no conclusions about open investigations, then connected to the entries that explain the science and the law. General information, not legal advice.