Crash Record NJ0024710491

FMCSA crash record in BELLMAWR BORO on Apr 3, 2024.

Tow-Away Federal Recordable

What happened

On April 3, 2024, FMCSA recorded a tow-away crash with no reported injuries in BELLMAWR BORO, New Jersey. The vehicle was operated by VENEZIA BULK TRANSPORT INC (USDOT 1079966). Recorded conditions: 5 / 2 / 2 pavement. Reported by VENEZIA BULK TRANSPORT INC, FMCSA reference NJ0024710491.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

VENEZIA BULK TRANSPORT INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 19 injury

Crashes per 100 power units (24 mo)

5.4

24 crashes · 442 units

Days since prior carrier crash

Last on Mar 23, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,885 carriers

Geographic context

How this crash sits in its setting.

Within BELLMAWR BORO, New Jersey, 40 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: 5
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 #:: NJ0024710491
Date:: Apr 3, 2024
Time:: 0531
State:: New Jersey
City:: BELLMAWR BORO
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: VENEZIA BULK TRANSPORT INC (1079966)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	4	1M1AW02Y5HM082642	PVK7272 (NJ)	VENEZIA BULK TRANSPORT 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
cr_5123680	Mar 10, 2026	PA	Tow-Away	0	0
cr_5096167	Dec 23, 2025	PA	Tow-Away	0	0
cr_5078839	Dec 22, 2025	VA	Tow-Away	0	0
cr_5073230	Nov 12, 2025	WV	Tow-Away	0	0
cr_5054885	Oct 27, 2025	PA	Fatal	2	3
cr_5058507	Oct 23, 2025	GA	Tow-Away	0	0
cr_5033013	Sep 19, 2025	GA	Fatal	1	1
cr_5042464	Sep 19, 2025	GA	Fatal	1	1
cr_5100971	Sep 8, 2025	FL	Injury	0	1
cr_5007244	Jul 9, 2025	PA	Tow-Away	0	0

Related records

Vehicle

2017 MACK CXU (Pinnacle)

NHTSA recalls and complaints for this make/model/year.

Carrier

VENEZIA BULK TRANSPORT INC

USDOT 1079966 · 292 crashes · 500 inspections

Vehicle

VIN: 1M1AW02Y5HM082642

Decode this VIN for make, model, year, and recall data.

State

Crashes in New Jersey

Statewide crash records.

Agency

VENEZIA BULK TRANSPORT INC

Crashes reported by this law-enforcement agency.

City

Crashes in BELLMAWR 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.