Skip to main content
TruckCodex
Hubs

Crash Record PA211745200X

FMCSA crash record in SAINT MARYS CITY on Dec 8, 2022.

Injury Federal Recordable

What happened

On December 8, 2022, FMCSA recorded an injury crash with 2 people hurt in SAINT MARYS CITY, Pennsylvania. The vehicle was operated by J B HUNT TRANSPORT INC (USDOT 80806). Recorded conditions: 1 / 8 / 1 pavement. Reported by J B HUNT, FMCSA reference PA211745200X.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
3
Carrier
J B HUNT TRANSPORT INC
USDOT 80806
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,983
62 fatal · 665 injury
Crashes per 100 power units (24 mo)
4.5
1,141 crashes · 25,280 units
Days since prior carrier crash
1
Last on Dec 7, 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 SAINT MARYS CITY, Pennsylvania, 9 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
8
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 #:
PA211745200X
Date:
Dec 8, 2022
Time:
1154
State:
Pennsylvania
City:
SAINT MARYS CITY
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
J B HUNT TRANSPORT INC (80806)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HSDZAPR2MN304372 3056355 (IN) J B HUNT 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
cmup2ni260035l4z8bfo4gqwe Sep 25, 2026 WV Tow-Away 0 0
cmup2ni6l00a5l4z8lj8lkal7 Sep 21, 2026 VA Tow-Away 0 0
cmup2ni7j00c3l4z84c012rvc Sep 18, 2026 VA Injury 0 1
cmup2ni5q008jl4z8n96c7s7h Sep 18, 2026 AZ Injury 0 1
cmtazy7md004ppmln3x7bxlz4 Aug 19, 2026 WI Tow-Away 0 0
cmscrzzyn000dpetuul8cenmo Jul 28, 2026 NJ Tow-Away 0 0
cmrzwwgrf000hpe21u3lc12ai Jul 21, 2026 AR Tow-Away 0 0
cmrss3uvs0009pefbcciqom1j Jul 16, 2026 AR Injury 0 1
cmrpwdsgo0007pe2c86mm3oha Jul 14, 2026 NJ Tow-Away 0 0
cmrn1fcbi006tpez5rx8luhwd Jul 8, 2026 VA Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 80806 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
J B HUNT TRANSPORT INC
USDOT 80806 · 19,597 crashes · 35,112 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3HSDZAPR2MN304372
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
J B HUNT
Crashes reported by this law-enforcement agency.
City
Crashes in SAINT MARYS 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.