TruckCodex
Hubs

Crash Record NC0106600841

FMCSA crash record in RAEFORD on Jun 11, 2021.

Injury Federal Recordable

What happened

On June 11, 2021, FMCSA recorded an injury crash with one person hurt in RAEFORD, North Carolina. The vehicle was operated by XYLEM I LLC (USDOT 2520441). Recorded conditions: 1 / 1 / 1 pavement. Reported by XYLEM TREE EXPERTS, FMCSA reference NC0106600841.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
XYLEM I LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
17
1 fatal · 10 injury
Crashes per 100 power units (24 mo)
0.7
11 crashes · 1,558 units
Days since prior carrier crash
10
Last on Jun 1, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,835 carriers

Geographic context

How this crash sits in its setting.

Within RAEFORD, North Carolina, 31 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 #:
NC0106600841
Date:
Jun 11, 2021
Time:
0644
State:
North Carolina
City:
RAEFORD
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
XYLEM I LLC (2520441)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 98 3ALACWFD0JDJN1376 48586TB (VA) XYLEM TREE EXPERTS 2 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_5113234 Feb 19, 2026 MS Tow-Away 0 0
cr_5110067 Feb 11, 2026 GA Tow-Away 0 0
cr_5102794 Feb 2, 2026 GA Tow-Away 0 0
cr_5072006 Nov 20, 2025 TX Tow-Away 0 0
cr_5065526 Oct 29, 2025 AR Tow-Away 0 0
cr_5046862 Oct 21, 2025 AR Tow-Away 0 0
cr_4998613 Jul 31, 2025 KY Injury 0 1
cr_5000176 Jul 18, 2025 ME Injury 0 1
cr_4943536 May 15, 2025 SC Tow-Away 0 0
cr_4865619 Dec 23, 2024 NC Injury 0 4

Related records

Vehicle
2018 FREIGHTLINER M2
NHTSA recalls and complaints for this make/model/year.
Recall
21V484000
EXTERIOR LIGHTING
Recall
21V002000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Carrier
XYLEM I LLC
USDOT 2520441 · 65 crashes · 87 inspections
Vehicle
VIN: 3ALACWFD0JDJN1376
Decode this VIN for make, model, year, and recall data.
State
Crashes in North Carolina
Statewide crash records.
Agency
XYLEM TREE EXPERTS
Crashes reported by this law-enforcement agency.
City
Crashes in RAEFORD, 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.