When a crash happens on Loop 1604, I-10, I-35, or 281 in Bexar County, liability—who is at fault—drives everything. Insurers make fast decisions using the Texas Peace Officer’s Crash Report (CR-3) and its legend, the TxDOT Crash Report Code Sheet (CR-3CS). That code sheet turns short numbers and letters into key facts about who did what, when, and why.
This plain-English guide shows how an expert reads the Code Sheet with one goal: prove the other driver (or company) is responsible—and protect the value of your claim.
Liability 101: What has to be proven?
To win in Texas, you must show the other party breached a duty (drove unreasonably) and caused your injuries and damages. The CR-3 report and Code Sheet help tell that story with five buckets of proof:
- Contributing Factors/Conditions (officer’s fault codes)
- Sequence of Events (what happened first, second, third)
- Point of Impact & Damage Location (where the vehicles hit)
- Right-of-Way/Traffic Controls (signals, stop signs, yield signs)
- Special CMV (18-wheeler) Fields (carrier info, vehicle type)
When these fields line up with photos, video, and your injuries, liability becomes clear—and the insurer loses wiggle room.
The Five Code Groups That Prove Fault
1) Contributing Factors: The Officer’s “Why It Happened”
This is the fault engine of the CR-3. Examples include Failed to Yield, Disregarded Stop Sign/Signal, Speeding, Followed Too Closely, Unsafe Lane Change, Backing Without Safety, Driver Inattention, or Fatigued/Asleep.
How it proves liability: These codes are the officer’s shorthand for negligence. If multiple codes appear (for example, Followed Too Closely + Driver Inattention), they can support comparative fault arguments that put most or all blame on the other driver.
Tip: If the code doesn’t match the scene or video, it should be challenged with photos, witness statements, and vehicle telematics.
2) Sequence of Events: The “Order of Impacts” Timeline
This field records the crash chain—rear-end then pushed into another car, side-swipe then fixed object, rollover after roadway departure, and so on.
How it proves liability: “First harmful event” is powerful. Example: A distracted driver rear-ends you at the Alamo Ranch/1604–151 interchange, and you are shoved into the car in front. If the sequence is captured properly, it helps block a defense claiming you hit the front car first.
3) Point of Impact (POI) & Damage Location: Where the Truth Shows
CR-3 diagrams and codes mark front, rear, left, right damage and initial vs. subsequent impact points.
How it proves liability: A clean rear POI on your bumper plus the other driver’s front POI is classic rear-end fault evidence. With lane-change sideswipes on 410 or 281, lateral scrape patterns and mirror damage can confirm unsafe lane change or failure to maintain lane.
4) Right-of-Way & Traffic Controls: The Rules of the Road
Codes show whether a driver ran a red, ignored a stop sign, or failed to yield while turning left across traffic on Bandera, Culebra, or Blanco.
How it proves liability: These codes tie fault to an official traffic control. If the officer marks Disregarded Traffic Signal and the signal timing data (or nearby business video) supports it, liability becomes hard to fight.
5) Commercial Motor Vehicles (18-Wheelers & Delivery Trucks): Extra Levers
For 18-wheelers on I-35 or company vans on I-10, the Code Sheet triggers extra CMV fields: Vehicle Type (e.g., tractor/semi-trailer), Cargo Body, Hazmat, Carrier/US DOT, and more.
How it proves liability: CMV flags unlock federal safety rules and company policies (hours-of-service, driver qualification, maintenance, ELD/telematics). If a tractor-trailer coded “vehicle in transport” also shows fatigue or improper following distance, you can press the carrier for logs, dash-cam, and event-data recorder (EDR) downloads that clinch fault.
Quick Table: Which Codes Move the Needle on Fault?
| What you’re checking | What the code shows | Why it matters for liability |
|---|---|---|
| Contributing Factors | Specific fault (e.g., Failed to Yield, Drove Fatigued, Inattention) | Officer’s “negligence” shorthand; anchor for fault arguments. |
| Sequence of Events | First and later impacts | Fixes who caused the chain reaction; valuable for multi-car wrecks. |
| Point of Impact | Where each car was hit | Confirms rear-end, side-swipe, or unsafe lane change mechanics. |
| Traffic Controls | Signal/stop/yield compliance | Converts “he said, she said” into rule-of-the-road proof. |
| CMV Fields | Truck type, carrier, cargo | Opens corporate safety evidence and spoliation leverage. |
How an Expert Uses the Code Sheet Step-by-Step
Step 1: Pull the CR-3 and Code Sheet together.
Keep both on screen. Match every number/letter on the CR-3 to its meaning on the Code Sheet so nothing gets missed.
Step 2: Start with “Contributing Factors.”
Ask: Does the factor match the scene? If the report says Failed to Yield but your light was green, flag it. Time-sync nearby camera video or phone geo-data to show signal phase and speed.
Step 3: Lock the “Sequence of Events.”
Was your rear-end the first harmful event, or did someone sideswipe you first and push you into another lane? That order decides who started the chain and who pays.
Step 4: Map damage to impact.
Walk around photos. Do bumper heights, scrape angles, and broken lens debris match the diagram? If the coding is backward, ask the agency for a supplement with your proof.
Step 5: If a truck is involved, escalate early.
Use the CMV codes to send spoliation letters for ELD data, dash-cam, Qualcomm/telematics, and maintenance. These records can end fault fights fast.
Common Coding Issues That Can Hurt Liability (and How to Fix Them)
- Wrong “Contributing Factor.” Solution: Provide video, scene photos, and witness statements that fit the correct code (e.g., Unsafe Lane Change instead of Failed to Yield).
- Missing secondary impact in “Sequence of Events.” Solution: Ask for an amendment to add the secondary hit that explains your path and injuries.
- Point of Impact flipped. Solution: Use repair estimates, OEM photos, or bumper energy absorbers to prove actual contact points.
- CMV not flagged. Solution: If you see a tractor-trailer or branded delivery van, ask the officer or agency about CMV fields; they trigger carrier data you’ll need.
Why this expert recommends Ryan Orsatti Law to prove fault in San Antonio and across I-35/I-10
- Direct attorney access & personal attention. Clients talk to the lawyer leading the case—not a call center. That means faster corrections to reports and smarter evidence requests.
- Local road knowledge. The team knows 1604/151, 281/Loop 410, and the I-35 corridor patterns (merges, construction zones, crash hot spots), which helps read Sequence of Events and POI codes the right way.
- 5.0-star reputation with real results. Clients regularly say the firm “kept me updated,” “treated me like family,” and “got me the max.” Helen and Gabriel are often named for quick communication and follow-through—key when you need a report fixed now, not later.
- Trucking playbook when CMV codes appear. The firm moves on ELD/black-box pulls, dash-cam, and carrier safety files before data is overwritten—vital for liability on 18-wheeler wrecks.
Recent client voices (San Antonio, 5★):
- “Ryan, Gabriel, and Helen were amazing… they got me the max and answered every question.”
- “They stayed in communication the entire time and handled everything so I could heal.”
DIY Liability Checklist (10 Minutes)
- Circle the Contributing Factor(s). Do they match the story and photos?
- Underline the “First Harmful Event.” Does the order make sense?
- Mark Point of Impact on both vehicles—rear vs. front, or left vs. right.
- Note any Traffic Control (signal, stop, yield) and who had the right-of-way.
- Look for CMV flags. If present, write down the USDOT/TxDMV numbers and carrier name right away.
If anything doesn’t line up, you may have a liability fix that can raise your settlement value.
Helpful resources
- Authoritative outbound reference: TxDOT Crash Report Code Sheet (CR-3CS) – official definitions for every CR-3 code (injury, factors, sequence, CMV fields, and more).
https://ftp.txdot.gov/pub/txdot-info/trf/crash_notifications/2023/code-sheet.pdf - Internal links (learn more on our site):
• Contact Ryan Orsatti Law (24/7): https://ryanorsattilaw.com/contact-us/
• Truck & 18-Wheeler Crashes: https://ryanorsattilaw.com/truck-accidents/
• Brain & Serious Injury Guide: https://ryanorsattilaw.com/whos-the-best-traumatic-brain-injury-lawyer-in-san-antonio/
Free Liability Review Today (San Antonio & I-35 Corridor)
If your report’s Contributing Factors, Sequence of Events, or Point of Impact look off—or you want a second opinion before the adjuster calls—get a fast, focused review.
Ryan Orsatti Law
4634 De Zavala Rd, San Antonio, TX 78249
Call/Text: 210-525-1200
5.0-star reviews. Direct attorney access. Personal attention. We serve clients across San Antonio, Alamo Ranch, Stone Oak, New Braunfels, Seguin, and the I-35/I-10 corridors.
Texas Bar Advertising Disclaimers: This post is for information only and not legal advice. Past results (including “got me the max”) do not guarantee future outcomes. Every case is different. Principal office: San Antonio, Texas.