TruckCodex
Hubs

Crash Record PA206874600X

FMCSA crash record in PHILADELPHIA CITY on Jul 21, 2022.

Injury Federal Recordable

What happened

On July 21, 2022, FMCSA recorded an injury crash with one person hurt in PHILADELPHIA CITY, Pennsylvania. The vehicle was operated by ENTERPRISE RENT-A-CAR COMPANY OF LOS ANGELES LLC (USDOT 2022631). Recorded conditions: 1 / 1 / 1 pavement. Reported by ENTERPRISE RENTACAR ALAMO RENTACAR NATIONAL CAR RENTAL ENTERPRISE TRUCK RENTAL, FMCSA reference PA206874600X.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
ENTERPRISE RENT-A-CAR COMPANY OF LOS ANGELES LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
35
13 injury · 35 tow-away
Crashes per 100 power units (24 mo)
0.4
7 crashes · 1,792 units
Days since prior carrier crash
27
Last on Jun 24, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within PHILADELPHIA CITY, Pennsylvania, 584 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
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 #:
PA206874600X
Date:
Jul 21, 2022
Time:
1040
State:
Pennsylvania
City:
PHILADELPHIA CITY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
ENTERPRISE RENT-A-CAR COMPANY OF LOS ANGELES LLC (2022631)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 98 3C63R3HL9MG635729 A440423 (IN) ENTERPRISE RENTACAR ALAMO RENTACAR NATIONAL CAR RENTAL ENTERPRISE TRUCK RENTAL 2 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
cr_5116411 Feb 8, 2026 CA Injury 0 1
cr_5024463 Aug 8, 2025 CA Tow-Away 0 0
cr_4991203 Jul 9, 2025 CA Injury 0 2
cr_4989841 Jun 22, 2025 CA Injury 0 1
cr_4989228 Jun 19, 2025 CA Injury 0 4
cr_4909866 Mar 12, 2025 NV Injury 0 2
cr_4902457 Feb 27, 2025 AZ Injury 0 1
cr_4779014 Jun 24, 2024 CA Tow-Away 0 0
cr_4760695 May 27, 2024 CA Injury 0 1
cr_4759012 May 17, 2024 CA Tow-Away 0 0

Related records

Vehicle
2021 RAM 3500
NHTSA recalls and complaints for this make/model/year.
Recall
25V765000
AIR BAGS
Recall
24V436000
BACK OVER PREVENTION
Recall
23V060000
ELECTRICAL SYSTEM:WIRING:RELAYS/SOLENOIDS
Carrier
ENTERPRISE RENT-A-CAR COMPANY OF LOS ANGELES LLC
USDOT 2022631 · 127 crashes · 305 inspections
Vehicle
VIN: 3C63R3HL9MG635729
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
ENTERPRISE RENTACAR ALAMO RENTACAR NATIONAL CAR RENTAL ENTERPRISE TRUCK RENTAL
Crashes reported by this law-enforcement agency.
City
Crashes in PHILADELPHIA CITY, 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.