Skip to main content
TruckCodex
Hubs

Crash Record NC0107287427

FMCSA crash record in CONCORD on Mar 22, 2023.

Injury Federal Recordable

What happened

On March 22, 2023, FMCSA recorded an injury crash with one person hurt in CONCORD, North Carolina. The vehicle was operated by UNITRANS LLC (USDOT 2997967). Recorded conditions: 1 / 2 / 2 pavement. Reported by UNITRANS LLC, FMCSA reference NC0107287427.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 129 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
UNITRANS LLC
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)
16.0
8 crashes · 50 units
Days since prior carrier crash
34
Last on Feb 16, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,194 carriers

Geographic context

How this crash sits in its setting.

Within CONCORD, North Carolina, 129 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
2
Road surface
2

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 #:
NC0107287427
Date:
Mar 22, 2023
Time:
1234
State:
North Carolina
City:
CONCORD
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
UNITRANS LLC (2997967)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 98 1FUJHHDR4KLKZ9149 2863410 (IN) UNITRANS LLC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4992406 May 16, 2025 GA Tow-Away 0 0
cr_4941389 Apr 7, 2025 GA Tow-Away 0 0
cr_4909685 Mar 11, 2025 MO Tow-Away 0 0
cr_4840775 Nov 9, 2024 TN Tow-Away 0 0
cr_4843915 Oct 22, 2024 GA Injury 0 2
cr_4826368 Oct 4, 2024 MO Tow-Away 0 0
cr_4816380 Sep 29, 2024 AL Tow-Away 0 0
cr_4820499 Sep 27, 2024 SC Tow-Away 0 0
cr_4823201 Sep 10, 2024 TX Injury 0 1
cr_4792931 Aug 2, 2024 VA Injury 0 1

Related records

Carrier
UNITRANS LLC
USDOT 2997967 · 25 crashes · 263 inspections
Vehicle
VIN: 1FUJHHDR4KLKZ9149
Decode this VIN for make, model, year, and recall data.
State
Crashes in North Carolina
Statewide crash records.
Agency
UNITRANS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in CONCORD, 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.