HaulerCheck · https://haulercheck.com/carrier/2012801-jose-avalos/ · Checked 2026-10-19 07:50 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
JOSE AVALOS
Doing business as AVALOS TRUCKING
No risk signals in the last-known data
How risk signals workNothing 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.
No cargo cover filed with FMCSA
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.
What to verify next
- Confirm authority and insurance on the official Motus record ↗: our copy is the last known status from May 14, 2026. Safety record: SAFER ↗.
- Call back on the number on file, (509) 398-0215, not a number from an email or load board.
- Check that the MC number you were given is MC724713.
- Ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
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.
| Type | Docket | Layer | Insurer | Coverage | Effective | Status |
|---|---|---|---|---|---|---|
| Liability (BI&PD) | MC724713 | Primary | UNITED FINANCIAL CASUALTY COMPANY Policy CA02813666 · 91X | $750,000 | Jan 16, 2022 | Active |
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 18, 2024 – Oct 18, 2026
4 of 11 · Washington avg 24.5%
2 of 16 · Washington avg 4.9%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Jul 17, 2026 | WA | 2 | 4 | Yes |
| Feb 24, 2026 | NV | 3 | 0 | No |
| Jan 13, 2026 | WA | 2 | 4 | Yes |
| Dec 30, 2025 | NV | 3 | 0 | No |
| Aug 27, 2025 | ID | 1 | 4 | No |
| Aug 13, 2025 | WA | 2 | 0 | No |
| Aug 11, 2025 | AZ | 2 | 6 | No |
| Jul 22, 2025 | OR | 2 | 2 | Yes |
| Jul 2, 2025 | OR | 3 | 3 | Yes |
| Jun 25, 2025 | WA | 3 | 2 | Yes |
How these rates are calculated
Period: Oct 18, 2024 – Oct 18, 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 Washington average covers 48,815 vehicle and 83,315 driver inspections of all Washington-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
46 violations counted in FMCSA's Safety Measurement System (SMS), 9 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 38 violations above?
The inspections section's number counts every violation written on the inspection reports in our Oct 18, 2024 – Oct 18, 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) | Violations | Out of service | Share | Washington share |
|---|---|---|---|---|
| Vehicle Maintenance | 33 | 6 | 71.7% | 71.3% |
| Hours-of-Service Compliance | 8 | 1 | 17.4% | 12.4% |
| Driver Fitness | 4 | 2 | 8.7% | 3.9% |
| Unsafe Driving | 1 | 0 | 2.2% | 12.0% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| Driver cannot satisfy the English language proficiency requirements of 391.11(b)(2) in accordance with the current corresponding FMCSA enforcement guidance (391. General Driver Qualification · Driver Fitness · code 39111B2Q | 3 | 2 |
| Air Brake - Audible air leak at a proper connection Brakes All Others · Vehicle Maintenance · code 39345DB | 3 | 0 |
| Air Brake - CMV other than truck-tractor manufactured on or after March 1 1998 not equipped with an antilock brake system. System does not function or indicates Brakes All Others · Vehicle Maintenance · code 39355C2B | 3 | 0 |
| Air Brake - ABS malfunction lamp defective on trailers manufactured on or after March 1 1998 Brakes All Others · Vehicle Maintenance · code 39355EB | 3 | 0 |
| Operating a CMV without documentation of a periodic inspection Inspection Reports · Vehicle Maintenance · code 39617CPI | 3 | 0 |
| Brake - Defective brake(s) are equal to or greater than 20% of the service brakes on the vehicle/combination Brake Out Of Service · Vehicle Maintenance · code 3963A1BOS | 2 | 2 |
| Tires - All others leaking or inflation less than 50% of the maximum inflation pressure on tire not equipped with ATIS Tires · Vehicle Maintenance · code 39375A3TAOL | 2 | 2 |
| HOS - False record of duty status driver improper use of Personal Conveyance - Not OOS False Log · Hours-of-Service Compliance · code 3958E1PC | 2 | 0 |
| Windshield - Damaged or Discolored Windshield/ Glass/ Markings · Vehicle Maintenance · code 39360C | 2 | 0 |
| HOS (Property) - Driver produces a false record of duty status that concealed an HOS limitation violation after the last rest period. Explain: False Log · Hours-of-Service Compliance · code 3958EHOSPDOOS | 1 | 1 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 18, 2026. "Share" is this company's mix of violations; the Washington column is the mix across all Washington-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 18, 2024 – Oct 18, 2026
No reportable crashes in this period.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 2012801 |
|---|---|
| MC / docket | MC724713 |
| Legal name | JOSE AVALOS |
| DBA name | AVALOS TRUCKING |
| Operation | Interstate |
| Business type | — |
| Power units | 5 |
| Drivers | 5 |
| Annual mileage | 462,913 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Mar 28, 2010 · 16 years ago |
| Last MCS-150 update | Dec 19, 2025 |
Cargo carried
General FreightLogs, Poles, Beams, LumberBuilding MaterialsFresh ProduceGrain, Feed, HayMeatRefrigerated FoodConstructionOtherWater
Questions about JOSE AVALOS
What does JOSE AVALOS's operating authority allow?
MC724713: Common carrier (may haul regulated property for hire for the general public).
Which information about JOSE AVALOS 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. FMCSA has not issued a safety rating, which means no compliance review is on record, not that the carrier is unsafe.
What should I verify before booking JOSE AVALOS?
Confirm the authority and insurance on the Motus record for USDOT 2012801. Call the company back on the phone number on file, (509) 398-0215, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC724713, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Quincy, WA →
Company details from the FMCSA Company Census File (Oct 18, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).
Page generated 2026-10-19 07:50 UTC.