Crash Record ILX003119146
FMCSA crash record in E ST LOUIS TWP on Aug 15, 2023.
Tow-Away
Federal Recordable
What happened
On August 15, 2023, FMCSA recorded a tow-away crash with no reported injuries in E ST LOUIS TWP, Illinois. The vehicle was operated by JIMBASS TRANSPORTATION LLC (USDOT 4097711). Recorded conditions: 1 / 1 / 1 pavement. Reported by JIMBASS TRANSPORTATION LLC, FMCSA reference ILX003119146.
Geographic note
This crash is part of an active corridor: 45 crashes occurred in the same city in the past 24 months.
Fatalities
0
Injuries
0
Vehicles
1
Vehicle Type
Truck
Severity
Tow-Away
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 1 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,577,319 carriers
Geographic context
How this crash sits in its setting.
Within E ST LOUIS TWP, Illinois, 45 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- ALUPUR TRANSPORT INC · 1 reports
- BEELMAN TRUCK CO · 1 reports
- AJS XPRESS LLC · 1 reports
Contributing factors
What the responding officer recorded.
- Light
- 1
- 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 #:
- ILX003119146
- Date:
- Aug 15, 2023
- Time:
- 1920
- State:
- Illinois
- City:
- E ST LOUIS TWP
- Fatalities:
- 0
- Injuries:
- 0
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 1
- Carrier (USDOT):
- JIMBASS TRANSPORTATION LLC (4097711)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | — | 5 | 3C63RRHL6NG266834 | 178547C (IL) | JIMBASS TRANSPORTATION LLC | 3 | No |
Other crashes by this carrier
8 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_4768879 | May 29, 2024 | NJ | Tow-Away | 0 | 0 |
| cr_4634873 | Sep 30, 2023 | PA | Tow-Away | 0 | 0 |
| cr_4630363 | Sep 24, 2023 | LA | Injury | 0 | 3 |
| cr_4709169 | Sep 19, 2023 | IL | Tow-Away | 0 | 0 |
| cr_4631920 | Sep 14, 2023 | MI | Tow-Away | 0 | 0 |
| cr_4611878 | Aug 27, 2023 | AZ | Tow-Away | 0 | 0 |
| cr_4608188 | Aug 21, 2023 | NC | Injury | 0 | 1 |
| cr_4612289 | Aug 18, 2023 | NH | Tow-Away | 0 | 0 |
Carrier booking & risk tools
Check booking and risk signals for USDOT 4097711 — tools open pre-filled.
Related records
Vehicle
2022 RAM 3500
NHTSA recalls and complaints for this make/model/year.
Recall
25V765000
AIR BAGS
Recall
24V436000
BACK OVER PREVENTION
Recall
24V415000
ELECTRONIC STABILITY CONTROL (ESC)
Carrier
JIMBASS TRANSPORTATION LLC
USDOT 4097711 · 9 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3C63RRHL6NG266834
Decode this VIN for make, model, year, and recall data.
State
Crashes in Illinois
Statewide crash records.
Agency
JIMBASS TRANSPORTATION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in E ST LOUIS TWP, IL
All crashes on file for this city.
Station
IL-3
Weigh / inspection station matching this crash location.
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.