TruckCodex
Hubs

Crash Record IN0904226926

FMCSA crash record in DAYTON on Feb 15, 2023.

Tow-Away Federal Recordable

What happened

On February 15, 2023, FMCSA recorded a tow-away crash with no reported injuries in DAYTON, Indiana. The vehicle was operated by EVANS DELIVERY COMPANY INC (USDOT 38111). Recorded conditions: 1 / 7 / 1 pavement. Reported by EVANS DELIVERY COMPANY INC, FMCSA reference IN0904226926.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
EVANS DELIVERY COMPANY INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
489
13 fatal · 168 injury
Crashes per 100 power units (24 mo)
5.3
287 crashes · 5,445 units
Days since prior carrier crash
2
Last on Feb 13, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,836 carriers

Geographic context

How this crash sits in its setting.

Within DAYTON, Indiana, 16 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
7
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 #:
IN0904226926
Date:
Feb 15, 2023
Time:
0930
State:
Indiana
City:
DAYTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
EVANS DELIVERY COMPANY INC (38111)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 13 1XKDD49X26J143472 3250513 (IN) EVANS DELIVERY COMPANY INC 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmouyr2tx005pnu1k9aeruhmh Apr 30, 2026 NJ Injury 0 1
cmogoa8dz001vnvt8egwjxw0v Apr 21, 2026 KY Injury 0 1
cmo6itlhn00evo1aufvw619fb Apr 9, 2026 SC Injury 0 2
cmo6itllr00huo1auwioumpsh Apr 8, 2026 TN Tow-Away 0 0
cmny3yh2l0123k38v24i6gcjb Mar 31, 2026 AR Tow-Away 0 0
cr_5125914 Mar 19, 2026 TX Tow-Away 0 0
cr_5124292 Mar 12, 2026 GA Tow-Away 0 0
cr_5125223 Mar 12, 2026 NC Tow-Away 0 0
cr_5113062 Feb 26, 2026 NC Tow-Away 0 0
cr_5119006 Feb 24, 2026 GA Tow-Away 0 0

Related records

Vehicle
2006 KENWORTH T8 Series
NHTSA recalls and complaints for this make/model/year.
Carrier
EVANS DELIVERY COMPANY INC
USDOT 38111 · 2,579 crashes · 8,820 inspections
Vehicle
VIN: 1XKDD49X26J143472
Decode this VIN for make, model, year, and recall data.
State
Crashes in Indiana
Statewide crash records.
Agency
EVANS DELIVERY COMPANY INC
Crashes reported by this law-enforcement agency.
City
Crashes in DAYTON, 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.