TruckCodex
Hubs

Crash Record NJ0023542900

FMCSA crash record in FORT LEE BORO on Jul 16, 2023.

Injury Federal Recordable

What happened

On July 16, 2023, FMCSA recorded an injury crash with one person hurt in FORT LEE BORO, New Jersey. The vehicle was operated by P&S TRANSPORTATION LLC (USDOT 1243338). Recorded conditions: 1 / 2 / 2 pavement. Reported by P&S TRANSPORTATION LLC, FMCSA reference NJ0023542900.

Carrier pattern note

This is the carrier's 136 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
P&S TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
136
5 fatal · 54 injury
Crashes per 100 power units (24 mo)
6.4
148 crashes · 2,303 units
Days since prior carrier crash
1
Last on Jul 15, 2023
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 #:
NJ0023542900
Date:
Jul 16, 2023
Time:
1230
State:
New Jersey
City:
FORT LEE BORO
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
P&S TRANSPORTATION LLC (1243338)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDRXRSUW8332 3414568 (IN) P&S TRANSPORTATION 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
cmqkg77zd0061p8fybp5p44rq Jun 12, 2026 NC Tow-Away 0 0
cmo6itlt500nqo1aubdbgdj2u Apr 10, 2026 AL Tow-Away 0 0
cr_5123883 Mar 15, 2026 OK Tow-Away 0 0
cr_5118712 Mar 5, 2026 OK Tow-Away 0 0
cr_5120979 Feb 18, 2026 GA Injury 0 1
cr_5109680 Feb 13, 2026 TX Injury 0 1
cr_5117625 Feb 12, 2026 OK Tow-Away 0 0
cr_5106059 Feb 11, 2026 AL Tow-Away 0 0
cr_5103541 Feb 5, 2026 AL Tow-Away 0 0
cr_5119452 Feb 4, 2026 LA Tow-Away 0 0

Related records

Carrier
P&S TRANSPORTATION LLC
USDOT 1243338 · 1,041 crashes · 6,119 inspections
Vehicle
VIN: 3AKJHHDRXRSUW8332
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
P&S TRANSPORTATION 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.