Skip to main content
TruckCodex
Hubs

Crash Record TX6IEAHQE19L

FMCSA crash record in SAN ANTONIO on Jan 1, 2023.

Injury Federal Recordable

What happened

On January 1, 2023, FMCSA recorded an injury crash with one person hurt in SAN ANTONIO, Texas. The vehicle was operated by INGRAM READYMIX INC (USDOT 627215). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference TX6IEAHQE19L.

Carrier pattern note

This is the carrier's 29 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.

Geographic note

This crash is part of an active corridor: 1206 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
INGRAM READYMIX INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
29
15 injury · 25 tow-away
Crashes per 100 power units (24 mo)
2.0
12 crashes · 600 units
Days since prior carrier crash
17
Last on Dec 15, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,853 carriers

Geographic context

How this crash sits in its setting.

Within SAN ANTONIO, Texas, 1,206 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
TX6IEAHQE19L
Date:
Jan 1, 2023
Time:
1030
State:
Texas
City:
SAN ANTONIO
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
INGRAM READYMIX INC (627215)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 6 7 1HTESTZT2MH250669 PLX7224 (TX) INGRAM READYMIX INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5072216 Nov 21, 2025 TX Tow-Away 0 0
cr_5028814 Sep 2, 2025 TX Tow-Away 0 0
cr_5010781 Jun 16, 2025 TX Tow-Away 0 0
cr_5010036 Jun 13, 2025 TX Injury 0 1
cr_4931423 Apr 11, 2025 TX Tow-Away 0 0
cr_4907429 Mar 5, 2025 TX Tow-Away 0 0
cr_4903440 Feb 26, 2025 TX Tow-Away 0 0
cr_4901139 Feb 21, 2025 TX Tow-Away 0 0
cr_4889625 Jan 31, 2025 TX Injury 0 1
cr_4862075 Dec 10, 2024 TX Tow-Away 0 0

Related records

Carrier
INGRAM READYMIX INC
USDOT 627215 · 364 crashes · 431 inspections
Vehicle
VIN: 1HTESTZT2MH250669
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
City
Crashes in SAN ANTONIO, TX
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.