Skip to main content
TruckCodex
Hubs

Crash Record OK2507002375

FMCSA crash record in DEPEW on Jul 12, 2025.

Tow-Away Federal Recordable

What happened

On July 12, 2025, FMCSA recorded a tow-away crash with no reported injuries in DEPEW, Oklahoma. The vehicle was operated by EXTRA MILE INTERNATIONAL INC (USDOT 3169488). Recorded conditions: 1 / 2 / 2 pavement. FMCSA reference OK2507002375.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 33 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
EXTRA MILE INTERNATIONAL INC
USDOT 3169488
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
26
2 fatal · 7 injury
Crashes per 100 power units (24 mo)
9.3
17 crashes · 182 units
Days since prior carrier crash
99
Last on Apr 4, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within DEPEW, Oklahoma, 33 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
2
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 #:
OK2507002375
Date:
Jul 12, 2025
Time:
1153
State:
Oklahoma
City:
DEPEW
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
EXTRA MILE INTERNATIONAL INC (3169488)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHHDR4SSVX9979 P1258493 (IL) EXTRA MILE INTERNATIONAL 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
cmqyq8pqj006jp8ar094vfsvt Jun 23, 2026 AL Fatal 1 0
cr_5109615 Jan 11, 2026 TX Fatal 2 1
cr_5080959 Dec 30, 2025 MN Injury 0 1
cr_5030969 Sep 18, 2025 OH Tow-Away 0 0
cr_5028552 Aug 27, 2025 VA Tow-Away 0 0
cr_5009345 Jul 16, 2025 TN Tow-Away 0 0
cr_4946706 Apr 4, 2025 IN Tow-Away 0 0
cr_4926803 Mar 13, 2025 MI Injury 0 1
cr_4906541 Feb 11, 2025 CA Tow-Away 0 0
cr_4891406 Feb 7, 2025 NE Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
EXTRA MILE INTERNATIONAL INC
USDOT 3169488 · 41 crashes · 961 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR4SSVX9979
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oklahoma
Statewide crash records.
City
Crashes in DEPEW, OK
All crashes on file for this city.
Station
I-44
Weigh / inspection station matching this crash location.
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.