Skip to main content
TruckCodex
Hubs

Crash Record AZ0000049720

FMCSA crash record in UNKNOWN on Aug 27, 2023.

Tow-Away Federal Recordable

What happened

On August 27, 2023, FMCSA recorded a tow-away crash with no reported injuries in UNKNOWN, Arizona. The vehicle was operated by JIMBASS TRANSPORTATION LLC (USDOT 4097711). Recorded conditions: 1 / 1 / 1 pavement. Reported by JIMBASS TRANSPORTATION LLC, FMCSA reference AZ0000049720.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
JIMBASS TRANSPORTATION LLC
USDOT 4097711
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 injury · 4 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 1 units
Days since prior carrier crash
6
Last on Aug 21, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,577,319 carriers

Geographic context

How this crash sits in its setting.

Within UNKNOWN, Arizona, 411 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 #:
AZ0000049720
Date:
Aug 27, 2023
Time:
1451
State:
Arizona
City:
UNKNOWN
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
JIMBASS TRANSPORTATION LLC (4097711)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 8 3C7WRSCL8NG335210 AS31ER (FL) JIMBASS TRANSPORTATION LLC 2 No

Crash event

Event sequence description.

1:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT;2:98:OTHER:RAN_OFF_ROAD_LEFT

Other crashes by this carrier

8 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4768879 May 29, 2024 NJ Tow-Away 0 0
cr_4634873 Sep 30, 2023 PA Tow-Away 0 0
cr_4630363 Sep 24, 2023 LA Injury 0 3
cr_4709169 Sep 19, 2023 IL Tow-Away 0 0
cr_4631920 Sep 14, 2023 MI Tow-Away 0 0
cr_4608188 Aug 21, 2023 NC Injury 0 1
cr_4612289 Aug 18, 2023 NH Tow-Away 0 0
cr_4716487 Aug 15, 2023 IL Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
JIMBASS TRANSPORTATION LLC
USDOT 4097711 · 9 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3C7WRSCL8NG335210
Decode this VIN for make, model, year, and recall data.
State
Crashes in Arizona
Statewide crash records.
Agency
JIMBASS TRANSPORTATION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in UNKNOWN, 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.