Skip to main content
TruckCodex
Hubs

Crash Record MD23A1061925

FMCSA crash record in Maryland on Sep 6, 2023.

Tow-Away Federal Recordable

What happened

On September 6, 2023, FMCSA recorded a tow-away crash with no reported injuries in Maryland. The vehicle was operated by JERRY PRESTON HAULING INCORPORATED (USDOT 428030). Recorded conditions: 6 / 1 / 1 pavement. Reported by JERRY PRESTON HAULING INCORPORATED, FMCSA reference MD23A1061925.

Carrier pattern note

This is the carrier's 5 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities
0
Injuries
0
Vehicles
3
Carrier
JERRY PRESTON HAULING INCORPORATED
USDOT 428030
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
2 injury · 5 tow-away
Crashes per 100 power units (24 mo)
5.7
3 crashes · 53 units
Days since prior carrier crash
337
Last on Oct 4, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 3,855 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
6
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 #:
MD23A1061925
Date:
Sep 6, 2023
Time:
0357
State:
Maryland
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
JERRY PRESTON HAULING INCORPORATED (428030)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 6 1NPXX4EX5PD822666 259ED39 (MD) JERRY PRESTON HAULING INCORPORATED 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2: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_5057909 Oct 8, 2025 MD Tow-Away 0 0
cr_5000410 Jul 9, 2025 MD Injury 0 1
cr_4891045 Dec 10, 2024 MD Injury 0 1
cr_4891000 Aug 14, 2024 MD Injury 0 2
cr_4662224 Oct 3, 2023 MD Tow-Away 0 0
cr_4437777 Oct 4, 2022 MD Tow-Away 0 0
cr_4437657 Sep 26, 2022 MD Injury 0 1
cr_4380727 Jun 20, 2022 MD Tow-Away 0 0
cr_4356431 May 6, 2022 MD Injury 0 1
cr_4230053 Aug 25, 2021 PA Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 428030 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
JERRY PRESTON HAULING INCORPORATED
USDOT 428030 · 51 crashes · 284 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1NPXX4EX5PD822666
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
JERRY PRESTON HAULING INCORPORATED
Crashes reported by this law-enforcement agency.
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.