Skip to main content
TruckCodex
Hubs

Crash Record CA8502300149

FMCSA crash record in HESPERIA on Feb 2, 2023.

Tow-Away Federal Recordable

What happened

On February 2, 2023, FMCSA recorded a tow-away crash with no reported injuries in HESPERIA, California. The vehicle was operated by CME TRANSCO LLC (USDOT 1080997). Recorded conditions: 1 / 1 / 1 pavement. Reported by CME TRANSCO LLC, FMCSA reference CA8502300149.

Carrier pattern note

This is the carrier's 51 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
0
Vehicles
2
Carrier
CME TRANSCO LLC
USDOT 1080997
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
51
2 fatal · 14 injury
Crashes per 100 power units (24 mo)
3.5
62 crashes · 1,785 units
Days since prior carrier crash
17
Last on Jan 16, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,880 carriers

Geographic context

How this crash sits in its setting.

Within HESPERIA, California, 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 #:
CA8502300149
Date:
Feb 2, 2023
Time:
1135
State:
California
City:
HESPERIA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CME TRANSCO LLC (1080997)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUJGEDV9JLHZ8934 2637922 (IN) CME TRANSCO LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvettq2a00h7ogsslc0zpg6s Oct 9, 2026 KY Tow-Away 0 0
cmslgo0qd000dpeakr1xcjuhl Aug 4, 2026 OK Injury 0 1
cmny3yg6200hgk38vxo0g6pwu Apr 2, 2026 VA Tow-Away 0 0
cr_5116174 Feb 25, 2026 OH Injury 0 1
cr_5122930 Feb 25, 2026 MO Tow-Away 0 0
cr_5107521 Feb 19, 2026 MN Tow-Away 0 0
cr_5111398 Feb 16, 2026 GA Tow-Away 0 0
cr_5104289 Jan 29, 2026 TX Tow-Away 0 0
cr_5101116 Jan 20, 2026 FL Injury 0 1
cr_5084202 Jan 8, 2026 ME Injury 0 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2018 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V817000
FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL
Recall
20V567000
EXTERIOR LIGHTING:BRAKE LIGHTS
Carrier
CME TRANSCO LLC
USDOT 1080997 · 355 crashes · 3,072 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJGEDV9JLHZ8934
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
CME TRANSCO LLC
Crashes reported by this law-enforcement agency.
City
Crashes in HESPERIA, CA
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.