TruckCodex
Hubs

Crash Record NC0107416439

FMCSA crash record in BURGAW on Jul 27, 2023.

Injury Federal Recordable

What happened

On July 27, 2023, FMCSA recorded an injury crash with one person hurt in BURGAW, North Carolina. The vehicle was operated by J B HUNT TRANSPORT INC (USDOT 80806). Recorded conditions: 1 / 1 / 1 pavement. Reported by J B HUNT TRANSPORT INC, FMCSA reference NC0107416439.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
J B HUNT TRANSPORT INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2,021
55 fatal · 650 injury
Crashes per 100 power units (24 mo)
4.8
1,220 crashes · 25,280 units
Days since prior carrier crash
2
Last on Jul 25, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within BURGAW, North Carolina, 26 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
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 #:
NC0107416439
Date:
Jul 27, 2023
Time:
1540
State:
North Carolina
City:
BURGAW
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
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 5 3HSDZAPR5NN784716 3201531 (IN) J B HUNT TRANSPORT INC 3 No

Crash event

Event sequence description.

1:11:NONCOLLISION:UNKNOWN

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
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
cmr5veuze002tp8npurvrd3st Jun 29, 2026 WV Injury 0 1
cmqnbop3s002vp8idtib6dn48 Jun 16, 2026 NJ Tow-Away 0 0
cmq1vv00c000xpbjqi4a8xti4 Jun 2, 2026 TN Tow-Away 0 0
cmouyr2tv005nnu1kuno8axt6 Apr 29, 2026 AL Injury 0 6

Related records

Carrier
J B HUNT TRANSPORT INC
USDOT 80806 · 19,593 crashes · 34,292 inspections
Vehicle
VIN: 3HSDZAPR5NN784716
Decode this VIN for make, model, year, and recall data.
State
Crashes in North Carolina
Statewide crash records.
Agency
J B HUNT TRANSPORT INC
Crashes reported by this law-enforcement agency.
City
Crashes in BURGAW, NC
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.