HaulerCheck · https://haulercheck.com/carrier/565153-flemings-transportation-inc/ · Checked 2026-10-20 01:46 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
FLEMINGS TRANSPORTATION 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.
- Vehicle out-of-service rate well above the state average38.9% vs Connecticut average 23.7%.
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, (800) 225-0249, not a number from an email or load board.
- Check that the MC number you were given is MC222754.
- 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) | MC222754 | Primary | Sentry Select Insurance Company Policy A0078202001 · BMC-91X | $750,000 | Mar 1, 2024 | 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
7 of 18 · Connecticut avg 23.7%
0 of 33 · Connecticut avg 10.1%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 15, 2026 | CT | 1 | 10 | No |
| Oct 6, 2026 | NY | 3 | 1 | No |
| Aug 20, 2026 | NY | 2 | 3 | No |
| Aug 13, 2026 | CT | 3 | 0 | No |
| Jul 14, 2026 | US | 1 | 1 | No |
| Jul 8, 2026 | MA | 2 | 3 | No |
| Jun 30, 2026 | CT | 3 | 3 | No |
| Jun 25, 2026 | PA | 2 | 4 | Yes |
| May 18, 2026 | CT | 2 | 0 | No |
| Apr 24, 2026 | NJ | 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 Connecticut average covers 8,552 vehicle and 13,621 driver inspections of all Connecticut-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
47 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 71 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 | Connecticut share |
|---|---|---|---|---|
| Vehicle Maintenance | 18 | 7 | 38.3% | 68.4% |
| Hours-of-Service Compliance | 16 | 0 | 34.0% | 9.7% |
| Unsafe Driving | 13 | 0 | 27.7% | 13.7% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| 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 |
| HOS (ELD) - In-Vehicle Information - No user's manual for the driver describing how to operate the ELD. (May be electronic) EOBR Related · Hours-of-Service Compliance · code 39522H1ELDNUM | 3 | 0 |
| HOS (ELD) - In-Vehicle Information - Failing to have an instruction sheet for the driver describing ELD malfunction reporting requirements and recordkeeping proce EOBR Related · Hours-of-Service Compliance · code 39522H3ELDMF | 3 | 0 |
| 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 | 3 | 0 |
| State/Local Laws - Lane restriction violation Misc Violations · Unsafe Driving · code 3922SLLLR | 3 | 0 |
| State/Local Laws - Speeding 15 or more miles per hour over the speed limit Speeding 4 · Unsafe Driving · code 3922SLLS4 | 3 | 0 |
| HOS (ELD) Driver failing to have instruction sheet describing the data transfer mechanisms supported by the ELD and step-by-step instructions for the driver to pr EOBR Related · Hours-of-Service Compliance · code 39522H2ELDNISDT | 2 | 0 |
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 2 | 0 |
| Air Brake - ABS malfunction lamp defective on trailers manufactured on or after March 1 1998 Brakes All Others · Vehicle Maintenance · code 39355EB | 2 | 0 |
| Brake Out of Adjustment - Roto Clamp (Short & Long) DD-3 or Bolt Brakes Out of Adjustment · Vehicle Maintenance · code 39347E | 2 | 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 Connecticut column is the mix across all Connecticut-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
Crash details
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Sep 17, 2025 | Elmsford, NY | 0 | 1 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 565153 |
|---|---|
| MC / docket | MC222754 |
| Legal name | FLEMINGS TRANSPORTATION INC |
| Operation | Interstate |
| Business type | Corporation |
| Power units | 20 |
| Drivers | 20 |
| Annual mileage | 1,626,000 (2024) |
| Hazmat | No |
| Safety rating | Satisfactory (Feb 6, 2008) |
| USDOT number added | Jun 3, 1994 · 32 years ago |
| Last MCS-150 update | May 8, 2026 |
Cargo carried
General FreightHousehold GoodsU.S. MailChemicalsBeveragesPaper Products
Change history since Oct 18, 2026
1 change
| Date | What changed | Before | After |
|---|---|---|---|
| Oct 19, 2026 | Operating authority | MC222754: Broker of Property (Except Household Goods): Inactive; Motor Carrier of Property (Except Household Goods): Active | MC222754: Motor Carrier of Property (Except Household Goods): Active; Broker of Property (Except Household Goods): Inactive |
Changes we detected between daily FMCSA data refreshes.
Questions about FLEMINGS TRANSPORTATION INC
What does FLEMINGS TRANSPORTATION INC's operating authority allow?
MC222754: Motor carrier (may haul regulated property for hire).
Which information about FLEMINGS TRANSPORTATION INC 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 FLEMINGS TRANSPORTATION INC?
Confirm the authority and insurance on the Motus record for USDOT 565153. Call the company back on the phone number on file, (800) 225-0249, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC222754, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Suffield, CT →
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 01:46 UTC.