Skip to main content

Crash Record AL0009681654

FMCSA crash record in Alabama on Jul 1, 2019.

Injury

What happened

On July 1, 2019, FMCSA recorded an injury crash with one person hurt in Alabama. The vehicle was operated by FREEDOM TRANS LLC (USDOT 2930566). FMCSA reference AL0009681654.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
—
Carrier
FREEDOM TRANS LLC
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
7
1 injury · 7 tow-away
Crashes per 100 power units (24 mo)
7.5
9 crashes · 120 units
Days since prior carrier crash
32
Last on May 30, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,004 carriers

Geographic context

How this crash sits in its setting.

Within Alabama, 5,407 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 #:
AL0009681654
Date:
Jul 1, 2019
Time:
0910
State:
Alabama
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
FREEDOM TRANS LLC (2930566)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5120500 Mar 17, 2026 MI Tow-Away 0 0
cr_5086842 Jan 3, 2026 AR Tow-Away 0 0
cr_4995909 Jul 31, 2025 IL Tow-Away 0 0
cr_4996755 Jun 17, 2025 IN Tow-Away 0 0
cr_4953472 Apr 30, 2025 IN Injury 0 1
cr_4929223 Mar 11, 2025 GA Tow-Away 0 0
cr_4883786 Jan 23, 2025 TX Injury 0 1
cr_4874271 Jan 10, 2025 NC Injury 0 1
cr_4858457 Dec 8, 2024 NE Injury 0 1
cr_4774188 Jun 12, 2024 IL Injury 0 1

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.