Crash Record PA408630000X

FMCSA crash record in SNAKE SPRINGS TOWNSHIP on Sep 30, 2024.

Tow-Away Federal Recordable

What happened

On September 30, 2024, FMCSA recorded a tow-away crash with no reported injuries in SNAKE SPRINGS TOWNSHIP, Pennsylvania. The vehicle was operated by CONTRACT TRANSPORTATION SYSTEMS CO (USDOT 188891). Recorded conditions: 1 / 2 / 2 pavement. FMCSA reference PA408630000X.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

CONTRACT TRANSPORTATION SYSTEMS CO

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 fatal · 21 injury

Crashes per 100 power units (24 mo)

3.9

50 crashes · 1,288 units

Days since prior carrier crash

Last on Sep 24, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,853 carriers

Geographic context

How this crash sits in its setting.

Within SNAKE SPRINGS TOWNSHIP, Pennsylvania, 17 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

CLIFFORD LEE HAMBLETON · 1 reports
COWS R US TRANSPORT LLC · 1 reports
AMS TRUCKING LLC · 1 reports

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 #:: PA408630000X
Date:: Sep 30, 2024
Time:: 0710
State:: Pennsylvania
City:: SNAKE SPRINGS TOWNSHIP
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: CONTRACT TRANSPORTATION SYSTEMS CO (188891)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	4V4NC9EH0NN318201	PWU7912 (OH)	CONTRACT TRANSPORTATION SYSTEMS CO	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
cmsw88u6y00rxpev3bhe28u3k	Aug 5, 2026	PA	Injury	0	2
cr_5127778	Mar 23, 2026	NV	Tow-Away	0	0
cr_5118089	Feb 19, 2026	GA	Injury	0	1
cr_5115145	Feb 16, 2026	PA	Injury	0	1
cr_5097001	Jan 28, 2026	KY	Tow-Away	0	0
cr_5103978	Jan 22, 2026	MI	Injury	0	1
cr_5098540	Jan 7, 2026	SC	Fatal	1	0
cr_5087595	Dec 16, 2025	TX	Injury	0	1
cr_5086949	Dec 11, 2025	DE	Tow-Away	0	0
cr_5084663	Dec 8, 2025	WA	Tow-Away	0	0

Related records

Carrier

CONTRACT TRANSPORTATION SYSTEMS CO

USDOT 188891 · 614 crashes · 4,366 inspections

Vehicle

VIN: 4V4NC9EH0NN318201

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

State

Crashes in Pennsylvania

Statewide crash records.

City

Crashes in SNAKE SPRINGS 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.