Skip to main content

Crash Record ILX001939265

FMCSA crash record in Illinois on Jun 23, 2020.

Injury

What happened

On June 23, 2020, FMCSA recorded an injury crash with one person hurt in Illinois. The vehicle was operated by ATLASIB LLC (USDOT 2489236). FMCSA reference ILX001939265.

Carrier pattern note

This is the carrier's 4 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
ATLASIB LLC
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 injury · 4 tow-away
Crashes per 100 power units (24 mo)
7.3
11 crashes · 150 units
Days since prior carrier crash
35
Last on May 19, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,004 carriers

Geographic context

How this crash sits in its setting.

Within Illinois, 9,663 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 #:
ILX001939265
Date:
Jun 23, 2020
Time:
0244
State:
Illinois
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
ATLASIB LLC (2489236)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmrn1fc1i0001pez5pobjpzaf Jul 11, 2026 WY Injury 0 1
cr_5121226 Feb 4, 2026 MD Tow-Away 0 0
cr_5106096 Jan 25, 2026 AR Tow-Away 0 0
cr_5102917 Jan 15, 2026 IN Tow-Away 0 0
cr_5090821 Jan 9, 2026 KS Tow-Away 0 0
cr_5072734 Nov 26, 2025 TX Injury 0 1
cr_5072053 Nov 20, 2025 TX Injury 0 1
cr_5074347 Nov 17, 2025 IL Tow-Away 0 0
cr_5046878 Oct 23, 2025 AR Injury 0 1
cr_4927458 Apr 13, 2025 WV Tow-Away 0 0

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.