Skip to main content
TruckCodex
Hubs

Crash Record MD24A1156565

FMCSA crash record in BALTIMORE on Mar 23, 2024.

Tow-Away Federal Recordable

What happened

On March 23, 2024, FMCSA recorded a tow-away crash with no reported injuries in BALTIMORE, Maryland. The vehicle was operated by VENEZIA BULK TRANSPORT INC (USDOT 1079966). Recorded conditions: 1 / 2 / 2 pavement. Reported by VENEZIA BULK TRANSPORT INC, FMCSA reference MD24A1156565.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
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)
49
1 fatal · 19 injury
Crashes per 100 power units (24 mo)
5.4
24 crashes · 442 units
Days since prior carrier crash
10
Last on Mar 13, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,985 carriers

Geographic context

How this crash sits in its setting.

Within BALTIMORE, Maryland, 336 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 #:
MD24A1156565
Date:
Mar 23, 2024
Time:
1015
State:
Maryland
City:
BALTIMORE
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 8 12 3HSDWTZRXJN493477 PWH5220 (PA) 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

Carrier
VENEZIA BULK TRANSPORT INC
USDOT 1079966 · 292 crashes · 502 inspections
Vehicle
VIN: 3HSDWTZRXJN493477
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
VENEZIA BULK TRANSPORT INC
Crashes reported by this law-enforcement agency.
City
Crashes in BALTIMORE, MD
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.