TruckCodex
Hubs

Crash Record GA0010053356

FMCSA crash record in MACON on Sep 22, 2025.

Injury Federal Recordable

What happened

On September 22, 2025, FMCSA recorded an injury crash with one person hurt in MACON, Georgia. The vehicle was operated by TRANSCO INC (USDOT 1062707). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference GA0010053356.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
3
Carrier
TRANSCO INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
145
6 fatal · 56 injury
Crashes per 100 power units (24 mo)
5.7
107 crashes · 1,879 units
Days since prior carrier crash
19
Last on Sep 3, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within MACON, Georgia, 344 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
1
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 #:
GA0010053356
Date:
Sep 22, 2025
Time:
2014
State:
Georgia
City:
MACON
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
TRANSCO INC (1062707)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHTDV5RDUR5524 P966248 (IL) TRANSCO 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
cmsw88sbn00brpev35q6lzche Aug 7, 2026 WA Tow-Away 0 0
cms76vgs40033pehvzaihtgx2 Jul 23, 2026 ME Tow-Away 0 0
cmouyr2te004vnu1kusqxu6aj Apr 29, 2026 VA Injury 0 2
cr_5124533 Mar 16, 2026 PA Tow-Away 0 0
cr_5126131 Mar 14, 2026 NJ Injury 0 1
cr_5125705 Mar 12, 2026 GA Tow-Away 0 0
cr_5126994 Mar 5, 2026 CO Tow-Away 0 0
cr_5119841 Mar 2, 2026 MS Tow-Away 0 0
cr_5118319 Feb 19, 2026 ID Injury 0 2
cr_5116492 Feb 16, 2026 IN Injury 0 1

Related records

Carrier
TRANSCO INC
USDOT 1062707 · 2,043 crashes · 2,366 inspections
Vehicle
VIN: 3AKJHTDV5RDUR5524
Decode this VIN for make, model, year, and recall data.
State
Crashes in Georgia
Statewide crash records.
City
Crashes in MACON, 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.