Crash Record PA806102500X

FMCSA crash record in Pennsylvania on May 31, 2018.

Injury

What happened

On May 31, 2018, FMCSA recorded an injury crash with one person hurt in Pennsylvania. The vehicle was operated by SAMUEL SON & CO INC (USDOT 342033). FMCSA reference PA806102500X.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
Carrier
SAMUEL SON & CO INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
8
2 injury · 8 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 58 units
Days since prior carrier crash
49
Last on Apr 12, 2018
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,697 carriers

Geographic context

How this crash sits in its setting.

Within Pennsylvania, 12,964 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
PA806102500X
Date:
May 31, 2018
Time:
1607
State:
Pennsylvania
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
SAMUEL SON & CO INC (342033)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4594582 Jul 24, 2023 MN Tow-Away 0 0
cr_4585050 May 5, 2023 PA Injury 0 1
cr_4394255 May 24, 2022 LA Tow-Away 0 0
cr_4294527 Nov 9, 2021 GA Injury 0 1
cr_4254240 Oct 27, 2021 LA Injury 0 1
cr_4074501 Nov 17, 2020 TX Tow-Away 0 0
cr_3979857 May 28, 2020 OK Tow-Away 0 0
cr_3877386 Nov 8, 2019 NY Injury 0 1
cr_3901146 Oct 4, 2019 CO Injury 0 1
cr_3815674 Jun 24, 2019 FL Tow-Away 0 0

Related records

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.