TruckCodex
Hubs

Crash Record NJ0022912916

FMCSA crash record in JERSEY CITY on Oct 5, 2022.

Injury Federal Recordable

What happened

On October 5, 2022, FMCSA recorded an injury crash with one person hurt in JERSEY CITY, New Jersey. The vehicle was operated by SAMUELS AND SON SEAFOOD COMPANY PITTSBURGH INC (USDOT 613963). Recorded conditions: 1 / 1 / 1 pavement. Reported by SAMUELS & SON SEAFOOD CO INC, FMCSA reference NJ0022912916.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
SAMUELS AND SON SEAFOOD COMPANY PITTSBURGH INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
7
2 injury · 6 tow-away
Crashes per 100 power units (24 mo)
3.1
3 crashes · 97 units
Days since prior carrier crash
38
Last on Aug 28, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

Within JERSEY CITY, New Jersey, 208 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 #:
NJ0022912916
Date:
Oct 5, 2022
Time:
0858
State:
New Jersey
City:
JERSEY CITY
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SAMUELS AND SON SEAFOOD COMPANY PITTSBURGH INC (613963)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1FVACWDT2HHHV7859 ZPE4710 (PA) SAMUELS & SON SEAFOOD CO INC 2 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_5057200 Nov 1, 2025 PA Injury 0 1
cr_4926638 Mar 17, 2025 DE Injury 0 2
cr_4903092 Feb 8, 2025 PA Injury 0 1
cr_4815819 Sep 17, 2024 PA Tow-Away 0 0
cr_4776991 May 10, 2024 NJ Injury 0 3
cr_4913993 Jun 14, 2023 NJ Tow-Away 0 0
cr_4621552 May 12, 2023 NJ Tow-Away 0 0
cr_4490717 Nov 12, 2022 PA Tow-Away 0 0
cr_4418435 Aug 28, 2022 PA Tow-Away 0 0
cr_4421656 Aug 25, 2022 PA Tow-Away 0 0

Related records

Vehicle
2017 FREIGHTLINER M2
NHTSA recalls and complaints for this make/model/year.
Recall
21V528000
EXTERIOR LIGHTING
Recall
21V484000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Carrier
SAMUELS AND SON SEAFOOD COMPANY PITTSBURGH INC
USDOT 613963 · 31 crashes · 284 inspections
Vehicle
VIN: 1FVACWDT2HHHV7859
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
SAMUELS & SON SEAFOOD CO 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.