Crash Record AZ0002932225

FMCSA crash record in Arizona on Feb 11, 2015.

Tow-Away

What happened

On February 11, 2015, FMCSA recorded a tow-away crash with no reported injuries in Arizona. The vehicle was operated by ARIZONA PIPELINE COMPANY INC (USDOT 349324). FMCSA reference AZ0002932225.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
Carrier
ARIZONA PIPELINE COMPANY INC
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
1 injury · 5 tow-away
Crashes per 100 power units (24 mo)
1.1
5 crashes · 449 units
Days since prior carrier crash
114
Last on Oct 20, 2014
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,685 carriers

Geographic context

How this crash sits in its setting.

Within Arizona, 4,441 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 #:
AZ0002932225
Date:
Feb 11, 2015
Time:
1730
State:
Arizona
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5083093 Dec 19, 2025 AZ Tow-Away 0 0
cr_5062458 Oct 21, 2025 CA Injury 0 1
cr_4946891 Apr 29, 2025 NV Tow-Away 0 0
cr_4923573 Mar 28, 2025 CA Tow-Away 0 0
cr_5041757 Sep 8, 2024 CA Tow-Away 0 0
cr_4757523 May 21, 2024 CA Tow-Away 0 0
cr_4750183 May 15, 2024 CA Tow-Away 0 0
cr_4747001 Apr 22, 2024 CA Tow-Away 0 0
cr_4720167 Mar 12, 2024 AZ Tow-Away 0 0
cr_4720763 Feb 13, 2024 NV 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.