TruckCodex
Hubs

Crash Record PA112251300X

FMCSA crash record in DUNMORE BOROUGH on Dec 14, 2021.

Tow-Away Federal Recordable

What happened

On December 14, 2021, FMCSA recorded a tow-away crash with no reported injuries in DUNMORE BOROUGH, Pennsylvania. The vehicle was operated by FEDEX GROUND PACKAGE SYSTEM INC (USDOT 265752). Recorded conditions: 3 / 1 / 1 pavement. Reported by FEDEX GROUND, FMCSA reference PA112251300X.

Carrier pattern note

This is the carrier's 2833 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: 35 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FEDEX GROUND PACKAGE SYSTEM INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2,833
89 fatal · 984 injury
Crashes per 100 power units (24 mo)
0.1
115 crashes · 101,844 units
Days since prior carrier crash
1
Last on Dec 13, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,845 carriers

Geographic context

How this crash sits in its setting.

Within DUNMORE BOROUGH, Pennsylvania, 35 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
3
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 #:
PA112251300X
Date:
Dec 14, 2021
Time:
1655
State:
Pennsylvania
City:
DUNMORE BOROUGH
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FEDEX GROUND PACKAGE SYSTEM INC (265752)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4WC9EG7MN273283 AH01919 (PA) FEDEX GROUND 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
cmtdwm2os000dpmb912lq5gvt Aug 24, 2026 WY Injury 0 1
cr_5123971 Mar 11, 2026 TX Injury 0 1
cr_5099818 Jan 21, 2026 NM Injury 0 1
cr_5093015 Jan 20, 2026 MI Tow-Away 0 0
cr_5090944 Jan 17, 2026 VA Tow-Away 0 0
cr_5106462 Jan 11, 2026 TX Injury 0 1
cr_5083060 Dec 26, 2025 AL Injury 0 1
cr_5103301 Dec 20, 2025 NY Injury 0 2
cr_5089808 Dec 14, 2025 CT Tow-Away 0 0
cr_5083799 Dec 6, 2025 NY Injury 0 3

Related records

Carrier
FEDEX GROUND PACKAGE SYSTEM INC
USDOT 265752 · 17,192 crashes · 0 inspections
Vehicle
VIN: 4V4WC9EG7MN273283
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
FEDEX GROUND
Crashes reported by this law-enforcement agency.
City
Crashes in DUNMORE BOROUGH, 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.