CSA
UnknownUSDOT 2684442· CARRIER
⬇ PDF report

FRANCISCO AGUILAR

67-455 PEINETA RD, CATHEDRAL CITY, CA, 92234(760) 325-1705FRANCISCO AGUILAR
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
0
on file (MCS-150)
Drivers
1
0 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
FRANCISCO AGUILAR
Operation
Intrastate (Non-Hazmat)
Registered since
2015-06-12
Census status
Active

Fleet: 0 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.

Connections

carrier graph

This carrier shares officers with 15 other carriers — review the connections below as part of your vetting.

15
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
15
Strong links
Possible reincarnation pattern: FRANCISCO AGUILAR (USDOT 1323124, registered 2005) is inactive, shares this carrier’s officer, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 15
1
203 LOGISTICS LLC
USDOT 4455245Inactive· MERIDEN, CT
Strong
Officer
2
AGUILAR LOGISTICS LLC
USDOT 3992795Inactive· HERNDON, VA
Strong
Officer
3
AGUILAR TOWING LLC
USDOT 2396952Active· DENVER, CO
Strong
Officer
4
DEL RIO CONCRETE PRECAST INC.
USDOT 8332325Active· BRIGHTON, CO
Strong
Officer
5
EAGLE TRUCKING
USDOT 2412067Active· WEST COLUMBIA, TX
Strong
Officer
6
FRANCISCO AGUILAR
USDOT 3533243Active· WEST COVINA, CA
Strong
Officer
7
FRANCISCO AGUILAR
USDOT 2733004Active· LOS ANGELES, CA
Strong
Officer
8
FRANCISCO AGUILAR
USDOT 1033730Active· MCFARLAND, CA
Strong
Officer
9
FRANCISCO AGUILAR
USDOT 1323124Inactive· SUMMIT, IL
Strong
Officer
10
FRANCISCO AGUILAR
USDOT 3014368Inactive· LAREDO, TX
Strong
Officer
11
I&P CONSTRUCTION LLC
USDOT 3106078Active· NORFOLK, NE
Strong
Officer
12
MAFA DELIVERY LLC
USDOT 3594440Active· PHOENIX, AZ
Strong
Officer
13
PANDA DELIVERY LLC
USDOT 3847944Active· LAS VEGAS, NV
Strong
Officer
14
WILDCAT TRUCKING LLC
USDOT 1801518Active· SIDNEY, MT
Strong
Officer
15
YAFRA FOODS LLC
USDOT 1399972Inactive· ST PAUL, MN
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.

🚛

Operations

Classification

  • AUTHORIZED FOR HIRE

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
0
⚡

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