Skip to main content
TruckCodex
Hubs

Crash Record OK2508001798

FMCSA crash record in OKLAHOMA CITY on Aug 5, 2025.

Tow-Away Federal Recordable

What happened

On August 5, 2025, FMCSA recorded a tow-away crash with no reported injuries in OKLAHOMA CITY, Oklahoma. The vehicle was operated by DC TRANSPORTATION SERVICES INC (USDOT 1018527). Recorded conditions: 1 / 1 / 1 pavement. Reported by DC TRANSPORTATION SERVICES INC, FMCSA reference OK2508001798.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
DC TRANSPORTATION SERVICES INC
USDOT 1018527
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
0 injury · 9 tow-away
Crashes per 100 power units (24 mo)
4.1
7 crashes · 172 units
Days since prior carrier crash
38
Last on Jun 28, 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 OKLAHOMA CITY, Oklahoma, 884 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 #:
OK2508001798
Date:
Aug 5, 2025
Time:
0916
State:
Oklahoma
City:
OKLAHOMA CITY
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
DC TRANSPORTATION SERVICES INC (1018527)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4NC9EH6JN902581 XP22611 (CA) DC TRANSPORTATION SERVICES 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
cr_5106003 Feb 8, 2026 WY Fatal 2 0
cr_5094618 Dec 13, 2025 IA Tow-Away 0 0
cr_5023611 Jun 28, 2025 NV Tow-Away 0 0
cr_4951253 May 16, 2025 NV Tow-Away 0 0
cr_4896178 Feb 19, 2025 FL Tow-Away 0 0
cr_4884511 Jan 5, 2025 IN Tow-Away 0 0
cr_4737194 Apr 11, 2024 PA Tow-Away 0 0
cr_4697190 Feb 8, 2024 AZ Tow-Away 0 0
cr_4644449 Oct 18, 2023 PA Tow-Away 0 0
cr_4616731 Sep 9, 2023 WY Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
DC TRANSPORTATION SERVICES INC
USDOT 1018527 · 151 crashes · 542 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 4V4NC9EH6JN902581
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oklahoma
Statewide crash records.
Agency
DC TRANSPORTATION SERVICES INC
Crashes reported by this law-enforcement agency.
City
Crashes in OKLAHOMA CITY, 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.