Skip to main content
TruckCodex
Hubs

Crash Record NM0710639198

FMCSA crash record in 97 on Mar 4, 2021.

Injury Federal Recordable

What happened

On March 4, 2021, FMCSA recorded an injury crash with 2 people hurt in 97, New Mexico. The vehicle was operated by VALUE TRUCK OF AZ LLC (USDOT 822809). Recorded conditions: 2 / 1 / 1 pavement. Reported by VALUE TRUCK OF AZ INC, FMCSA reference NM0710639198.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
3
Carrier
VALUE TRUCK OF AZ LLC
USDOT 822809
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
12
4 injury · 12 tow-away
Crashes per 100 power units (24 mo)
3.9
12 crashes · 305 units
Days since prior carrier crash
14
Last on Feb 18, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within 97, New Mexico, 7 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 #:
NM0710639198
Date:
Mar 4, 2021
Time:
1913
State:
New Mexico
City:
97
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
VALUE TRUCK OF AZ LLC (822809)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XPXD49X0HD451412 R436064 (TX) VALUE TRUCK OF AZ INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5122222 Mar 8, 2026 TX Tow-Away 0 0
cr_5121386 Mar 5, 2026 TX Injury 0 1
cr_5112569 Feb 18, 2026 TX Tow-Away 0 0
cr_5103517 Feb 6, 2026 AL Tow-Away 0 0
cr_5077013 Dec 5, 2025 TX Tow-Away 0 0
cr_5072107 Oct 26, 2025 TX Tow-Away 0 0
cr_5047511 Oct 21, 2025 AR Fatal 1 0
cr_5014238 Aug 4, 2025 TX Tow-Away 0 0
cr_4955911 May 17, 2025 CA Tow-Away 0 0
cr_4888558 Feb 5, 2025 AZ Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2017 PETERBILT 389
NHTSA recalls and complaints for this make/model/year.
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
20V130000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Recall
18V657000
ENGINE AND ENGINE COOLING:ENGINE:DIESEL
Carrier
VALUE TRUCK OF AZ LLC
USDOT 822809 · 98 crashes · 2,157 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: 1XPXD49X0HD451412
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Mexico
Statewide crash records.
Agency
VALUE TRUCK OF AZ INC
Crashes reported by this law-enforcement agency.
City
Crashes in 97, NM
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.