HaulerCheck · https://haulercheck.com/carrier/4217415-skyhigh-freight-inc/ · Checked 2026-10-19 06:10 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
SKYHIGH FREIGHT INC
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. Authority and insurance are last known from May 14, 2026.
- Operating authority is pending (last known)FMCSA has not granted the authority yet.
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, (916) 230-6947, not a number from an email or load board.
- Check that the MC number you were given is MC1629542.
- 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) | MC1629542 | Primary | SOUTHLAKE SPECIALTY INSURANCE COMPANY Policy TMA91001988 · 91X | $750,000 | Feb 12, 2026 | Cancelled Jun 4, 2026 |
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
5 of 23 · California avg 19.8%
4 of 34 · California avg 6.3%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Sep 16, 2026 | CA | 3 | 0 | No |
| Aug 28, 2026 | IA | 3 | 7 | No |
| Aug 27, 2026 | IL | 3 | 0 | No |
| Jul 29, 2026 | AZ | 2 | 11 | Yes |
| Jul 29, 2026 | CA | 3 | 1 | No |
| Jul 13, 2026 | IN | 3 | 1 | No |
| Jun 22, 2026 | CA | 2 | 0 | No |
| Apr 9, 2026 | IL | 2 | 2 | No |
| Feb 20, 2026 | AZ | 2 | 1 | Yes |
| Jan 5, 2026 | IL | 3 | 0 | No |
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 California average covers 398,428 vehicle and 509,934 driver inspections of all California-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
52 violations counted in FMCSA's Safety Measurement System (SMS), 11 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 94 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 | California share |
|---|---|---|---|---|
| Vehicle Maintenance | 26 | 7 | 50.0% | 71.7% |
| Hours-of-Service Compliance | 21 | 4 | 40.4% | 16.6% |
| Unsafe Driving | 5 | 0 | 9.6% | 8.0% |
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 | 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 |
| HOS (Property) - Failing to have a record of duty status using the method prescribed Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958A1HOSP | 2 | 2 |
| HOS (ELD) - In-Vehicle Information - Failing to have a supply of blank driver's records of duty status graph-grids sufficient to record the driver's duty status a EOBR Related · Hours-of-Service Compliance · code 39522H4ELDBRODS | 2 | 0 |
| Air Brake - ABS malfunction lamp defective on trailers manufactured on or after March 1 1998 Brakes All Others · Vehicle Maintenance · code 39355EB | 2 | 0 |
| Operating a CMV without documentation of a periodic inspection Inspection Reports · Vehicle Maintenance · code 39617CPI | 2 | 0 |
| Tires - Less than 2/32 inch tread depth Tires · Vehicle Maintenance · code 39375CTAOTDLT232 | 2 | 0 |
| HOS (Property) - Tampering with an ELD so that the device does not accurately record and retain required data. Explain: False Log · Hours-of-Service Compliance · code 3958EHOSPDELDT | 1 | 1 |
| HOS (Property) - Failing to have in possession RODS for the previous seven consecutive days and available for inspection while on duty Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958K2HOSP | 1 | 1 |
| Brake hose or tubing chafing and/or kinking Brakes All Others · Vehicle Maintenance · code 39345B2 | 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 California column is the mix across all California-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
Crash details
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| May 25, 2025 | KS | 0 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 4217415 |
|---|---|
| MC / docket | MC1629542 |
| Legal name | SKYHIGH FREIGHT INC |
| Operation | Interstate |
| Business type | — |
| Power units | 7 |
| Drivers | 7 |
| Annual mileage | 218,571 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Mar 28, 2024 · 2 years ago |
| Last MCS-150 update | Jul 31, 2025 |
Cargo carried
General Freight
Questions about SKYHIGH FREIGHT INC
What does SKYHIGH FREIGHT INC's operating authority allow?
FMCSA records show no active operating authority for SKYHIGH FREIGHT INC (MC1629542), so it may not haul regulated interstate freight for hire or broker loads under these dockets.
Which information about SKYHIGH FREIGHT INC 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 SKYHIGH FREIGHT INC?
Confirm the authority and insurance on the Motus record for USDOT 4217415. Call the company back on the phone number on file, (916) 230-6947, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1629542, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Rancho Cucamonga, CA →
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 06:10 UTC.