HaulerCheck · https://haulercheck.com/carrier/3638141-letida-llc/ · Checked 2026-10-19 00:58 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
LETIDA LLC
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.
- No active liability insurance in the last known dataPolicies on file as of May 14, 2026 have been cancelled since. A replacement may have been filed; confirm on Motus.
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.
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, (303) 653-4176, not a number from an email or load board.
- Check that the MC number you were given is MC1249090.
- 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) | MC1249090 | Primary | CANAL INSURANCE CO. Policy CT0677103504 · 91X | $750,000 | Jul 29, 2025 | Cancelled Jul 29, 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
1 of 10 · Minnesota avg 25.5%
3 of 13 · Minnesota avg 3.8%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Sep 28, 2026 | MN | 1 | 3 | No |
| Aug 28, 2026 | TX | 2 | 3 | Yes |
| Aug 5, 2026 | AZ | 1 | 6 | Yes |
| May 14, 2026 | MN | 1 | 0 | No |
| May 6, 2026 | KS | 2 | 0 | No |
| Feb 24, 2026 | MO | 1 | 9 | No |
| Feb 20, 2026 | IA | 2 | 4 | Yes |
| Jan 19, 2026 | NC | 2 | 0 | No |
| Jan 13, 2026 | WI | 2 | 2 | No |
| Dec 31, 2025 | KS | 3 | 4 | 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 Minnesota average covers 31,491 vehicle and 62,770 driver inspections of all Minnesota-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
23 violations counted in FMCSA's Safety Measurement System (SMS), 3 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 40 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 | Minnesota share |
|---|---|---|---|---|
| Hours-of-Service Compliance | 14 | 3 | 60.9% | 14.2% |
| Vehicle Maintenance | 8 | 0 | 34.8% | 65.4% |
| Unsafe Driving | 1 | 0 | 4.3% | 16.7% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| 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 | 2 | 2 |
| HOS (Property) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958EHOSPD | 2 | 0 |
| Driving beyond 8 hour driving limit since the end of the last on duty off duty or sleeper period of at least 30 minutes Hours · Hours-of-Service Compliance · code 3953A3II | 2 | 0 |
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 2 | 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 | 2 | 0 |
| False Record of Duty Status - Improper use of Personal Conveyance Exception False Log · Hours-of-Service Compliance · code 3958E1PC | 1 | 1 |
| 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 | 1 | 0 |
| HOS (Passenger) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958E1HOSPVID | 1 | 0 |
| HOS (ELD) - Driver failing to manually input or verify shipping document number. Other Log/Form & Manner · Hours-of-Service Compliance · code 39524C2IIIELDSDN | 1 | 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 | 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 Minnesota column is the mix across all Minnesota-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 | 3638141 |
|---|---|
| MC / docket | MC1249090 |
| Legal name | LETIDA LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 3 |
| Drivers | 3 |
| Annual mileage | 36,000 (2025) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | May 18, 2021 · 5 years ago |
| Last MCS-150 update | Feb 21, 2026 |
Cargo carried
General Freight
Questions about LETIDA LLC
What does LETIDA LLC's operating authority allow?
MC1249090: Common carrier (may haul regulated property for hire for the general public).
Which information about LETIDA LLC 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 LETIDA LLC?
Confirm the authority and insurance on the Motus record for USDOT 3638141. Call the company back on the phone number on file, (303) 653-4176, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1249090, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Elk River, MN →
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 00:58 UTC.