Skip to main content
TruckCodex
Hubs

Crash Record NM0023218956

FMCSA crash record in New Mexico on Mar 28, 2010.

Tow-Away

What happened

On March 28, 2010, FMCSA recorded a tow-away crash with no reported injuries in New Mexico. The vehicle was operated by BOB MELTON TRUCK SERVICE INC (USDOT 312891). FMCSA reference NM0023218956.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
—
Carrier
BOB MELTON TRUCK SERVICE INC
Vehicle Type
—
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
0 injury · 4 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 20 units
Days since prior carrier crash
111
Last on Dec 7, 2009
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,194 carriers

Geographic context

How this crash sits in its setting.

Within New Mexico, 1,292 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
NM0023218956
Date:
Mar 28, 2010
Time:
1936
State:
New Mexico
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4651521 Jul 10, 2023 IL Tow-Away 0 0
cr_4521038 Mar 3, 2023 IL Tow-Away 0 0
cr_4201584 Jun 9, 2021 IL Injury 0 1
cr_4195767 May 24, 2021 IL Tow-Away 0 0
cr_3861862 Jul 6, 2019 IL Injury 0 1
cr_3762103 Mar 26, 2019 IN Tow-Away 0 0
cr_3692001 Nov 18, 2018 TN Injury 0 1
cr_3489547 Nov 14, 2017 NC Injury 0 1
cr_3510473 May 12, 2017 IL Injury 0 1
cr_3323409 Dec 16, 2016 IL Tow-Away 0 0

Related records

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.