Skip to main content
TruckCodex
Hubs

Crash Record AL0001617353

FMCSA crash record in RURAL MACON on Feb 19, 2021.

Tow-Away Federal Recordable

What happened

On February 19, 2021, FMCSA recorded a tow-away crash with no reported injuries in RURAL MACON, Alabama. The vehicle was operated by PAN AMERICAN EXPRESS INC (USDOT 347196). Recorded conditions: 3 / 1 / 1 pavement. Reported by PAN AMERICAN EXPRESS INC, FMCSA reference AL0001617353.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 90 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
1
Carrier
PAN AMERICAN EXPRESS INC
USDOT 347196
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
14
1 fatal · 5 injury
Crashes per 100 power units (24 mo)
3.7
7 crashes · 191 units
Days since prior carrier crash
114
Last on Oct 28, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,367 carriers

Geographic context

How this crash sits in its setting.

Within RURAL MACON, Alabama, 90 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
3
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 #:
AL0001617353
Date:
Feb 19, 2021
Time:
0245
State:
Alabama
City:
RURAL MACON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
PAN AMERICAN EXPRESS INC (347196)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDR5KSKE8727 R345664 (TX) PAN AMERICAN EXPRESS INC 2 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
cr_5103531 Jan 25, 2026 AR Injury 0 1
cr_5067597 Nov 6, 2025 IL Injury 0 1
cr_5059797 Nov 4, 2025 MO Tow-Away 0 0
cr_5011133 Jun 17, 2025 TX Injury 0 1
cr_4937936 Apr 22, 2025 TX Tow-Away 0 0
cr_4903545 Feb 19, 2025 IL Tow-Away 0 0
cr_4906179 Feb 12, 2025 IN Injury 0 1
cr_4750139 May 7, 2024 TX Tow-Away 0 0
cr_4641037 Oct 8, 2023 TX Tow-Away 0 0
cr_4600085 Jun 16, 2023 TX Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2019 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V105000
STEERING:LINKAGES:DRAG:LINK:CONNECTION
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V919000
TIRES
Carrier
PAN AMERICAN EXPRESS INC
USDOT 347196 · 185 crashes · 548 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR5KSKE8727
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
Agency
PAN AMERICAN EXPRESS INC
Crashes reported by this law-enforcement agency.
City
Crashes in RURAL MACON, AL
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.