Skip to main content
TruckCodex
Hubs

Crash Record GA4316083301

FMCSA crash record in Georgia on Jul 28, 2004.

Injury

What happened

On July 28, 2004, FMCSA recorded an injury crash with one person hurt in Georgia. The vehicle was operated by OXFORD CONSTRUCTION COMPANY (USDOT 669167). FMCSA reference GA4316083301.

Fatalities
0
Injuries
1
Vehicles
—
Carrier
USDOT 669167
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
2 injury · 2 tow-away
Crashes per 100 power units (24 mo)
2.9
3 crashes · 102 units
Days since prior carrier crash
628
Last on Nov 8, 2002
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,189 carriers

Geographic context

How this crash sits in its setting.

Within Georgia, 13,902 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 #:
GA4316083301
Date:
Jul 28, 2004
Time:
1008
State:
Georgia
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5026043 Aug 19, 2025 GA Tow-Away 0 0
cr_4992506 Mar 6, 2025 GA Injury 0 2
cr_4992520 Dec 2, 2024 GA Tow-Away 0 0
cr_4708852 Nov 18, 2023 GA Tow-Away 0 0
cr_4498498 Nov 17, 2022 GA Tow-Away 0 0
cr_3960255 Mar 20, 2020 GA Injury 0 1
cr_3666259 Sep 20, 2018 GA Injury 0 1
cr_3544448 Jan 22, 2018 GA Tow-Away 0 0
cr_3717483 Oct 19, 2017 GA Fatal 1 0
cr_3373619 Mar 7, 2017 GA Tow-Away 0 0

Carrier booking & risk tools

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

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.