HaulerCheck · https://haulercheck.com/carrier/4373749-king-champion-logistics-llc/ · Checked 2026-10-19 14:31 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
KING CHAMPION LOGISTICS 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.
- Vehicle out-of-service rate well above the state average38.5% vs Tennessee average 23.5%.
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, (865) 805-7160, not a number from an email or load board.
- Check that the MC number you were given is MC1713472.
- 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) | MC1713472 | Primary | GEICO MARINE INSURANCE COMPANY Policy 9300130896 · 91X | $1,000,000 | Mar 2, 2026 | 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
5 of 13 · Tennessee avg 23.5%
1 of 13 · Tennessee avg 3.7%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Sep 30, 2026 | AR | 1 | 3 | Yes |
| Sep 28, 2026 | KS | 1 | 6 | No |
| Sep 11, 2026 | TN | 2 | 2 | No |
| Aug 25, 2026 | MO | 1 | 17 | Yes |
| Aug 18, 2026 | KY | 1 | 7 | Yes |
| Aug 5, 2026 | MS | 1 | 1 | No |
| Aug 5, 2026 | NJ | 1 | 0 | No |
| Aug 4, 2026 | TN | 1 | 0 | No |
| Jul 30, 2026 | TN | 1 | 0 | No |
| Jul 29, 2026 | TN | 1 | 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 Tennessee average covers 76,642 vehicle and 133,725 driver inspections of all Tennessee-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
32 violations counted in FMCSA's Safety Measurement System (SMS), 10 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 64 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 | Tennessee share |
|---|---|---|---|---|
| Vehicle Maintenance | 22 | 9 | 68.8% | 64.1% |
| Hours-of-Service Compliance | 9 | 1 | 28.1% | 13.1% |
| Unsafe Driving | 1 | 0 | 3.1% | 18.1% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| Brake - Breakaway not attached to the towing vehicle Brakes All Others · Vehicle Maintenance · code 39343DBMA | 3 | 3 |
| Lighting - Turn signal - Any inoperative on the rearmost vehicle. Lighting · Vehicle Maintenance · code 3939ALTSI | 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 |
| 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 |
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 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 |
| Lighting - Stop lamps - Any inoperative. Lighting · Vehicle Maintenance · code 3939ALSLI | 2 | 0 |
| Horn - Inoperative or defective Other Vehicle Defect · Vehicle Maintenance · code 39381H | 2 | 0 |
| Cargo - Loose or unfastened tiedown Tiedown · Vehicle Maintenance · code 393104F3C | 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 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 18, 2026. "Share" is this company's mix of violations; the Tennessee column is the mix across all Tennessee-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 | 4373749 |
|---|---|
| MC / docket | MC1713472 |
| Legal name | KING CHAMPION LOGISTICS LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 3 |
| Drivers | 3 |
| Hazmat | Yes |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Mar 7, 2025 · 1 year ago |
| Last MCS-150 update | Feb 23, 2026 |
Cargo carried
General FreightMetal: Sheets, Coils, RollsLogs, Poles, Beams, LumberBuilding MaterialsMachinery, Large ObjectsAgricultural/Farm SuppliesConstruction
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 KING CHAMPION LOGISTICS LLC
What does KING CHAMPION LOGISTICS LLC's operating authority allow?
MC1713472: Common carrier (may haul regulated property for hire for the general public).
Which information about KING CHAMPION LOGISTICS 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 KING CHAMPION LOGISTICS LLC?
Confirm the authority and insurance on the Motus record for USDOT 4373749. Call the company back on the phone number on file, (865) 805-7160, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1713472, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Rogersville, TN →
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 14:31 UTC.