Crash Record AZ0I25044671

FMCSA crash record in LITTLEFIELD on Jul 25, 2025.

Tow-Away Federal Recordable

What happened

On July 25, 2025, FMCSA recorded a tow-away crash with no reported injuries in LITTLEFIELD, Arizona. The vehicle was operated by SEVEN O SEVEN TRANSPORTATION LLC (USDOT 3566257). Recorded conditions: 1 / 1 / 1 pavement. Reported by SEVEN O SEVEN TRANSPORTATION LLC, FMCSA reference AZ0I25044671.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

SEVEN O SEVEN TRANSPORTATION LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 5 injury

Crashes per 100 power units (24 mo)

12.4

21 crashes · 170 units

Days since prior carrier crash

Last on Jun 12, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

AVP TRANSPORT INC · 1 reports
CCRV TRUCKING INC · 1 reports
APA FREIGHT SOLUTIONS LLC · 1 reports

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 #:: AZ0I25044671
Date:: Jul 25, 2025
Time:: 0600
State:: Arizona
City:: LITTLEFIELD
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: SEVEN O SEVEN TRANSPORTATION LLC (3566257)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3HSDZAPR3SN300084	3818198 (IN)	SEVEN O SEVEN TRANSPORTATION LLC	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	Injuries
cr_5119828	Feb 27, 2026	MS	Injury	1
cr_5109914	Feb 18, 2026	WY	Tow-Away	0
cr_5095273	Jan 18, 2026	SD	Tow-Away	0
cr_5086766	Jan 9, 2026	WY	Tow-Away	0
cr_5087167	Dec 2, 2025	PA	Injury	2
cr_5068107	Nov 25, 2025	LA	Injury	3
cr_5065336	Nov 14, 2025	AL	Tow-Away	0
cr_5043511	Oct 17, 2025	TN	Tow-Away	0
cr_5063181	Oct 15, 2025	KS	Tow-Away	0
cr_5056739	Oct 3, 2025	CA	Tow-Away	0

Related records

Carrier

SEVEN O SEVEN TRANSPORTATION LLC

USDOT 3566257 · 25 crashes · 532 inspections

Vehicle

VIN: 3HSDZAPR3SN300084

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

State

Crashes in Arizona

Statewide crash records.

Agency

SEVEN O SEVEN TRANSPORTATION LLC

Crashes reported by this law-enforcement agency.

City

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