HaulerCheck · https://haulercheck.com/carrier/3455753-eagle-transit-inc/ · Checked 2026-10-19 06:20 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: FMCSA Motus · Oct 18, 2026
EAGLE TRANSIT INC
No risk signals found
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.
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, (650) 546-5285, not a number from an email or load board.
- Check that the MC number you were given is MC1126398.
- 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) | MC1126398 | — | National Union Fire Insurance Company of Pittsburgh, Pa. Policy 025823327 · BMC-91X | $750,000 | May 23, 2026 | Active |
Source: FMCSA Motus · Oct 18, 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 18, 2024 – Oct 18, 2026
0 of 0 · California avg 19.8%
0 of 9 · California avg 6.3%
9 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 6, 2026 | CA | 3 | 0 | No |
| May 8, 2026 | CA | 3 | 0 | No |
| May 3, 2026 | CA | 3 | 0 | No |
| Jan 16, 2026 | NV | 3 | 0 | No |
| Dec 2, 2025 | CA | 3 | 0 | No |
| Nov 10, 2025 | UT | 3 | 1 | No |
| Sep 17, 2025 | CA | 3 | 0 | No |
| Jul 25, 2025 | NV | 3 | 1 | No |
| Jun 6, 2025 | CA | 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
1 violation counted in FMCSA's Safety Measurement System (SMS), 0 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 2 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 |
|---|---|---|---|---|
| Unsafe Driving | 1 | 0 | 100.0% | 8.0% |
1 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| 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 | 1 | 0 |
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
4 most recent crashes
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Apr 23, 2026 | Not Reported, UT | 0 | 0 |
| Nov 14, 2025 | Modesto, CA | 0 | 1 |
| Oct 12, 2025 | Wells, NV | 0 | 1 |
| Sep 17, 2025 | Industry, CA | 0 | 1 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 3455753 |
|---|---|
| MC / docket | MC1126398 |
| Legal name | EAGLE TRANSIT INC |
| Operation | Interstate |
| Business type | — |
| Power units | 8 |
| Drivers | 9 |
| Annual mileage | 68,679 (2024) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Jul 17, 2020 · 6 years ago |
| Last MCS-150 update | Dec 15, 2025 |
Cargo carried
General FreightBeverages
Questions about EAGLE TRANSIT INC
What does EAGLE TRANSIT INC's operating authority allow?
MC1126398: Motor carrier (may haul regulated property for hire).
Which information about EAGLE TRANSIT INC is old or missing?
There are too few vehicle inspections in the last 24 months to judge the out-of-service rate. 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 EAGLE TRANSIT INC?
Confirm the authority and insurance on the Motus record for USDOT 3455753. Call the company back on the phone number on file, (650) 546-5285, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1126398, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Manteca, 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:20 UTC.