Crash Record NC0107629570

FMCSA crash record in GREENSBORO on Feb 14, 2024.

Injury Federal Recordable

What happened

On February 14, 2024, FMCSA recorded an injury crash with 2 people hurt in GREENSBORO, North Carolina. The vehicle was operated by GREENBUSH LOGISTICS INC (USDOT 159292). Recorded conditions: 1 / 1 / 1 pavement. Reported by GREENBUSH LOGISTICS INC, FMCSA reference NC0107629570.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

GREENBUSH LOGISTICS INC

USDOT 159292

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 8 injury

Crashes per 100 power units (24 mo)

5.9

21 crashes · 357 units

Days since prior carrier crash

Last on Jan 16, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,254 carriers

Geographic context

How this crash sits in its setting.

Within GREENSBORO, North Carolina, 470 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

CITY OF GREENSBORO · 8 reports
GUILFORD COUNTY BOARD OF EDUCATION · 4 reports
GUILFORD COUNTY BOARD OF EDU · 3 reports

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 #:: NC0107629570
Date:: Feb 14, 2024
Time:: 0938
State:: North Carolina
City:: GREENSBORO
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: GREENBUSH LOGISTICS INC (159292)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	3	1XKZD49X6HJ164415	1202639 (AL)	GREENBUSH LOGISTICS INC	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	Injuries
cmqesjpmu003xp4usbftnnxbp	Jun 8, 2026	AL	Tow-Away	0
cr_5115370	Feb 27, 2026	AR	Tow-Away	0
cr_5106795	Feb 3, 2026	TX	Tow-Away	0
cr_5082643	Dec 29, 2025	PA	Tow-Away	0
cr_5082414	Dec 23, 2025	GA	Tow-Away	0
cr_5073509	Dec 11, 2025	AL	Injury	2
cr_5034690	Sep 12, 2025	GA	Injury	2
cr_5019996	Aug 22, 2025	LA	Tow-Away	0
cr_5012498	Jul 15, 2025	TX	Injury	1
cr_5089240	Jun 30, 2025	NC	Injury	1

Carrier booking & risk tools

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

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

Related records

Carrier

GREENBUSH LOGISTICS INC

USDOT 159292 · 295 crashes · 660 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XKZD49X6HJ164415

Decode this VIN for make, model, year, and recall data.

State

Crashes in North Carolina

Statewide crash records.

Agency

GREENBUSH LOGISTICS INC

Crashes reported by this law-enforcement agency.

City

Crashes in GREENSBORO, NC

All crashes on file for this city.

Station

Weigh / inspection station matching this crash location.

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.