Skip to main content
TruckCodex
Hubs

Crash Record OK0021019850

FMCSA crash record in SPRINGER on Aug 23, 2021.

Tow-Away Federal Recordable

What happened

On August 23, 2021, FMCSA recorded a tow-away crash with no reported injuries in SPRINGER, Oklahoma. The vehicle was operated by TOTAL TRANSPORTATION OF MISSISSIPPI LLC (USDOT 434467). Recorded conditions: 1 / 1 / 1 pavement. Reported by TOTAL TRANSPORTATION OF MISSISSIPPI LLC, FMCSA reference OK0021019850.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
TOTAL TRANSPORTATION OF MISSISSIPPI LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
84
3 fatal · 25 injury
Crashes per 100 power units (24 mo)
8.1
89 crashes · 1,100 units
Days since prior carrier crash
3
Last on Aug 20, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,858 carriers

Geographic context

How this crash sits in its setting.

Within SPRINGER, Oklahoma, 13 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 #:
OK0021019850
Date:
Aug 23, 2021
Time:
1449
State:
Oklahoma
City:
SPRINGER
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
TOTAL TRANSPORTATION OF MISSISSIPPI LLC (434467)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4NC9EH1LN226611 3FH076 (OK) TOTAL TRANSPORTATION OF MISSISSIPPI LLC 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmqlxkk0t0029p8tr3ba8smvu Jun 14, 2026 NC Injury 0 2
cmqkg787z00glp8fya4imoh95 Jun 10, 2026 NC Tow-Away 0 0
cr_5121843 Mar 13, 2026 PA Tow-Away 0 0
cr_5122830 Mar 13, 2026 OH Tow-Away 0 0
cr_5115714 Mar 5, 2026 VA Tow-Away 0 0
cr_5114063 Feb 26, 2026 NM Tow-Away 0 0
cr_5124413 Feb 22, 2026 IN Tow-Away 0 0
cr_5108318 Feb 13, 2026 MS Tow-Away 0 0
cr_5107951 Feb 6, 2026 LA Injury 0 1
cr_5104350 Feb 5, 2026 TN Tow-Away 0 0

Related records

Carrier
TOTAL TRANSPORTATION OF MISSISSIPPI LLC
USDOT 434467 · 1,051 crashes · 3,966 inspections
Vehicle
VIN: 4V4NC9EH1LN226611
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oklahoma
Statewide crash records.
Agency
TOTAL TRANSPORTATION OF MISSISSIPPI LLC
Crashes reported by this law-enforcement agency.
City
Crashes in SPRINGER, OK
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.