Crash Record NC0107386349

FMCSA crash record in APEX on Jun 20, 2023.

Injury Federal Recordable

What happened

On June 20, 2023, FMCSA recorded an injury crash with one person hurt in APEX, North Carolina. The vehicle was operated by GYPSUM EXPRESS LTD (USDOT 623098). Recorded conditions: 1 / 2 / 2 pavement. Reported by GYPSUM EXPRESS LTD, FMCSA reference NC0107386349.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

GYPSUM EXPRESS LTD

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 17 injury

Crashes per 100 power units (24 mo)

5.1

24 crashes · 471 units

Days since prior carrier crash

Last on Jun 13, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,672 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

WAKE COUNTY BOARD OF EDUCATION · 3 reports
PACIFIC TRUCKING INC · 2 reports
BUDGET TRUCK RENTAL LLC · 1 reports

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 #:: NC0107386349
Date:: Jun 20, 2023
Time:: 1819
State:: North Carolina
City:: APEX
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: GYPSUM EXPRESS LTD (623098)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	98	1FUJHPDV2LLLC4408	2276969 (IN)	GYPSUM EXPRESS LTD	3	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5103080	Feb 4, 2026	SC	Tow-Away	0
cr_5125785	Feb 2, 2026	IN	Injury	1
cr_5125959	Feb 2, 2026	PA	Tow-Away	0
cr_5061846	Nov 3, 2025	SC	Injury	1
cr_5052230	Oct 31, 2025	KY	Tow-Away	0
cr_5052635	Oct 23, 2025	WI	Tow-Away	0
cr_5019508	Aug 12, 2025	IN	Tow-Away	0
cr_4996009	Jul 28, 2025	IL	Tow-Away	0
cr_4997441	Jul 9, 2025	IN	Tow-Away	0
cr_5005788	Jun 29, 2025	OH	Injury	1

Related records

Vehicle

2020 FREIGHTLINER Cascadia

NHTSA recalls and complaints for this make/model/year.

Recall

23V299000

ELECTRONIC STABILITY CONTROL (ESC)

STEERING:LINKAGES:DRAG:LINK:CONNECTION

Carrier

GYPSUM EXPRESS LTD

USDOT 623098 · 619 crashes · 854 inspections

Vehicle

VIN: 1FUJHPDV2LLLC4408

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

State

Crashes in North Carolina

Statewide crash records.

Agency

GYPSUM EXPRESS LTD

Crashes reported by this law-enforcement agency.

City

Crashes in APEX, 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.