TruckCodex
Hubs

Crash Record PA303206400X

FMCSA crash record in DUNMORE BOROUGH on Mar 29, 2023.

Tow-Away Federal Recordable

What happened

On March 29, 2023, FMCSA recorded a tow-away crash with no reported injuries in DUNMORE BOROUGH, Pennsylvania. The vehicle was operated by CORE X GRESS TRANSPORTATION LLC (USDOT 3476018). Recorded conditions: 3 / 1 / 1 pavement. Reported by RLS GRESS TRANSPORTATION LLC, FMCSA reference PA303206400X.

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
1
Carrier
CORE X GRESS TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
1 injury · 3 tow-away
Crashes per 100 power units (24 mo)
13.6
3 crashes · 22 units
Days since prior carrier crash
208
Last on Sep 2, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 313,835 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 #:
PA303206400X
Date:
Mar 29, 2023
Time:
0351
State:
Pennsylvania
City:
DUNMORE BOROUGH
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
CORE X GRESS TRANSPORTATION LLC (3476018)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XKYD49X7LJ347486 AH03205 (PA) RLS GRESS TRANSPORTATION LLC 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT;3:18:COLLISION INVOLVING FIXED OBJECT;4:17:COLLISION INVOLVING ANIMAL;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

8 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmq4psc3l000npb36pazzylwy Jun 3, 2026 PA Tow-Away 0 0
cr_5032035 Sep 4, 2025 CT Tow-Away 0 0
cr_4900074 Jan 15, 2025 PA Tow-Away 0 0
cr_4621820 Sep 11, 2023 MN Tow-Away 0 0
cr_4638050 Sep 9, 2023 PA Injury 0 1
cr_4418361 Sep 2, 2022 PA Injury 0 1
cr_4257735 Nov 16, 2021 PA Tow-Away 0 0
cr_4130917 Feb 22, 2021 PA Injury 0 1

Related records

Vehicle
2020 KENWORTH T680
NHTSA recalls and complaints for this make/model/year.
Recall
24V145000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V00N000
ELECTRICAL SYSTEM:WIRING
Carrier
CORE X GRESS TRANSPORTATION LLC
USDOT 3476018 · 9 crashes · 45 inspections
Vehicle
VIN: 1XKYD49X7LJ347486
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
RLS GRESS TRANSPORTATION LLC
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.