TruckCodex
Hubs

Crash Record DE3021044558

FMCSA crash record in WILMINGTON on Jun 10, 2021.

Tow-Away Federal Recordable

What happened

On June 10, 2021, FMCSA recorded a tow-away crash with no reported injuries in WILMINGTON, Delaware. The vehicle was operated by A J BLOSENSKI INC (USDOT 593732). Recorded conditions: 1 / 1 / 1 pavement. Reported by A J BLOSENSKI INC, FMCSA reference DE3021044558.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 109 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
1
Carrier
A J BLOSENSKI INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
12
4 injury · 12 tow-away
Crashes per 100 power units (24 mo)
4.0
7 crashes · 176 units
Days since prior carrier crash
1
Last on Jun 9, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within WILMINGTON, Delaware, 109 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 #:
DE3021044558
Date:
Jun 10, 2021
Time:
1037
State:
Delaware
City:
WILMINGTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
A J BLOSENSKI INC (593732)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1M2P267C03M065466 AG23424 (PA) A J BLOSENSKI INC 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5071479 Dec 2, 2025 PA Tow-Away 0 0
cr_5006997 Jun 5, 2025 PA Tow-Away 0 0
cr_4905809 Mar 6, 2025 PA Tow-Away 0 0
cr_4895627 Jan 28, 2025 PA Tow-Away 0 0
cr_4864618 Dec 19, 2024 PA Tow-Away 0 0
cr_4832974 Oct 8, 2024 PA Tow-Away 0 0
cr_4808693 Aug 29, 2024 PA Tow-Away 0 0
cr_4804944 Aug 13, 2024 PA Tow-Away 0 0
cr_4792719 Jul 12, 2024 PA Tow-Away 0 0
cr_4744127 Apr 30, 2024 PA Tow-Away 0 0

Related records

Vehicle
2003 MACK RD
NHTSA recalls and complaints for this make/model/year.
Recall
10V069000
POWER TRAIN:AXLE ASSEMBLY
Carrier
A J BLOSENSKI INC
USDOT 593732 · 76 crashes · 205 inspections
Vehicle
VIN: 1M2P267C03M065466
Decode this VIN for make, model, year, and recall data.
State
Crashes in Delaware
Statewide crash records.
Agency
A J BLOSENSKI INC
Crashes reported by this law-enforcement agency.
City
Crashes in WILMINGTON, DE
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.