HaulerCheck · https://haulercheck.com/carrier/1303808-crown-victoria-express-inc/ · Checked 2026-10-20 02:43 UTC · Census and inspections Oct 19, 2026 · Authority and insurance: FMCSA Motus · Oct 19, 2026
CROWN VICTORIA EXPRESS 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 average33.3% vs North Carolina average 21.9%.
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, (980) 920-5900, not a number from an email or load board.
- Check that the MC number you were given is MC505788.
- 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) | MC505788 | — | United States Fire Insurance Company Policy 5069503863 · BMC-91X | $750,000 | Aug 10, 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
2 of 6 · North Carolina avg 21.9%
1 of 20 · North Carolina avg 5.9%
10 most recent inspections
| Date | State | Level | Violations | Out of service |
|---|---|---|---|---|
| Oct 15, 2026 | KY | 3 | 1 | No |
| Oct 6, 2026 | IN | 3 | 0 | No |
| Sep 14, 2026 | MT | 2 | 0 | No |
| Sep 9, 2026 | GA | 2 | 1 | Yes |
| Aug 17, 2026 | WA | 2 | 1 | Yes |
| Aug 11, 2026 | TX | 2 | 2 | No |
| Aug 6, 2026 | UT | 3 | 0 | No |
| Jun 5, 2026 | TN | 3 | 1 | No |
| Jun 4, 2026 | WY | 2 | 1 | No |
| Apr 28, 2026 | LA | 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 North Carolina average covers 60,599 vehicle and 118,016 driver inspections of all North Carolina-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
16 violations counted in FMCSA's Safety Measurement System (SMS), 3 of them serious enough to put the driver or vehicle out of service.
Why is this different from the 31 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 | North Carolina share |
|---|---|---|---|---|
| Hours-of-Service Compliance | 10 | 1 | 62.5% | 15.9% |
| Unsafe Driving | 3 | 0 | 18.8% | 13.4% |
| Vehicle Maintenance | 3 | 2 | 18.8% | 63.4% |
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 | 2 | 2 |
| HOS (Property) - Driving beyond the 14 hour after coming on duty following 10 consecutive hours off duty during the current 8 consecutive day period. Date and Tim Hours · Hours-of-Service Compliance · code 3953A2HOSPD | 2 | 0 |
| 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 (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 - 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 (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 berth period of at least 30 consecutive minutes Hours · Hours-of-Service Compliance · code 3953AII | 1 | 0 |
| 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 |
| HOS (Form) - Paper Log/Logging Programs Form and Manner Other Log/Form & Manner · Hours-of-Service Compliance · code 3958A | 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 North Carolina column is the mix across all North Carolina-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 4, 2026 | Lampasas, TX | 0 | 0 |
Reportable crashes do not imply the carrier was at fault.
Company details FMCSA census · Oct 19, 2026
| USDOT number | 1303808 |
|---|---|
| MC / docket | MC505788 |
| Legal name | CROWN VICTORIA EXPRESS INC |
| Operation | Interstate |
| Business type | — |
| Power units | 14 |
| Drivers | 15 |
| Annual mileage | 568,383 (2025) |
| Hazmat | No |
| Safety rating | Not rated (no compliance review on record) |
| USDOT number added | Nov 12, 2004 · 21 years ago |
| Last MCS-150 update | Mar 2, 2026 |
Cargo carried
General FreightHousehold GoodsMetal: Sheets, Coils, RollsFresh ProduceMeatRefrigerated Food
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 CROWN VICTORIA EXPRESS INC
What does CROWN VICTORIA EXPRESS INC's operating authority allow?
MC505788: Motor carrier (may haul regulated property for hire).
Which information about CROWN VICTORIA EXPRESS INC is old or missing?
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 CROWN VICTORIA EXPRESS INC?
Confirm the authority and insurance on the Motus record for USDOT 1303808. Call the company back on the phone number on file, (980) 920-5900, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC505788, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.
Other trucking companies in Indian Trail, NC →
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 02:43 UTC.