HaulerCheck · https://haulercheck.com/carrier/3089183-jap-logistics-inc/ · Checked 2026-10-19 06:28 UTC · Census and inspections Oct 18, 2026 · Authority and insurance: Last known · FMCSA snapshot May 14, 2026
JAP LOGISTICS 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.
- 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
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, (661) 520-6868, not a number from an email or load board.
- Check that the MC number you were given is MC70976.
- 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) | MC70976 | Primary | CANAL INSURANCE CO. Policy CT1089349731 · 91X | $750,000 | Mar 25, 2026 | Cancelled Jul 8, 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
3 of 9 · Indiana avg 23.1%
2 of 23 · Indiana avg 5.5%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Jun 19, 2026 | MI | 2 | 2 | Yes |
| May 15, 2026 | PA | 3 | 4 | Yes |
| May 7, 2026 | PA | 3 | 2 | No |
| May 5, 2026 | OH | 3 | 0 | No |
| Mar 18, 2026 | GA | 3 | 2 | Yes |
| Mar 4, 2026 | OH | 1 | 1 | No |
| Feb 11, 2026 | MI | 2 | 8 | Yes |
| Jan 30, 2026 | PA | 3 | 1 | No |
| Nov 13, 2025 | MN | 1 | 10 | Yes |
| Oct 28, 2025 | PA | 3 | 1 | 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 Indiana average covers 61,530 vehicle and 111,152 driver inspections of all Indiana-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
33 violations counted in FMCSA's Safety Measurement System (SMS), 7 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 48 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 | Indiana share |
|---|---|---|---|---|
| Vehicle Maintenance | 18 | 3 | 54.5% | 58.8% |
| Hours-of-Service Compliance | 8 | 4 | 24.2% | 18.1% |
| Unsafe Driving | 7 | 0 | 21.2% | 19.1% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| State/Local Laws - Speeding 6-10 miles per hour over the speed limit Speeding 2 · Unsafe Driving · code 3922SLLS2 | 3 | 0 |
| Driver failed to certify the accuracy of the information gathered by the ELD Other Log/Form & Manner · Hours-of-Service Compliance · code 39530B1 | 2 | 0 |
| 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 | 1 | 1 |
| HOS (Property) - Driver driving beyond the 14 hour after coming on duty following 10 consecutive hours off duty at the time of inspection. Time Hours · Hours-of-Service Compliance · code 3953A2HOSPDIT | 1 | 1 |
| HOS (Property) - Driving more than 11 hours following 10 consecutive hours off duty at the time of inspection. Time Hours · Hours-of-Service Compliance · code 3953A3IHOSPDIT | 1 | 1 |
| HOS (Property) - Failing to have a record of duty status using the method prescribed Incomplete/Wrong Log · Hours-of-Service Compliance · code 3958A1HOSP | 1 | 1 |
| Brake - Defective brake(s) are equal to or greater than 20% of the service brakes on the vehicle/combination Brake Out Of Service · Vehicle Maintenance · code 3963A1BOS | 1 | 1 |
| Cargo - Insufficient aggregate working load limit for cargo transported Tiedown · Vehicle Maintenance · code 393106DC | 1 | 1 |
| Tires - All others leaking or inflation less than 50% of the maximum inflation pressure on tire not equipped with ATIS Tires · Vehicle Maintenance · code 39375A3TAOL | 1 | 1 |
| HOS (Property) - No driver may make a false report in connection with a duty status. Explain False Log · Hours-of-Service Compliance · code 3958EHOSPD | 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 Indiana column is the mix across all Indiana-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
2 most recent crashes
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Nov 13, 2025 | Woodbury, MN | 0 | 1 |
| Oct 9, 2025 | New York -Bronx, NY | 0 | 2 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 18, 2026
| USDOT number | 3089183 |
|---|---|
| MC / docket | MC70976 |
| Legal name | JAP LOGISTICS INC |
| Operation | Interstate |
| Business type | — |
| Power units | 14 |
| Drivers | 16 |
| Annual mileage | 500,000 (2026) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Jan 23, 2018 · 8 years ago |
| Last MCS-150 update | May 1, 2026 |
Cargo carried
General Freight
Questions about JAP LOGISTICS INC
What does JAP LOGISTICS INC's operating authority allow?
MC70976: Common carrier (may haul regulated property for hire for the general public).
Which information about JAP LOGISTICS 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 JAP LOGISTICS INC?
Confirm the authority and insurance on the Motus record for USDOT 3089183. Call the company back on the phone number on file, (661) 520-6868, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC70976, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Greenwood, IN →
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:28 UTC.