TruckCodex
Hubs

Crash Record IN0904030652

FMCSA crash record in OSCEOLA on May 9, 2022.

Tow-Away Federal Recordable

What happened

On May 9, 2022, FMCSA recorded a tow-away crash with no reported injuries in OSCEOLA, Indiana. The vehicle was operated by MOONLIGHT LOGISTICS INC (USDOT 1579552). Recorded conditions: 1 / 1 / 1 pavement. Reported by MOONLIGHT LOGISTICS INC, FMCSA reference IN0904030652.

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
0
Vehicles
1
Carrier
MOONLIGHT LOGISTICS INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
1 fatal · 2 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 62 units
Days since prior carrier crash
8
Last on May 1, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,672 carriers

Geographic context

How this crash sits in its setting.

Within OSCEOLA, Indiana, 6 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
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 #:
IN0904030652
Date:
May 9, 2022
Time:
1730
State:
Indiana
City:
OSCEOLA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
MOONLIGHT LOGISTICS INC (1579552)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XKYD49X1LJ424983 P1027546 (IL) MOONLIGHT LOGISTICS INC 3 No

Crash event

Event sequence description.

3:17:COLLISION INVOLVING ANIMAL;1:11:NONCOLLISION:UNKNOWN;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4492876 Dec 30, 2022 IN Tow-Away 0 0
cr_4428107 Aug 8, 2022 MS Injury 0 1
cr_4408350 Jul 24, 2022 IN Tow-Away 0 0
cr_4388146 Jul 6, 2022 TX Fatal 4 3
cr_4413482 Jun 22, 2022 IL Tow-Away 0 0
cr_4367828 May 18, 2022 FL Tow-Away 0 0
cr_4364263 May 1, 2022 MS Injury 0 1
cr_4275381 Oct 21, 2021 IN Tow-Away 0 0
cr_4200704 Jun 24, 2021 IN Tow-Away 0 0
cr_4148606 Apr 23, 2021 PA Tow-Away 0 0

Related records

Vehicle
2020 KENWORTH T680
NHTSA recalls and complaints for this make/model/year.
Recall
24V145000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V00N000
ELECTRICAL SYSTEM:WIRING
Carrier
MOONLIGHT LOGISTICS INC
USDOT 1579552 · 37 crashes · 0 inspections
Vehicle
VIN: 1XKYD49X1LJ424983
Decode this VIN for make, model, year, and recall data.
State
Crashes in Indiana
Statewide crash records.
Agency
MOONLIGHT LOGISTICS INC
Crashes reported by this law-enforcement agency.
City
Crashes in OSCEOLA, 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.