CSA
UnknownUSDOT 2900777· CARRIER
⬇ PDF report

JOSE A SALAZAR

126 HOLLIE DR, RED OAK, TX, 75154-6602(469) 337-5070jose.salazar86@yahoo.comJOSE A SALAZAR
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

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
  • Intrastate · <100 mi1 drivers
Company officer
JOSE A SALAZAR
Operation
Intrastate (Non-Hazmat)
Registered since
2016-06-15
Last MCS-150 update
2016-06-15
Census status
Active

Fleet: 1 trucks · 1 owned tractors · 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.

Connections

carrier graph

This carrier shares addresses, phone numbers, officers or emails with 10 other carriers — review the connections below as part of your vetting.

10
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
10
Strong links
Possible reincarnation pattern: JOSE A SALAZAR (USDOT 2554505, registered 2014) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 10
1
JOSE A SALAZAR
USDOT 2554505Inactive· PALMDALE, CA
Strong
Officer
2
JOSE A SALAZAR
USDOT 2776028Active· WHITTIER, CA
Strong
Officer
3
JOSE A SALAZAR
USDOT 2747042Active· PALMDALE, CA
Strong
Officer
4
JOSE A SALAZAR
USDOT 2753844Active· VAN NUYS, CA
Strong
Officer
5
JOSE A SALAZAR
USDOT 2762644Inactive· LOS ANGELES, CA
Strong
Officer
6
JOSE A SALAZAR
USDOT 2448594Inactive· SANTA MARIA, CA
Strong
Officer
7
JOSE A SALAZAR
USDOT 2483137Inactive· GARLAND, TX
Strong
Officer
8
JOSE ANGEL SALAZAR
USDOT 2898164Active· RED OAK, TX
Strong
MailingEmailPhoneAddress
9
PRECISION ANODIZING & PLATING INC
USDOT 2662584Active· ANAHEIM, CA
Strong
Officer
10
RGV TIRES LLC
USDOT 3337458Inactive· BROWNSVILLE, TX
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/15/2016Registered with FMCSA

    AUTHORIZED FOR HIRE

  2. 06/15/2016MCS-150 update filed

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
2016-06-15
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 22, 2026, 3:18 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.