TruckCodex
Hubs

Crash Record NJ0022547781

FMCSA crash record in FORT LEE BORO on Jun 5, 2022.

Injury Federal Recordable

What happened

On June 5, 2022, FMCSA recorded an injury crash with one person hurt in FORT LEE BORO, New Jersey. The vehicle was operated by AMAZON LOGISTICS LLC (USDOT 1781487). Recorded conditions: 3 / 1 / 1 pavement. Reported by AMAZON LOGISTICS LLC, FMCSA reference NJ0022547781.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
4
Carrier
AMAZON LOGISTICS LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
5 injury · 5 tow-away
Crashes per 100 power units (24 mo)
1000.0
20 crashes · 2 units
Days since prior carrier crash
52
Last on Apr 14, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,561,123 carriers

Geographic context

How this crash sits in its setting.

Within FORT LEE BORO, New Jersey, 29 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
3
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 #:
NJ0022547781
Date:
Jun 5, 2022
Time:
0125
State:
New Jersey
City:
FORT LEE BORO
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
4
Carrier (USDOT):
AMAZON LOGISTICS LLC (1781487)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 13 4V4NC9UG6NN314050 3170625 (IN) AMAZON LOGISTICS 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 Fatalities Injuries
cmo6itlm100i0o1au5umnx6i9 Apr 9, 2026 OK Tow-Away 0 0
cr_5123007 Mar 4, 2026 MI Tow-Away 0 0
cr_5120151 Mar 3, 2026 GA Tow-Away 0 0
cr_5110935 Jan 29, 2026 MI Tow-Away 0 0
cr_5072862 Oct 16, 2025 WA Injury 0 1
cr_5051277 Sep 28, 2025 MI Tow-Away 0 0
cr_5056214 Sep 25, 2025 MI Tow-Away 0 0
cr_5008770 Jul 3, 2025 SC Tow-Away 0 0
cr_4931238 Apr 14, 2025 AZ Injury 0 3
cr_4904775 Feb 19, 2025 WA Tow-Away 0 0

Related records

Vehicle
2022 VOLVO TRUCK VNL
NHTSA recalls and complaints for this make/model/year.
Carrier
AMAZON LOGISTICS LLC
USDOT 1781487 · 65 crashes · 8 inspections
Vehicle
VIN: 4V4NC9UG6NN314050
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
AMAZON LOGISTICS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in FORT LEE BORO, 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.