Speeding Semis and Speed Limiter Data in Illinois Truck Crash Cases: What the ECM Records and How It Is Preserved

Were you hit by a semi that seemed to be moving far too fast for the road, the traffic, or the weather? The truck itself may hold the proof — and in a Chicago crash case, that proof can begin disappearing within days.

Most modern tractors carry an engine control module, or ECM, that manages the engine and records how the truck was driven. That same system holds the road speed governor setting, which shows the top speed the carrier allowed the truck to reach.

We understand that in the aftermath of a serious truck crash, the last thing you need is a technical fight over engine software. That said, speed data is often one of the clearest objective records of what happened, and it deserves attention early.

This post explains what a speed limiter and ECM record, how that data can show a carrier set a truck to run faster than conditions allowed, and how a preservation letter keeps it from being overwritten. It sits within our broader coverage of common causes of Chicago truck crashes.

A speed limiter — also called a road speed governor — is a programmable setting inside the ECM that caps how fast the engine will push the truck. The carrier or its maintenance vendor chooses the number, and it can usually be changed with the engine manufacturer's service software.

Keep in mind that the governor and the speed record are two different things. The governor sets a ceiling, while the ECM's event and trip records show how the truck actually moved beneath that ceiling.

Depending on the engine manufacturer and the software version, the data an ECM may hold includes but is not limited to:

• Governed road speed. The maximum vehicle speed programmed into the engine shows the ceiling the carrier allowed. A truck governed well above the posted limits on its regular routes tells a story about the carrier's priorities.
• Cruise control settings. The ECM may store the maximum cruise speed and whether cruise was engaged near the time of the crash. Cruise engaged in heavy Chicago traffic or poor weather can be significant on its own.
• Hard-brake and last-stop records. Many ECMs capture a short window of second-by-second data when the truck decelerates sharply or stops suddenly. These snapshots typically include road speed, brake application, throttle position, clutch status, and engine speed.
• Trip and life-of-engine summaries. These totals can include time spent over a set speed, average speed, and idle time. Over weeks or months, the summaries can reveal a pattern rather than a single bad moment.
• Diagnostic fault codes. Engine or sensor faults active before the crash are often logged alongside the speed data. Fault codes can also help answer a defense claim that the data is unreliable.

What's more, the ECM is rarely the only electronic witness on a commercial truck. Telematics platforms, forward-facing cameras, collision-mitigation systems, and the electronic logging device can each hold overlapping speed and location data, which is why speed evidence and ELD data preservation in Chicago truck cases usually go hand in hand.

Note that exact capabilities vary widely by make, model year, and configuration. A qualified download technician working from the actual module determines what a particular truck stored.

Speed cases often focus on the driver's foot on the pedal. However, governor settings and trip summaries can move the question up the chain to the motor carrier that configured the truck and built the schedule.

Federal regulations speak to both levels. Under 49 CFR 392.6, a motor carrier may not schedule a run, or permit or require a truck to operate between points, in a period of time that would require speeds greater than those prescribed by the jurisdictions it travels through.

In addition, 49 CFR 392.14 requires extreme caution when hazardous conditions such as snow, ice, fog, rain, or smoke adversely affect visibility or traction, including reducing speed. Illinois law runs in the same direction — 625 ILCS 5/11-601 bars driving at a speed greater than is reasonable and proper for the conditions, regardless of the posted limit.

Also be aware that federal speed limiter policy remains unsettled. FMCSA and NHTSA have proposed requiring speed limiters on heavy trucks, but to our knowledge no final federal rule mandates them, so the governor setting on a given truck reflects the carrier's own choice.

Here is how speed data can connect to those rules in a real case:

• A governor set above the roads the truck runs. If a truck spends most of its life on Chicago-area expressways and city streets but is governed well above those limits, the carrier made a choice it may have to explain. That choice matters most when combined with the other evidence below.
• Dispatch times that only work at high speed. Comparing pickup and delivery windows against route distance can expose a schedule that was achievable only by speeding. That comparison is the core of a 392.6 theory.
• Over-speed time in trip summaries. Repeated time logged above the posted limit over weeks of operation suggests a pattern the carrier could have seen in its own fleet reports. Many fleet systems flag over-speed events for safety managers, and those alerts can become discoverable records.
• Speed at the moment of the crash. The hard-brake record may show the truck traveling at or near its governed speed in a construction zone, in rain, or in stop-and-go traffic. That evidence speaks directly to the reasonable-and-proper standard under Illinois law.

Of course, a high governor setting alone does not prove that speed caused a crash. The legal question is causation — whether the speed made the crash happen or made the injuries worse — and answering it requires reconstruction, not assumption.

Speed also rarely acts alone. A rushed schedule frequently overlaps with driver fatigue and hours-of-service violations, and a carrier that tolerates speeding may also have gaps in its driver qualification files.

Physics explains why the stakes are so high. A fully loaded tractor-trailer can weigh up to 80,000 pounds under federal size and weight limits, and stopping distance grows sharply with speed — which is why excess speed so often turns a manageable situation into a jackknife crash or an underride collision.

ECM data is durable in one sense and fragile in another. The module survives most crashes, yet the specific records that matter can be lost through ordinary business decisions in the days that follow.

The most common ways speed evidence is lost include:

