Skip to main content
TruckCodex
Hubs

Crash Record NVNLPD000674

FMCSA crash record in N LAS VEGAS on Jan 11, 2024.

Tow-Away Federal Recordable

What happened

On January 11, 2024, FMCSA recorded a tow-away crash with no reported injuries in N LAS VEGAS, Nevada. The vehicle was operated by TANTARA TRANSPORTATION INC (USDOT 587180). Recorded conditions: 1 / 1 / 1 pavement. Reported by TANTARA TRANSPORTATION INC, FMCSA reference NVNLPD000674.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
TANTARA TRANSPORTATION INC
USDOT 587180
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
3 injury · 9 tow-away
Crashes per 100 power units (24 mo)
4.4
8 crashes · 180 units
Days since prior carrier crash
100
Last on Oct 3, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within N LAS VEGAS, Nevada, 41 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 #:
NVNLPD000674
Date:
Jan 11, 2024
Time:
1359
State:
Nevada
City:
N LAS VEGAS
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
TANTARA TRANSPORTATION INC (587180)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 12 2HSCUAPR3AC177185 RH74404 (MI) TANTARA TRANSPORTATION INC 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 Fatalities Injuries
cr_5104112 Feb 5, 2026 MI Tow-Away 0 0
cr_5068755 Dec 2, 2025 MI Tow-Away 0 0
cr_4933739 Apr 6, 2025 NY Injury 0 2
cr_4905376 Feb 21, 2025 MI Tow-Away 0 0
cr_4873939 Jan 5, 2025 OH Injury 0 1
cr_4868435 Jan 3, 2025 TN Tow-Away 0 0
cr_4858425 Dec 4, 2024 MI Tow-Away 0 0
cr_4844746 Nov 11, 2024 TX Injury 0 1
cr_4798022 Jul 30, 2024 MI Injury 0 1
cr_4662219 Oct 3, 2023 MD Injury 0 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2010 INTERNATIONAL LF627
NHTSA recalls and complaints for this make/model/year.
Carrier
TANTARA TRANSPORTATION INC
USDOT 587180 · 60 crashes · 131 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 2HSCUAPR3AC177185
Decode this VIN for make, model, year, and recall data.
State
Crashes in Nevada
Statewide crash records.
Agency
TANTARA TRANSPORTATION INC
Crashes reported by this law-enforcement agency.
City
Crashes in N LAS VEGAS, NV
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.