Skip to main content
TruckCodex
Hubs

Crash Record NJ0000012728

FMCSA crash record in JERSEY CITY on Apr 13, 2024.

Injury Federal Recordable

What happened

On April 13, 2024, FMCSA recorded an injury crash with one person hurt in JERSEY CITY, New Jersey. The vehicle was operated by NEW PRIME INC (USDOT 3706). Recorded conditions: 1 / 1 / 1 pavement. Reported by NEW PRIME INC, FMCSA reference NJ0000012728.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
NEW PRIME INC
USDOT 3706
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
761
13 fatal · 232 injury
Crashes per 100 power units (24 mo)
7.2
568 crashes · 7,919 units
Days since prior carrier crash
1
Last on Apr 12, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,877 carriers

Geographic context

How this crash sits in its setting.

Within JERSEY CITY, New Jersey, 197 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 #:
NJ0000012728
Date:
Apr 13, 2024
Time:
0849
State:
New Jersey
City:
JERSEY CITY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
NEW PRIME INC (3706)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDR3PSLK4263 22KS2Y (MO) NEW PRIME 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
cmvettq2500grogsswzb5o55q Oct 9, 2026 WV Tow-Away 0 0
cmu0qsldq001zpmtn7urywycp Sep 9, 2026 WV Tow-Away 0 0
cmtwgmdze000jpmiyxvcd5fu4 Sep 5, 2026 OH Tow-Away 0 0
cmt5ony12003tpmdmn5u0wwkf Aug 18, 2026 MT Tow-Away 0 0
cmt1jo0xn000lpevkww23vrzm Aug 16, 2026 PA Injury 0 2
cmsw88s8r0081pev3iijez3z3 Aug 8, 2026 AR Injury 0 1
cmsw88skb00lxpev3vrx3pu0r Aug 6, 2026 AR Tow-Away 0 0
cms2qwgil000jpey1l0ve1gta Jul 23, 2026 NC Injury 0 1
cmr7aydgr002lp8qsh65m7ug4 Jun 30, 2026 VA Tow-Away 0 0
cmqxb777i000hp8f0k9tjafab Jun 24, 2026 OK Injury 0 1

Carrier booking & risk tools

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

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

Related records

Carrier
NEW PRIME INC
USDOT 3706 · 9,430 crashes · 29,953 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR3PSLK4263
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
NEW PRIME INC
Crashes reported by this law-enforcement agency.
City
Crashes in JERSEY CITY, NJ
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.