• Putting the truck back in service. Some event records are overwritten when the truck logs new hard-brake or stop events. A tractor that is repaired and dispatched within days may write over the crash snapshot.
• Repairs and module replacement. Body shops and dealers may replace or reflash a damaged ECM as part of routine repair work. Once the original module is swapped or reprogrammed, its stored records may be gone.
• Improper downloads. Powering up the module or connecting with the wrong software can change stored values or add new entries. A careless download can also give the defense an opening to challenge the data's integrity.
• Salvage and sale. A totaled tractor may be sold for parts or scrap. When the truck leaves the carrier's control, the evidence can leave with it.
• Telematics retention windows. Cloud-based fleet systems often keep detailed data only for a limited period under the vendor's settings. After that window closes, granular speed data may be purged automatically.

Remember that federal record-retention rules do not reach all of this evidence. For instance, 49 CFR 395.8(k) requires carriers to keep records of duty status and supporting documents for six months, but we are aware of no federal rule that specifically requires a carrier to hold ECM event data for a set period after a crash.

This is why timing matters so much. Our guide to the first 72 hours after a semi crash walks through the steps that protect evidence while you focus on recovery.

A preservation letter — sometimes called a spoliation letter or litigation hold notice — is a written demand that tells the carrier, and often its insurer and maintenance vendors, to preserve specific evidence. It puts them on formal notice that litigation is reasonably anticipated.

In Illinois, that notice carries weight. In Boyd v. Travelers Insurance Co., 166 Ill. 2d 188 (1995), the Illinois Supreme Court recognized that a duty to preserve evidence can arise from an agreement, a contract, a statute, a special circumstance, or a voluntary undertaking, and that negligently losing evidence a party should have kept can create liability.

Moreover, Illinois courts can impose sanctions under Illinois Supreme Court Rule 219(c) when a party fails to comply with discovery obligations. Juries may also receive Illinois Pattern Jury Instruction 5.01, which can allow an adverse inference against a party that failed to produce evidence under its control, though that remedy depends heavily on the facts and is never automatic.

An effective preservation letter for speed evidence is specific. A strong letter typically asks the carrier to preserve, among other items:

• The tractor and its ECM in post-crash condition. The letter asks that the truck not be repaired, reflashed, sold, or returned to service until a joint download occurs. Where that is impractical, it asks that repairs wait until the data is captured.
• All engine and powertrain modules. Some trucks store speed-related data in more than one module, including brake and collision-mitigation controllers. Naming them all prevents a narrow reading of the request.
• Governor and parameter history. The request covers the current programmed settings plus any records of when and by whom those settings were changed. A change shortly before or after the crash can matter as much as the number itself.
• Telematics, camera, and ELD data. The letter seeks fleet platform exports, dashcam video, and logging-device records for the trip and a reasonable period before it. Suspending automatic deletion is the critical request here.
• Dispatch and scheduling records. Load assignments, delivery appointments, and driver communications for the trip belong on the list. These records turn a speed reading into a carrier-level 392.6 question.
• Fleet speed policies and over-speed reports. Written speed policies, safety-manager alerts, and any discipline tied to speeding round out the request. These documents show what the carrier knew before your crash.

Once the letter goes out, the next step is usually a coordinated download. Both sides' experts attend, a qualified technician images the module with the manufacturer's software, and the raw files and reports are shared so neither side can later claim the data was altered.

Keep in mind that a carrier may refuse to cooperate even after receiving a letter. In that situation, an attorney may ask the court for a preservation or protective order, which is another reason to involve counsel early.

Speed data works best as the anchor of a reconstruction that ties together scene measurements, vehicle damage, witness accounts, video, and physical evidence on the roadway. On its own, a number from a module invites argument; matched to the scene, it becomes far harder to dispute.

For instance, an accident reconstructionist can compare the ECM's recorded speed with tire marks, crush profiles, and dashcam timing to confirm the data is consistent with the physical scene. When those sources agree, the speed record carries real weight with an adjuster or a jury.

On Chicago-area expressways, where traffic can shift from free-flow to a standstill within a short distance, that analysis often centers on whether the driver adjusted speed to the conditions ahead. Heavy truck corridors such as those discussed in our post on Tri-State Tollway truck crashes show how quickly a too-fast approach can become a rear-end or multi-vehicle collision.

What's more, speed evidence can affect both who is responsible and how much the claim is worth. Proof that a carrier configured or scheduled a truck to run too fast can support direct negligence claims against the company, and documented speeding can shape how a case is valued — topics we cover in our guide to Illinois truck accident settlement value.

Illinois also applies modified comparative fault under 735 ILCS 5/2-1116, which bars recovery if the injured person is more than 50% at fault and otherwise reduces damages by that person's share. Objective speed data from the truck can be a strong answer when the defense tries to shift blame to the injured driver.

Finally, keep the filing deadline in mind. Most Illinois personal injury claims must be filed within two years under 735 ILCS 5/13-202, but electronic speed evidence can be lost in days or weeks, so the practical deadline for protecting your case arrives much sooner.

We understand that a truck crash can turn your world upside down in a split second, and that your focus belongs on healing and on your family. While nothing can undo what happened, you may be entitled to compensation for medical bills, lost wages, and pain and suffering — and preserving the truck's speed data early can make that claim stronger.

Our team moves quickly to send preservation letters, coordinate ECM downloads, and work with reconstruction experts who know how to read governor settings and event records. Do you think a speeding semi caused your crash or a loved one's injuries?

We welcome the opportunity to review your situation and help you determine the next steps. Free consultation. No fee unless we recover.

This article is for informational purposes and does not constitute legal advice. Consult a qualified attorney in your jurisdiction about your specific situation.