Crash Record OK2310001786

FMCSA crash record in TULSA on Oct 14, 2023.

Injury Federal Recordable

What happened

On October 14, 2023, FMCSA recorded an injury crash with one person hurt in TULSA, Oklahoma. The vehicle was operated by MUNDS ENERGY INC (USDOT 3695947). Recorded conditions: 2 / 1 / 1 pavement. Reported by MUNDS ENERGY INC, FMCSA reference OK2310001786.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

MUNDS ENERGY INC

USDOT 3695947

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 2 injury

Crashes per 100 power units (24 mo)

5.4

7 crashes · 130 units

Days since prior carrier crash

220

Last on Mar 8, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,189 carriers

Geographic context

How this crash sits in its setting.

Within TULSA, Oklahoma, 434 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: 2
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 #:: OK2310001786
Date:: Oct 14, 2023
Time:: 0031
State:: Oklahoma
City:: TULSA
Fatalities:: 0
Injuries:: 1
Tow-Away:: No
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: MUNDS ENERGY INC (3695947)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	98	3HSDZAPR8LN800324	BW215422 (KS)	MUNDS ENERGY INC	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_4953262	May 30, 2025	OK	Injury	0	1
cr_4926766	Apr 12, 2025	KS	Tow-Away	0	0
cr_4997667	Mar 14, 2025	KS	Fatal	1	3
cr_5067896	Mar 14, 2025	KS	Injury	0	5
cr_4894644	Feb 4, 2025	MO	Tow-Away	0	0
cr_4915862	Jan 4, 2025	KS	Tow-Away	0	0
cr_4846307	Nov 8, 2024	KS	Tow-Away	0	0
cr_4847971	Sep 8, 2024	OK	Tow-Away	0	0
cr_4766214	May 17, 2024	KS	Tow-Away	0	0
cr_4724842	Mar 1, 2024	KS	Tow-Away	0	0

Carrier booking & risk tools

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

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

Related records

Carrier

MUNDS ENERGY INC

USDOT 3695947 · 19 crashes · 498 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3HSDZAPR8LN800324

Decode this VIN for make, model, year, and recall data.

State

Crashes in Oklahoma

Statewide crash records.

Agency

MUNDS ENERGY INC

Crashes reported by this law-enforcement agency.

City

Crashes in TULSA, 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.