AA & S CORPORATION

Doing business as A & R TRANSPORT

Brigham City, UT · Interstate · 13 power units · Safety rating: Satisfactory · USDOT since Aug 25, 1989 (37 years)

No risk signals in the last-known data

How risk signals work

Nothing in the FMCSA record matched our risk signals. That is not a guarantee, and it does not confirm who you are talking to; follow the checks below. Authority and insurance are last known from May 14, 2026.

Confirm on Motus ↗ Call (435) 744-2201 Safety: SAFER ↗
Operating authority
Last known: Active
MC205992: Contract carrier active
Last known · FMCSA snapshot May 14, 2026
Liability insurance (BI&PD)
$1,000,000
Required minimum: $750,000
No cargo cover filed with FMCSA
Last known · FMCSA snapshot May 14, 2026
Vehicle out-of-service rate
0.0%
Only 4 vehicle inspections; too few to compare
FMCSA inspections · Oct 19, 2024 – Oct 19, 2026

Not a live check. FMCSA has not published a Motus record for this carrier, so authority and insurance show the last known status from May 14, 2026. Confirm on Motus ↗ before booking.

Confirm on Motus ↗Call

Operating authority

MC205992 Last known · FMCSA snapshot May 14, 2026

Contract carrier
Contract Carrier
Active
Liability insurance on file$1,000,000 (required: $750,000)

Last known status. This authority record comes from the FMCSA snapshot of May 14, 2026, the last one published before FMCSA moved registration to Motus. It may have changed since. Confirm current authority: Motus record for USDOT 363751 ↗

Insurance on file

Liability (BI&PD) pays for injury and damage to other people and property; it does not cover the freight. Cargo insurance covers the freight. FMCSA only requires cargo filings from household goods carriers and freight forwarders, so most carriers file none: ask for a cargo certificate that fits your load. No cargo cover filed with FMCSA.

TypeDocketLayerInsurerCoverageEffectiveStatus
Liability (BI&PD)MC205992PrimaryGREAT WEST CASUALTY CO.
Policy GRT08273A · 91X
$1,000,000Sep 15, 2023Active

Source: Last known · FMCSA snapshot May 14, 2026. Identical filings repeated in the FMCSA data are shown once; a filing listed under two dockets is one policy, not extra coverage. Coverage is the maximum amount filed with FMCSA, not the full policy.

Last known filings. Insurance for this carrier comes from the FMCSA snapshot of May 14, 2026. Policies may have been cancelled or replaced since. Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.

Roadside inspections Oct 19, 2024 – Oct 19, 2026

24inspections
0.0%vehicle out-of-service
0 of 4 · Utah avg 23.6%
0.0%driver out-of-service
0 of 24 · Utah avg 4.5%
17violations written on inspection reports
10 most recent inspections
DateStateLevelViolationsOut of service
Sep 9, 2026UT30No
Jun 19, 2026UT30No
Jun 9, 2026UT30No
Mar 30, 2026MT30No
Mar 27, 2026MT30No
Mar 18, 2026UT31No
Feb 19, 2026WA32No
Jan 19, 2026MT33No
Jan 13, 2026MT30No
Dec 30, 2025UT30No
How these rates are calculated

Period: Oct 19, 2024 – Oct 19, 2026. Vehicle rate = vehicle inspections with a vehicle out-of-service order ÷ vehicle inspections (levels 1, 2, 5 and 6). Driver rate uses levels 1, 2, 3 and 6. The Utah average covers 22,772 vehicle and 39,441 driver inspections of all Utah-based carriers in this period. It mixes every type of operation, so compare with care; rates based on a handful of inspections say little. FMCSA's own SMS measures are weighted differently: SMS profile ↗ · SAFER snapshot ↗

Violations in FMCSA's SMS last 24 months

12 violations counted in FMCSA's Safety Measurement System (SMS), 2 of them serious enough to put the driver or vehicle out of service.

Why is this different from the 17 violations above?

