Crash Record SC0023287016
FMCSA crash record in SPRINGDALE on Nov 27, 2023.
What happened
On November 27, 2023, FMCSA recorded a tow-away crash with no reported injuries in SPRINGDALE, South Carolina. The vehicle was operated by SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC (USDOT 54283). Recorded conditions: 1 / 8 / 1 pavement. Reported by SWIFT TRANSPORTATION CO OF ARIZONA LLC, FMCSA reference SC0023287016.
Carrier pattern note
This is the carrier's 990 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.
This carrier's crash pattern
Derived from the carrier's full crash history.
Geographic context
How this crash sits in its setting.
Within SPRINGDALE, South Carolina, 12 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- CANDELARIO FOMPEROSA, LUIS ALBERTO · 1 reports
- C R LEVESQUE TRUCKING CORP · 1 reports
- ACTIVE DAY FLEET INC · 1 reports
Contributing factors
What the responding officer recorded.
- Light
- 1
- Weather
- 8
- 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 #:
- SC0023287016
- Date:
- Nov 27, 2023
- Time:
- 0820
- State:
- South Carolina
- City:
- SPRINGDALE
- Fatalities:
- 0
- Injuries:
- 0
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 1
- Carrier (USDOT):
- SWIFT TRANSPORTATION COMPANY OF ARIZONA LLC (54283)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 9 | 3 | 3AKJHHDR1PSUF0374 | 3226901 (IN) | SWIFT TRANSPORTATION CO OF ARIZONA LLC | 3 | No |
Crash event
Event sequence description.
1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT
Other crashes by this carrier
10 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cmrn1fcc0007vpez5e22v1hyc | Jul 8, 2026 | IA | Tow-Away | 0 | 0 |
| cmrd638yj0011p8pq7huct9ay | Jul 4, 2026 | GA | Injury | 0 | 1 |
| cmqxb77ce0069p8f0vlotdce9 | Jun 22, 2026 | AR | Tow-Away | 0 | 0 |
| cmq1vv02s003hpbjqlgbhqsvb | May 31, 2026 | KY | Tow-Away | 0 | 0 |
| cmp993806002pnu4jyeljpeby | May 11, 2026 | VA | Tow-Away | 0 | 0 |
| cmoweinxt000tnud54bindmpw | May 2, 2026 | VA | Tow-Away | 0 | 0 |
| cmokyirjc001pnv1d2z3h1u6r | Apr 24, 2026 | NC | Tow-Away | 0 | 0 |
| cmny3yfqd0040k38vr6p1f2fi | Apr 7, 2026 | KY | Tow-Away | 0 | 0 |
| cmny3yfqf0041k38vnr01a0bu | Apr 7, 2026 | IA | Tow-Away | 0 | 0 |
| cmny3yfyo00c5k38vfhdufwum | Apr 4, 2026 | VA | Injury | 0 | 1 |
Related records
How to evaluate a carrier's crash record
- Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
- Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
- Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
- Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
- Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.
Frequently asked questions about FMCSA crash records
What does this crash report tell me about the carrier? ▾
Was this crash the carrier's fault? ▾
How does this crash affect the carrier's safety scores? ▾
Will this crash show up on the carrier's CSA SMS scores? ▾
How do I check the carrier's full crash history? ▾
What if details look wrong — how do I correct an FMCSA crash record? ▾
Data sources & freshness
TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.
Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.