Skip to main content
TruckCodex
Hubs

Crash Record PA908693600X

FMCSA crash record in Pennsylvania on Jul 2, 2019.

Injury

What happened

On July 2, 2019, FMCSA recorded an injury crash with 2 people hurt in Pennsylvania. The vehicle was operated by WHITEFORD & SON INC (USDOT 2111049). FMCSA reference PA908693600X.

Fatalities
0
Injuries
2
Vehicles
—
Carrier
USDOT 2111049
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 injury · 0 tow-away
Crashes per 100 power units (24 mo)
15.4
2 crashes · 13 units
Days since prior carrier crash
1,253
Last on Jan 26, 2016
Vs fleet-size peers
above the median
Cohort median 0.0 · 316,014 carriers

Geographic context

How this crash sits in its setting.

Within Pennsylvania, 11,820 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 #:
PA908693600X
Date:
Jul 2, 2019
Time:
0950
State:
Pennsylvania
Fatalities:
0
Injuries:
2
Tow-Away:
No
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5008175 Aug 11, 2025 PA Injury 0 1
cr_4900143 Feb 17, 2025 PA Tow-Away 0 0
cr_4762165 May 28, 2024 PA Tow-Away 0 0
cr_4642442 Oct 19, 2023 PA Tow-Away 0 0
cr_4548085 Apr 17, 2023 PA Injury 0 1
cr_4288660 Dec 14, 2021 PA Fatal 1 1
cr_3171764 Jan 26, 2016 PA Injury 0 2
cr_2968204 Dec 19, 2014 PA Tow-Away 0 0
cr_2923798 Sep 4, 2014 PA Tow-Away 0 0
cr_2739147 Jun 10, 2013 PA Tow-Away 0 0

Carrier booking & risk tools

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

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.