TruckCodex
Hubs

Crash Record AL0004719916

FMCSA crash record in RURAL MOBILE on Nov 7, 2024.

Tow-Away Federal Recordable

What happened

On November 7, 2024, FMCSA recorded a tow-away crash with no reported injuries in RURAL MOBILE, Alabama. The vehicle was operated by FEDERAL EXPRESS CORPORATION (USDOT 86876). Recorded conditions: 3 / 1 / 1 pavement. Reported by FEDEX EXPRESS FEDEX, FMCSA reference AL0004719916.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FEDERAL EXPRESS CORPORATION
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,031
20 fatal · 380 injury
Crashes per 100 power units (24 mo)
1.8
2,459 crashes · 138,481 units
Days since prior carrier crash
1
Last on Nov 6, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,845 carriers

Geographic context

How this crash sits in its setting.

Within RURAL MOBILE, Alabama, 95 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 #:
AL0004719916
Date:
Nov 7, 2024
Time:
1705
State:
Alabama
City:
RURAL MOBILE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FEDERAL EXPRESS CORPORATION (86876)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1GB3G3BG2E1186022 5A05T6X (AL) FEDEX EXPRESS FEDEX 2 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
cmu507cav000hpmtod4z1831t Sep 13, 2026 ME Tow-Away 0 0
cmu507ces005rpmtow13xvjpw Sep 9, 2026 NJ Tow-Away 0 0
cmtzbpprh000zpmsr5qlx21nw Sep 8, 2026 VA Injury 0 1
cmtqq5agv001zpmkttbo81660 Sep 2, 2026 NJ Injury 0 2
cmtmftnpq002vpmdxdrb4lbq3 Aug 28, 2026 KY Tow-Away 0 0
cmtl0dt2a002zpm66q8qu1cl3 Aug 27, 2026 NC Tow-Away 0 0
cmtfchmfj0009pmjnybpu3leu Aug 26, 2026 OK Tow-Away 0 0
cmtdwm2p5000ppmb9mlqlgnkh Aug 24, 2026 NJ Tow-Away 0 0
cmtazy7j7001bpmln8osd34ic Aug 20, 2026 OH Injury 0 1
cmt5ony23005fpmdm8265vd2x Aug 17, 2026 NJ Tow-Away 0 0

Related records

Vehicle
2014 CHEVROLET Express
NHTSA recalls and complaints for this make/model/year.
Recall
18V295000
VISIBILITY:POWER WINDOW DEVICES AND CONTROLS
Recall
18V267000
EQUIPMENT
Recall
16V184000
TIRES:PRESSURE MONITORING AND REGULATING SYSTEMS
Carrier
FEDERAL EXPRESS CORPORATION
USDOT 86876 · 9,255 crashes · 26,389 inspections
Vehicle
VIN: 1GB3G3BG2E1186022
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
Agency
FEDEX EXPRESS FEDEX
Crashes reported by this law-enforcement agency.
City
Crashes in RURAL MOBILE, 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.