HaulerCheck · https://haulercheck.com/carrier/2295334-concord-express-llc/ · Checked 2026-10-19 18:33 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
CONCORD EXPRESS LLC
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, (540) 560-7175, not a number from an email or load board.
- Check that the MC number you were given is MC783769.
- 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) | MC783769 | Primary | Incline Casualty Company Policy ICC-E4233-451923 · BMC-91X | $750,000 | Apr 17, 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
0 of 3 · Virginia avg 21.3%
1 of 12 · Virginia avg 6.0%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Aug 4, 2026 | PA | 3 | 1 | No |
| Jul 7, 2026 | NY | 3 | 8 | Yes |
| May 19, 2026 | WV | 3 | 1 | No |
| Apr 27, 2026 | NY | 3 | 0 | No |
| Apr 1, 2026 | CT | 3 | 1 | No |
| Mar 17, 2026 | MA | 3 | 4 | No |
| Mar 11, 2026 | MA | 3 | 1 | No |
| Feb 14, 2026 | NY | 2 | 3 | No |
| Jun 20, 2025 | PA | 3 | 1 | No |
| Dec 31, 2024 | NY | 1 | 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
17 violations counted in FMCSA's Safety Measurement System (SMS), 1 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 22 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 | 11 | 1 | 64.7% | 12.8% |
| Unsafe Driving | 5 | 0 | 29.4% | 13.5% |
| Vehicle Maintenance | 1 | 0 | 5.9% | 67.5% |
10 most frequent violations
| Violation | Times | Out of service |
|---|---|---|
| State/Local Laws - Speeding 15 or more miles per hour over the speed limit Speeding 4 · Unsafe Driving · code 3922SLLS4 | 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 (ELD) - A portable ELD is not mounted in a fixed position and visible to the driver when seated in the normal driving position. EOBR Related · Hours-of-Service Compliance · code 39522GELDMFV | 1 | 0 |
| 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 | 1 | 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 | 1 | 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 | 1 | 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 | 1 | 0 |
| HOS - False record of duty status driver improper use of Personal Conveyance - Not OOS False Log · Hours-of-Service Compliance · code 3958E1PC | 1 | 0 |
| HOS (Property) - Driving more than 11 hours following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Time Hours · Hours-of-Service Compliance · code 3953A1HOSPD | 1 | 0 |
| Driving beyond 8 hour driving limit since the end of the last on duty off duty or sleeper period of at least 30 minutes Hours · Hours-of-Service Compliance · code 3953A3II | 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
Crash details
| Date | Location | Fatalities | Injuries |
|---|---|---|---|
| Aug 18, 2026 | Not Reported, VA | 0 | 1 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 2295334 |
|---|---|
| MC / docket | MC783769 |
| Legal name | CONCORD EXPRESS LLC |
| Operation | Interstate |
| Business type | — |
| Power units | 16 |
| Drivers | 14 |
| Annual mileage | 1,355,608 (2023) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Apr 16, 2012 · 14 years ago |
| Last MCS-150 update | Jan 23, 2025 |
Cargo carried
General FreightFresh ProduceMeatRefrigerated FoodPaper 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 CONCORD EXPRESS LLC
What does CONCORD EXPRESS LLC's operating authority allow?
MC783769: Motor carrier (may haul regulated property for hire).
Which information about CONCORD EXPRESS LLC 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 CONCORD EXPRESS LLC?
Confirm the authority and insurance on the Motus record for USDOT 2295334. Call the company back on the phone number on file, (540) 560-7175, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC783769, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Harrisonburg, 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 18:33 UTC.