Skip to main content
TruckCodex
Hubs

Crash Record PA207572000X

FMCSA crash record in MIDDLE PAXTON TOWNSHIP on Jun 24, 2022.

Tow-Away Federal Recordable

What happened

On June 24, 2022, FMCSA recorded a tow-away crash with no reported injuries in MIDDLE PAXTON TOWNSHIP, Pennsylvania. The vehicle was operated by CHALLENGER MOTOR FREIGHT INC (USDOT 247765). Recorded conditions: 2 / 1 / 1 pavement. Reported by CHALLENGER MOTOR FREIGHT INC, FMCSA reference PA207572000X.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
CHALLENGER MOTOR FREIGHT INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
23
1 fatal · 6 injury
Crashes per 100 power units (24 mo)
1.3
11 crashes · 833 units
Days since prior carrier crash
10
Last on Jun 14, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,864 carriers

Geographic context

How this crash sits in its setting.

Within MIDDLE PAXTON TOWNSHIP, Pennsylvania, 18 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 #:
PA207572000X
Date:
Jun 24, 2022
Time:
0040
State:
Pennsylvania
City:
MIDDLE PAXTON TOWNSHIP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CHALLENGER MOTOR FREIGHT INC (247765)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XPBD49X4HD423820 8261PY (ON) CHALLENGER MOTOR FREIGHT 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
cr_5115770 Feb 26, 2026 TX Tow-Away 0 0
cr_5102582 Jan 25, 2026 OH Tow-Away 0 0
cr_5070758 Dec 2, 2025 OH Tow-Away 0 0
cr_5080132 Dec 2, 2025 PA Tow-Away 0 0
cr_5035900 Sep 22, 2025 OH Tow-Away 0 0
cr_5005228 Jul 25, 2025 OH Tow-Away 0 0
cr_5025387 Jun 10, 2025 IN Injury 0 1
cr_4901059 Feb 26, 2025 OH Tow-Away 0 0
cr_4856368 Nov 25, 2024 IL Tow-Away 0 0
cr_4896462 Nov 17, 2024 MO Fatal 3 3

Related records

Carrier
CHALLENGER MOTOR FREIGHT INC
USDOT 247765 · 530 crashes · 807 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XPBD49X4HD423820
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
CHALLENGER MOTOR FREIGHT INC
Crashes reported by this law-enforcement agency.
City
Crashes in MIDDLE PAXTON 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.