Skip to main content
TruckCodex
Hubs

Crash Record IN0904374484

FMCSA crash record in NEW CASTLE on Oct 17, 2023.

Injury Federal Recordable

What happened

On October 17, 2023, FMCSA recorded an injury crash with one person hurt in NEW CASTLE, Indiana. The vehicle was operated by APOLLO FREIGHT SYSTEMS INC (USDOT 3170105). Recorded conditions: 1 / 8 / 1 pavement. Reported by APOLLO FREIGHT SYSTEMS INC, FMCSA reference IN0904374484.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
APOLLO FREIGHT SYSTEMS INC
USDOT 3170105
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
3 injury · 9 tow-away
Crashes per 100 power units (24 mo)
9.2
12 crashes · 130 units
Days since prior carrier crash
148
Last on May 22, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,157 carriers

Geographic context

How this crash sits in its setting.

Within NEW CASTLE, Indiana, 18 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
1
Weather
8
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 #:
IN0904374484
Date:
Oct 17, 2023
Time:
0940
State:
Indiana
City:
NEW CASTLE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
APOLLO FREIGHT SYSTEMS INC (3170105)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 12 3AKJHHDR5RSUW8206 P1075458 (IL) APOLLO FREIGHT SYSTEMS INC 3 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
cr_5089632 Jan 14, 2026 OH Tow-Away 0 0
cr_5102317 Dec 31, 2025 PA Tow-Away 0 0
cr_5077204 Dec 10, 2025 TN Tow-Away 0 0
cr_5073122 Nov 10, 2025 WV Tow-Away 0 0
cr_5056387 Nov 4, 2025 VA Injury 0 1
cr_5046592 Oct 7, 2025 OH Injury 0 1
cr_4993661 Jun 25, 2025 GA Injury 0 2
cr_4936707 May 1, 2025 TN Tow-Away 0 0
cr_4931888 Apr 14, 2025 OK Injury 0 1
cr_4894436 Feb 12, 2025 NC Injury 0 2

Carrier booking & risk tools

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

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

Related records

Carrier
APOLLO FREIGHT SYSTEMS INC
USDOT 3170105 · 41 crashes · 510 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR5RSUW8206
Decode this VIN for make, model, year, and recall data.
State
Crashes in Indiana
Statewide crash records.
Agency
APOLLO FREIGHT SYSTEMS INC
Crashes reported by this law-enforcement agency.
City
Crashes in NEW CASTLE, IN
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.