CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 2020693· CARRIER
⬇ PDF report

ROBERT TYLER

96 BIGELOW HOLLOW RD, UNION, CT, 06079(860) 684-0603tobytyler3@yahoo.comROBERT TYLER
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
1 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi1 drivers
Company officer
ROBERT TYLER
Operation
Interstate
Registered since
2010-04-14
Last MCS-150 update
2010-04-14
Census status
I

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

7
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
7
Strong links
Possible reincarnation pattern: ROBERT D TYLER (USDOT 1197527, registered 2004) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 7
1
BRIGHTVIEW LANDSCAPES LLC
USDOT 362827Active· BLUE BELL, PA
Strong
Officer
2
HIGH END COMMERCIAL CABINETS LLC
USDOT 2171193Active· PRESCOTT, AZ
Strong
Officer
3
ROBERT D TYLER
USDOT 1197527Inactive· LODI, CA
Strong
Officer
4
RT'S AUTOMOTIVE TRANSPORT SERVICE LLC
USDOT 1996402Inactive· MARYSVILLE, WA
Strong
Officer
5
SUNCRETE HAWAII INC
USDOT 4181062Active· HONOLULU, HI
Strong
Officer
6
TYLER CONSTRUCTION
USDOT 2363846Active· LA VERNIA, TX
Strong
Officer
7
TYLERS TRUCKING LLC
USDOT 2290960Inactive· WASHINGTON, DC
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

3 events
  1. 05/29/2012Federal out-of-service order

    New Entrant Revoked - Refusal of Audit/No Contact

  2. 04/14/2010Registered with FMCSA

    PRIVATE PROPERTY

  3. 04/14/2010MCS-150 update filed

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate
📄

MCS-150 registration

Form date
2010-04-14
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 25, 2026, 12:04 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.