Crash Record NY001022330A

FMCSA crash record in New York on Mar 29, 2000.

Tow-Away

What happened

On March 29, 2000, FMCSA recorded a tow-away crash with no reported injuries in New York. The vehicle was operated by 410648 ONTARIO LTD (USDOT 440301). FMCSA reference NY001022330A.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
Carrier
410648 ONTARIO LTD
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 fatal · 2 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 50 units
Days since prior carrier crash
369
Last on Mar 26, 1999
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,424 carriers

Geographic context

How this crash sits in its setting.

Within New York, 6,333 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 #:
NY001022330A
Date:
Mar 29, 2000
Time:
2015
State:
New York
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
410648 ONTARIO LTD (440301)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4202308 Aug 11, 2021 MI Tow-Away 0 0
cr_4106778 Jan 28, 2021 KY Tow-Away 0 0
cr_4103786 Jan 21, 2021 MI Tow-Away 0 0
cr_3898899 Dec 1, 2019 PA Tow-Away 0 0
cr_3866012 Oct 19, 2019 NY Tow-Away 0 0
cr_3849470 Aug 22, 2019 MI Tow-Away 0 0
cr_3857652 Aug 15, 2019 PA Tow-Away 0 0
cr_3739370 Jan 22, 2019 MI Tow-Away 0 0
cr_3584324 Apr 24, 2018 VA Injury 0 1
cr_3528265 Jan 17, 2018 NY Tow-Away 0 0

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.