Crash Record PA204641600X

FMCSA crash record in WEST WHITELAND TOWNSHIP on May 18, 2022.

Tow-Away Federal Recordable

What happened

On May 18, 2022, FMCSA recorded a tow-away crash with no reported injuries in WEST WHITELAND TOWNSHIP, Pennsylvania. The vehicle was operated by BFI WASTE SERVICES OF PENNSYLVANIA LLC (USDOT 962087). Recorded conditions: 1 / 1 / 1 pavement. Reported by ALLIED WASTE SERVICES OF PITTSBURGH OR REPUBLIC SERVICES OF PITTSBURGH OR ALLIED WASTE SERVICES OF SCHUYLKILL VALLEY, FMCSA reference PA204641600X.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

BFI WASTE SERVICES OF PENNSYLVANIA LLC

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

Crashes per 100 power units (24 mo)

3.9

11 crashes · 279 units

Days since prior carrier crash

Last on Apr 25, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

PENNDOT · 2 reports
DMSC LOGISTICS LLC · 1 reports
ANTHONY PORRECA · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
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 #:: PA204641600X
Date:: May 18, 2022
Time:: 0920
State:: Pennsylvania
City:: WEST WHITELAND TOWNSHIP
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: BFI WASTE SERVICES OF PENNSYLVANIA LLC (962087)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	6	9	1M2AV02C4EM011821	AG77624 (PA)	ALLIED WASTE SERVICES OF PITTSBURGH OR REPUBLIC SERVICES OF PITTSBURGH OR ALLIED WASTE SERVICES OF SCHUYLKILL VALLEY	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	Injuries
cr_5096183	Dec 24, 2025	PA	Tow-Away	0
cr_5070971	Nov 11, 2025	PA	Tow-Away	0
cr_5045103	Oct 9, 2025	PA	Tow-Away	0
cr_5046575	Oct 3, 2025	PA	Tow-Away	0
cr_5119860	Aug 20, 2025	PA	Tow-Away	0
cr_5006985	Jun 11, 2025	PA	Tow-Away	0
cr_4948077	Apr 9, 2025	PA	Tow-Away	0
cr_4893422	Feb 10, 2025	DC	Injury	1
cr_4854014	Nov 13, 2024	PA	Injury	1
cr_4844620	Nov 6, 2024	PA	Tow-Away	0

Related records

Vehicle

2014 MACK MRU (TerraPro)

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

Carrier

BFI WASTE SERVICES OF PENNSYLVANIA LLC

USDOT 962087 · 261 crashes · 341 inspections

Vehicle

VIN: 1M2AV02C4EM011821

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

State

Crashes in Pennsylvania

Statewide crash records.

Agency

ALLIED WASTE SERVICES OF PITTSBURGH OR REPUBLIC SERVICES OF PITTSBURGH OR ALLIED WASTE SERVICES OF SCHUYLKILL VALLEY

Crashes reported by this law-enforcement agency.

City

Crashes in WEST WHITELAND 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.