Skip to main content
TruckCodex
Hubs

Crash Record NY3388615100

FMCSA crash record in New York on May 4, 2011.

Tow-Away

What happened

On May 4, 2011, FMCSA recorded a tow-away crash with no reported injuries in New York. The vehicle was operated by DELFINO INSULATION CO INC (USDOT 1362312). FMCSA reference NY3388615100.

Fatalities
0
Injuries
0
Vehicles
—
Carrier
DELFINO INSULATION CO INC
Vehicle Type
—
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 · 23 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,932 carriers

Geographic context

How this crash sits in its setting.

Within New York, 5,811 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
NY3388615100
Date:
May 4, 2011
Time:
1107
State:
New York
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

7 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4722850 Mar 25, 2024 NY Injury 0 2
cr_4255976 Sep 21, 2021 NY Tow-Away 0 0
cr_4170619 Feb 3, 2021 NY Tow-Away 0 0
cr_4069417 Aug 31, 2020 NY Fatal 1 1
cr_3204621 Apr 29, 2016 NY Tow-Away 0 0
cr_2943922 Nov 5, 2014 NY Injury 0 4
cr_2798120 Nov 13, 2013 NY Injury 0 1

Carrier booking & risk tools

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

Related records

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.