Skip to main content
TruckCodex
Hubs

Crash Record PA111725900X

FMCSA crash record in WEST PROVIDENCE TOWNSHIP on Nov 30, 2021.

Injury Federal Recordable

What happened

On November 30, 2021, FMCSA recorded an injury crash with 2 people hurt in WEST PROVIDENCE TOWNSHIP, Pennsylvania. The vehicle was operated by CRST EXPEDITED INC (USDOT 53773). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference PA111725900X.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
2
Carrier
CRST EXPEDITED INC
USDOT 53773
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
407
13 fatal · 127 injury
Crashes per 100 power units (24 mo)
3.3
143 crashes · 4,362 units
Days since prior carrier crash
4
Last on Nov 26, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within WEST PROVIDENCE TOWNSHIP, Pennsylvania, 14 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
2
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 #:
PA111725900X
Date:
Nov 30, 2021
Time:
0235
State:
Pennsylvania
City:
WEST PROVIDENCE TOWNSHIP
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CRST EXPEDITED INC (53773)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHHDR2LSLP7109 2806828 (IN) CRST EXPEDITED INC 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
cmoz9e2gp004tnufy3s6jw0lq May 5, 2026 AZ Injury 0 1
cr_5123667 Feb 21, 2026 TX Tow-Away 0 0
cr_5110739 Feb 20, 2026 IA Tow-Away 0 0
cr_5123284 Feb 17, 2026 CA Injury 0 1
cr_5110844 Feb 6, 2026 IN Injury 0 2
cr_5109152 Feb 5, 2026 TX Tow-Away 0 0
cr_5109105 Feb 5, 2026 TX Tow-Away 0 0
cr_5106473 Jan 28, 2026 TX Tow-Away 0 0
cr_5121624 Jan 26, 2026 CA Injury 0 2
cr_5113451 Jan 19, 2026 PA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
CRST EXPEDITED INC
USDOT 53773 · 4,955 crashes · 9,989 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR2LSLP7109
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
City
Crashes in WEST PROVIDENCE 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.