HaulerCheck · https://haulercheck.com/carrier/2952115-pawar-transport-inc/ · Checked 2026-10-19 23:23 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
PAWAR TRANSPORT INC
No risk signals found
How risk signals workNothing in the FMCSA record matched our risk signals. That is not a guarantee, and it does not confirm who you are talking to; follow the checks below.
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, (917) 620-1595, not a number from an email or load board.
- Check that the MC number you were given is MC119.
- 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) | MC119 | — | Accredited Specialty Insurance Company Policy 2CWHVA19S034702101 · BMC-91X | $750,000 | Jun 4, 2026 | 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
0 of 0 · Virginia avg 21.3%
0 of 5 · Virginia avg 6.0%
5 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Jul 30, 2026 | AR | 3 | 0 | No |
| Feb 11, 2026 | AL | 3 | 7 | No |
| Jan 20, 2026 | AR | 3 | 0 | No |
| Mar 3, 2025 | LA | 3 | 1 | No |
| Jan 16, 2025 | TN | 3 | 0 | 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 Virginia average covers 31,578 vehicle and 51,675 driver inspections of all Virginia-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
2 violations counted in FMCSA's Safety Measurement System (SMS), 0 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 8 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 | Virginia share |
|---|---|---|---|---|
| Hours-of-Service Compliance | 2 | 0 | 100.0% | 12.8% |
2 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| HOS (ELD) - ELD Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 39524 | 1 | 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 | 1 | 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 Virginia column is the mix across all Virginia-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
No reportable crashes in this period.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 2952115 |
|---|---|
| MC / docket | MC119 |
| Legal name | PAWAR TRANSPORT INC |
| Operation | Interstate |
| Business type | — |
| Power units | 1 |
| Drivers | 2 |
| Annual mileage | 140,000 (2026) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Dec 7, 2016 · 9 years ago |
| Last MCS-150 update | Jun 10, 2026 |
Cargo carried
General FreightFresh ProduceMeatCommodities Dry BulkRefrigerated FoodBeveragesPaper Products
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 PAWAR TRANSPORT INC
What does PAWAR TRANSPORT INC's operating authority allow?
MC119: Motor carrier (may haul regulated property for hire).
Which information about PAWAR TRANSPORT INC is old or missing?
There are too few vehicle inspections in the last 24 months to judge the out-of-service rate. 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 PAWAR TRANSPORT INC?
Confirm the authority and insurance on the Motus record for USDOT 2952115. Call the company back on the phone number on file, (917) 620-1595, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC119, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Bristow, VA →
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-19 23:23 UTC.