CSA
UnknownUSDOT 2033134· CARRIER
⬇ PDF report

FRANCISCO GUERRERO

6351 FRENCH CHATEAU DR, HOUSTON, TX, 77088(713) 856-8274pacoguerrero11@gmail.comFRANCISCO GUERRERO
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%

Recommendations

What’s driving each score, what to do about it, and where it could go.

Driver out-of-service rate exceeds the national average

High impact

Driver OOS rate is 33.3% vs the 6.7% national average. Carriers above the national OOS average draw more enforcement attention (audits, roadside stops) and can see higher insurance premiums.

What to do
  • Review recent inspections with out-of-service violations and fix the root causes with equipment and drivers
  • Run a preventative-maintenance program; periodically inspect tires, brakes and lights
  • Reinforce thorough pre-trip and post-trip inspections; retrain where needed

Recommendations are generated from the carrier’s public FMCSA roadside-inspection record. Percentiles and projections are VioCodes estimates, not official FMCSA figures. Informational, not legal advice.

90-day safety improvement plan

What this carrier has struggled with most in the last 90 days — where to focus now.

No roadside inspections in the last 90 days — nothing to work on right now.

Inspection & crash map

live · FMCSA MCMIS

Every inspection and crash on record — hover a point for the summary, click for full detail (codes, severity, CSA points).

8
Inspections
65
Violations
7
Out-of-service
32
CSA points
1
Crashes
1
States
cleanviolOOS

CSA points = violation severity weight × FMCSA time weight (3× in the last 6 months, 2× at 6–12, 1× at 12–24). Points are spread within each state — FMCSA records the inspection state, not an exact location. Source: FMCSA MCMIS.

Equipment

VINs via NHTSA

3 distinct vehicles seen in this carrier’s roadside inspections.

3 truck
1994 KENWORTH T600seen 5×
1XKADR9X9RS611101· NBH6550 TX
2003 KENWORTH T600seen 2×
1XKAD49X53J704021· SNP2410 TX
1999 KENWORTH W900
1XKWDR9X2XR824806· SVM4978 TX

Equipment is inferred from VINs recorded on roadside inspections (FMCSA MCMIS), decoded via the NHTSA vPIC API — it reflects vehicles inspected, not a current fleet roster.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
4
on file (MCS-150)
Drivers
2
2 hold a CDL
Annual mileage
1M mi
reported 2010
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · <100 mi2 drivers
Company officer
FRANCISCO GUERRERO
Operation
Intrastate (Non-Hazmat)
Registered since
2010-05-12
Last MCS-150 update
2010-05-13
Census status
Active

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

14
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
14
Strong links
Possible reincarnation pattern: FRANCICO GUERRERO (USDOT 1357220, 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· 14
1
A & E TRANSPORTATION LLC
USDOT 3301489Active· PROVIDENCE, RI
Strong
Officer
2
DATE READY MIX LLC
USDOT 2840024Active· PHOENIX, AZ
Strong
Officer
3
FG FARMS LLC
USDOT 4456390Active· GILA BEND, AZ
Strong
Officer
4
FG LOGISTICS INC
USDOT 1974773Active· ROMEOVILLE, IL
Strong
Officer
5
FRANCICO GUERRERO
USDOT 1357220Inactive· CHICAGO, IL
Strong
Officer
6
FRANCISCO GUERRERO
USDOT 3413832Active· KAUFMAN, TX
Strong
Officer
7
FRANCISCO GUERRERO
USDOT 1741522Active· EPHRATA, WA
Strong
Officer
8
FRANCISCO GUERRERO
USDOT 1810887Inactive· SALINAS, CA
Strong
Officer
9
FRANCISCO GUERRERO
USDOT 2109474Active· ENTIAT, WA
Strong
Officer
10
FRANCISCO GUERRERO CO
USDOT 1744257Inactive· ELIZABETH, NJ
Strong
Officer
11
GUERRERO EXPRESS INC
USDOT 1199364Inactive· ROMEOVILLE, IL
Strong
Officer
12
J & C TOWING LLC
USDOT 3071060Active· EVERETT, WA
Strong
Officer
13
LEON PALLETS
USDOT 1831807Active· MILWAUKEE, WI
Strong
Officer
14
RXG TRANSPORTATION LLC
USDOT 4236859Active· EL CAJON, CA
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. 05/13/2010MCS-150 update filed

    1.0M mi reported (2010)

  2. 05/12/2010Registered with FMCSA

    PRIVATE PROPERTY

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
2010-05-13
Reported mileage
1,040,000 mi (2010)
⚡

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