CSA
UnknownUSDOT 2286350· CARRIER
⬇ PDF report

TIMOTHY J SMITH

5161 JORDAN RD, GREER, SC, 29651(864) 483-2878TIMOTHY J SMITH
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%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census

AUTHORIZED FOR HIRE;EXEMPT FOR HIRE

Power units
1
on file (MCS-150)
Drivers
1
1 hold a CDL
Annual mileage
0M mi
reported 2011
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi1 drivers
Company officer
TIMOTHY J SMITH
Operation
Intrastate (Non-Hazmat)
Registered since
2012-03-21
Last MCS-150 update
2012-03-21
Census status
Active

Fleet: 1 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 8 other carriers — review the connections below as part of your vetting.

8
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
8
Strong links
Possible reincarnation pattern: TIMOTHY SMITH (USDOT 1610380, registered 2007) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 8
1
DENVER TRANSIT CONSTRUCTORS
USDOT 2358979Active· DENVER, CO
Strong
Officer
2
GRIZZLYBEAR TRANSPORT INC
USDOT 3576332Active· CHESAPEAKE, VA
Strong
Officer
3
STONE FRUIT COMPANY LLC
USDOT 4134060Active· PALISADE, CO
Strong
Officer
4
T'S TRANSPORTATION
USDOT 3475633Active· HOUSTON, TX
Strong
Officer
5
TIMOTHY J SMITH
USDOT 1254930Active· FREDERICKTOWN, OH
Strong
Officer
6
TIMOTHY J SMITH
USDOT 2746962Active· ESCONDIDO, CA
Strong
Officer
7
TIMOTHY J SMITH
USDOT 2006872Active· COZAD, NE
Strong
Officer
8
TIMOTHY SMITH
USDOT 1610380Inactive· DOVER, OH
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. 03/21/2012Registered with FMCSA

    AUTHORIZED FOR HIRE;EXEMPT FOR HIRE

  2. 03/21/2012MCS-150 update filed

    0.0M mi reported (2011)

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

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE;EXEMPT FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2012-03-21
Reported mileage
38,400 mi (2011)
⚡

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 28, 2026, 2:50 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.