The inspections section's number counts every violation written on the inspection reports in our Oct 19, 2024 – Oct 19, 2026 window. The SMS count comes from FMCSA's own monthly SMS snapshot, which uses its own 24-month window and only the violations it scores. Both are FMCSA figures; they measure different things.

Category (FMCSA BASIC)ViolationsOut of serviceShareUtah share
Hours-of-Service Compliance5041.7%12.6%
Unsafe Driving4033.3%9.8%
Vehicle Maintenance2116.7%73.3%
Driver Fitness118.3%3.3%
10 most frequent violations
ViolationTimesOut of service
HOS (ELD) - Driver failing to review records and certify the accuracy of the information.
Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1ELDDFR
20
State/Local Laws - Speeding 6-10 miles per hour over the speed limit
Speeding 2 · Unsafe Driving · code 3922SLLS2
20
License (CDL) - Operate a CMV and does not possess a valid CDL
License-related: High · Driver Fitness · code 38323A2LCDLN
11
Hubs - Leaking hub
Wheels Studs Clamps Etc. · Vehicle Maintenance · code 3965HL
11
HOS (Property) - Driving beyond the 14 hour after coming on duty following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Tim
Hours · Hours-of-Service Compliance · code 3953A2HOSPD
10
HOS (ELD) - Driver failing to certify the record immediately after the final required entry has been made or corrected for the 24 hour period.
Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B2ELDDFC24
10
HOS (Form) - Paper Log/Logging Programs Form and Manner
Other Log/Form & Manner · Hours-of-Service Compliance · code 3958A
10
Driver - Move over/slow law - Failure to yield right of way to authorized emergency vehicles
Dangerous Driving · Unsafe Driving · code 3922DMOVE
10
State/Local Laws - Lane restriction violation
Misc Violations · Unsafe Driving · code 3922SLLLR
10
Air Brake - Hose/tubing damaged or not secured
Brakes All Others · Vehicle Maintenance · code 39345B2BAIR
10

Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 19, 2026. "Share" is this company's mix of violations; the Utah column is the mix across all Utah-based carriers, so you can see which kinds of problems stand out. A high count partly reflects fleet size and how often trucks are inspected.

Crashes Oct 19, 2024 – Oct 19, 2026

2crashes
0fatal
1injury
1tow-away
2 most recent crashes
DateLocationFatalitiesInjuries
Aug 3, 20254.06 W Brothers, OR00
Jul 3, 2025Sunset, UT01

Reportable crashes do not imply the carrier was at fault.

Company details FMCSA census · Oct 19, 2026

USDOT number363751
MC / docketMC205992
Legal nameAA & S CORPORATION
DBA nameA & R TRANSPORT
OperationInterstate
Business typeCorporation
Power units13
Drivers13
Annual mileage1,030,232 (2024)
HazmatNo
Safety ratingSatisfactory (Dec 15, 2011)
USDOT number addedAug 25, 1989 · 37 years ago
Last MCS-150 updateJan 7, 2026

Cargo carried

General FreightMetal: Sheets, Coils, RollsLogs, Poles, Beams, LumberBuilding MaterialsMachinery, Large ObjectsConstruction

Change history

No changes to name, contact details, authority or insurance since we started tracking on Oct 18, 2026. We compare every company's FMCSA record each day.

to see it on your watchlist when something changes.

Questions about AA & S CORPORATION

What does AA & S CORPORATION's operating authority allow?

MC205992: Contract carrier (may haul regulated property for hire under continuing contracts with specific shippers).

Which information about AA & S CORPORATION is old or missing?

Operating authority is the last known status from the FMCSA snapshot of May 14, 2026, not a current check. Insurance filings are from the same May 14, 2026 snapshot. There are too few vehicle inspections in the last 24 months to judge the out-of-service rate.

What should I verify before booking AA & S CORPORATION?

Confirm the authority and insurance on the Motus record for USDOT 363751. Call the company back on the phone number on file, (435) 744-2201, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC205992, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.

Company details from the FMCSA Company Census File (Oct 19, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).

Page generated 2026-10-20 07:08 UTC.