Crash Record PA205659900X

FMCSA crash record in EAST PROVIDENCE TOWNSHIP on May 5, 2022.

Injury Federal Recordable

What happened

On May 5, 2022, FMCSA recorded an injury crash with one person hurt in EAST PROVIDENCE TOWNSHIP, Pennsylvania. The vehicle was operated by METROPOLITAN TRANSPORT LLC (USDOT 2130303). Recorded conditions: 1 / 1 / 1 pavement. Reported by METROPOLITAN TRANSPORT LLC, FMCSA reference PA205659900X.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 28 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

METROPOLITAN TRANSPORT LLC

USDOT 2130303

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 5 tow-away

Crashes per 100 power units (24 mo)

18.2

2 crashes · 11 units

Days since prior carrier crash

Last on Apr 7, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 315,639 carriers

Geographic context

How this crash sits in its setting.

Within EAST PROVIDENCE TOWNSHIP, Pennsylvania, 28 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

AMERICA MIDWEST TRANSPORTATION LLC · 1 reports
AMERICAN BLINK CORPORATION · 1 reports
AG EXPEDITED INC · 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 #:: PA205659900X
Date:: May 5, 2022
Time:: 1408
State:: Pennsylvania
City:: EAST PROVIDENCE TOWNSHIP
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: METROPOLITAN TRANSPORT LLC (2130303)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	8	12	3AKJGLD52FSGP3838	3015744 (IN)	METROPOLITAN TRANSPORT LLC	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
cr_5024343	Dec 18, 2024	MD	Tow-Away
cr_4877623	Dec 18, 2024	MD	Tow-Away
cr_4349515	Apr 7, 2022	PA	Tow-Away
cr_4375151	Jan 21, 2022	VA	Tow-Away
cr_4280205	Dec 15, 2021	MD	Tow-Away
cr_4178435	Jun 2, 2021	VA	Tow-Away
cr_3945295	Feb 12, 2020	MD	Tow-Away
cr_3936343	Feb 2, 2020	NJ	Tow-Away
cr_3573334	Feb 15, 2018	MD	Tow-Away
cr_3491667	Oct 31, 2017	PA	Tow-Away

Carrier booking & risk tools

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

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

Related records

Vehicle

2015 FREIGHTLINER Cascadia

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

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Recall

19V093000

STEERING:LINKAGES:TIE ROD ASSEMBLY

Carrier

METROPOLITAN TRANSPORT LLC

USDOT 2130303 · 12 crashes · 31 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKJGLD52FSGP3838

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

State

Crashes in Pennsylvania

Statewide crash records.

Agency

METROPOLITAN TRANSPORT LLC

Crashes reported by this law-enforcement agency.

City

Crashes in EAST 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.