TruckCodex
Hubs

Crash Record MI0003261358

FMCSA crash record in LANSING on Aug 16, 2024.

Tow-Away Federal Recordable

What happened

On August 16, 2024, FMCSA recorded a tow-away crash with no reported injuries in LANSING, Michigan. The vehicle was operated by URS MIDWEST LLC (USDOT 790261). Recorded conditions: 1 / 1 / 2 pavement. FMCSA reference MI0003261358.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
URS MIDWEST LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
130
2 fatal · 36 injury
Crashes per 100 power units (24 mo)
7.2
94 crashes · 1,306 units
Days since prior carrier crash
4
Last on Aug 12, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within LANSING, Michigan, 105 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
2

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 #:
MI0003261358
Date:
Aug 16, 2024
Time:
1157
State:
Michigan
City:
LANSING
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
URS MIDWEST LLC (790261)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 7 8 4V5RC9EH5NN297228 RC11441 (MI) URS MIDWEST INC 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
cmqxb77ab002xp8f0vb98w931 Jun 23, 2026 OK Tow-Away 0 0
cmqugosa9001fp8o55shotjd8 Jun 21, 2026 KY Tow-Away 0 0
cr_5125724 Mar 2, 2026 IN Tow-Away 0 0
cr_5124696 Feb 26, 2026 IN Injury 0 1
cr_5106260 Feb 11, 2026 KY Tow-Away 0 0
cr_5111448 Feb 4, 2026 CA Injury 0 1
cr_5107720 Feb 2, 2026 NH Tow-Away 0 0
cr_5092861 Jan 14, 2026 MI Tow-Away 0 0
cr_5088223 Jan 13, 2026 GA Injury 0 1
cr_5097734 Dec 24, 2025 MD Injury 0 1

Related records

Carrier
URS MIDWEST LLC
USDOT 790261 · 1,382 crashes · 1,784 inspections
Vehicle
VIN: 4V5RC9EH5NN297228
Decode this VIN for make, model, year, and recall data.
State
Crashes in Michigan
Statewide crash records.
City
Crashes in LANSING, MI
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.