Crash Record SC0021463954

FMCSA crash record in LEXINGTON on Dec 29, 2021.

Injury Federal Recordable

What happened

On December 29, 2021, FMCSA recorded an injury crash with 2 people hurt in LEXINGTON, South Carolina. The vehicle was operated by E J POPE & SON INC (USDOT 338658). Recorded conditions: 1 / 1 pavement. Reported by POPE TRANSPORT CO, FMCSA reference SC0021463954.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

E J POPE & SON INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 6 injury

Crashes per 100 power units (24 mo)

4.0

2 crashes · 50 units

Days since prior carrier crash

Last on Nov 16, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 312,693 carriers

Geographic context

How this crash sits in its setting.

Within LEXINGTON, South Carolina, 92 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

AVERITT EXPRESS INC · 2 reports
SOUTH CAROLINA DEPARTMENT OF EDUCATION · 2 reports
TRAFFIC CONTROL SAFETY SERVICES INC · 2 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: —
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 #:: SC0021463954
Date:: Dec 29, 2021
Time:: 1200
State:: South Carolina
City:: LEXINGTON
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 4
Carrier (USDOT):: E J POPE & SON INC (338658)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	6	13	3AKJHTDV1MSMG6053	3048718 (IN)	POPE TRANSPORT CO	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
cr_5058212	Sep 24, 2025	NC	Tow-Away	0
cr_4904457	Mar 7, 2025	NC	Injury	1
cr_4749695	May 16, 2024	NC	Tow-Away	0
cr_4741644	May 4, 2024	NC	Tow-Away	0
cr_4656150	Oct 17, 2023	GA	Injury	1
cr_4594457	Jul 23, 2023	NC	Tow-Away	0
cr_4589595	Jul 7, 2023	SC	Tow-Away	0
cr_4555188	May 8, 2023	NC	Tow-Away	0
cr_4555808	May 8, 2023	SC	Injury	1
cr_4406168	Aug 19, 2022	VA	Tow-Away	0

Related records

Vehicle

2021 FREIGHTLINER Cascadia

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

Recall

23V299000

ELECTRONIC STABILITY CONTROL (ESC)

STEERING:LINKAGES:DRAG:LINK:CONNECTION

Carrier

E J POPE & SON INC

USDOT 338658 · 149 crashes · 0 inspections

Vehicle

VIN: 3AKJHTDV1MSMG6053

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

State

Crashes in South Carolina

Statewide crash records.

Agency

POPE TRANSPORT CO

Crashes reported by this law-enforcement agency.

City

Crashes in LEXINGTON, SC

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.