Skip to main content
TruckCodex
Hubs

Crash Record TX68GEHQE1A7

FMCSA crash record in LANCASTER on Jan 31, 2022.

Injury Federal Recordable

What happened

On January 31, 2022, FMCSA recorded an injury crash with one person hurt in LANCASTER, Texas. The vehicle was operated by CARDINAL LOGISTICS MANAGEMENT CORPORATION (USDOT 191496). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference TX68GEHQE1A7.

Carrier pattern note

This is the carrier's 200 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: 63 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CARDINAL LOGISTICS MANAGEMENT CORPORATION
USDOT 191496
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
200
6 fatal · 70 injury
Crashes per 100 power units (24 mo)
3.5
103 crashes · 2,954 units
Days since prior carrier crash
2
Last on Jan 29, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,893 carriers

Geographic context

How this crash sits in its setting.

Within LANCASTER, Texas, 63 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 #:
TX68GEHQE1A7
Date:
Jan 31, 2022
Time:
1157
State:
Texas
City:
LANCASTER
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CARDINAL LOGISTICS MANAGEMENT CORPORATION (191496)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 5 3 3ALACWFEXNDMZ8907 3168406 (IN) CARDINAL LOGISTICS MANAGEMENT CORPORATION 2 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmw8qxshd0009o3gnxhikt15p Nov 4, 2026 AL Tow-Away 0 0
cmtwgme33005vpmiyvtfth9bb Sep 2, 2026 MT Tow-Away 0 0
cr_5127348 Mar 25, 2026 VA Injury 0 1
cr_5122205 Mar 5, 2026 TX Tow-Away 0 0
cr_5121757 Feb 27, 2026 GA Tow-Away 0 0
cr_5113732 Feb 20, 2026 IA Tow-Away 0 0
cr_5112778 Feb 11, 2026 GA Tow-Away 0 0
cr_5109639 Feb 10, 2026 TX Tow-Away 0 0
cr_5102411 Feb 5, 2026 VA Injury 0 1
cr_5102749 Feb 3, 2026 GA Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 191496 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
CARDINAL LOGISTICS MANAGEMENT CORPORATION
USDOT 191496 · 1,968 crashes · 5,325 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Insurance
Insurance-lapse watch · HIGH
BMC-91 filing instability signal for this carrier.
HIGH
Vehicle
VIN: 3ALACWFEXNDMZ8907
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
City
Crashes in LANCASTER, 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.