If your Texas crash report shows Code 22: Failed to Control Speed, the reporting officer is saying a driver didn’t slow or stop in time to avoid a collision. That single code can be a powerful liability anchor in a personal-injury claim—especially in rear-end, chain-reaction, and wet-road crashes. Below, I’ll translate Code 22 into plain English, connect it to Texas law, and show how we use it to win cases for injured clients across San Antonio and the I-35/I-10 corridors.


Quick Take


What “Failed to Control Speed” Actually Covers

On the Texas Peace Officer’s Crash Report (CR-3), Contributing Factor Code 22 = Failed to Control Speed. Officers use it when a driver should have reduced speed to avoid a known or foreseeable hazard—slowed traffic, stopped vehicles, congestion, weather, or a changing light. (Texas Department of Transportation FTP)

This isn’t only “speeding over the limit.” A driver can be under the posted limit and still be too fast for rain, glare, construction, or heavy braking ahead. Texas law codifies that duty:

Bottom line: Code 22 + the statutory duty to drive “reasonable and prudent” gives you a strong framework for proving fault.


How We Prove Code 22 in Real Cases

To turn a crash code into a winning claim, we build a layered evidence file:

  1. CR-3 & Code Sheet
    We obtain the official CR-3 and the TxDOT code sheet that defines Code 22. We cross-check officer narrative, diagrams, and contributing factors for internal consistency. (Texas Department of Transportation FTP)
  2. Scene & Conditions
    • Photos/video: intersection lines, sightlines, sun angle, signage, surface conditions.
    • Weather & lighting: we correlate to time of day and precipitation.
    • Traffic pattern: construction zones, lane closures, prior slow-downs.
  3. Vehicle & Driver Data
    • ECM/EDR (“black box”) download for speed/braking.
    • Dash-cam / telematics (personal, fleet, or rideshare).
    • Phone records to rule in/out distraction.
  4. Physics & Stopping Distance
    Stopping distance balloons with speed and road condition. We use accepted formulas and, if needed, an accident-reconstruction expert to model whether a reasonable driver would have stopped in time.
  5. Comparators
    If surrounding traffic slowed safely but the at-fault driver didn’t, that contrast supports the Code 22 finding.

Common Code 22 Scenarios We See in San Antonio


Liability: How Code 22 Supports Negligence

In Texas, a traffic-law violation is strong evidence of negligence. With Code 22 and §545.351/§545.352, we argue:

When facts show gross negligence (egregious speeding, repeat violations, impairment), we preserve a punitive-damages claim.


Insurance Adjuster Playbook (and How We Counter)


Your Claim Checklist (Save or Screenshot)


Damages We Pursue in Code 22 Cases


FAQ

Is Code 22 the same as “speeding”?
Not exactly. Speeding over the posted limit is addressed by §545.352; Code 22 often captures being too fast for conditions even below the limit. Both support negligence; conditions govern. (Justia)

Can Code 22 apply in a multi-car pileup?
Yes. We analyze timing, inter-vehicle gaps, and braking data to locate the first negligent actor and any following drivers who also failed to control speed.

What if the officer didn’t mark Code 22?
We can still prove negligence under §545.351 using evidence that a prudent driver would have slowed sooner. The absence of a code isn’t the end of your claim. (Texas Statutes)


Why Choose Ryan Orsatti Law for Code 22 Crashes?


Helpful Resources


Next Steps: Free Case Review

If your crash report shows Code 22, call us before you talk to the insurer. We’ll secure the evidence, protect your medical recovery, and maximize your claim.

Ryan Orsatti Law
4634 De Zavala Road, San Antonio, TX 78249
Phone: 210-525-1200

Get started today: We handle car18-wheelerrideshare, and delivery-truck crashes throughout San Antonio and the I-35/I-10 corridors.