HaulerCheck · https://haulercheck.com/carrier/3313613-pyrolyx-transportation-llc/ · Checked 2026-10-20 05:53 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
PYROLYX TRANSPORTATION LLC
Review before booking · 2 signals
How risk signals workFacts from the FMCSA record that call for a closer look. They are not a finding of wrongdoing.
- Conditional FMCSA safety ratingRated Sep 16, 2026. FMCSA found safety controls that needed correcting.
- Vehicle out-of-service rate well above the state average34.7% vs Indiana average 23.1%.
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, (765) 245-2190, not a number from an email or load board.
- Check that the MC number you were given is MC1064114.
- 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) | MC1064114 | Primary | Riverport Insurance Company Policy SCA 3502185-10 · BMC-91X | $1,000,000 | Dec 31, 2025 | Active |
Source: FMCSA Motus · Oct 19, 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 19, 2024 – Oct 19, 2026
17 of 49 · Indiana avg 23.1%
10 of 89 · Indiana avg 5.5%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 13, 2026 | IN | 2 | 8 | No |
| Oct 5, 2026 | IL | 2 | 2 | Yes |
| Sep 20, 2026 | IL | 3 | 0 | No |
| Sep 17, 2026 | IN | 2 | 6 | No |
| Sep 9, 2026 | IL | 3 | 0 | No |
| Sep 2, 2026 | IL | 3 | 0 | No |
| Sep 1, 2026 | MO | 3 | 0 | No |
| Aug 23, 2026 | IL | 2 | 2 | No |
| Aug 4, 2026 | MO | 3 | 6 | Yes |
| Aug 3, 2026 | IL | 3 | 1 | No |
How these rates are calculated
Period: Oct 19, 2024 – Oct 19, 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,543 vehicle and 111,154 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
146 violations counted in FMCSA's Safety Measurement System (SMS), 37 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 213 violations above?
The inspections section's number counts every violation written on the inspection reports in our Oct 19, 2024 – Oct 19, 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 | 103 | 25 | 70.5% | 58.8% |
| Unsafe Driving | 22 | 0 | 15.1% | 19.1% |
| Hours-of-Service Compliance | 12 | 3 | 8.2% | 18.1% |
| Driver Fitness | 8 | 8 | 5.5% | 3.6% |
| Controlled Substances/Alcohol | 1 | 1 | 0.7% | 0.3% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| Operating a CMV without documentation of a periodic inspection Inspection Reports · Vehicle Maintenance · code 39617CPI | 8 | 0 |
| State/Local Laws - Speeding work/construction zone Speeding 4 · Unsafe Driving · code 3922SLLSWZ | 6 | 0 |
| Lighting - Identification lamp(s) inoperative Clearance Identification Lamps/Other · Vehicle Maintenance · code 3939ALIL | 6 | 0 |
| License (CDL) - Operate a CMV and does not possess a valid CDL License-related: High · Driver Fitness · code 38323A2LCDLN | 4 | 4 |
| Lighting - Turn signal - Any inoperative on the rearmost vehicle. Lighting · Vehicle Maintenance · code 3939ALTSI | 4 | 4 |
| 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 | 4 | 4 |
| 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 | 4 | 0 |
| State/Local Laws - Speeding 6-10 miles per hour over the speed limit Speeding 2 · Unsafe Driving · code 3922SLLS2 | 4 | 0 |
| Air Brake - ABS malfunction lamp defective on trailers manufactured on or after March 1 1998 Brakes All Others · Vehicle Maintenance · code 39355EB | 4 | 0 |
| Lighting - Tail lamp - Any inoperative Lighting · Vehicle Maintenance · code 3939ALRLI | 4 | 0 |
Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 19, 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 19, 2024 – Oct 19, 2026
10 most recent crashes
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| May 27, 2026 | Veedersburg, IN | 0 | 1 |
| Mar 30, 2026 | Harrison (Township Of), OH | 0 | 1 |
| Jun 13, 2025 | Union (Township Of), OH | 0 | 0 |
| Jun 13, 2025 | Kirkersville, OH | 0 | 0 |
| Apr 29, 2025 | St Cloud, MO | 0 | 0 |
| Apr 28, 2025 | Cuyahoga Falls, OH | 0 | 1 |
| Jan 23, 2025 | Bruceville, IN | 0 | 0 |
| Jan 17, 2025 | Breckenridge Hills, MO | 0 | 0 |
| Jan 7, 2025 | Non-City Or Unincorporate, MO | 0 | 0 |
| Dec 19, 2024 | Butler (Township Of), OH | 0 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 3313613 |
|---|---|
| MC / docket | MC1064114 |
| Legal name | PYROLYX TRANSPORTATION LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 80 |
| Drivers | 56 |
| Annual mileage | 1,210,000 (2025) |
| Hazmat | No |
| Safety rating | Conditional (Sep 16, 2026) |
| USDOT number added | Jul 22, 2019 · 7 years ago |
| Last MCS-150 update | May 2, 2025 |
Cargo carried
General FreightOtherUsed Tires
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 PYROLYX TRANSPORTATION LLC
What does PYROLYX TRANSPORTATION LLC's operating authority allow?
MC1064114: Motor carrier (may haul regulated property for hire).
Which information about PYROLYX TRANSPORTATION LLC is old or missing?
Nothing notable: authority and insurance come from current Motus data and there is enough inspection history to compare.
What should I verify before booking PYROLYX TRANSPORTATION LLC?
Confirm the authority and insurance on the Motus record for USDOT 3313613. Call the company back on the phone number on file, (765) 245-2190, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1064114, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Hillsdale, IN →
Company details from the FMCSA Company Census File (Oct 19, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).
Page generated 2026-10-20 05:53 UTC.