Crash Record PA310789600X

FMCSA crash record in HAMPTON TOWNSHIP on Nov 28, 2023.

Tow-Away Federal Recordable

What happened

On November 28, 2023, FMCSA recorded a tow-away crash with no reported injuries in HAMPTON TOWNSHIP, Pennsylvania. The vehicle was operated by ROADSAFE TRAFFIC LP (USDOT 717663). Recorded conditions: 1 / 6 pavement. Reported by ROADSAFE TRAFFIC SYSTEMS, FMCSA reference PA310789600X.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

ROADSAFE TRAFFIC LP

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 · 8 injury

Crashes per 100 power units (24 mo)

2.3

30 crashes · 1,311 units

Days since prior carrier crash

Last on Sep 13, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within HAMPTON TOWNSHIP, Pennsylvania, 15 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

AD EXPRESS TRUCKING LLC · 2 reports
ADLER AND SONS INC · 1 reports
ACCESS GRANTED LOGISTICS LLC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: —
Road surface: 6

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 #:: PA310789600X
Date:: Nov 28, 2023
Time:: 0700
State:: Pennsylvania
City:: HAMPTON TOWNSHIP
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: ROADSAFE TRAFFIC LP (717663)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	5	3C7WRKBL6JG185741	ZMH6776 (NJ)	ROADSAFE TRAFFIC SYSTEMS	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	Injuries
cr_5110816	Jan 28, 2026	IN	Tow-Away	0
cr_5091123	Dec 11, 2025	PA	Tow-Away	0
cr_5071330	Nov 26, 2025	SC	Tow-Away	0
cr_5054654	Oct 20, 2025	IL	Tow-Away	0
cr_5054723	Oct 4, 2025	IN	Injury	1
cr_5055292	Oct 2, 2025	IN	Tow-Away	0
cr_5049956	Sep 29, 2025	CO	Tow-Away	0
cr_5037544	Sep 24, 2025	AZ	Tow-Away	0
cr_5032330	Sep 22, 2025	NC	Injury	1
cr_5035338	Sep 8, 2025	CO	Tow-Away	0

Related records

Vehicle

2018 RAM 4500

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

Recall

24V896000

SERVICE BRAKES, HYDRAULIC

Recall

21V398000

WHEELS:LUGS/NUTS/BOLTS/STUDS

Recall

19V236000

EXTERIOR LIGHTING:BRAKE LIGHTS

Carrier

ROADSAFE TRAFFIC LP

USDOT 717663 · 237 crashes · 153 inspections

Vehicle

VIN: 3C7WRKBL6JG185741

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

State

Crashes in Pennsylvania

Statewide crash records.

Agency

ROADSAFE TRAFFIC SYSTEMS

Crashes reported by this law-enforcement agency.

City

Crashes in HAMPTON TOWNSHIP, PA

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.