Crash Record AZ0004254147

FMCSA crash record in Avondale on Dec 5, 2024.

Tow-Away Federal Recordable

What happened

On December 5, 2024, FMCSA recorded a tow-away crash with no reported injuries in Avondale, Arizona. The vehicle was operated by GURMAN TRUCKING INC (USDOT 1244207). Recorded conditions: 3 / 1 / 1 pavement. FMCSA reference AZ0004254147.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

GURMAN TRUCKING INC

USDOT 1244207

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

17 injury · 41 tow-away

Crashes per 100 power units (24 mo)

16.3

40 crashes · 245 units

Days since prior carrier crash

Last on Nov 27, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,045 carriers

Geographic context

How this crash sits in its setting.

Within Avondale, Arizona, 62 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

AMERICAN PRIDE CARGO INC · 1 reports
BENJAMIN TRANSPORTATION LLC · 1 reports
AD CARGO INC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 3
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 #:: AZ0004254147
Date:: Dec 5, 2024
Time:: 1820
State:: Arizona
City:: Avondale
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: GURMAN TRUCKING INC (1244207)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
3	7	12	3AKJHHDRXRSVH9409	XB800H (FL)	GURMAN TRUCKING INC	2	No

Crash event

Event sequence description.

1:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5112979	Feb 27, 2026	NV	Tow-Away	0
cr_5108433	Feb 12, 2026	AR	Tow-Away	0
cr_5083439	Jan 4, 2026	SC	Injury	2
cr_5081884	Dec 30, 2025	MN	Injury	1
cr_5083743	Dec 7, 2025	NM	Tow-Away	0
cr_5073226	Dec 4, 2025	WY	Tow-Away	0
cr_5065878	Nov 10, 2025	AZ	Injury	1
cr_5043075	Oct 2, 2025	AZ	Tow-Away	0
cr_5029131	Sep 5, 2025	MO	Tow-Away	0
cr_5035630	Aug 15, 2025	MO	Tow-Away	0

Carrier booking & risk tools

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

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

Related records

Vehicle

2024 FREIGHTLINER Cascadia

NHTSA recalls and complaints for this make/model/year.

ELECTRONIC STABILITY CONTROL (ESC)

Carrier

GURMAN TRUCKING INC

USDOT 1244207 · 124 crashes · 1,733 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Insurance

Insurance-lapse watch · HIGH

BMC-91 filing instability signal for this carrier.

HIGH

Vehicle

VIN: 3AKJHHDRXRSVH9409

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

State

Crashes in Arizona

Statewide crash records.

City

Crashes in Avondale, AZ

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.