Skip to main content
TruckCodex
Hubs

Crash Record OK2502000622

FMCSA crash record in CHICKASHA on Jan 29, 2025.

Tow-Away Federal Recordable

What happened

On January 29, 2025, FMCSA recorded a tow-away crash with no reported injuries in CHICKASHA, Oklahoma. The vehicle was operated by MCELROY TRUCK LINES INC (USDOT 271424). Recorded conditions: 1 / 2 / 2 pavement. Reported by MCELROY TRUCK LINES INC, FMCSA reference OK2502000622.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
MCELROY TRUCK LINES INC
USDOT 271424
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
47
4 fatal · 19 injury
Crashes per 100 power units (24 mo)
5.6
32 crashes · 568 units
Days since prior carrier crash
31
Last on Dec 29, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within CHICKASHA, Oklahoma, 34 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 #:
OK2502000622
Date:
Jan 29, 2025
Time:
1348
State:
Oklahoma
City:
CHICKASHA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
MCELROY TRUCK LINES INC (271424)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 5 3HSDZAPR1LN805462 1183964 (AL) MCELROY TRUCK LINES INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE 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
cmtwgme0r001rpmiy1ox6p9ed Sep 3, 2026 NC Tow-Away 0 0
cr_5126508 Mar 24, 2026 LA Injury 0 1
cr_5115608 Feb 6, 2026 NC Tow-Away 0 0
cr_5088114 Jan 14, 2026 TN Tow-Away 0 0
cr_5105633 Jan 13, 2026 MS Tow-Away 0 0
cr_5083500 Jan 5, 2026 TN Tow-Away 0 0
cr_5081113 Dec 29, 2025 TN Tow-Away 0 0
cr_5083065 Dec 28, 2025 AL Tow-Away 0 0
cr_5080553 Dec 9, 2025 TX Injury 0 1
cr_5065405 Nov 21, 2025 AL Injury 0 2

Carrier booking & risk tools

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

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

Related records

Vehicle
2020 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
MCELROY TRUCK LINES INC
USDOT 271424 · 991 crashes · 1,415 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3HSDZAPR1LN805462
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oklahoma
Statewide crash records.
Agency
MCELROY TRUCK LINES INC
Crashes reported by this law-enforcement agency.
City
Crashes in CHICKASHA, 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.