TruckCodex
Hubs

Crash Record NJ0021549416

FMCSA crash record in FORT LEE BORO on Aug 9, 2021.

Injury Federal Recordable

What happened

On August 9, 2021, FMCSA recorded an injury crash with one person hurt in FORT LEE BORO, New Jersey. The vehicle was operated by WESTERN EXPRESS INC (USDOT 511412). Recorded conditions: 1 / 2 / 2 pavement. Reported by WESTERN EXPRESS INC, FMCSA reference NJ0021549416.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
WESTERN EXPRESS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
743
13 fatal · 217 injury
Crashes per 100 power units (24 mo)
14.7
490 crashes · 3,332 units
Days since prior carrier crash
1
Last on Aug 8, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,845 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
1
Weather
2
Road surface
2

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 #:
NJ0021549416
Date:
Aug 9, 2021
Time:
1220
State:
New Jersey
City:
FORT LEE BORO
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
WESTERN EXPRESS INC (511412)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HSDZAPR6KN319213 J7294HY (TN) WESTERN EXPRESS 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
cmroiq15z003zpemc9w9vabll Jul 10, 2026 KY Tow-Away 0 0
cmq1vv00p001fpbjqk3gtbq8i Jun 1, 2026 VA Tow-Away 0 0
cmpaoq9c9000xnu1hqvqf7tln May 13, 2026 AR Injury 0 1
cmoz9e2g10039nufypztut88i May 5, 2026 OR Tow-Away 0 0
cmodru16m004hnvfd1y91643j Apr 20, 2026 TN Tow-Away 0 0
cmo6itlbe00ajo1auw99jsomo Apr 10, 2026 SC Injury 0 1
cr_5126108 Mar 27, 2026 NC Injury 0 4
cr_5126129 Mar 25, 2026 NJ Tow-Away 0 0
cr_5124866 Mar 19, 2026 VA Injury 0 1
cr_5123526 Mar 18, 2026 MI Tow-Away 0 0

Related records

Carrier
WESTERN EXPRESS INC
USDOT 511412 · 6,312 crashes · 20,350 inspections
Vehicle
VIN: 3HSDZAPR6KN319213
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
WESTERN EXPRESS INC
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.