TruckCodex
Hubs

Crash Record AZ0000013564

FMCSA crash record in UNKNOWN on Mar 10, 2022.

Tow-Away Federal Recordable

What happened

On March 10, 2022, FMCSA recorded a tow-away crash with no reported injuries in UNKNOWN, Arizona. The vehicle was operated by AUSLANDER CORPORATION (USDOT 674045). Recorded conditions: 2 / 1 / 1 pavement. Reported by AUSCOR TRANSPORTATION SERVICES, FMCSA reference AZ0000013564.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
AUSLANDER CORPORATION
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
8
3 injury · 8 tow-away
Crashes per 100 power units (24 mo)
5.6
1 crashes · 18 units
Days since prior carrier crash
91
Last on Dec 9, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 313,483 carriers

Geographic context

How this crash sits in its setting.

Within UNKNOWN, Arizona, 414 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
2
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 #:
AZ0000013564
Date:
Mar 10, 2022
Time:
1942
State:
Arizona
City:
UNKNOWN
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
AUSLANDER CORPORATION (674045)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3ALXFB006KDKK2100 AW499H (NJ) AUSCOR TRANSPORTATION SERVICES 3 No

Crash event

Event sequence description.

1:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5014391 Aug 5, 2025 TX Injury 0 2
cr_4803313 Aug 17, 2024 IN Injury 0 1
cr_4791637 Jul 27, 2024 MO Tow-Away 0 0
cr_4779418 Jun 13, 2024 PA Tow-Away 0 0
cr_4618240 Sep 8, 2023 PA Tow-Away 0 0
cr_4379795 Jun 30, 2022 AZ Tow-Away 0 0
cr_4318023 Mar 11, 2022 NV Injury 0 2
cr_4297727 Dec 9, 2021 CA Injury 0 1
cr_4113469 Jan 24, 2021 MO Tow-Away 0 0
cr_4079400 Nov 9, 2020 NJ Tow-Away 0 0

Related records

Carrier
AUSLANDER CORPORATION
USDOT 674045 · 116 crashes · 156 inspections
Vehicle
VIN: 3ALXFB006KDKK2100
Decode this VIN for make, model, year, and recall data.
State
Crashes in Arizona
Statewide crash records.
Agency
AUSCOR TRANSPORTATION SERVICES
Crashes reported by this law-enforcement agency.
City
Crashes in UNKNOWN, AZ
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.