HaulerCheck · https://haulercheck.com/carrier/2329752-osso-corporation/ · Checked 2026-10-19 20:14 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
OSSO CORPORATION
Review before booking · 1 signal
How risk signals workFacts from the FMCSA record that call for a closer look. They are not a finding of wrongdoing.
- Vehicle out-of-service rate well above the state average35.5% vs Utah average 23.6%.
No cargo cover filed with FMCSA
Green means the FMCSA record shows it. It does not confirm who you are talking to, or that a policy covers your specific load.
What to verify next
- Confirm authority and insurance on the official Motus record ↗. Safety record: SAFER ↗.
- Call back on the number on file, (213) 465-4839, not a number from an email or load board.
- Check that the MC number you were given is MC795318.
- 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) | MC795318 | — | MSIG Specialty Insurance USA Inc Policy AWT1000113-00 · BMC-91X | $1,000,000 | Oct 1, 2026 | Active |
Source: FMCSA Motus · Oct 19, 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.
Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.
Roadside inspections Oct 19, 2024 – Oct 19, 2026
11 of 31 · Utah avg 23.6%
6 of 74 · Utah avg 4.5%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 14, 2026 | AZ | 3 | 2 | No |
| Oct 7, 2026 | CO | 3 | 3 | No |
| Oct 5, 2026 | ID | 3 | 0 | No |
| Sep 17, 2026 | CA | 2 | 2 | No |
| Sep 3, 2026 | CA | 3 | 3 | No |
| Sep 3, 2026 | TX | 1 | 5 | No |
| Aug 17, 2026 | OR | 2 | 1 | Yes |
| Jul 24, 2026 | LA | 3 | 2 | No |
| Jul 16, 2026 | CA | 2 | 0 | No |
| Jul 10, 2026 | CA | 3 | 1 | No |
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
69 violations counted in FMCSA's Safety Measurement System (SMS), 20 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 132 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) | Violations | Out of service | Share | Utah share |
|---|---|---|---|---|
| Vehicle Maintenance | 27 | 13 | 39.1% | 73.3% |
| Hours-of-Service Compliance | 24 | 4 | 34.8% | 12.6% |
| Unsafe Driving | 15 | 0 | 21.7% | 9.8% |
| Driver Fitness | 3 | 3 | 4.3% | 3.3% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 4 | 0 |
| HOS (Property) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958EHOSPD | 3 | 0 |
| HOS (ELD) - Driver failing to review records and certify the accuracy of the information. Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1ELDDFR | 3 | 0 |
| Light Weight Vehicles - Improper securement of automobiles light trucks and vans Improper Load Securement · Vehicle Maintenance · code 393128BCLWV | 2 | 2 |
| Tires - Front weight carried exceeds tire load limit Tire vs. Load · Vehicle Maintenance · code 39375GTFWETL | 2 | 2 |
| HOS (Property) - Driving more than 11 hours following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Time Hours · Hours-of-Service Compliance · code 3953A1HOSPD | 2 | 1 |
| HOS (ELD) - On request by an authorized safety official a driver must produce and transfer from an ELD the driver's hours of service records in accordance with t Fail to transfer ELD records · Hours-of-Service Compliance · code 39524DELDPT | 2 | 0 |
| 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 | 2 | 0 |
| 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 | 2 | 0 |
| State/Local Laws - Failed to obey a traffic control device - Permanent or Temporary - e.g. safety official signal sign light lane marking other Dangerous Driving · Unsafe Driving · code 3922SLLTCD | 2 | 0 |
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
2 most recent crashes
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Jun 10, 2025 | Camarillo, CA | 0 | 0 |
| Dec 3, 2024 | Not Listed, TX | 0 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 2329752 |
|---|---|
| MC / docket | MC795318 |
| Legal name | OSSO CORPORATION |
| Operation | Interstate |
| Business type | — |
| Power units | 25 |
| Drivers | 25 |
| Annual mileage | 2,345,000 (2025) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Jul 31, 2012 · 14 years ago |
| Last MCS-150 update | Jan 21, 2026 |
Cargo carried
General FreightHousehold GoodsMotor VehiclesFresh ProduceMeatRefrigerated FoodBeveragesPaper Products
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 OSSO CORPORATION
What does OSSO CORPORATION's operating authority allow?
MC795318: Motor carrier (may haul regulated property for hire).
Which information about OSSO CORPORATION is old or missing?
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 OSSO CORPORATION?
Confirm the authority and insurance on the Motus record for USDOT 2329752. Call the company back on the phone number on file, (213) 465-4839, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC795318, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in American Fork, UT →
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-19 20:14 UTC.