TruckCodex
Hubs

Crash Record MN0230040166

FMCSA crash record in OAK on Jan 4, 2023.

Tow-Away Federal Recordable

What happened

On January 4, 2023, FMCSA recorded a tow-away crash with no reported injuries in OAK, Minnesota. The vehicle was operated by TOTAL EXPRESS SERVICES LTD (USDOT 2172351). Recorded conditions: 1 / 4 / 6 pavement. Reported by TOTAL EXPRESS SERVICES LTD, FMCSA reference MN0230040166.

Carrier pattern note

This is the carrier's 5 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 power units.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
TOTAL EXPRESS SERVICES LTD
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
0 injury · 5 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 10 units
Days since prior carrier crash
279
Last on Mar 31, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,512 carriers

Geographic context

How this crash sits in its setting.

Within OAK, Minnesota, 12 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
4
Road surface
6

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 #:
MN0230040166
Date:
Jan 4, 2023
Time:
0954
State:
Minnesota
City:
OAK
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
TOTAL EXPRESS SERVICES LTD (2172351)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUJGLD53GLGT7251 P1073280 (IL) TOTAL EXPRESS SERVICES LTD 3 No

Crash event

Event sequence description.

3:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;1:15:COLLISION INVOLVING TRAIN;4:18:COLLISION INVOLVING FIXED OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4503815 Feb 2, 2023 AR Injury 0 2
cr_4371685 Mar 31, 2022 IN Tow-Away 0 0
cr_4322994 Mar 12, 2022 MO Tow-Away 0 0
cr_4285696 Jan 6, 2022 WV Tow-Away 0 0
cr_4222549 Jul 21, 2021 IL Tow-Away 0 0
cr_3796408 Feb 20, 2019 IL Tow-Away 0 0
cr_3740340 Dec 5, 2018 IL Injury 0 1
cr_3411407 May 29, 2017 MT Injury 0 1
cr_3345317 Jan 18, 2017 MT Tow-Away 0 0
cr_3127117 Nov 20, 2015 MT Tow-Away 0 0

Related records

Vehicle
2016 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V093000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
TOTAL EXPRESS SERVICES LTD
USDOT 2172351 · 12 crashes · 0 inspections
Vehicle
VIN: 1FUJGLD53GLGT7251
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
TOTAL EXPRESS SERVICES LTD
Crashes reported by this law-enforcement agency.
City
Crashes in OAK, MN
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.