CSA
UnknownUSDOT 2014112· CARRIER· EIN 11-3733950
⬇ PDF report

DAVID BATES

425 NORTH CANTON CLUB CIR, JACKSON, MS, 39211(769) 798-3300DAVID BATES
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
80
/ 100

Risk factors

Low riskVioCodes score
Possible reincarnation pattern — tied to an older inactive carrier

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

Company profile

FMCSA census

AUTHORIZED FOR HIRE

Power units
1
on file (MCS-150)
Drivers
—
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
Company officer
DAVID BATES
Operation
Intrastate (Non-Hazmat)
Registered since
2010-03-30
Last MCS-150 update
2010-06-18
Census status
I

Fleet: 0 trucks.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Data change history

Every FMCSA record change we’ve detected — address, fleet size, contacts, MCS-150 — newest first.

Connections

carrier graph

This carrier shares officers with 16 other carriers — review the connections below as part of your vetting.

16
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
16
Strong links
Possible reincarnation pattern: DAVID BATES (USDOT 1772474, registered 2008) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 16
1
DAVID B BATES
USDOT 3895083Active· MOBILE, AL
Strong
Officer
2
DAVID BATES
USDOT 1929422Active· YADKINVILLE, NC
Strong
Officer
3
DAVID BATES
USDOT 2554362Inactive· HAWKINS, TX
Strong
Officer
4
DAVID BATES
USDOT 1741410Active· SHREVEPORT, LA
Strong
Officer
5
DAVID BATES
USDOT 1772474Inactive· SPIRIT LAKE, ID
Strong
Officer
6
DAVID BATES
USDOT 2154704Inactive· PARKRERSBURG, WV
Strong
Officer
7
DAVID BATES
USDOT 1575388Inactive· HAWLEY, PA
Strong
Officer
8
DAVID BATES
USDOT 2354578Inactive· MEXIA, TX
Strong
Officer
9
DAVID BATES
USDOT 2869970Inactive· SHEPHERDSVLLE, KY
Strong
Officer
10
DAVID LLOYD BATES
USDOT 4471628Active· JONESBORO, TX
Strong
Officer
11
ECOSPHERE INC
USDOT 2395134Active· EL PRADO, NM
Strong
Officer
12
GENESIS HOTSHOT LLC
USDOT 4464584Inactive· FATE, TX
Strong
Officer
13
JD DIVERSIFIED SERVICES INC
USDOT 936015Inactive· SPRINGBORO, PA
Strong
Officer
14
STILLE RIDERS LOGISTICS LLC
USDOT 3940982Active· BRANDON, MS
Strong
Officer
15
THE NEON DOCTOR LLC
USDOT 4573211Active· WEST MIFFLIN, PA
Strong
Officer
16
TRAFFIC MARKINGS INC
USDOT 1595045Active· FAIRBANKS, AK
Strong
Officer

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

2 events
  1. 06/18/2010MCS-150 update filed
  2. 03/30/2010Registered with FMCSA

    AUTHORIZED FOR HIRE

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2010-06-18
Reported mileage
—
⚡

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
ⓘ
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 26, 2026, 1:56 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.