CSA
UnknownUSDOT 2423910· CARRIER· EIN 87-0630612
⬇ PDF report

GREENHEAD LANDSCAPING

6510 W 5800 S, HOOPER, UT, 84315(801) 232-6464staceyjackson52@gmail.comBRAD JACKSON
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

PRIVATE PROPERTY

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

Fleet: 1 trucks · 1 owned trailers.

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: BRAD JACKSON (USDOT 2008485, registered 2010) 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
BRAD A JACKSON
USDOT 831141Active· MEDARYVILLE, IN
Strong
Officer
2
BRAD JACKSON
USDOT 2645345Active· MAYSVILLE, KY
Strong
Officer
3
BRAD JACKSON
USDOT 2008485Inactive· LA MOILLE, IL
Strong
Officer
4
CHUCK DIESEL LLC
USDOT 3985056Active· GAUTIER, MS
Strong
Officer
5
FR8 PUSHAS LLC
USDOT 3939710Inactive· MAYSVILLE, KY
Strong
Officer
6
JACKSON TRANSPORTATION LLC
USDOT 4571618Active· MILFORD, IN
Strong
Officer
7
STATEWIDE RESTORATION SERVICES INC
USDOT 3051140Inactive· FREMONT, CA
Strong
Officer
8
TRADITIONAL LINKS LLC
USDOT 4178701Active· RIVERHEAD, NY
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. 07/23/2013Registered with FMCSA

    PRIVATE PROPERTY

  2. 07/23/2013MCS-150 update filed

    0.2M mi reported (2012)

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2013-07-23
Reported mileage
180,000 mi (2012)
⚡

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 27, 2026, 9:43 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.