Crash Record GA0003426973

FMCSA crash record in Georgia on Jun 21, 2010.

Injury

What happened

On June 21, 2010, FMCSA recorded an injury crash with 2 people hurt in Georgia. The vehicle was operated by ATLANTA BEVERAGE COMPANY AGGP (USDOT 913575). FMCSA reference GA0003426973.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
Carrier
ATLANTA BEVERAGE COMPANY AGGP
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
4 injury · 5 tow-away
Crashes per 100 power units (24 mo)
2.7
3 crashes · 111 units
Days since prior carrier crash
292
Last on Sep 2, 2009
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within Georgia, 15,645 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
GA0003426973
Date:
Jun 21, 2010
Time:
1618
State:
Georgia
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5066896 Nov 11, 2025 GA Injury 0 1
cr_5044079 Oct 6, 2025 GA Injury 0 1
cr_5026795 Aug 27, 2025 GA Tow-Away 0 0
cr_4734299 Mar 15, 2024 GA Tow-Away 0 0
cr_4690535 Dec 28, 2023 GA Tow-Away 0 0
cr_4649679 Oct 17, 2023 GA Tow-Away 0 0
cr_4595687 Jul 13, 2023 GA Tow-Away 0 0
cr_4590169 Jun 29, 2023 GA Injury 0 1
cr_4474160 Oct 11, 2022 GA Injury 0 1
cr_4422038 Jun 21, 2022 GA Tow-Away 0 0

Related records

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.