TruckCodex
Hubs

Crash Record PA301065200X

FMCSA crash record in GREAT BEND TOWNSHIP on Jan 8, 2023.

Injury Federal Recordable

What happened

On January 8, 2023, FMCSA recorded an injury crash with one person hurt in GREAT BEND TOWNSHIP, Pennsylvania. The vehicle was operated by THE MUSKET TRANSPORT LTD (USDOT 580397). Recorded conditions: 2 / 1 / 1 pavement. Reported by THE MUSKET TRANSPORT LTD, FMCSA reference PA301065200X.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
THE MUSKET TRANSPORT LTD
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
10
3 injury · 10 tow-away
Crashes per 100 power units (24 mo)
0.4
3 crashes · 730 units
Days since prior carrier crash
25
Last on Dec 14, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,847 carriers

Geographic context

How this crash sits in its setting.

Within GREAT BEND TOWNSHIP, Pennsylvania, 11 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 #:
PA301065200X
Date:
Jan 8, 2023
Time:
2334
State:
Pennsylvania
City:
GREAT BEND TOWNSHIP
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
THE MUSKET TRANSPORT LTD (580397)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 98 4V4WC9EH7NN308723 PA54596 (ON) THE MUSKET TRANSPORT LTD 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_5108889 Jan 15, 2026 PA Fatal 1 2
cr_5084507 Dec 1, 2025 NY Injury 0 1
cr_5003959 Jun 2, 2025 NY Fatal 1 0
cr_4816207 Aug 9, 2024 NJ Tow-Away 0 0
cr_4878534 Jul 11, 2024 NJ Tow-Away 0 0
cr_4727445 Apr 1, 2024 NY Injury 0 1
cr_4694526 Jan 16, 2024 PA Tow-Away 0 0
cr_4555573 May 8, 2023 NY Injury 0 1
cr_4507628 Jan 25, 2023 NY Tow-Away 0 0
cr_4760842 Jan 25, 2023 NY Tow-Away 0 0

Related records

Carrier
THE MUSKET TRANSPORT LTD
USDOT 580397 · 143 crashes · 409 inspections
Vehicle
VIN: 4V4WC9EH7NN308723
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
THE MUSKET TRANSPORT LTD
Crashes reported by this law-enforcement agency.
City
Crashes in GREAT BEND 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.