CSA
UnknownUSDOT 1942599· CARRIER
⬇ PDF report

CARLOS VELASCO

530 WEST MAIN ST, EAGLE LAKE, TX, 77434(281) 541-1742maria.dbarker1@farmersagency.comCARLOS VELASCO
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
2
on file (MCS-150)
Drivers
2
0 hold a CDL
Annual mileage
0M mi
reported 2008
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi2 drivers
Company officer
CARLOS VELASCO
Operation
Intrastate (Non-Hazmat)
Registered since
2009-09-22
Last MCS-150 update
2009-09-22
Census status
Active

Fleet: 2 trucks · 2 owned tractors.

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

11
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
11
Strong links
Possible reincarnation pattern: CARLOS VELASCO (USDOT 1159735, registered 2003) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 11
1
CARLOS VELASCO
USDOT 2838091Inactive· N LAS VEGAS, NV
Strong
Officer
2
CARLOS VELASCO
USDOT 2683581Active· STOCKTON, CA
Strong
Officer
3
CARLOS VELASCO
USDOT 1159735Inactive· OAKDALE, CA
Strong
Officer
4
CARLOS VELASCO
USDOT 1456471Inactive· REEDLEY, CA
Strong
Officer
5
CHEMICAL MANUFACTURERS INCORPORATED
USDOT 2851231Active· LOS ANGELES, CA
Strong
Officer
6
DJ 21 TRANSPORT INC
USDOT 1963605Active· HOCKLEY, TX
Strong
Officer
7
DJ 21 TRANSPORT INC
USDOT 3742103Inactive· KATY, TX
Strong
Officer
8
INTERSTATE FOODS INC
USDOT 3070000Active· COMPTON, CA
Strong
Officer
9
INTERSTATE POULTRY INC
USDOT 2526818Inactive· LOS ANGELES, CA
Strong
Officer
10
TEXCA TRANSPORTATION LLC
USDOT 3634183Inactive· BAKERSFIELD, CA
Strong
Officer
11
VELASCO TRUCK
USDOT 1409994Inactive· WARRENTON, VA
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. 09/22/2009Registered with FMCSA

    AUTHORIZED FOR HIRE

  2. 09/22/2009MCS-150 update filed

    0.0M mi reported (2008)

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
2009-09-22
Reported mileage
30,000 mi (2008)
📜

Changes on file

FMCSA census history
  1. January, 2021

    First on-record entry — CARLOS VELASCO, EAGLE LAKE, TX

⚡

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