PS

PARTRIDGE SIBLEY INDUSTRIAL INC

DOT 282981MC 779512ActiveMotor CarrierInterstateIMPERIUM INSURANCE COMPANY +1JACKSON, MS

COMPANY

Authority since
2012-03-30
MCS-150
2026-02-06 · 189,000 mi (2025)
Fleet
20 units · 28 trailers · 5 drivers

ADDRESS

Physical
4273 I 55 NORTH # 1-B
JACKSON, MS 39206
Mailing
Same as physical

CONTACT

Phone
6017131911
Email
drutland@thepartridgecompanies.com

OFFICERS

Primary Officer

OPERATION & CARGO

Operation classification
Private Property;authorized For Hire
Specialty
Tanker / Bulk Liquids
Cargo types
4
Building MaterialsLiquids / GasesConstructionOther
Self-reported by the company on its latest MCS-150 filing (FMCSA census). Reflects what the carrier is authorized and equipped to haul, not actual recent loads.
AUTHORITY
175 mo
Active authority
INSURANCE
2 active
IMPERIUM INSURANCE COMPANY
RISK GRADE
Minimal Risk
0 risk factors · 3 strengths
OOS RATE
33.3%
3 / 9 inspections

Fleet vs Reality

last 12 months · power-unit VINs from roadside inspections
Checking local VIN index…

Minimal Risk

1/100 risk points0 risk factors · 3 strengths · 5 data pointsmedium confidence

Weighted heuristic: crashes are decayed by recency and normalized per 100 power units, out-of-service and violation rates use a rolling 24-month window, plus FMCSA BASIC alerts and the CarrierIntel Safety Score (which also decays when compliance has not been verified by a recent inspection). Not the official FMCSA SMS score.

SAFETY PERFORMANCE

Crash Record
12 crashes · 2 fatal · 3 with injuries · 12 tow-away
Clean Inspection Rate
67% — 6 clean of 9 inspections
Out-of-Service Rate
33.3% — driver OOS 0, vehicle OOS 3

COMPLIANCE & AUTHORITY

Operating Authority
Active operating authority on file
Authority Events
1 historical event(s) on file
MCS-150 Filing
Last filed 2026-02-06

INSURANCE

Active Coverage
2 active policy(ies) · total max coverage $5,000,000

SUMMARY

No crashes in the last 24 months
Active insurance on file
Coverage $5.0M
2 fatal crashes on record, none in the last 24 months
FMCSA crash records do not state who was at fault