Skip to main content
TruckCodex
Hubs

Crash Record GA0009240013

FMCSA crash record in TIFTON on Nov 22, 2023.

Injury Federal Recordable

What happened

On November 22, 2023, FMCSA recorded an injury crash with one person hurt in TIFTON, Georgia. The vehicle was operated by COCA-COLA BOTTLING COMPANY UNITED INC (USDOT 251147). Recorded conditions: 2 / 1 pavement. Reported by COCA-COLA BOTTLING COMPANY UNITED INC, FMCSA reference GA0009240013.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
COCA-COLA BOTTLING COMPANY UNITED INC
USDOT 251147
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
60
1 fatal · 26 injury
Crashes per 100 power units (24 mo)
0.7
15 crashes · 2,266 units
Days since prior carrier crash
1
Last on Nov 21, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within TIFTON, Georgia, 25 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
2
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 #:
GA0009240013
Date:
Nov 22, 2023
Time:
0603
State:
Georgia
City:
TIFTON
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
COCA-COLA BOTTLING COMPANY UNITED INC (251147)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHLDV9NSMV8952 3079884 (IN) COCA-COLA BOTTLING COMPANY UNITED 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 Fatalities Injuries
cr_4933796 Mar 17, 2025 AL Tow-Away 0 0
cr_4912942 Mar 15, 2025 LA Tow-Away 0 0
cr_4922909 Feb 27, 2025 FL Tow-Away 0 0
cr_4892577 Feb 13, 2025 LA Tow-Away 0 0
cr_4889247 Jan 25, 2025 LA Injury 0 1
cr_4882918 Jan 24, 2025 AL Injury 0 2
cr_4880788 Jan 16, 2025 AZ Tow-Away 0 0
cr_4889222 Jan 16, 2025 LA Tow-Away 0 0
cr_4886766 Jan 9, 2025 GA Injury 0 1
cr_4873380 Dec 20, 2024 LA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2022 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
26V583000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V299000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V238000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
COCA-COLA BOTTLING COMPANY UNITED INC
USDOT 251147 · 369 crashes · 695 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHLDV9NSMV8952
Decode this VIN for make, model, year, and recall data.
State
Crashes in Georgia
Statewide crash records.
Agency
COCA-COLA BOTTLING COMPANY UNITED INC
Crashes reported by this law-enforcement agency.
City
Crashes in TIFTON, GA
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.